Baseband processors for user equipment and base stations

Abstract

The present invention provides systems, methods, and circuits for supporting aggregated retransmissions. In one example, a method includes receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission. Identify the time slot group to which a selected time slot of the one or more time slots belongs. The method includes configuring an operation based on these resources to receive the PDSCH transmission or transmit the PUSCH transmission. In response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configure an operation to provide hybrid automatic repeat request (HARQ) feedback based on the PDSCH / PUSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH / PUSCH scheduled for a time slot outside the identified time slot group.

Description

Technical Field

[0001] The present disclosure relates to an aggregate retransmission scheme. Background Art

[0002] Some wireless communication networks, such as non-terrestrial networks, may be susceptible to high-latency links, which complicate many aspects of communication. Summary of the Invention

[0003] The present invention provides systems, methods, and circuits for supporting aggregated retransmissions. In one example, a method includes receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission. Identify the time slot group to which a selected time slot of the one or more time slots belongs. The method includes configuring an operation based on these resources to receive the PDSCH transmission or transmit the PUSCH transmission. In response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configure an operation to provide hybrid automatic repeat request (HARQ) feedback based on the PDSCH / PUSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH / PUSCH scheduled for a time slot outside the identified time slot group. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Some examples of circuits, devices and / or methods will be described below by way of example only.In this context, reference will be made to the accompanying drawings.

[0005] Figures 1A to 1D is a block diagram outlining four different types of retransmission schemes.

[0006] Figures 2A to 2B is a block diagram illustrating two exemplary different time slot grouping schemes in accordance with various aspects of the disclosure.

[0007] Figure 3A is a block diagram illustrating an example PDSCH spanning groups of slots in accordance with various disclosed aspects.

[0008] Figure 3B is a diagram showing a method for receiving / transmitting according to various aspects of the disclosure Figure 3A A block diagram of an exemplary technique for implementing a PDSCH.

[0009] Figure 3C is a flow chart of an example method for processing PDSCH / PUSCH across slot groups in accordance with various disclosed aspects.

[0010] Figure 3Dis a flow chart of an example method for processing PDSCH / PUSCH across slot groups in accordance with various disclosed aspects.

[0011] Figure 4 is a flow chart illustrating a method for determining a number of repetitions according to control information according to various aspects disclosed.

[0012] Figure 5A An exemplary time-domain resource allocation table indicating a redundancy version sequence according to various disclosed aspects is shown.

[0013] Figure 5B An exemplary redundant version sequence table indicating redundant version sequences mapped to redundant version sequence indexes according to various disclosed aspects is shown.

[0014] Figure 6 is a flow chart illustrating an exemplary method for configuring operation for retransmission on non-contiguous time slots in accordance with various disclosed aspects.

[0015] Figure 7 Two different exemplary time domain resource allocation tables are shown that support retransmissions on non-contiguous time slots in accordance with various disclosed aspects.

[0016] Figure 8 is a flow chart illustrating an example method for applying limited buffer rate matching based on a number of supported hybrid automatic repeat request processes supported by a device in accordance with various aspects disclosed.

[0017] Figure 9 An exemplary communication network in accordance with various disclosed aspects is shown.

[0018] Figure 10 Examples of infrastructure equipment devices (e.g., BS, eNB, gNB) according to various aspects of the disclosure are shown.

[0019] Figure 11 An example of a user equipment device (referred to interchangeably herein as a "UE" or a "UE device") in accordance with various aspects of the disclosure is shown. DETAILED DESCRIPTION

[0020] The present disclosure is described with reference to the accompanying drawings. The drawings are not drawn to scale and are provided solely for the purpose of illustrating the present disclosure. Several aspects of the present disclosure are described below with reference to example applications for illustration. Many specific details, relationships, and methods are set forth to provide an understanding of the present disclosure. The present disclosure is not limited by the order of the actions or events illustrated, as some actions may occur in a different order and / or simultaneously with other actions or events. Furthermore, not all illustrated actions or events are necessary to implement the method according to the selected disclosure.

[0021] As the number of mobile devices connected to wireless networks and the demand for mobile data traffic continues to increase, system requirements and architectures are changing to meet the current and expected surge in demand. For example, wireless communication networks such as 5G New Radio (NR) systems may need to be deployed using satellites as part of a non-terrestrial network (NTN). In one deployment scenario for an NTN, satellites known as transparent satellites can act as relays to link user devices with land-based base stations and the 5G core network by implementing transparent payloads. In another deployment scenario, satellites known as regenerative satellites can have onboard processing capabilities to perform the functions of a base station by implementing regenerative payloads between user devices and the land-based 5G core network.

[0022] Due to the wide coverage area of ​​satellites and the long distance between satellites and ground user devices, the propagation delay difference between two user devices within the beam footprint is greater than the propagation delay difference encountered in a strictly terrestrial network. For example, for an NTN deploying satellites in geostationary orbit (GEO), the maximum differential delay between the lowest point and the edge of the coverage area can be 10.3ms. For an NTN deploying satellites in low Earth orbit (LEO), the maximum differential delay can be 3.12ms and 3.18ms for altitudes of 600km and 900km, respectively.

[0023] Large propagation delays of user equipment and large differences in propagation delays between user equipment in the beam footprint can cause problems with the use of hybrid automatic repeat request (HARQ) feedback. To cope with large propagation delays, it may be advantageous for user equipment (UE) devices to support an increased number of HARQ processes. However, this increased number of HARQ processes introduces design challenges with respect to transmitting HARQ process identifiers and the storage / processing capabilities of the UE device. The potential loss of link reliability due to long distances and mobile base stations can be compensated by performing active aggregation retransmissions or blind retransmissions. In addition, in many cases, simply disabling HARQ feedback may be beneficial, which means that the use of compensation techniques such as aggregation retransmissions or blind retransmissions may become more common.

[0024] Disclosed herein are systems, circuits, and techniques for signaling and performance supporting retransmission techniques when HARQ feedback may be disabled in the presence of high-latency links or large-propagation links.

[0025] As used herein, "retransmission" means retransmitting the same physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) data (and associated error coded bits) (or a redundant version of the same transport block) at least once after the initial transmission of the transport block. The retransmission can be proactive, meaning that the retransmission can be performed independently of any received HARQ feedback. A retransmission can be indicated, for example, by the same HARQ process number or an untoggled New Data Indicator (NDI) bit compared to a new data transmission. In some examples, the retransmissions are combined by the receiving device according to a soft decoding scheme.

[0026] In some examples, the number of times the PDSCH / PUSCH is to be actively retransmitted is referred to as a repetition number, which may be indicated by uplink (UL) or downlink (DL) downlink control information (DCI), which is generally referred to herein as "control information". In some examples, other signaling methods besides DCI may be used instead of DCI to convey the described control information. In this specification, the terms "retransmission" and "repetition" may be used interchangeably. Unless otherwise noted, it should be assumed that the exemplary downlink communications used for these techniques are also applicable to uplink communications.

[0027] Figures 1A to 1D Several different retransmission schemes are shown. Figure 1A Conventional retransmissions are shown. It can be seen that each transmission of DL data (including each retransmission of DL data) is indicated by corresponding DL HARQ feedback and is individually acknowledged by DL HARQ feedback. Figure 1B Conventional aggregated retransmissions with HARQ feedback are shown. A single DCI is used to schedule the transmission and several retransmissions of the same DL data. A single HARQ feedback communication (e.g., a bit) is used to acknowledge (ACK) or negatively acknowledge (NACK) successful receipt of the DL data. Retransmissions occur in consecutive time slots using the same frequency resources. In some examples, time slots are arranged into time slot groups of consecutive time slots, where each time slot group is associated with a set of HARQ process numbers.

[0028] In some high-latency situations, HARQ feedback may be disabled. Figure 1C Aggregated retransmissions without HARQ feedback are shown. A single DCI is used to schedule the transmission and several retransmissions of the same DL data. Another type of retransmission scheme that may be beneficial when HARQ feedback is disabled is blind retransmission, which is used in Figure 1D Each blind retransmission is signaled by its own DCI, which means that a blind retransmission can be an active retransmission of the same PDSCH / PUSCH on resources that are not related to the previous transmission. Figure 1B and Figure 1CCompared to the illustrated aggregate retransmission technique, the blind retransmission method provides the advantage of time and / or frequency diversity, where the same frequency resources and consecutive time slots are used for retransmission.

[0029] Figure 2A and Figure 2B Two exemplary ways of arranging time slots into time slot groups are shown. Each time slot group is associated with a series of HARQ process numbers. Figure 2A In the example shown, the time slots in a time slot group are consecutive. Figure 2B In the example shown, the time slots in each time slot group are interleaved with the time slots in other time slot groups. Figure 3A 15. The following diagram illustrates a potential ambiguity that arises when one or more retransmissions of an aggregate retransmission are to occur in different slot groups. For example, the slot group may be determined based on the slot in which the initial DL data (PDSCH) is carried, or alternatively the slot in which the Physical Downlink Control Channel (PDCCH) or DCI is carried. In either case, the aggregate retransmission shown belongs to slot group 1. This means that the HARQ process numbers for the aggregate retransmission are in the range 0-15. The next two retransmissions of the PDSCH will occur in slots associated with slot group 2, which is associated with HARQ process groups 16-31. This raises the question of how to combine the PDSCH or PUSCH and handle HARQ feedback for the aggregate retransmissions. Figure 3B A possible solution is shown in which the UE applies HARQ feedback after the last retransmission in a slot group (or before a slot boundary shown with a dashed line). HARQ feedback indicating ACK / NACK is provided in an appropriate slot (e.g., after expiration of K1, which is a configurable feedback timing parameter) after receiving and decoding (and possibly combining) two retransmissions in the first slot group.

[0030] Figure 3C3 is a flow chart outlining an exemplary method 360 for performing HARQ feedback for aggregated retransmissions that may span more than one slot group. At 362, a downlink grant is received that indicates a HARQ process number with HARQ feedback enabled and at least one remaining retransmission (e.g., indicating a repetition count > 0). At 364, downlink data is received and decoded, and possibly soft-combined with previous retransmissions. At 366, a determination is made as to whether decoding was successful. If so, ACK feedback is provided at 372 on the appropriate slot. If not, a determination is made at 368 as to whether a slot boundary between slot groups has been reached. If so, NACK feedback is provided at 374 on the appropriate slot. If not, a determination is made at 370 as to whether a maximum number of retransmissions has been reached (e.g., based on the repetition count). If so, NACK feedback is provided at 374 on the appropriate slot. If not, the method returns to 364 and the next retransmission is received and decoded.

[0031] Figure 3D 380 is a flow chart outlining an exemplary method 380 that may be performed by a UE device for handling aggregated retransmissions that may span more than one time slot group. At 382, ​​control information indicating resources including one or more time slots for transmitting PDSCH / PUSCH transmissions including at least one retransmission is received. At 384, a time slot group is identified based on one of the one or more time slots (e.g., and an index of a first PDSCH / PUSCH time slot or a PDCCH time slot). At 386, a determination is made based on whether a next retransmission is scheduled for a time slot outside the identified time slot group. If not, at 388, operations are configured to receive / transmit the next PDSCH / PUSCH retransmission. If the next retransmission is scheduled for a time slot outside the identified time slot group, at 390, a hybrid automatic repeat request (HARQ) is configured, the UE device refrains from transmitting PUSCH or receiving PDSCH, and HARQ feedback is configured based on the PDSCH retransmissions scheduled for the time slots within the identified time slot group. Therefore, HARQ feedback is not based on PDSCH scheduled for slots outside the identified slot group.For the sake of brevity, a similar approach for the base station is not described herein.

[0032] In some cases, it may be advantageous to have the ability to dynamically indicate the number of retransmissions, for example on a per-DCI basis. This would allow the number of retransmissions to be dynamically adjusted based on, for example, quality of service (e.g., latency and reliability) requirements associated with different data or changing network conditions. However, the number of bits available in DCI is limited, and for compatibility and signaling overhead reasons, it is not desirable to increase the number of bits in DCI.

[0033] Figure 44 is a flow chart outlining an exemplary method 400 for determining the number of retransmissions by reinterpreting a control information field that typically carries HARQ feedback-related information (e.g., a redundancy version sequence or NDI) to convey a retransmission count (e.g., a repetition count). At 410, DCI is received. At 420, a determination is made as to whether HARQ feedback is disabled. If not, at 430, the DCI feedback-related field is read to determine the feedback-related information.

[0034] However, if HARQ feedback is disabled, then at 440, the DCI feedback-related field is read to determine the number of retransmissions. In this way, DCI bits are conserved by reusing feedback-related bits to encode the number of repetitions when feedback is not enabled. The DCI bit carrying the repetition number may indicate a repetition index value that cannot be represented by the number of available DCI bits mapped to it via previous signaling.

[0035] Figure 5A and Figure 5B Two different exemplary techniques for dynamically signaling a redundancy version sequence in an uplink or downlink DCI are shown. Figure 5A In the PDSCH Time Domain Resource Allocation (TDRA) table, the table is modified to include a column for Redundancy Version (RV) sequences. The DCI can indicate a specific RV sequence by indicating the TDRA index. Thus, a TDRA index of 0 as signaled in the DCI will result in the RV sequence [0 2 3 1], as shown in FIG. Figure 5A Similar modifications may be made to the PUSCH TDRA table. The PUSCH TDRA table is not shown, but will include a column for K2 instead of K0. Figure 5B An alternative technique is shown in which an RV sequence is configured separately and the DCI indicates the configured RV sequence.

[0036] Introducing time diversity into retransmissions can increase the likelihood of successful decoding. Figure 6 6 is a flow chart outlining an exemplary method 600 for configuring operation for retransmission in non-contiguous time slots. The method includes, at 610, receiving DCI indicating two or more non-contiguous time slots for PDSCH / PUSCH including at least one retransmission. At 620, configuring operation to receive / transmit PDSCH / PUSCH.

[0037] Figure 7Two different PDSCH TDRA tables are shown that have been modified to allow indication of retransmissions in non-continuous time slots. Similar modifications can be made to the PUSCH TDRA table. The PUSCH TDRA table is not shown, but will include a column for K2 instead of K0. In both tables, columns are provided for indicating the time gaps (e.g., expressed in time slots) between corresponding consecutive retransmission pairs. For example, the time interval sequence [2 3 1] configured by the DCI indication of TDRA index (row) 0 produces the retransmission sequence shown. A gap of two time slots occurs between the first consecutive PDSCH / PUSCH transmission pair. A gap of three time slots occurs between the second PDSCH / PUSCH transmission pair. A gap of one time slot occurs between the third PDSCH / PUSCH transmission pair.

[0038] In the second TDRA, the column for the number of repetitions has been removed, and the number of repetitions is implied by the number of time slots indicated in the time interval sequence. In another alternative (not shown), the time slots may specify fixed time intervals, and the repeat column may be maintained to allow retransmissions on non-consecutive time slots to be dynamically indicated in a regular pattern.

[0039] As discussed above, the increased latency of some networks may mean that up to 32 or more HARQ processes may be used. This may affect the performance of some UE devices with limited storage media used as HARQ buffers. Limited Buffer Rate Matching (LBRM) is a technique that transmits a reduced number of redundant coded bits in each retransmission (compared to non-LBRM operation). While this may reduce the probability of successful decoding to some extent, LBRM operation means that fewer bits are stored for each retransmission, thereby saving HARQ buffer space. In some examples, when transmission is performed in LBRM mode, a predetermined fraction (e.g., 2 / 3) of the bits are transmitted.

[0040] When the UE supports a significantly larger number of HARQ processes, selectively employing LBRM may be advantageous. Figure 8 A method 800 is shown in which, at 810, it is determined that the UE supports more than 16 HARQ processes, and at 820, LBRM is selectively applied. In one example, LBRM is automatically applied (e.g., without requiring separate configuration) when the UE supports more than 16 HARQ processes. In one example, when a given UE supports more than 16 HARQ processes, separate configuration determines whether LBRM is applied for that UE. In one example, the UE device may indicate to the base station which of the two schemes the UE uses, depending on the UE device capabilities. In one example, the number of coded bits to be transmitted during LBRM operation is configurable, depending on the UE device capabilities. For example, 4 / 5 of the coded bits may be transmitted.

[0041] Any of the aforementioned methods for leveraging aggregated retransmissions is well-suited for use in NTNs. For example, signals encoding DCI and PDSCH generated by a base station (on the ground or on a regenerative satellite) can be transmitted to UEs via satellite. Additionally, signals encoding PUSCH and HARQ feedback can be received from UEs via satellite.

[0042] Included herein are several flow charts outlining exemplary methods. In this specification and the appended claims, the use of the term "determine" in describing method steps or functions with reference to some entities (e.g., parameters, variables, etc.) is to be interpreted broadly. For example, "determine" is to be interpreted as covering communications such as receiving and parsing an encoded entity or value of an entity. "Determine" should be interpreted as covering accessing and reading a memory (e.g., a lookup table, register, device memory, remote memory, etc.) that stores an entity or a value for an entity. "Determine" should be interpreted as covering calculating or deriving an entity or a value of an entity based on other quantities or entities. "Determine" should be interpreted as covering any way of inferring or identifying an entity or a value of an entity.

[0043] As used herein, the term "identify," when used with reference to an entity or a value of an entity, is to be broadly interpreted to encompass any manner of determining an entity or a value of an entity. For example, the term "identify" is to be interpreted to encompass, for example, receiving and parsing communications encoding an entity or a value of an entity. The term "identify" should be interpreted to encompass accessing and reading a memory (e.g., a device queue, a lookup table, a register, a device memory, a remote memory, etc.) storing an entity or a value for an entity.

[0044] As used herein, the term "select" when used with reference to an entity or value of an entity is to be interpreted broadly to encompass any way of determining an entity or a value of an entity from a plurality or a range of possible choices. For example, the term "select" is to be interpreted as encompassing accessing and reading a memory (e.g., a lookup table, register, device memory, remote memory, etc.) that stores entities or values ​​for entities and returning an entity or entity value from those stored. The term "select" is to be interpreted as applying one or more constraints or rules to a set of input parameters to determine an appropriate entity or entity value. The term "select" is to be interpreted broadly to encompass any way of selecting an entity based on one or more parameters or conditions.

[0045] As used herein, the term "derive" is to be interpreted broadly when used with reference to an entity or a value of an entity. "Deriving" should be interpreted to encompass accessing and reading a memory (e.g., a lookup table, registers, device memory, remote memory, etc.) that stores some initial or base values, and performing processing and / or logical / mathematical operations on one or more values ​​to generate a derived entity or value for an entity. "Deriving" should be interpreted to encompass calculating or measuring an entity or a value for an entity based on other quantities or entities. "Deriving" should be interpreted to encompass any way of inferring or identifying an entity or a value for an entity.

[0046] The term "coupled" is used throughout this specification. This term encompasses any connection, communication, or signal path that enables a functional relationship consistent with the description of this disclosure. For example, if device A generates a signal to control device B to perform an action, then in the first example, device A is coupled to device B. Alternatively, in the second example, if the intermediate component C does not substantially change the functional relationship between devices A and B such that device B is controlled by device A via the control signal generated by the devices, then device A is coupled to device B via the intermediate component C.

[0047] Figure 9 An exemplary architecture of a system 900 for a communication network according to various aspects is shown. The following description is provided for an exemplary system 900 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary aspects are not limited in this regard, and the described aspects may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G) systems), IEEE 702.16 protocols (e.g., WLAN, WiMAX, etc.), and the like.

[0048] like Figure 9As shown, system 900 includes UE 901a and UE 901b (collectively referred to as "UEs 901" or "UE 901"). In this example, UE 901 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smartphone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a connected or "smart" appliance, a MTC device, an M2M device, an IoT device, etc.

[0049] In some aspects, any of the UEs 901 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. The M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0050] UE 901 may be configured to connect to, e.g., be communicatively coupled to, a RAN 910. In one aspect, RAN 910 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term "NGRAN," etc., may refer to the RAN 910 operating in an NR or 5G system 900, while the term "E-UTRAN," etc., may refer to the RAN 910 operating in an LTE or 4G system 900. UE 901 utilizes connections (or channels) 903 and 904, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0051] In this example, connections 903 and 904 are shown as air interfaces to achieve communication coupling and can be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an aspect, the UE 901 can directly exchange communication data via a ProSe interface 905. The ProSe interface 905 can alternatively be referred to as an SL interface 905 and can include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0052] UE 901b is shown as being configured to access AP 906 (also referred to as "WLAN node 906," "WLAN 906," "WLAN terminal 906," "WT 906," etc.) via connection 907. Connection 907 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, wherein AP 906 would include Wireless Fidelity. router. In this example, AP 906 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various aspects, UE 901b, RAN 910, and AP 906 can be configured to utilize LWA operation and / or LWIP operation. LWA operation can involve RAN nodes 911a-b configuring UE 901b in the RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP operation can involve UE 901b using WLAN radio resources (e.g., connection 907) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 907. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0053] RAN 910 may include one or more AN nodes or RAN nodes 911a and 911b (collectively, "RAN nodes 911") that enable connections 903 and 904. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As described below, in some implementations, satellite 960 may operate as a base station (e.g., RAN node 911) relative to UE 901. Therefore, references herein to base stations, RAN nodes, and the like may relate to implementations in which the base stations, RAN nodes, and the like are terrestrial network nodes, as well as implementations in which the base stations, RAN nodes, and the like are non-terrestrial network nodes (e.g., satellite 160).

[0054] As used herein, the term "NG RAN node" or the like may refer to a RAN node 911 (e.g., a gNB) operating in an NR or 5G system 900, while the term "E-UTRAN node" or the like may refer to a RAN node 911 (e.g., an eNB) operating in an LTE or 4G system 900. According to various aspects, the RAN node 911 may be implemented as one or more dedicated physical devices such as a macrocell base station and / or a low-power (LP) base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

[0055] According to various aspects, the UE 901 and the RAN node 911 communicate data (e.g., transmit data and receive data) via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0056] To operate in the unlicensed spectrum, the UE 901 and the RAN node 911 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 901 and the RAN node 911 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0057] LBT is a mechanism by which equipment (e.g., UE 901, RAN node 911, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0058] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 702.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 901, AP 906, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 8 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0059] The LAA mechanism is built on the Carrier Adaptation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL ​​and UL.

[0060] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 901 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0061] The PDSCH carries user data and higher-layer signaling to UE 901. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It can also inform UE 901 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 901b within a cell) can be performed on any of the RAN nodes 911 based on channel quality information fed back from any of the UEs 901. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 901.

[0062] RAN 910 is shown as being communicatively coupled to a core network, in this aspect, to a core network (CN) 920. CN 920 may include multiple network elements 922 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 901) connected to CN 920 via RAN 910. Components of CN 920 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some aspects, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored on one or more computer-readable storage media. A logical instance of CN 920 may be referred to as a network slice, and a logical instance of a portion of CN 920 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0063] As shown, exemplary network 900 may include an NTN, which may include one or more satellites 960-1 and 960-2 (collectively, "satellites 960"). Satellites 960 may communicate with UE 901 via a serving link or wireless interface 962, and / or communicate with RAN 910 via a feeder link or wireless interface 964 (depicted individually as 964-1 and 964). In some implementations, satellites 960 may operate as passive or transparent network relay nodes with respect to communications between UE 901 and a terrestrial network (e.g., RAN 910). In some implementations, satellites 960 may operate as active or regenerative network nodes, such that satellites 960 may operate as base stations for UE 901 (e.g., as gNBs for RAN 910) with respect to communications between UE 901 and RAN 910. In some implementations, the satellites 960 may communicate with each other via a direct wireless interface (e.g., 966) or an indirect wireless interface (e.g., via the RAN 910 using interfaces 964-1 and 964-2). Additionally or alternatively, the satellites 960 may include GEO satellites, LEO satellites, or another type of satellite. The satellites 960 may also or alternatively relate to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS), a global positioning system (GPS), a global navigation satellite system (GLONASS), a BeiDou navigation satellite system (BDS), etc. In some implementations, the satellites 960 may operate as base stations (e.g., RAN nodes 911) relative to the UE 901. Therefore, references herein to base stations, RAN nodes 911, etc. may relate to implementations in which the base stations, RAN nodes 911, etc. are terrestrial network nodes, as well as implementations in which the base stations, RAN nodes 911, etc. are non-terrestrial network nodes (e.g., satellites 960).

[0064] Figure 10 An example of infrastructure equipment 1000 according to various aspects is shown. Infrastructure equipment 1000 (or "system 1000") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 911 and / or AP 906 shown and described previously), an application server 930, and / or any other element / device discussed herein. In other examples, system 1000 can be implemented in or by a UE.

[0065] System 1000 includes application circuitry 1005, baseband circuitry 1010, one or more radio front-end modules (RFEMs) 1015, memory circuitry 1020, a power management integrated circuit (PMIC) 1025, power tee circuitry 1030, network controller circuitry 1035, a network interface connector 1040, satellite positioning circuitry 1045, and a user interface 1050. In some aspects, device 1000 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other aspects, the components described below may be included in more than one device. For example, the circuitry may be separately included in more than one device for a CRAN, vBBU, or other similar implementation.

[0066] Application circuit 1005 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout voltage regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar product, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of application circuit 1005 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1000. In some implementations, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0067] The processor of the application circuit 1005 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some aspects, the application circuit 1005 may include or may be a dedicated processor / controller for operating in accordance with various aspects herein. As an example, the processor of the application circuit 1005 may include one or more processor, Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM Holdings, Ltd. licensed ARM-based processors, such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some aspects, system 1000 may not utilize application circuit 1005 and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0068] The user interface circuitry 1050 may include one or more user interfaces designed to enable a user to interact with the system 1000 or a peripheral component interface designed to enable a peripheral component to interact with the system 1000. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.

[0069] Figure 10The components shown can communicate with each other using interface circuitry that can include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0070] Figure 11 An example of a platform 1100 (or "device 1100") according to various aspects is shown. In aspects, computer platform 1100 can be suitable for use as UE 901, application server 930, and / or any other element / device discussed herein. Platform 1100 can include any combination of the components shown in the examples. Components of platform 1100 can be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 1100, or as components otherwise incorporated within a chassis of a larger system. Figure 11 The block diagram is intended to show a high-level view of the components of computer platform 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0071] The application circuit 1105 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of an LDO, an interrupt controller, a serial interface (such as SPI), I2C or a general-purpose programmable serial interface module, an RTC, a timer (including an interval timer and a watchdog timer), general-purpose I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 1105 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1100. In some implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0072] For example, the processor of the application circuit 1105 may include a general-purpose or special-purpose processor, such as a commercially available Inc., Cupertino, CA A series processor (e.g., A13 Bionic) or any other such processor. The processor of application circuit 1105 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s core processors, from Snapdragon by Technologies, Inc. TM processors, Texas Instruments, Open Multimedia ApplicationsPlatform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 1105 can be part of a system on a chip (SoC), in which the application circuit 1105 and other components are formed as a single integrated circuit or a single package.

[0073] Baseband circuit 1110 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0074] Platform 1100 may also include an interface circuit (not shown) for connecting external devices to platform 1100. External devices connected to platform 1100 via the interface circuit include sensor circuit 1121 and electromechanical components (EMC) 1122, as well as a removable memory device coupled to removable memory circuit 1123.

[0075] Battery 1130 can power platform 1100, but in some examples, platform 1100 can be installed in a fixed location and can have a power source coupled to the power grid. Battery 1130 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, battery 1130 can be a typical lead-acid automobile battery.

[0076] Although the method is shown and described as a series of actions or events above, it should be understood that the order of such actions or events shown should not be interpreted as having a limiting meaning. For example, some actions can occur in different orders and / or simultaneously with other actions or events other than those shown and / or described herein. In addition, it may not be necessary for all the actions shown to implement one or more aspects or embodiments disclosed herein. In addition, one or more actions in the actions shown herein can be performed in one or more separate actions and / or stages. In some embodiments, the method shown above can be implemented in a computer-readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the present disclosure protected by the claims.

[0077] Example

[0078] Embodiment 1 is a user equipment (UE) device, which includes a processor configured to perform operations including: receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs; configuring an operation to receive the PDSCH transmission or transmit the PUSCH transmission based on the resources; and in response to determining that the PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring an operation to avoid receiving the PDSCH retransmission or avoid transmitting the PUSCH retransmission, and providing hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for a time slot outside the identified time slot group.

[0079] Embodiment 2 includes the subject matter of embodiment 1, including or excluding the optional elements, wherein each time slot group includes a group of consecutive time slots.

[0080] Embodiment 3 includes the subject matter of embodiment 1, including or excluding the optional elements, wherein each time slot group includes time slots that are interleaved with time slots from other groups.

[0081] Embodiment 4 includes the subject matter of embodiment 1, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

[0082] Embodiment 5 includes the subject matter of embodiment 1, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

[0083] Embodiment 5 is a method comprising: receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs; configuring an operation based on these resources to receive the PDSCH transmission or transmit the PUSCH transmission; and in response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring an operation to avoid receiving the PDSCH retransmission or avoid transmitting the PUSCH retransmission, and providing hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for a time slot outside the identified time slot group.

[0084] Embodiment 7 includes the subject matter of embodiment 6, including or excluding the optional elements, wherein each time slot group includes a group of consecutive time slots.

[0085] Embodiment 8 includes the subject matter of embodiment 6, including or excluding the optional elements, wherein each time slot group includes time slots that are interleaved with time slots from other groups.

[0086] Embodiment 9 includes the subject matter of embodiment 6, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

[0087] Embodiment 10 includes the subject matter of embodiment 6, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

[0088] Embodiment 11 is a base station comprising a processor configured to perform operations comprising: receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs; configuring an operation based on the resources to receive the PUSCH transmission or transmit the PDSCH transmission; and in response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring an operation to avoid transmitting the PDSCH retransmission or avoid receiving the PUSCH retransmission, and receiving hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for a time slot outside the identified time slot group.

[0089] Embodiment 12 includes the subject matter of embodiment 11, including or excluding the optional elements, wherein each time slot group includes a group of consecutive time slots.

[0090] Embodiment 13 includes the subject matter of embodiment 11, including or excluding the optional elements, wherein each time slot group includes time slots that are interleaved with time slots from other groups.

[0091] Embodiment 14 includes the subject matter of embodiment 11, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

[0092] Embodiment 15 includes the subject matter of embodiment 11, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

[0093] Embodiment 16 is a method comprising: transmitting control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs; configuring an operation based on these resources to receive the PUSCH transmission or transmit the PDSCH transmission; and in response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring an operation to avoid transmitting the PDSCH retransmission or avoid receiving the PUSCH retransmission, and receiving hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for a time slot outside the identified time slot group.

[0094] Embodiment 17 includes the subject matter of embodiment 16, including or excluding the optional elements, wherein each time slot group includes a group of consecutive time slots.

[0095] Embodiment 18 includes the subject matter of embodiment 16, including or excluding the optional elements, wherein each time slot group includes time slots that are interleaved with time slots from other groups.

[0096] Embodiment 19 includes the subject matter of embodiment 16, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

[0097] Embodiment 20 includes the subject matter of embodiment 16, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

[0098] Embodiment 21 is a user equipment (UE) device comprising a processor configured to perform operations comprising: receiving control information indicating HARQ information associated with a PDSCH or PUSCH transmission that transmits at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; determining, based on the control information, that HARQ feedback is disabled; determining, based on information in a control information field that carries information related to HARQ feedback when HARQ feedback is enabled, a repetition number that defines the number of retransmissions in the PDSCH / PUSCH; and configuring operations to receive the PDSCH transmission or transmit the PUSCH transmission based on the HARQ information and the repetition number.

[0099] Embodiment 22 includes the subject matter of embodiment 21, including or excluding the optional elements, wherein the control information field includes a field carrying redundancy version sequence information when HARQ feedback is enabled.

[0100] Embodiment 23 includes the subject matter of embodiment 21, including or excluding the optional elements, wherein the control information field includes a field carrying a new data indicator when HARQ feedback is enabled.

[0101] Embodiment 24 includes the subject matter of embodiment 21, including or excluding optional elements, wherein the processor is configured to perform operations comprising: determining a redundant version sequence for the PDSCH / PUSCH based on a time domain resource allocation (TDRA) table index indicated in the control information.

[0102] Embodiment 25 includes the subject matter of embodiment 21, including or excluding the optional elements, wherein the processor is configured to perform operations comprising: determining a redundant version sequence based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0103] Embodiment 26 includes the subject matter of embodiment 25, including or excluding optional elements, wherein the processor is configured to perform operations comprising: determining the redundant version sequence based on a redundant version sequence index indicated in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0104] Embodiment 27 is a method comprising: receiving control information indicating HARQ information associated with a PDSCH or PUSCH transmission that transmits at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; determining, based on the control information, that HARQ feedback is disabled; determining, based on information in a control information field that carries information related to HARQ feedback when HARQ feedback is enabled, a repetition number that defines the number of retransmissions in the PDSCH / PUSCH; and configuring an operation to receive the PDSCH transmission or transmit the PUSCH transmission based on the HARQ information and the repetition number.

[0105] Embodiment 28 includes the subject matter of embodiment 27, including or excluding the optional elements, wherein the control information field includes a field carrying redundancy version sequence information when HARQ feedback is enabled.

[0106] Embodiment 29 includes the subject matter of embodiment 27, including or excluding the optional elements, wherein the control information field includes a field carrying a new data indicator when HARQ feedback is enabled.

[0107] Embodiment 30 includes the subject matter of embodiment 27, including or excluding the optional elements, and further comprising: determining a redundant version sequence for the PDSCH / PUSCH based on a time domain resource allocation (TDRA) table index indicated in the control information.

[0108] Embodiment 31 includes the subject matter of embodiment 27, including or excluding the optional elements, and further comprising: determining a redundancy version sequence based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0109] Embodiment 32 includes the subject matter of embodiment 31, including or excluding the optional elements, and further comprising: determining the redundant version sequence based on a redundant version sequence index indicated in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0110] Embodiment 33 is a base station comprising a processor configured to perform operations comprising: transmitting control information indicating HARQ information associated with a PDSCH or PUSCH transmission that includes at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the control information further indicates that HARQ feedback is disabled; encoding a number of repetitions defining the number of retransmissions in the PDSCH / PUSCH based on information in a control information field that carries information related to HARQ feedback when HARQ feedback is enabled; transmitting the control information; and configuring operations to transmit the PDSCH transmission or receive the PUSCH transmission based on the HARQ information and the number of repetitions.

[0111] Embodiment 34 includes the subject matter of embodiment 33, including or excluding the optional elements, wherein the control information field includes a field carrying redundancy version sequence information when HARQ feedback is enabled.

[0112] Embodiment 35 includes the subject matter of embodiment 33, including or excluding the optional elements, wherein the control information field includes a field carrying a new data indicator when HARQ feedback is enabled.

[0113] Embodiment 36 includes the subject matter of embodiment 33, including or excluding optional elements, wherein the processor is configured to perform operations comprising: indicating a redundant version sequence for the PDSCH / PUSCH based on a time domain resource allocation (TDRA) table index indicated in the control information.

[0114] Embodiment 37 includes the subject matter of embodiment 33, including or excluding the optional elements, wherein the processor is configured to perform operations comprising: indicating a redundant version sequence based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0115] Embodiment 38 includes the subject matter of embodiment 37, including or excluding optional elements, wherein the processor is configured to perform operations comprising: indicating the redundant version sequence based on a redundant version sequence index indicated in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0116] Embodiment 39 is a method comprising: transmitting control information indicating HARQ information associated with a PDSCH or PUSCH transmission that transmits at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the control information further indicates that HARQ feedback is disabled; encoding a number of repetitions defining the number of retransmissions in the PDSCH / PUSCH based on information in a control information field that carries information related to HARQ feedback when HARQ feedback is enabled; transmitting the control information; and configuring an operation to transmit the PDSCH transmission or receive the PUSCH transmission based on the HARQ information and the number of repetitions.

[0117] Embodiment 40 includes the subject matter of embodiment 39, including or excluding the optional elements, wherein the control information field includes a field carrying redundancy version sequence information when HARQ feedback is enabled.

[0118] Embodiment 41 includes the subject matter of embodiment 39, including or excluding the optional elements, wherein the control information field includes a field carrying a new data indicator when HARQ feedback is enabled.

[0119] Embodiment 42 includes the subject matter of embodiment 39, including or excluding the optional elements, and further includes: indicating a redundant version sequence for the PDSCH / PUSCH based on a time domain resource allocation (TDRA) table index indicated in the control information.

[0120] Embodiment 43 includes the subject matter of embodiment 39, including or excluding the optional elements, and further comprising indicating a redundancy version sequence based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0121] Embodiment 44 includes the subject matter of embodiment 43, including or excluding the optional elements, and further comprising indicating the redundant version sequence based on a redundant version sequence index indicated in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0122] Embodiment 45 is a user equipment (UE) device comprising a processor configured to perform operations comprising: receiving control information indicating resources comprising one or more time slots for transmitting a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission comprising at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the one or more time slots are non-contiguous and each contiguous time slot pair in the one or more time slots is separated by a corresponding time slot comprising one or more time slots; and configuring operations based on the resources to receive the PDSCH transmission or transmit the PUSCH transmission.

[0123] Embodiment 46 includes the subject matter of embodiment 45, including or excluding the optional elements, wherein the processor is configured to perform operations comprising: determining a set of gaps interleaved between the one or more time slots based on a time domain (TDRA) table index indicated by the control information.

[0124] Embodiment 47 includes the subject matter of embodiment 46, including or excluding the optional elements, wherein the TDRA table index identifies a row in the TDRA table indicating a sequence of time slots.

[0125] Embodiment 48 includes the subject matter of embodiment 47, including or excluding the optional elements, wherein the row further indicates a repetition number indicating a number of retransmissions included in the PDSCH / PUSCH transmission.

[0126] Embodiment 49 includes the subject matter of embodiment 45, including or excluding the optional elements, wherein each of the corresponding time slots includes the same number of time slots.

[0127] Embodiment 50 is a method comprising: receiving control information indicating resources including one or more time slots for transmitting a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the one or more time slots are non-contiguous and each contiguous time slot pair in the one or more time slots is separated by a corresponding time slot, which includes one or more time slots; and configuring an operation based on these resources to receive the PDSCH transmission or transmit the PUSCH transmission.

[0128] Embodiment 51 includes the subject matter of embodiment 50, including or excluding the optional elements, and further comprising: determining a set of gaps interleaved between the one or more time slots based on a time domain (TDRA) table index indicated by the control information.

[0129] Embodiment 52 includes the subject matter of embodiment 51, including or excluding the optional elements, wherein the TDRA table index identifies a row in the TDRA table indicating a sequence of time slots.

[0130] Embodiment 53 includes the subject matter of embodiment 52, including or excluding the optional elements, wherein the row further indicates a repetition number indicating a number of retransmissions included in the PDSCH / PUSCH transmission.

[0131] Embodiment 54 includes the subject matter of embodiment 50, including or excluding the optional elements, wherein each of the corresponding time slots includes the same number of time slots.

[0132] Embodiment 55 is a base station comprising a processor configured to perform operations comprising: receiving control information indicating resources comprising one or more time slots for transmitting a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission comprising at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the one or more time slots are non-contiguous and each consecutive time slot pair in the one or more time slots is separated by a corresponding time slot comprising one or more time slots; and configuring operations based on the resources to receive the PDSCH transmission or transmit the PUSCH transmission.

[0133] Embodiment 56 includes the subject matter of embodiment 55, including or excluding the optional elements, wherein the processor is configured to perform operations comprising: indicating a set of gaps interleaved between the one or more time slots based on a time domain (TDRA) table index indicated by the control information.

[0134] Embodiment 57 includes the subject matter of embodiment 56, including or excluding the optional elements, wherein the TDRA table index identifies a row in the TDRA table indicating a sequence of time slots.

[0135] Embodiment 58 includes the subject matter of Embodiment 57, including or excluding the optional elements, wherein the row further indicates a repetition number indicating a number of retransmissions included in the PDSCH / PUSCH transmission.

[0136] Embodiment 59 includes the subject matter of embodiment 55, including or excluding the optional elements, wherein each of the corresponding time slots includes the same number of time slots.

[0137] Embodiment 60 is a method comprising: transmitting control information indicating resources including one or more time slots for transmitting a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the one or more time slots are non-contiguous and each contiguous time slot pair in the one or more time slots is separated by a corresponding time slot comprising one or more time slots; and configuring an operation based on these resources to receive the PDSCH transmission or transmit the PUSCH transmission.

[0138] Embodiment 61 includes the subject matter of embodiment 60, including or excluding the optional elements, and further comprising: indicating a set of gaps interleaved between the one or more time slots based on a time domain (TDRA) table index indicated by the control information.

[0139] Embodiment 62 includes the subject matter of embodiment 61, including or excluding the optional elements, wherein the TDRA table index identifies a row in the TDRA table indicating a sequence of time slots.

[0140] Embodiment 63 includes the subject matter of embodiment 62, including or excluding the optional elements, wherein the row further indicates a repetition number indicating a number of retransmissions included in the PDSCH / PUSCH transmission.

[0141] Embodiment 64 includes the subject matter of embodiment 60, including or excluding the optional elements, wherein each of the corresponding time slots includes the same number of time slots.

[0142] Embodiment 65 is a user equipment (UE) device comprising a processor configured to perform operations comprising selectively configuring the operation of the UE device to apply limited buffer rate matching (LBRM) when the UE supports more than 16 HARQ processes.

[0143] Embodiment 66 includes the subject matter of embodiment 65, including or excluding the optional elements, wherein the processor is configured to automatically configure operation of the UE device to apply LBRM when the UE supports more than 16 HARQ processes.

[0144] Embodiment 67 includes the subject matter of embodiment 65, including or excluding the optional elements, wherein the processor is configured to selectively configure the operation of the UE device to apply LBRM based on the received configuration information when the UE device supports more than 16 HARQ processes.

[0145] Embodiment 68 includes the subject matter of embodiment 65, including or excluding the optional elements, wherein the processor is configured to cause the UE device to transmit capability information to the base station indicating how the UE device applies LBRM when the UE device supports more than 16 HARQ processes.

[0146] Embodiment 69 includes the subject matter of embodiment 65, including or excluding the optional elements, wherein the processor is configured to configure a reduced size transport block (TB) when the UE device supports more than 16 HARQ processes.

[0147] Embodiment 70 includes the subject matter of embodiment 69, including or excluding the optional elements, wherein the reduced size is greater than 2 / 3 of the configured TB size when the UE device supports less than 16 HARQ processes.

[0148] Embodiment 71 is a method comprising: when a user equipment (UE) device supports more than 16 HARQ processes, the UE device selectively configuring operation of the UE device to apply limited buffer rate matching (LBRM).

[0149] Embodiment 72 includes the subject matter of embodiment 71, including or excluding the optional elements, and further includes: when the UE device supports more than 16 HARQ processes, automatically configuring the operation of the UE device to apply LBRM.

[0150] Embodiment 73 includes the subject matter of embodiment 71, including or excluding the optional elements, and further includes: when the UE device supports more than 16 HARQ processes, selectively configuring the operation of the UE device to apply LBRM based on the received configuration information.

[0151] Embodiment 74 includes the subject matter of embodiment 71, including or excluding optional elements, and further includes: when the UE device supports more than 16 HARQ processes, controlling the UE device to transmit capability information to the base station indicating how the UE device applies LBRM.

[0152] Embodiment 75 includes the subject matter of embodiment 71, including or excluding the optional elements, and further comprising: configuring a reduced size transport block (TB) when the UE device supports more than 16 HARQ processes.

[0153] Embodiment 76 includes the subject matter of embodiment 75, including or excluding the optional elements, wherein the reduced size is greater than 2 / 3 of the configured TB size when the UE device supports less than 16 HARQ processes.

[0154] Embodiment 77 is a base station comprising a processor configured to perform operations comprising selectively configuring the operation of a user equipment (UE) device to apply limited buffer rate matching (LBRM) when the UE device supports more than 16 HARQ processes.

[0155] Embodiment 78 includes the subject matter of embodiment 77, including or excluding the optional elements, wherein the processor is configured to automatically apply LBRM when the UE device supports more than 16 HARQ processes.

[0156] Embodiment 79 includes the subject matter of embodiment 77, including or excluding the optional elements, wherein the processor is configured to transmit LBRM configuration information to the UE device to selectively configure the operation of the UE device to apply LBRM when the UE device supports more than 16 HARQ processes.

[0157] Embodiment 80 includes the subject matter of embodiment 77, including or excluding the optional elements, wherein the processor is configured to receive capability information from the UE device indicating how the UE device applies LBRM when the UE device supports more than 16 HARQ processes.

[0158] Embodiment 81 includes the subject matter of embodiment 77, including or excluding the optional elements, wherein the processor is configured to configure a reduced size transport block (TB) when the UE device supports more than 16 HARQ processes.

[0159] Embodiment 82 includes the subject matter of embodiment 81, including or excluding the optional elements, wherein the reduced size is greater than 2 / 3 of the configured TB size when the UE supports less than 16 HARQ processes.

[0160] Embodiment 83 is a method comprising selectively configuring operation of a user equipment (UE) device to apply limited buffer rate matching (LBRM) when the UE device supports more than 16 HARQ processes.

[0161] Embodiment 84 includes the subject matter of embodiment 83, including or excluding the optional elements, and further comprising: automatically applying LBRM when the UE device supports more than 16 HARQ processes.

[0162] Embodiment 85 includes the subject matter of embodiment 83, including or excluding the optional elements, and further includes: when the UE device supports more than 16 HARQ processes, transmitting LBRM configuration information to the UE device to selectively configure the operation of the UE device to apply LBRM.

[0163] Embodiment 86 includes the subject matter of embodiment 83, including or excluding the optional elements, and further includes: when the UE device supports more than 16 HARQ processes, receiving capability information from the UE device indicating how the UE device applies LBRM.

[0164] Embodiment 87 includes the subject matter of embodiment 83, including or excluding the optional elements, and further comprising: configuring a reduced size transport block (TB) when the UE device supports more than 16 HARQ processes.

[0165] Embodiment 88 includes the subject matter of embodiment 87, including or excluding the optional elements, wherein the reduced size is greater than 2 / 3 of the configured TB size when the UE supports less than 16 HARQ processes.

[0166] Embodiment 89 is a baseband processor of a user equipment (UE) device, the baseband processor being configured to perform operations comprising: receiving control information indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs; configuring an operation based on the resources to receive the PDSCH transmission or transmit the PUSCH transmission; and in response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring an operation to avoid receiving the PDSCH retransmission or avoid transmitting the PUSCH retransmission, and providing hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for a time slot outside the identified time slot group.

[0167] Embodiment 90 includes the subject matter of embodiment 89, including or excluding the optional elements, wherein each time slot group includes a group of consecutive time slots.

[0168] Embodiment 91 includes the subject matter of embodiment 89, including or excluding the optional elements, wherein each time slot group includes time slots that are interleaved with time slots from other groups.

[0169] Embodiment 92 includes the subject matter of Embodiment 89, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

[0170] Embodiment 93 includes the subject matter of embodiment 89, including or excluding the optional elements, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

[0171] Embodiment 94 is a baseband processor of a user equipment (UE) device, the baseband processor being configured to perform operations comprising: receiving control information indicating HARQ information associated with a PDSCH or PUSCH transmission that transmits at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; determining, based on the control information, that HARQ feedback is disabled; determining, based on information in a control information field that carries information related to HARQ feedback when HARQ feedback is enabled, a repetition count that defines the number of retransmissions in the PDSCH / PUSCH; and configuring operations to receive the PDSCH transmission or transmit the PUSCH transmission based on the HARQ information and the repetition count.

[0172] Embodiment 95 includes the subject matter of embodiment 94, including or excluding the optional elements, wherein the control information field includes a field carrying redundant version sequence information when HARQ feedback is enabled.

[0173] Embodiment 96 includes the subject matter of embodiment 94, including or excluding the optional elements, wherein the control information field includes a field carrying a new data indicator when HARQ feedback is enabled.

[0174] Embodiment 97 includes the subject matter of embodiment 94, including or excluding optional elements, wherein the baseband processor is configured to perform operations comprising: determining a redundant version sequence for the PDSCH / PUSCH based on a time domain resource allocation (TDRA) table index indicated in the control information.

[0175] Embodiment 98 includes the subject matter of embodiment 94, including or excluding optional elements, wherein the baseband processor is configured to perform operations comprising: determining a redundant version sequence based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0176] Embodiment 99 includes the subject matter of embodiment 98, including or excluding optional elements, wherein the baseband processor is configured to perform operations comprising: determining the redundant version sequence based on a redundant version sequence index indicated in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

[0177] Embodiment 100 is a baseband processor of a user equipment (UE) device, the baseband processor being configured to perform operations comprising: receiving control information indicating resources comprising one or more time slots for transmitting a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission comprising at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the one or more time slots are non-contiguous and each contiguous time slot pair in the one or more time slots is separated by a corresponding time slot comprising one or more time slots; and configuring operations based on the resources to receive the PDSCH transmission or transmit the PUSCH transmission.

[0178] Embodiment 101 includes the subject matter of embodiment 100, including or excluding optional elements, wherein the baseband processor is configured to perform operations comprising: determining a set of gaps interleaved between the one or more time slots based on a time domain (TDRA) table index indicated by the control information.

[0179] Embodiment 102 includes the subject matter of embodiment 101, including or excluding the optional elements, wherein the TDRA table index identifies a row in the TDRA table that indicates a sequence of time slots.

[0180] Embodiment 103 includes the subject matter of embodiment 102, including or excluding the optional elements, wherein the row further indicates a repetition number indicating a number of retransmissions included in the PDSCH / PUSCH transmission.

[0181] Embodiment 104 includes the subject matter of embodiment 100, including or excluding the optional elements, wherein each of the corresponding time slots includes the same number of time slots.

[0182] Embodiment 105 is a baseband processor of a user equipment (UE) device, configured to perform operations including selectively configuring the operation of the UE device to apply limited buffer rate matching (LBRM) when the UE supports more than 16 HARQ processes.

[0183] Embodiment 106 includes the subject matter of embodiment 105, including or excluding the optional elements, wherein the baseband processor is configured to automatically configure the operation of the UE device to apply LBRM when the UE supports more than 16 HARQ processes.

[0184] Embodiment 107 includes the subject matter of embodiment 105, including or excluding the optional elements, wherein the baseband processor is configured to selectively configure the operation of the UE device to apply LBRM based on the received configuration information when the UE device supports more than 16 HARQ processes.

[0185] Embodiment 108 includes the subject matter of embodiment 105, including or excluding optional elements, wherein the baseband processor is configured to cause the UE device to transmit capability information to the base station indicating how the UE device applies LBRM when the UE device supports more than 16 HARQ processes.

[0186] Embodiment 109 includes the subject matter of embodiment 105, including or excluding the optional elements, wherein the baseband processor is configured to configure a reduced size transport block (TB) when the UE device supports more than 16 HARQ processes.

[0187] Embodiment 110 includes the subject matter of embodiment 109, including or excluding the optional elements, wherein the reduced size is greater than 2 / 3 of a configured TB size when the UE device supports fewer than 16 HARQ processes.

[0188] Embodiment 111 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0189] Embodiment 112 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the PUSCH or HARQ feedback is transmitted to a satellite.

[0190] Embodiment 113 includes the subject matter of embodiment 11, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0191] Embodiment 114 includes the subject matter of embodiment 11, including or omitting optional elements, wherein the PUSCH or HARQ feedback is transmitted to a satellite.

[0192] Embodiment 115 includes the subject matter of embodiment 21, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0193] Embodiment 116 includes the subject matter of embodiment 21, including or omitting optional elements, wherein the PUSCH is transmitted to a satellite.

[0194] Embodiment 117 includes the subject matter of embodiment 33, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0195] Embodiment 118 includes the subject matter of embodiment 33, including or omitting optional elements, wherein the PUSCH is transmitted to a satellite.

[0196] Embodiment 119 includes the subject matter of embodiment 55, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0197] Embodiment 120 includes the subject matter of embodiment 55, including or omitting optional elements, wherein the PUSCH is transmitted to a satellite.

[0198] Embodiment 121 includes the subject matter of embodiment 89, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0199] Embodiment 122 includes the subject matter of embodiment 89, including or omitting optional elements, wherein the PUSCH or HARQ feedback is transmitted to a satellite.

[0200] Embodiment 123 includes the subject matter of embodiment 94, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0201] Embodiment 124 includes the subject matter of embodiment 94, including or omitting optional elements, wherein the PUSCH is transmitted to a satellite.

[0202] Embodiment 125 includes the subject matter of embodiment 100, including or omitting optional elements, wherein the control information or PDSCH is transmitted by a satellite.

[0203] Embodiment 126 includes the subject matter of embodiment 100, including or omitting optional elements, wherein the PUSCH is transmitted to a satellite.

[0204] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

Claims

1. A baseband processor of a user equipment (UE) device, wherein the baseband processor is configured to perform operations, the operations comprising: receiving control information indicating resources comprising one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs, wherein the time slot group is associated with a range of hybrid automatic repeat request (HARQ) process numbers; configuring operations based on the resources to receive the PDSCH transmission or to transmit the PUSCH transmission; and In response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring operations to avoid receiving the PDSCH retransmission or to avoid transmitting the PUSCH retransmission, and providing hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for the time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for the time slot outside the identified time slot group.

2. The baseband processor of the UE device according to claim 1, wherein each time slot group comprises a group of consecutive time slots.

3. The baseband processor of the UE device of claim 1 , wherein each time slot group comprises time slots interleaved with time slots from other groups. 4 . The baseband processor of the UE device according to claim 1 , wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

5. The baseband processor of the UE device according to claim 1, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

6. A base station, comprising a processor, wherein the processor is configured to perform operations, the operations comprising: transmitting control information indicating resources, the resources comprising one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; identifying a time slot group to which a selected time slot of the one or more time slots belongs, wherein the time slot group is associated with a range of hybrid automatic repeat request (HARQ) process numbers; configuring operation based on the resources to receive the PUSCH transmission or to transmit the PDSCH transmission; as well as In response to determining that a PDSCH / PUSCH retransmission of the PDSCH / PUSCH transmission is scheduled for a time slot outside the identified time slot group, configuring operations to avoid transmitting the PDSCH retransmission or avoid receiving the PUSCH retransmission, and receiving hybrid automatic repeat request (HARQ) feedback based on the PDSCH retransmission scheduled for a time slot within the identified time slot group, wherein the HARQ feedback is not based on the PDSCH scheduled for the time slot outside the identified time slot group.

7. The base station of claim 6, wherein each time slot group comprises a group of consecutive time slots.

8. The base station of claim 6, wherein each time slot group comprises time slots that are interleaved with time slots from other groups.

9. The base station of claim 6, wherein the selected time slot of the one or more time slots comprises a first time slot of the PDSCH / PUSCH.

10. The base station of claim 6, wherein the selected time slot of the one or more time slots comprises a first time slot of a physical downlink control channel (PDCCH) associated with the PDSCH / PUSCH.

11. A baseband processor of a user equipment (UE) device, wherein the baseband processor is configured to perform operations, the operations comprising: receiving control information indicating HARQ information associated with a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission; determining, based on the control information, that HARQ feedback is disabled; determining a repetition number defining the number of retransmissions in the PDSCH / PUSCH based on information in a control information field carrying information related to HARQ feedback when HARQ feedback is enabled; and Operation is configured to receive the PDSCH transmission or to transmit the PUSCH transmission based on the HARQ information and the number of repetitions.

12. The baseband processor of the UE device according to claim 11, wherein the control information field includes a field carrying redundancy version sequence information when HARQ feedback is enabled.

13. The baseband processor of the UE device according to claim 11, wherein the control information field comprises a field carrying a new data indicator when HARQ feedback is enabled.

14. The baseband processor of the UE device according to claim 11, wherein the baseband processor is configured to perform operations, the operations comprising: A redundant version sequence for the PDSCH / PUSCH is determined based on a time domain resource allocation TDRA table index indicated in the control information.

15. The baseband processor of the UE device according to claim 11, wherein the baseband processor is configured to perform operations, the operations comprising: A redundancy version sequence is determined based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

16. The baseband processor of the UE device according to claim 15, wherein the baseband processor is configured to perform operations, the operations comprising: The redundancy version sequence is determined based on a redundancy version sequence index indicated in the control field carrying information related to HARQ feedback when HARQ feedback is enabled.

17. A base station, comprising a processor, wherein the processor is configured to perform operations, the operations comprising: transmitting control information indicating HARQ information associated with a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the control information further indicates that HARQ feedback is disabled; encoding a repetition number defining the number of retransmissions in the PDSCH / PUSCH based on information in a control information field carrying information related to HARQ feedback when HARQ feedback is enabled; transmitting the control information; and Operation is configured to transmit the PDSCH transmission or receive the PUSCH transmission based on the HARQ information and the number of repetitions.

18. The base station of claim 17, wherein the control information field comprises a field carrying redundancy version sequence information when HARQ feedback is enabled.

19. The base station of claim 17, wherein the control information field comprises a field carrying a new data indicator when HARQ feedback is enabled.

20. The base station of claim 17, wherein the processor is configured to perform operations comprising: A redundant version sequence for the PDSCH / PUSCH is indicated based on a time domain resource allocation TDRA table index indicated in the control information.

21. The base station of claim 17, wherein the processor is configured to perform operations comprising: A redundancy version sequence is indicated based on the information in the control field that carries information related to HARQ feedback when HARQ feedback is enabled.

22. The base station of claim 21 , wherein the processor is configured to perform operations comprising: The redundancy version sequence is indicated based on a redundancy version sequence index indicated in the control field carrying information related to HARQ feedback when HARQ feedback is enabled.

23. A baseband processor of a user equipment (UE) device, wherein the baseband processor is configured to perform operations, the operations comprising: receiving control information indicating a time domain resource allocation (TDRA) table index, the TDRA table index indicating resources including one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) retransmission, wherein the TDRA table index is mapped to a set of time slots such that the indicated resources include one or more time slots, the one or more time slots are non-contiguous, and each pair of consecutive time slots in the one or more time slots is separated by a corresponding time slot in the set of time slots, the corresponding time slots including one or more time slots; and Operation is configured based on the resources to receive the PDSCH transmission or to transmit the PUSCH transmission.

24. The baseband processor of the UE device of claim 23, wherein the TDRA table index identifies a row in a TDRA table indicating a sequence of time slots.

25. The baseband processor of the UE device according to claim 24, wherein the row further indicates a repetition number, the repetition number indicating the number of retransmissions included in the PDSCH / PUSCH transmission.

26. The baseband processor of the UE device of claim 23, wherein each of the corresponding time slots includes a same number of time slots.

27. A base station, comprising a processor, wherein the processor is configured to perform operations, the operations comprising: transmission control information, the control information indicating a time domain resource allocation TDRA table index, the TDRA table index indicating resources, the resources comprising one or more time slots for transmitting a PDSCH or PUSCH transmission including at least one physical downlink shared channel PDSCH / physical uplink shared channel PUSCH retransmission, wherein the TDRA table index is mapped to a set of time slots such that the indicated resources include one or more time slots, the one or more time slots are non-contiguous, and each pair of consecutive time slots in the one or more time slots is separated by a corresponding time slot in the set of time slots, the corresponding time slots including one or more time slots; and Operation is configured based on the resources to receive the PDSCH transmission or to transmit the PUSCH transmission.

28. The base station of claim 27, wherein the TDRA table index identifies a row in a TDRA table indicating a sequence of time slots.

29. The base station according to claim 28, wherein the row further indicates a repetition number, the repetition number indicating the number of retransmissions included in the PDSCH / PUSCH transmission.

30. The base station of claim 27, wherein each of the corresponding time slots comprises a same number of time slots.

Images