Receiving and Transmitting in New Radio (NR) Based on Subcarrier Spacing

Abstract

To provide user equipment (UE) that provides reception and transmission in 5G NR (New Radio) with a subcarrier spacing larger than 120 KHz at a frequency larger than 52.6 GHz, a method, and a storage medium.SOLUTION: A method includes: receiving, by user equipment (UE), downlink control information (DCI) indicating a station-signaled slot offset, from a base station; determining a minimum slot offset based on subcarrier spacing of a physical downlink channel larger than 120 KHz; determining a slot offset (K1) between data reception on the physical downlink channel and hybrid automatic repeat request (HARQ) transmission on a physical uplink channel, on the basis of the minimum slot offset and the station-signaled slot offset; and transmitting HARQ feedback for the data reception, on the basis of the slot offset (K1), on the physical uplink channel.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The fifth generation mobile network (5G) is a radio standard aimed at improving data transmission speed, reliability, availability, etc. This standard is still under development and includes many details related to various aspects of wireless communication, such as New Radio (NR) and NR in spectra greater than 52.6 GHz.

Brief Description of the Drawings

[0002]

Figure 1

[0003]

Figure 2

[0004]

Figure 3

[0005]

Figure 4

[0006]

Figure 5

[0007]

Figure 6

[0008]

Figure 7

[0009]

Figure 8

[0010]

Figure 9

[0011]

Figure 10

[0012]

Figure 11

[0013]

Figure 12

[0014]

Figure 13

[0015]

Figure 14

[0016]

Figure 15

[0017]

Figure 16

[0018]

Figure 17

[0019]

Figure 18

Best Mode for Carrying Out the Invention

[0020] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details of various structures, architectures, interfaces, techniques, etc. are described to provide a complete understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art in the technical field having the benefit of this disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this disclosure, "A or B" means (A), (B), or (A and B).

[0021] The following is a glossary of terms that may be used in this disclosure.

[0022] As used herein, the term "circuit" refers to, is part of, or includes a hardware component configured to provide the described functionality, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group), or a memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP). In some embodiments, the circuit can execute one or more software or firmware programs to provide at least a portion of the described functionality. The term "circuit" can also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and the program code used to execute the functions of that program code. In these embodiments, the combination of the hardware element and the program code can be referred to as a particular type of circuit.

[0023] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuit" can refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single core processor, a dual core processor, a triple core processor, a quad core processor, or any other device capable of executing or operating computer executable instructions, such as program code, software modules, or functional processes.

[0024] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, I / O interface, peripheral component interface, network interface card, or the like.

[0025] As used herein, the term "user equipment" or "UE" refers to a device having a wireless communication function and can represent a remote user of network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, reconfigurable mobile device, etc. Further, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0026] As used herein, the term "base station" refers to a network element of a communication network and refers to a device having a wireless communication function that can be configured as an access node in a communication network. Access of a UE to a communication network can be at least partially managed by a base station, whereby the UE connects to the base station to access the communication network. Depending on the radio access technology (RAT), the base station may be referred to as a gNodeB (gNB), eNodeB (eNB), access point, etc.

[0027] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Further, the terms "computer system" or "system" can refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or networking resources.

[0028] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computer device, a mechanical device, a memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, workload units, etc. "Hardware resource" may refer to a computing resource, a memory resource, or a network resource provided by a physical hardware element. "Virtualized resource" may refer to a computing resource, a storage resource, or a network resource provided to an application, a device, a system, etc. by a virtualization infrastructure. The term "network resource" or "communication resource" may refer to a resource accessible by a computer device / system via a communication network. The term "system resource" may refer to any type of shared entity for providing a service and may include a computing resource or a network resource. A system resource can be considered as a set of coherent functions, network data objects or services that are accessible via a server where such system resources exist on a single host or multiple hosts and are clearly identifiable.

[0029] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or a data stream. The term "channel" may be synonymous or equivalent to any other similar term indicating a path or medium through which data is communicated, such as "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", or the like. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0030] As used herein, terms such as "instantiate" and "instantiation" refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0031] The term "connected" may mean that two or more elements in a common communication protocol layer have a signaling relationship established with each other via a communication channel, link, interface, or reference point.

[0032] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with, or referred to as, a networked computer, network hardware, network device, network node, virtualized network function, and the like.

[0033] The term "information element" refers to a structural element that includes one or more fields. The term "field" refers to the individual content of an information element or a data element that includes content. An information element may include one or more further information elements.

[0034] FIG. 1 shows a network environment 100 according to some embodiments. The network environment 100 may include a UE 104 and a gNB 108. The gNB 108 may be a base station that provides a radio access cell, for example, a Third Generation Partnership Project (3GPP (registered trademark)) New Radio (NR) cell, through which the UE 104 can communicate with the gNB 108. The UE 104 and the gNB 108 can communicate via an air interface compliant with 3GPP technical specifications, such as those that define the Fifth Generation (5G) NR system standard.

[0035] The gNB 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and mapping transport channels onto physical channels. Logical channels can transfer data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer, transport channels can transfer data between the MAC layer and the PHY layer, and physical channels can transfer information via the air interface. Physical channels can include a Physical Broadcast Channel (PBCH), a Physical Downlink Control Channel (PDCCH), and a Physical Downlink Shared Channel (PDSCH).

[0036] The PBCH can be used to broadcast system information that the UE 104 can use for initial access to the serving cell. The PBCH can be transmitted together with a Physical Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) in a Synchronization Signal (SS) / PBCH block. The SS / PBCH block (SSB) can be used by the UE 104 during the cell search procedure and for beam selection.

[0037] The PDSCH can be used to transfer end-user application data, Signaling Radio Bearer (SRB) messages, system information messages (e.g., other than the Master Information Block (MIB)) system information messages, and paging messages.

[0038] The PDCCH can transfer downlink control information (DCI) used by the scheduler of gNB 108 to allocate both uplink resources and downlink resources. The DCI can also be used to provide uplink power control commands, configure slot formats, or indicate that preemption has occurred.

[0039] gNB 108 can also transmit various reference signals to UE 104. The reference signals can include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with the transmitted known DMRS sequence to estimate the influence of the propagation channel. Then, UE 104 can apply the inverse of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0040] The reference signals can also include channel state information reference signals (CSI-RS). The CSI-RS can be a multi-purpose downlink transmission that can be used for CSI reporting, beam management, connected-mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.

[0041] References signals and information from a physical channel can be mapped to resources of a resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there is one resource grid. The basic unit of an NR downlink resource grid can be a resource element that can be defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include one PRB in the frequency domain and one OFDM symbol in the time domain, and can include, for example, 12 resource elements. A control channel element (CCE) can represent a group of resources used to transmit a PDCCH. One CCE can be mapped to several REGs, for example, 6 REGs.

[0042] Transmissions using different antenna ports may experience different radio channels. However, in some situations, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler shift, Doppler spread, average delay, delay spread, or spatial receiver parameters (e.g., characteristics related to the downlink received signal angle of arrival at the UE). Antenna ports sharing one or more of these large-scale radio channel characteristics can be said to be quasi co-located (QCL) with each other. 3GPP has defined four types of QCL to indicate which specific channel characteristics are shared. For example, in QCL type A, the antenna ports share Doppler shift, Doppler spread, average delay, and delay spread. In QCL type B, the antenna ports share Doppler shift and Doppler spread is shared. In QCL type C, the antenna ports share Doppler shift and average delay. In QCL type D, the antenna ports share spatial receiver parameters.

[0043] gNB 108 may provide the UE 104 with transmission configuration indicator (TCI) state information to indicate the quasi - co - location (QCL) relationship between the antenna port used for reference signals (e.g., synchronization signal / PBCH or CSI - RS) and downlink data or control signaling, e.g., PDSCH or PDCCH. gNB 108 can use a combination of RRC signaling, MAC control element signaling, and DCI to notify the UE 104 of these QCL relationships.

[0044] The UE 104 can transmit data and control information to the gNB 108 using physical uplink channels. For example, different types of physical uplink channels are possible, including the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH). The PUCCH carries control information, such as uplink control information (UCI), from the UE 104 to the gNB 108, while the PUSCH can carry data traffic (e.g., end - user application data) and can also carry UCI.

[0045] The UE 104 and the gNB 108 may perform beam management operations to identify and maintain the desired beams for transmission in the uplink and downlink directions. Beam management can be applied to both the PDSCH and PDCCH in the downlink direction and the PUSCH and PUCCH in the uplink direction.

[0046] The frequency bands for 5G networks, as described in Figure 1, fall into two sets: Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 covers communications from 450 megahertz (MHz) to 7.125 gigahertz (GHz), including the LTE frequency range. FR2 covers 24.25 GHz to 52.6 GHz. FR2 is known as the millimeter wave (mmWave) spectrum. Research and development for communication via NR in the unlicensed bands above FR2 are underway. For example, industrial interest is developing in the spectrum above the 52.6 GHz band, including frequencies greater than 52.6 GHz, such as between 52.6 GHz and 71 GHz. The radio waves in this band have wavelengths in the so-called millimeter wave band, and the radiation in this band is known as millimeter wave. When operating at these frequencies, 5G NR enables both uplink and downlink operations in unlicensed and / or licensed bands and supports features such as, but not limited to, wideband carriers, flexible numerology, dynamic time division duplexing (TDD), beamforming, and dynamic scheduling / hybrid automatic repeat request (HARQ) timing. Frequencies between 52.6 GHz and 71 GHz are interesting due to their proximity to sub-52.6 GHz (current NR systems), as well as the (un)licensed spectrum between 52.6 GHz and 71 GHz, between 52.6 GHz and 114.25 GHz, between 71 GHz and 114.25 GHz, or any other spectrum where a subcarrier spacing greater than 120 KHz may be required to mitigate phase noise, for immediate commercial opportunities for high data rate communications.

[0047] For transmissions above 52.6 GHz, the subcarrier spacing (SCS) is increased to provide robustness against phase noise. In one embodiment, the subcarrier spacings supported by the UE and gNB (or other network nodes) are a group of subcarrier spacings including 120, 240, 480, 960, and 1920 KHz. However, the group of subcarrier spacings may include fewer subcarrier spacings than all of these subcarrier spacings and / or may include other subcarrier spacings. The 120 KHz subcarrier spacing is currently used for data in FR2. The 240 KHz subcarrier spacing is used for the synchronization signal block (SSB) in FR2. Research is ongoing regarding the feasibility of reusing the 120 KHz subcarrier spacing for spectra above 52.6 GHz. The remaining subcarrier spacings are also under consideration and are likely to require implementation changes. Some of these implementation changes are described herein and are related to communication scheduling and HARQ processing.

[0048] In particular, an increase in subcarrier spacing beyond 120 KHz (e.g., 240 KHz and above) presents implementation challenges related to communication scheduling and HARQ processing. This increase results in a decrease in the size of the symbol (e.g., OFDM symbol). For example, comparing a 120 KHz subcarrier spacing to a 960 KHz subcarrier spacing, the symbol size is reduced by a factor of eight. If the communication scheduling and HARQ processing procedures are not changed from the 5G NR technical specifications (e.g., when subcarrier spacings below 120 KHz are used), the UE may be required to increase a portion of its processing capabilities. In the previous example, the UE has to perform up to eight times the amount of data and HARQ processing when comparing 120 KHz to 960 KHz.

[0049] Embodiments of the present disclosure are described in relation to a frequency spectrum of 52.6 GHz or higher, but the embodiments are not so limited. Instead, the embodiments are equally applicable to other frequency ranges. For example, a particular frequency range may require a particular range of subcarrier spacing. Given the associated subcarrier spacing, communication scheduling and / or HARQ processing may be adjusted for each embodiment of the present disclosure.

[0050] FIG. 2 is a diagram showing examples of subcarrier spacing and slot length according to some embodiments. Compared with previous-generation wireless communications, 5G NR supports multiple different types of subcarrier spacing. For example, LTE supports only 15 KHz, while 5G NR supports subcarrier spacings of 15 KHz, 30 KHz, 60 KHz, and 120 KHz, which are called 0, 1, 2, and 3 in 3GPP TS 38.211 v16.3.0 (2020-10-01) and are denoted by a mathematical mystery "μ". Generally, the slot length depends on the mathematical mystery. A slot contains several symbols. When OFDM symbols are used (e.g., 14 OFDM symbols in a slot) and modulated using the subcarrier spacing, the resulting slot length becomes shorter as the subcarrier spacing becomes wider (or equivalently, as the mathematical mystery increases).

[0051] In the illustration of FIG. 2, a comparison is made between a first subcarrier spacing 210, a second subcarrier spacing 220, and the resulting slot length. The first subcarrier spacing 210 is 120 KHz, and when used, the resulting length of slot 212 is 0.125 milliseconds. In comparison, the second subcarrier spacing 240 is 240 KHz, and when used, the resulting length of slot 222 is 0.0625 milliseconds. In other words, the second subcarrier spacing 240 is twice the first subcarrier spacing 210, but the length of slot 222 is half the length of slot 212. Table 1 below summarizes the mathematical mystery, subcarrier spacing, and slot length for slots containing 14 OFDM symbols.

Table 1

[0052] FIG. 3 is a diagram showing an example of a frame structure according to some embodiments. Regardless of the subcarrier spacing, the length of the radio frame and the length of one subframe remain the same respectively. The radio frame is 10 milliseconds long, and the subframe is 1 millisecond long. The change in subcarrier spacing allows flexibility regarding the length of a slot and the number of slots within a subframe. The number of symbols within a slot may vary based on the subcarrier spacing, but does not have to vary and can vary according to the slot configuration type. In the case of slot configuration 0, the number of symbols within a slot is 14. In comparison, in the case of slot configuration 1, this number is 7.

[0053] In the illustration of FIG. 3, a comparison is made between a first radio frame 310 and a second radio frame 320. The first radio frame 310 corresponds to a subcarrier spacing of 120 KHz, and the second radio frame 320 corresponds to a subcarrier spacing of 240 KHz. Both radio frames 310 and 320 have the same length of 10 milliseconds. Both radio frames 310 and 320 also include 10 subframes, each of which is 1 millisecond. However, the number and length of slots vary between the two radio frames 310 and 320.

[0054] The subframe 312 of the radio frame 310 contains 8 slots. Since the subframe 312 is 1 millisecond in length, each of the 8 slots is 0.125 milliseconds. As shown in the figure, the slot 314 of the subframe 312 contains 14 symbols and is 0.125 milliseconds in length. In comparison, the subframe 322 of the radio frame 320 contains 16 slots. Since the subframe 322 is 1 millisecond in length, each of the 16 slots is 0.0625 milliseconds. As shown in the figure, the slot 324 of the subframe 322 contains 14 symbols and is 0.0625 milliseconds in length. Therefore, the radio frame 320 contains twice the number of slots and symbols as the radio frame 310, but their lengths are the same. This comparison is similarly applicable to other subcarrier intervals. For example, for a radio frame with a 120KHz subcarrier interval, a radio frame with a 480KHz subcarrier interval contains four times the number of slots and symbols, a radio frame with a 960KHz subcarrier interval contains eight times the number of slots and symbols, and a radio frame with a 1920KHz subcarrier interval contains sixteen times the number of slots and symbols.

[0055] Figure 4 is a diagram showing an example of communication scheduling according to some embodiments. Generally, communication scheduling is defined based on slots rather than actual time. For example, different types of communication including DCI reception, data reception, data transmission, and HARQ transmission are possible. The communication can be performed on a physical channel (downlink or uplink) that has a frequency greater than 52.6 GHz and can use a subcarrier interval greater than 120KHz (e.g., 240, 480, 960, and / or 1920KHz).

[0056] In the present disclosure, uplink slots and downlink slots are referred to. An uplink slot refers to a slot that can include symbols used to send uplink traffic (data and / or control). The slot itself can also include symbols used to receive downlink traffic (data and / or control). Conversely, a downlink slot refers to a slot that can include symbols used to receive downlink traffic and / or control. The slot itself can also include symbols used to send uplink traffic and / or control. In particular, 5G NR enables each slot to be used either for only uplink traffic (in which case the slot is referred to herein as an uplink slot), only downlink traffic (in which case the slot is referred to herein as a downlink slot), or both uplink and downlink traffic (in which case the slot is known as a flexible slot and is referred to herein as an uplink slot when referring to uplink traffic and as a downlink slot when referring to downlink traffic).

[0057] In the example of FIG. 4, the UE receives DCI 410 from the base station (e.g., on the PDCCH). DCI 410 can have format 1_0, format 1_1, or format 1_2, and can schedule data reception (e.g., on PDSCH 420) and HARQ transmission (e.g., positive / negative acknowledgment (ACK / NAK) on PUCCH 430). The scheduling of data reception follows a slot offset (K0) from DCI reception, and the scheduling of HARQ feedback follows a slot offset (K1) from data reception (or K0 + K1 from DCI reception). Newer DCI formats are possible (since Release 17 of the 3GPP technical specifications) and can be referred to herein as DCI format 1_x. Embodiments of the present disclosure are equally applicable to DC format 1_x, whereby the slot offset (K) can depend on the subcarrier spacing using any of the techniques described in FIGS. 5 to 12.

[0058] The slot offset (K0) is the slot offset delay between downlink allocation and downlink data reception. This slot offset delay can be defined as the number of slots between the downlink slot in which the PDCCH (DCI) for downlink scheduling is received and the downlink slot in which the PDSCH data is scheduled. The slot offset (K1) is the slot offset delay between downlink data reception and the corresponding HARQ feedback on the uplink (e.g., the HARQ codebook to be sent within an uplink slot on the PUCCH for downlink data reception). This slot offset delay can be defined as the number of slots between the downlink slot in which the data is scheduled on the PDSCH and the uplink slot in which the ACK / NACK feedback for the scheduled PDSCH data needs to be sent. The slot offset (K1) can be a function of the number of OFDM symbols (N1) required for UE processing from the end of data reception to the earliest possible start of HARQ transmission (e.g., from the end of PDSCH reception to the earliest possible start of ACK / NAK transmission). The aspects of the slot offset (K0) and the slot offset (K1) are described in 3GPP TS 38.214 v16.3.0 (2020-10-02) and 3GPP TS 38.213 v16.3.0 (2020-10-02), respectively.

[0059] The UE also receives DCI 440 from the base station (e.g., on the PDCCH). DCI 440 can have format 0_0, format 0_1, or format 0_2, and can schedule data transmission (e.g., on PUSCH 450). The scheduling of the data transmission follows a slot offset (K2) from the DCI reception. The slot offset (K2) is the slot offset delay between the uplink grant reception in the downlink and the corresponding uplink data transmission. This slot offset delay can be defined as the number of slots between the downlink slot in which the PDCCH (DCI) for uplink scheduling is received and the uplink slot in which the uplink data needs to be transmitted on the PUSCH. The slot offset (K2) can be a function of the number of OFDM symbols (N2) from the DCI reception to the earliest possible start of the uplink data transmission (e.g., from the PDCCH to the earliest possible start of the PUSCH). The aspects of the slot offset (K2) are described in 3GPP TS 38.214 v16.3.0 (2020-10-02).

[0060] In addition, the UE can receive multiple DCIs within a time frame (shown as the first DCI 460 and the second DCI 470), and multiplex the corresponding HARQ feedback on the uplink channel according to their timings. The possibility of performing multiplexing depends on the number of symbols (N3) between the second DCI 470 and the first HARQ feedback transmission (e.g., the number of symbols between the downlink slot in which the second DCI 470 is received and the uplink slot scheduled by the first DCI 460 for the transmission of the HARQ feedback). The aspects of the number of symbols (N3) are described in 3GPP TS 38.213 v16.3.0 (2020-10-02).

[0061] Communication scheduling is defined based on slots rather than actual time, and since the number of slots changes within the same unit of time according to the subcarrier frequency, the amount of processing performed within the same unit of time also changes. As described above, an increase in the subcarrier spacing results in a decrease in the slot duration. Therefore, within the same unit of time, an increase requires additional slot-based processing. For example, comparing a 120 KHz subcarrier spacing to a 240 KHz subcarrier spacing, the slot size is reduced by half. In 1 millisecond, for a 120 KHz subcarrier spacing, 8 slots need to be processed, and for a 240 KHz subcarrier spacing, 16 slots need to be processed. In other words, a device such as UE104 needs to perform up to twice as much HARQ and data processing in the same unit of time for a 240 KHz subcarrier spacing related to a 120 KHz subcarrier spacing. To mitigate the impact of processing, communication scheduling (e.g., the timeline between DCI reception, data reception, data transmission, and / or HARQ feedback transmission) can take into account changes to the slot length so that the processing amount does not, in some cases, increase significantly within the same unit of time. Embodiments for such types of communication scheduling are described herein.

[0062] Referring back to the above slot offset and number of OFDM symbols, the UE processing time depends on such parameters that depend on the subcarrier spacing. For example, according to 3GPP TS 38.214 v16.3.0 (2020-10-02), "if the first uplink symbol of the PUCCH carrying HARQ-ACK information, defined by the allocated HARQ-ACK timing K1 and the PUCCH resources used and including the effect of the timing advance, does not start earlier than symbol L1, where L1 is after the end of the last symbol of the PDSCH carrying the TB that is acknowledged being acknowledged, T proc,1 =(N1 + d 1,1 + d2)(2048 + 144)·κ2 -μ ·T c + T extIt is defined as the next uplink symbol at which the CP starts after that, and the UE is assumed to provide a valid HARQ-ACK message, and "N1 is based on μ in Table 5.3-1 and Table 5.3-2 for UE processing capabilities 1 and 2, respectively." These two tables are copied below in this specification for reference as Table 2 and Table 3, respectively.

Table 2

Table 3

[0063] As shown in the above two tables, as the numerology "μ" (e.g., subcarrier spacing) increases, the number of OFDM symbols (N1) increases, and the processing time (e.g., T proc,1 ) increases.

[0064] Similarly, according to 3GPP TS 38.214 v16.3.0 (2020-10-02), "the first uplink symbol in the PUSCH allocation for a transport block, including DM-RS and including the effect of timing advance, as defined by the slot offset K2 of the scheduling DCI and the start and length indicator SLIV, is not earlier than symbol L2, where L2 is after the reception of the last symbol of the PDCCH that carries the DCI that schedules the PUSCH has ended, and its CPT proc,2 =max((N2 + d 2,1 + d2)(2048 + 144)·κ2 -μ ·T c + T ext + T switch , d 2,2 is defined as the next uplink symbol having, and the UE is assumed to transmit the transport block", and "N2 is based on μ in Table 6.4-1 and Table 6.4-2 for UE processing capabilities 1 and 2, respectively." These two tables are copied below in this specification for reference as Table 4 and Table 5, respectively.

Table 4

Table 5

[0065] Here too, as shown in the above two tables, when the numerology "μ" (e.g., subcarrier spacing) increases, the number of OFDM symbols (N2) increases, and the processing time (e.g., T proc,2 ) increases.

[0066] Regarding the number of OFDM symbols (N3), 3GPP TS 38.213 v16.3.0 (2020-10-02) states that "if the UE detects a first DCI format indicating the first resource for PUCCH transmission with the corresponding HARQ-ACK information in a slot and detects a second DCI format indicating the second resource for PUCCH transmission with the corresponding HARQ-ACK information at a later time in the slot, if the PDCCH reception including the second DCI format is not before the start of the first symbol of the first resource for PUCCH transmission within the slot by N3·(2048 + 144)·κ·2 -μ ·T c , the UE does not expect to multiplex the HARQ-ACK information corresponding to the second DCI format in the PUCCH resource in the slot, where κ and T_c are defined in Section 4.1 of [4, TS 38.211] and correspond to the minimum SCS configuration among the SCS configuration of the PDCCH providing the DCI format and the SCS configuration of the PUCCH." Using this timing formula, as the numerology "μ" (e.g., subcarrier spacing) increases, the number of OFDM symbols (N3) increases and the processing time increases.

[0067] In addition to the impact on processing time, the change to the subcarrier spacing may affect the manner of HARQ processing. Two types of HARQ codebooks are defined: type 1 codebook (semi-static) and type 2 codebook (dynamic). In the type 1 codebook, the size of the HARQ codebook is fixed by RRC signaling and depends on the DCI format used to allocate resources. For DCI format 1_0 (fallback DCI), the size can be set from 8 consecutive slots. DCI format 1_1 (non-fallback DCI) includes an indicator indicating the size, such as the PDSCH-to-HARQ_feedback_timing_indicator field that can be used to select a maximum of 8 values in the range from 0 to 15: dl-data-to-ULACK from {0,1,5,7,9,10,11,15} PUCCH-Config::=SEQUENCE{ dl-DataToUL-ACK SEQUENCE(SIZE(8))OF INTEGER(0..15)OPTIONAL,--Need M }。

[0068] The Type 1 codebook is robust against UEs that fail to detect / decipher resource allocations on the PDCCH. However, its fixed size can result in a large overhead. In the case of the Type 2 codebook, the size varies based on the number of resource allocations. This codebook defines a counter dynamic allocation index (cDAI) and a total dynamic allocation index (tDAI). The cDAI included in the DCI indicates the number of scheduled downlink transmissions up to the point when the DCI was received in the carrier first time second manner. The tDAI included in the DCI indicates the total number of downlink transmissions across all carriers up to this point (e.g., the highest cDAI at the current time). The Type 2 codebook is transmitted using the DAI field in the DCAI format 1_0 (cDAI only) as a 2-bit field and the DCI format 1_1 (cDAI and tDAI) as a 4-bit field. The gNB uses the first / second DAI in the DCI format 0_1 to request HARQ transmissions, where the 2-bit field is used to indicate the total DAI (e.g., the total number of HARQ ACKs to be returned to the gNB). Compared to the Type 1 codebook, the Type 2 codebook is less robust but more resource-efficient.

[0069] Assuming a larger subcarrier spacing (smaller symbol duration), as explained above, the number of symbols required for processing (e.g., PDSCH (N1)) increases. The increase affects the delay between downlink data reception and the corresponding HARQ-ACK feedback on the uplink and its associated signaling (e.g., by N1), the delay between DCI reception and uplink transmission (e.g., by N2), the overhead required by the HARQ codebook to be fed back, the UE timeline requirements for multiplexing multiple HARQ ACKs in the feedback (e.g., by N1 or N2 and N3), and the number of HARQ ACK processes required.

[0070] To mitigate the impact, it is possible to consider modifications to the number of OFDM symbols N1, N2, and N3. However, as further explained in the following figure, a better approach can be used by adopting scheduling and HARQ processing for the increased subcarrier interval.

[0071] As long as it is N1, only the PDSCH processing capacity 1 is required (for example, referring back to Table 3, the PDSCH processing capacity 2 has already not been considered beyond the mathematical mystery "μ" of 2 corresponding to the 60KHz subcarrier interval). One option is to keep T proc,1 the same value as the time processing for the 120KHz subcarrier interval (T proc,1 (120KHz)). Another option is to set T proc,1 to be smaller than the time processing for the 120KHz subcarrier interval (where T proc,1 = T proc,1 (120KHz)). Yet another option is to keep N1 the same value as the number of OFDM symbols for the 120KHz subcarrier interval (N1(120KHz)). A further option is to set N1 to be smaller than the number of OFDM symbols for the 120KHz subcarrier interval (where N1 = N1(120KHz)). However, for subcarrier intervals below 120KHz and for processing in the same unit time, any of these four options will lead to a significant increase in the number of symbols (or equivalently, slots) before HARQ feedback transmission. This conclusion is shown in Tables 6 and 7 below based on the T proc,1 definition. As a result, an increase in the slot offset (K1) is required, resulting in an increase in the memory size required for symbol storage before HARQ feedback transmission, an increase in the number of HARQ processes, and modifications based on the limitations on HARQ resources.

Table 6

Table 7

[0072] The number of OFDM symbols (N1) in Table 6 is for dmrs-AdditionalPosition = pos0 in DMRS-DownlinkConfig for both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB. The values for the first 4 rows are also shown in Table 2. The values for the last 4 rows are based on T proc,1 and. These last 4 values are linear, but non-linear values can also be derived. Similarly, the number of OFDM symbols (N1) in Table 7 is for cases where dmrs-AdditionalPosition ≠ pos0 in DMRS-DownlinkConfig for either dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB, or when the upper layer parameters are not configured. The values for the first 4 rows are also shown in Table 2. The values for the last 4 rows are based on T proc,1 and. These last 4 values are linear, but non-linear values can also be derived.

[0073] As long as it is N2, only PDSCH processing capability type 1 may be required (for example, referring back to Table 3, PDSCH processing capability type 2 is already not considered beyond the mathematical mystery of 2 "μ"). One option is to keep T proc,2 at the same value as the time processing T proc,2 (120KHz)) for a 120KHz subcarrier spacing. Another option is to set T proc,2 to be smaller than the time processing for a 120KHz subcarrier spacing (where T proc,2 = T proc,2(120 KHz)). Another option is to keep N2 the same value as the number of OFDM symbols for a 120 KHz subcarrier spacing (N2(120 KHz)). A further option is to set N2 to be less than the number of OFDM symbols for a 120 KHz subcarrier spacing (where N2 = N2(120 KHz)). However, for subcarrier spacings below 120 KHz and to process in the same unit time, any of these four options will lead to a significant increase in the number of symbols (or equivalently, slots) before PUSCH transmission. As a result, an increase in the slot offset (K2) and its related signaling is required, and consequently, the memory size required for symbol storage before PUSCH transmission increases.

[0074] Up to N3, only PDSCH processing capability type 1 may be required (for example, referring back to Table 3, PDSCH processing capability type 2 has already not been considered beyond a mathematical mystery number 'μ' of 2). One option is to keep N3 the same value as the number of OFDM symbols for a 120 KHz subcarrier spacing (N3(120 KHz)). Another option is to set N3 to be less than the number of OFDM symbols for a 120 KHz subcarrier spacing (where N3 = N3(120 KHz)). However, compared to subcarrier spacings below 120 KHz and to process in the same unit time, either of these two options will lead to a significant increase in the number of symbols (or equivalently, slots) before HARQ multiplexing. As a result, the memory size required for symbol storage increases or the limit on the number of symbols to be transmitted increases.

[0075] Figures 5 to 12 illustrate a scheduling-based approach to mitigate the impact of the increase in the number of symbols (or equivalently, slots) with respect to the increase in subcarrier spacing. Figures 13 to 15 illustrate a HARQ processing-based approach to mitigate this impact. Different approaches can be used independently of each other or in relation to each other.

[0076] FIG. 5 is a diagram showing an example of HARQ slot-based scheduling that increases the number of candidate slots according to some embodiments. The illustrated scheduling relates to a slot offset (K1) between data reception and HARQ feedback transmission. In a particular figure of FIG. 5, the use of DCI format 1_0 is shown. However, the embodiments are equally applicable to DCI formats 1_1 and 1_2, as will be further described below.

[0077] Several slots are shown at the top of FIG. 5. These slots may be available for communications using subcarrier spacing of 120 KHz or less. The downlink PDSCH slot is received by the UE. The DCI indicates that HARQ feedback transmission may occur in an uplink PUCCH slot having an offset with respect to the downlink PDSCH slot. For example, the DCI includes a slot offset indicator for this offset. In the case of DCI format 1_0, the slot offset indicator is 3 bits and can correspond to the "PDSCH-to-HARQ-timing-indicator" mapped to K1 = {1, 2, 3, 4, 5, 6, 7, 8}. Therefore, in DCI format 1_0, up to 8 consecutive slots are candidate slots 512 for HARQ feedback transmission. In particular, the uplink slot for HARQ feedback transmission can be selected to be candidate slot 510 from candidate slot 512. In the case of DCI formats 1_1 and 1_2, the "PDSCH-to-HARQ timing indicator" can be 0, 1, 2, or 3 bits in length. 3GPP TS 38.212 v16.3.0 (2020-10-01), Table 9.2.3-1 (hereinafter copied as Table 8) provides the mapping between the "PDSCH-to-HARQ timing indicator" and the number of slots for transmitting the feedback "dl-DataToUL-ACK" in PUCCH-Config within the RRC reconfiguration message. The "PDSCH-to-HARQ-timing-indicator" can be mapped to up to 15 consecutive slots that form the set of candidate slots 512.

Table 8

[0078] At the bottom of FIG. 5, several slots are also shown. However, these slots may be available for communication using a subcarrier spacing greater than 120 KHz. A subcarrier spacing of 240 KHz is shown for comparison with a subcarrier spacing of 120 KHz, but the embodiments are equally applicable to larger subcarrier spacings. Generally, the uplink slot for HARQ feedback transmission is determined to be a candidate slot from the set of candidate slots 522, where the size of this set is larger than the size of the set of candidate slots 512. For example, in DCI format 1_0, up to 8 consecutive candidate slots are available for a 120 KHz subcarrier spacing, but this number can be increased to 16 (or some other maximum value) for a 240 KHz subcarrier spacing (and can be further increased for larger subcarrier spacings). To do so, the "PDSCH-to-HARQ timing indicator" can be increased from 3 bits to "m" bits, where m is an integer greater than 3 (e.g., for a 240 KHz subcarrier spacing, "m = 4 bits" results in "2 4 = 16" consecutive slots as the upper limit of the set of candidate slots 522). Similarly, using DCI formats 1_1 and 1_2, the "PDSCH-to-HARQ timing indicator" can be increased from a maximum of 3 bits to a maximum of "m" bits, where m is an integer greater than 4 (e.g., for a 240 KHz subcarrier spacing, "m = 5 bits" results in "2 5 = 32" consecutive slots as the upper limit of the set of candidate slots 522). Additionally or alternatively, since the "PDSCH-to-HARQ timing indicator" is mapped to "dl-DataToUL-ACK" (or "dl-DataToUL-ACKForDCIFormat1_2"), the size of "dl-DataToUL-ACK" (or "dl-DataToUL-ACKForDCIFormat1_2") can be increased to account for the increased number of slots (e.g., to 30 slots for a 240 KHz subcarrier spacing).

[0079] At the top and bottom of FIG. 5, DCI candidate slots 512 and 522 are offset from the downlink slot for data reception (e.g., for DCI format 1_0, the offset can be up to 8 slots for a 120 KHz subcarrier spacing and can be increased to more slots for subcarrier spacings larger than 120 KHz). The DCI is received from a base station (e.g., gNB 108) and indicates the slot offset, so this indicated slot offset is referred to herein as the base station signaled slot offset. For DCI format 1_0, format 1_1, or format 1_2, the base station signaled slot offset is determined based on the “PDSCH-to-HARQ-timing-indicator” of the DCI.

[0080] FIG. 6 is a diagram showing an example of an operation flow / algorithm structure 600 for HARQ slot-based scheduling to increase the number of candidate slots according to some embodiments. A UE can implement the operation flow / algorithm structure 600 to determine the scheduling of HARQ feedback transmission and transmit HARQ feedback accordingly. The operation flow / algorithm structure 600 can be executed or implemented by a UE such as UE 104, 1700, etc., or its components, such as processor 1704.

[0081] The operation flow / algorithm structure 600 may include, at 602, signaling to the base station the UE's ability for data reception on a physical downlink channel having a frequency greater than 52.6 GHz, where the data reception uses a subcarrier spacing greater than 120 KHz. In some embodiments, the signaling can be RRC signaling.

[0082] The operation flow / algorithm structure 600 may further include, at 604, receiving downlink control information (DCI) including a slot offset indicator from a base station. In some embodiments, the DCI has format 1_0, format 1_1, or format 1_2 and includes a "PDSCH-to-HARQ-timing-indicator" that can schedule HARQ transmissions on an uplink physical channel (e.g., PUCCH).

[0083] The operation flow / algorithm structure 600 further includes, at 606, determining a slot offset (K1) between data reception and hybrid automatic repeat request (HARQ) transmission on a physical uplink channel based on a slot offset indicator, where the slot offset (K1) is greater than the minimum number of slots based on a subcarrier spacing greater than 120 KHz. In some embodiments, the DCI has format 1_0, format 1_1, or format 1_2 and includes a "PDSCH-to-HARQ-timing indicator". In the case of DCI format 1_0, the "PDSCH-to-HARQ-timing indicator" can include more than 3 bits based on the subcarrier spacing being greater than 120 KHz. The 3-bit value indicates a set of candidate slots for HARQ transmission. Similarly, in the case of DCI format 1_1 or format 1_2, the "PDSCH-to-HARQ-timing indicator" can include more than 3 bits based on the subcarrier spacing being greater than 120 KHz. The 4-bit value is mapped to "dl-DataToUL-ACK" (or "dl-DataToUL-ACKForDCIFormat1_2") which indicates a set of candidate slots for HARQ transmission. (The "PDSCH-to-HARQ-timing-indicator" can include up to 4 bits) Additionally or alternatively, "dl-DataToUL-ACK" (or "dl-DataToUL-ACKForDCIFormat1_2") indicates a set of candidate slots, where the set is based on a subcarrier spacing greater than 120 KHz.

[0084] The operation flow / algorithm structure 600 may further include, at 608, transmitting HARQ feedback for data reception based on a slot offset (K1) on an uplink physical channel. In some embodiments, the UE determines that a scheduled uplink slot for HARQ feedback transmission is an uplink slot delayed by a slot offset (K1) from a downlink slot (e.g., a PDSCH slot) for data reception. The UE generates one or more HARQ codebooks corresponding to data reception (e.g., one or more PDSCH slots or sub-slots) and transmits the HARQ codebook in the scheduled uplink slot.

[0085] FIG. 7 is a diagram illustrating an example of HARQ slot-based scheduling with a minimum slot offset according to some embodiments. Here, the upper part of FIG. 7 is the same as the upper part of FIG. 5, and its description is equally applicable to FIG. 7 and is used here for comparison.

[0086] As shown in the lower part of FIG. 7, instead of increasing the size of the candidate slot set (increasing from 8 to 16 as in FIG. 5), a minimum slot offset 710 is used. The same set size can be used for both sub-carrier intervals of 120 KHz or less and sub-carrier intervals of 240 KHz or more and can be signaled by DCI (e.g., the DCI indicates a base station-signaled slot offset similar to that described in FIG. 5). For example, in the case of DCI format 1_0, a maximum of 8 candidate slots 722 are possible. In the case of DCI format 1_1 or format 1_2, a maximum of 15 candidate slots 722 are possible. Nevertheless, it may be possible to use different (e.g., larger or smaller) set sizes for sub-carrier intervals of 240 KHz or more.

[0087] The minimum slot offset 710 is the minimum number of slots that follow a downlink slot for data reception (e.g., a PDSCH slot) and for which HARQ feedback transmission for the data reception is not scheduled (equivalently, HARQ feedback for the data reception cannot be transmitted). The candidate slot 722 is delayed by the minimum slot offset 710 with respect to the downlink slot. The minimum slot offset 710 can be signaled in an RRC message, indicated by DCI (e.g., as another DCI field of one or more bits), or defined in the UE configuration (e.g., this definition is incorporated in the 3GPP technical specification). Generally, the minimum slot offset 710 can be defined as a ceiling or floor integer equal to the ratio of (i) the number of OFDM symbols (N1) required for UE processing from the end of data reception to the earliest possible start of HARQ transmission, and (ii) the number of symbols in a slot. For example, according to Table 6, the number of OFDM symbols (N1) is 160 symbols for a subcarrier spacing of 960 KHz. In the case of slot configuration 0, the number of symbols in a slot is 14. Thus, in this figure, the minimum slot offset 710 is 11 slots.

[0088] FIG. 8 is a diagram illustrating an example of HARQ slot-based scheduling with discontinuous candidate slots having a uniform distribution, according to some embodiments. Here, the upper part of FIG. 8 is the same as the upper part of FIG. 5, and the description thereof is similarly applicable to FIG. 8. Further, similar to FIG. 7, the same set size of candidate slots can be used for both subcarrier spacings of 120 KHz or less and 240 KHz or more, and can be signaled by DCI (e.g., the DCI indicates a base station-signaled slot offset).

[0089] As shown in the lower part of FIG. 8, instead of using consecutive candidate slots (as in FIG. 7), non-consecutive candidate slots 812 with a uniform distribution are possible. The non-consecutive candidate slots 812 are equally spaced for each uniform distribution. A minimum slot offset 810 may be used, which may be similar to the minimum slot offset 710 in FIG. 7.

[0090] In the example of FIG. 8, the uniform distribution skips every other slot, and as a result, the candidate slots 812 are separated by only one intermediate non-candidate slot (e.g., a slot that may not be used for HARQ feedback transmission). The uniformity can be defined by a slot_offset_multiplier used to multiply the base station-signaled slot offset, where the slot_offset_multiplier is a linear multiplier. For example, if the base station-signaled slot offset is 8 slots, the slot_offset_slot_offset_multipler can be set to 2, and the multiplication results in a 16-slot distribution, thus distributing 8 candidate slots 812 over 16 slots that alternate between candidate and non-candidate slots.

[0091] Therefore, the slot offset (K1) is based on the minimum slot offset, the slot_offset_multiplier, and the base station-signaled slot offset. For example, the slot offset (K1) is equal to. The slot_offset_multiplier can be signaled in the RRC message, indicated by the DCI (e.g., as another DCI field of one or more bits), or defined in the UE configuration (e.g., this definition is incorporated in the 3GPP technical specification).

[0092] FIG. 9 illustrates an example of HARQ slot-based scheduling with discontinuous candidate slots having a non-uniform distribution according to some embodiments. Here, the upper part of FIG. 9 is the same as the upper part of FIG. 5, and the description thereof is similarly applicable to FIG. 9. Further, similar to FIG. 8, the same set size of candidate slots can be used for both subcarrier spacings of 120 KHz or less and subcarrier spacings of 240 KHz or more, and can be signaled by DCI (e.g., the DCI indicates a base station-signaled slot offset). Further, the minimum slot offset 910 can be used, which may be the same as or different from the minimum slot offset 810 of FIG. 8.

[0093] As shown in the lower part of FIG. 9, instead of using a uniform distribution of discontinuous candidate slots (as in FIG. 8), a non-uniform distribution of candidate slots 912 is possible. The candidate slots 912 are not equally spaced. The non-uniformity can be defined by a slot_offset_multiplier used to multiply the base station-signaled slot offset, where the slot_offset_multiplier is a non-linear multiplier that varies from one candidate slot to the next. For example, the slot_offset_multiplier can be defined using a pseudo-random function. In another example, a hash function can be used. In this figure, the slot position hash is generated by hashing at least the base station-signaled slot offset.

[0094] Thus, the slot offset (K1) is based on the minimum slot offset, the slot_offset_multiplier, and the base station-signaled slot offset. For example, the slot offset (K1) is equal to or equal to in the case of a random multiplier. The slot_offset_multiplier can be signaled in the RRC message, indicated by DCI (e.g., as another DCI field of one or more bits), or defined in the UE configuration (e.g., this definition is incorporated in the 3GPP technical specification).

[0095] In FIGS. 5 to 9, candidate slots are indicated by a hatching pattern. In FIGS. 6 to 9, the minimum slot offset is indicated by a horizontal pattern. In different embodiments of FIGS. 5 to 9, only PDSCH processing capability 1 is required for subcarrier spacings greater than 120 KHz (for example, referring back to Table 3, PDSCH processing capability 2 has already not been considered beyond the mathematical mystery "μ" of 2 corresponding to a 60 KHz subcarrier spacing). In addition, the base station can dynamically configure and signal a slot offset (K1) so as to be specific to the UE and / or the subcarrier spacing used by the UE.

[0096] FIG. 10 is a diagram showing an example of an operation flow / algorithm structure 1000 for HARQ slot-based scheduling with a minimum slot offset according to some embodiments. A UE can implement the operation flow / algorithm structure 1000 to determine the scheduling of HARQ feedback transmission and transmit HARQ feedback accordingly. The operation flow / algorithm structure 1000 can be executed or implemented by a UE such as UE104, 1700, etc., or a component thereof, such as a processor 1704.

[0097] The operation flow / algorithm structure 1000 may include, at 1002, receiving downlink control information (DCI) from the base station indicating the base station-signaled slot offset. In some embodiments, the DCI has format 1_0, format 1_1, or format 1_2 and includes a slot offset indicator indicating the base station-signaled slot offset. The slot offset indicator can be, for example, "PDSCH-to-HARQ-timing-indicator".

[0098] The operation flow / algorithm structure 1000 may include, at 1004, determining a minimum slot offset based on a subcarrier spacing of a physical downlink channel greater than 120 KHz. In some embodiments, the minimum slot offset is determined from the UE's RRC configuration, DCI (e.g., from a field within the DCI), or a predefined configuration of the UE.

[0099] The operation flow / algorithm structure 1000 may include, at 1006, determining a slot offset (K1) between data reception on a physical downlink channel and hybrid automatic repeat request (HARQ) transmission on a physical uplink channel based on the minimum slot offset and a base station signaled slot offset, where the physical downlink channel has a frequency greater than 52.10 gigahertz (GHz). In some embodiments, the slot offset (K1) corresponds to a delay of the base station signaled slot offset by the minimum slot offset, as in the case of FIG. 7. In some additional or alternative embodiments, the slot offset (K1) is determined based on a linear or non-linear multiplier of the base station signaled slot offset, as in FIGS. 8 and 9. The linear or non-linear multiplier may be determined from the UE's RRC configuration, DCI (e.g., from a field within the DCI), or a predefined configuration of the UE.

[0100] The operation flow / algorithm structure 1000 may include, at 1008, transmitting HARQ feedback for data reception based on a slot offset (K1) on a physical uplink channel. In some embodiments, the UE determines that the scheduled uplink slot for HARQ feedback transmission is an uplink slot delayed by a slot offset (K1) from the downlink slot (e.g., PDSCH slot) of data reception. The UE generates one or more HARQ codebooks corresponding to data reception (e.g., one or more PDSCH slots or sub-slots) and transmits the HARQ codebook in the scheduled uplink slot.

[0101] FIG. 11 shows an example of slot-based scheduling for data reception or data transmission according to some embodiments. Slot-based scheduling is indicated in DCI, schedules communication on a physical channel, the physical channel has a frequency greater than 52.6 GHz, and the communication uses a sub-carrier spacing greater than 120 KHz. The communication can be for data reception, in which case the DCI has format 1_0, format 1_1, or format 1_2 and indicates a base station-signaled slot offset (K0) for which the slot offset is determined. The communication can be for data transmission, in which case the DCI has format 0_0 or format 0_1 and indicates a base station-signaled slot offset (K2) for which the slot offset is determined.

[0102] Four options are shown in FIG. 11 and can be used independently of or in relation to each other. These four options are similar to the embodiments described in FIGS. 5, 7, 8, and 9, except that the scheduled downlink or uplink slot is for data communication rather than HARQ feedback transmission.

[0103] The first option is shown at the top of FIG. 11. In an example of this option, the size of the set formed by candidate slot 110 has the maximum number of slots, and the maximum number is based on the subcarrier spacing, similar to FIG. 5. Generally, the maximum number is larger than the maximum number used for subcarrier spacings of 120 KHz or less. Additionally, the maximum number can increase with an increase in subcarrier spacing across 120 KHz.

[0104] For example, on the downlink, DCI format 1_0, format 1_1, or format 1_2 carries a 4-bit field named "time domain resource allocation". The bit value of "time domain resource allocation" is mapped to the row index of a look-up table (default look-up tables A, B, or C, or an RRC configured look-up table called "pdsch-TimeDomainAllocationList"). Default look-up tables A, B, and C are copied herein below from 3GPP TS 38.214 v16.3.0 (2020-10-02) and are labeled as Table 9, Table 10, and Table 11 respectively. To show a larger maximum number for a subcarrier spacing across 120 KHz, the table can be modified to include additional rows that allocate an additional number of candidate slots up to the maximum number, and optionally, the size of the "time domain resource allocation" field can be increased to be larger than 4 bits to indicate the additional rows. Further, for type 1 configured grants, the value of timeDomainOffset can be increased. The slot offset (K0) can be determined from an existing row or an additional row of the look-up table based on the "time domain resource allocation".

Table 9

Table 10

Table 11

[0105] Similarly, on the uplink, DCI format 0_0 or format 0_1 carries a 4-bit field named "time domain resource allocation". The bit values of "time domain resource allocation" are mapped to a look-up table (an RRC configured look-up table called "pusch_TimeDomainAllocationList"). To indicate a larger maximum number for a subcarrier spacing spanning 120 KHz, the look-up table can be modified to include additional rows that allocate additional numbers of candidate slots up to the maximum, and optionally, the size of the "time domain resource allocation" field can be increased beyond 4 bits to indicate the additional rows. Further, for type 1 configured grants, the value of timeDomainOffset can be increased. The slot offset (K2) can be determined from the existing or additional rows of the look-up table based on the "time domain resource allocation".

[0106] In one example, the second option uses a minimum slot offset of 1112, similar to FIG. 7. The candidate slot 1114 is delayed from the DCI slot by the minimum slot offset 1112. The candidate slots 1114 form a set of consecutive slots, and the size of the set can be increased based on a subcarrier spacing greater than 120 KHz as explained in the first option, but does not have to be increased.

[0107] The minimum slot offset 1112 can also be a function of the subcarrier spacing. Generally, the minimum slot offset 1112 is the minimum number of slots following the DCI in which data reception or data transmission is not scheduled. In the case of data reception, the minimum slot offset 1112 (K0min) can be defined as the ceiling or floor integer equal to the ratio of (i) the number of OFDM symbols (N0) required for UE processing from the end of DCI reception to the earliest possible start of data reception, and (ii) the number of symbols in a slot. For example, the number of OFDM symbols (N0) is 72 for a 960 KHz subcarrier spacing. In the case of slot configuration 0, the number of symbols in a slot is 14. Thus, in this figure, the minimum slot offset (K0min) is 5 slots. In the case of data transmission, the minimum slot offset 1112 (K2min) can be defined as the ceiling or floor integer equal to the ratio of (i) the number of OFDM symbols (N2) required for UE processing from the end of the DCI to the earliest possible start of data transmission, and (ii) the number of symbols in a slot. For example, the number of OFDM symbols (N2) is 72 for a 960 KHz subcarrier spacing. In the case of slot configuration 0, the number of symbols in a slot is 14. Thus, in this figure, the minimum slot offset (K2min) is 5 slots. The minimum slot offset 1112 (K0min or K2min) can be signaled in the RRC message, indicated by the DCI (e.g., as another field of one or more bits), or defined in the UE configuration (e.g., if this definition is incorporated in the 3GPP technical specification). For example, the value of K0min is configured in the pdsch-TimeDomainAllocationList using pdsch-ConfigCommon or pudschConfig. For example, the value of K2min is configured in the pusch-TimeDomainAllocationList using pusch-ConfigCommon or puschConfig.

[0108] Therefore, the slot offset (K0 or K2) is based on the minimum slot offset and the base station signaled slot offset. For example, the slot offset (K0 or K2) is equal to.

[0109] In one example, a third option uses candidate slots 1116 that are non - contiguous but have a uniform distribution, similar to FIG. 8. The minimum slot offset may be used and may be the same as or different from the minimum offset 1112. The size of the set formed by the candidate slots 1116 can be increased based on the sub - carrier spacing being greater than 120 KHz as described in the first option, but does not have to be increased.

[0110] The uniform distribution skips every other slot (or some other distribution may be used), and as a result, the candidate slots 1116 are separated by only one intermediate non - candidate slot (e.g., a slot that may not be used for data reception or transmission). The uniformity can be defined by a slot_offset_multiplier that is used to multiply the base station signaled slot offset (e.g., a slot offset derived based on time - domain resource allocation), where the slot_offset_multiplier is a linear multiplier. For example, if the base station signaled slot offset is 8 slots, the slot_offset_slot_offset_multipler can be set to 2, and the multiplication results in a 16 - slot distribution, and thus, eight candidate slots 1116 are distributed over 16 slots that alternate between candidate and non - candidate slots.

[0111] Therefore, the slot offset (K0 or K2) is based on a minimum slot offset, a slot_offset_multiplier, and a base station signaled slot offset. For example, the slot offset (K0 or K2) is equal to. The slot_offset_multiplier is signaled in the RRC message, indicated by the DCI (e.g., as another field of one or more bits), can be defined in the UE configuration (e.g., this definition is incorporated in the 3GPP technical specification), or can be added to the start and length indicator (SLIV).

[0112] In one example, a fourth option uses candidate slot 1118 having a non-uniform distribution, similar to FIG. 9. The minimum slot offset may be used and may be the same as or different from the minimum offset 1112. The size of the set formed by the candidate slots 1118 may be increased based on the subcarrier spacing being greater than 120 KHz as described in the first option, but need not be increased.

[0113] The non-uniform distribution can be defined by the slot_offset_multiplier used to multiply the base station signaled slot offset (e.g., the slot offset derived based on the time domain resource allocation), where the slot_offset_multiplier is a non-linear multiplier that varies from one candidate slot to the next. For example, the slot_offset_multiplier can be defined using a pseudo-random function. In another example, a hash function can be used. In this figure, the slot position hash is generated by hashing at least the base station signaled slot offset.

[0114] Therefore, the slot offset (K0 or K2) is based on the minimum slot offset, the slot_offset_multiplier, and the base station signaled slot offset. For example, the slot offset (K0 or K2) can be equal in the case of a random multiplier or equal to the slot_offset_multiplier, which is signaled in the RRC message, indicated by the DCI (e.g., as another field of one or more bits), and can be defined in the UE configuration (e.g., this definition is incorporated in the 3GPP technical specification), or can be added to the start and length indicator (SLIV).

[0115] In FIG. 11, candidate slots are indicated by a hatched pattern and the minimum slot offset is indicated by a horizontal pattern. In different embodiments, only PDSCH processing capability 1 is required for subcarrier spacings greater than 120 KHz (e.g., referring back to Table 3, PDSCH processing capability 2 is already not considered beyond the mathematical mystery "μ" of 2 corresponding to a 60 KHz subcarrier spacing). In addition, the base station can dynamically configure and signal the slot offset (K0 or K2) to be specific to the UE and / or the subcarrier spacing used by the UE.

[0116] FIG. 12 is a diagram illustrating an example of an operation flow / algorithm structure 1200 for slot-based scheduling for data reception or data transmission according to some embodiments. The UE can implement the operation flow / algorithm structure 1200 to determine the scheduling of communication on a physical channel having a frequency greater than 52.6 GHz (e.g., data reception on the PDSCH or data transmission on the PUSCH), and the communication uses a subcarrier spacing greater than 120 KHz. The operation flow / algorithm structure 1200 can be executed or implemented by a UE such as UE104, 1700, etc., or its components, such as the processor 1704.

[0117] The operation flow / algorithm structure 1200 may include, at 1202, receiving downlink control information (DCI) on a physical channel from a base station and data communication, where the data communication is either downlink data reception or uplink data transmission, and the data communication uses a subcarrier spacing greater than 120 KHz. The physical channel has a frequency greater than 52.6 GHz, and the data communication uses a subcarrier spacing greater than 120 KHz. In some embodiments, the DCI has format 1_0, format 1_1, or format 1_2 for data reception, or format 0_0 or format 0_1 for data transmission. The DCI includes a slot offset indicator indicating a base station-signaled slot offset. The slot offset indicator may be, for example, a "time domain resource allocation".

[0118] The operation flow / algorithm structure 1200 may include, at 1204, determining a minimum slot offset based on a subcarrier spacing greater than 120 KHz. In some embodiments, the minimum slot offset is determined from the UE's RRC configuration, the DCI (e.g., from a field within the DCI), and the UE's predefined configuration.

[0119] The operation flow / algorithm structure 1200 may include, at 1206, determining a slot offset based on a minimum slot offset and a base station-signaled slot offset. In some embodiments, the slot offset (K0) is determined for data reception and / or the slot offset (K2) is determined for data transmission. In some embodiments, the slot offset (K0 or K2) corresponds to the delay of the base station-signaled slot offset by the minimum slot offset, as in the case of FIG. 11. In some additional or alternative embodiments, the slot offset (K0 or K2) is determined based on a linear or non-linear multiplier of the base station-signaled slot offset, as in FIG. 11. The linear or non-linear multiplier may be determined from the UE's RRC configuration, DCI (e.g., from a field in the DCI), a predefined configuration of the UE, or the SLIV.

[0120] The operation flow / algorithm structure 1200 may include, at 1208, when the data communication is downlink data reception, receiving downlink data on a physical channel based on a slot offset, or when the data communication is uplink data transmission, transmitting uplink data on a physical channel based on a slot offset. Data reception is performed when the DCI has format 1_0, format 1_1, or format 1_2. Data transmission is performed when the DCI has format 0_0 or format 0_1. In some embodiments, the UE determines a scheduled downlink slot for data reception or a scheduled uplink slot for data transmission, if applicable, and the scheduled slot is delayed from the DCI slot by only a slot offset (K0 for a scheduled downlink slot or K2 for a scheduled uplink slot). If applicable, the UE receives and processes data from the scheduled downlink slot or processes and transmits data in the scheduled uplink slot.

[0121] FIGS. 13 to 15 show another method for mitigating the impact of a subcarrier spacing greater than 120 KHz on HARQ processing. HARQ feedback transmission may be scheduled according to the embodiments described in FIGS. 5 to 10, but it is not necessary to be scheduled. The data for which HARQ feedback should be generated may be scheduled according to the embodiments described in FIGS. 11 to 12, but it is not necessary to be scheduled.

[0122] FIG. 13 shows an example of HARQ processing according to some embodiments. DCI 1310 is received by the UE and schedules data reception by the UE (shown as PDSCH 1320) and HARQ feedback transmission (shown as HARQ 1330 on PUCCH). The downlink data slot is delayed by a slot offset (K0) with respect to the DCI slot. The uplink HARQ slot is delayed by a slot offset (K1) with respect to the downlink data slot. These two slot offsets (K0 and K1) can be base station signaled slot offsets or can be set according to the embodiments described in FIGS. 5-12.

[0123] Within HARQ slot 1330, the UE determines the specific symbols (shown with a hatched pattern in FIG. 13) to use for transmission of a set of HARQ codebooks 1332. This determination uses the slot offset (K1) and the SLIV, where the slot offset (K1) indicates the uplink slot to be used and the SLIV indicates the start (e.g., the first symbol) and length (e.g., the number of symbols) within the uplink slot for HARQ transmission as defined in the PUCCH resource table. The PUCCH resource table can be predefined (e.g., Table 12 below is an example copied from 38.213 V16.2.0) or can be defined using an RRC message.

Table 12

[0124] When a subcarrier spacing greater than 120 KHz is used, the HARQ process can be performed on a group basis of slots rather than on an individual slot basis. In particular, a set of slots can be aggregated to function as a single HARQ group, and this set is referred to herein as a HARQ slot group. In other words, a HARQ slot group represents a set of two or more slots in which a set of HARQ codebooks can be transmitted.

[0125] In a simple example, the HARQ slot group is two slots long and is scheduled such that a single HARQ codebook is transmitted. (For example, using slot offset (K1), SLIV, and the PUCCH resource table) The above HARQ process can be applied at the group level or at the slot level within the HARQ slot group to determine the specific symbols to be used for HARQ codebook transmission. This type of process is further explained in the following figures.

[0126] FIG. 14 is a diagram showing an example of HARQ slot group-based processing according to some embodiments. The upper part of FIG. 14 shows the HARQ process for each Release 15 of the 3GPP technical specification. The central part of FIG. 14 shows the options for HARQ processing according to Release 16 of the 3GPP technical specification. The lower part of FIG. 14 shows the HARQ slot group-based processing.

[0127] According to Release 15 of the 3GPP technical specification, the HARQ slot 1410 can be defined as a slot containing 14 symbols 1412. According to Table 11 above, some of the symbols are used to encode the HARQ codebook. The UE is not expected to transmit two or more HARQ codebooks in the HARQ slot 1410.

[0128] Release 16 of the 3GPP technical specification enables the UE to transmit two or more HARQ codebooks within a slot. In particular, Release 16 enables the definition of two sub-slots within a slot (shown as sub-slot 1420A and sub-slot 1420B, each of which is 7 symbols long, and whose combination has the same 14-symbol length as HARQ slot 1410). Given two sub-slots, two HARQ codebooks with up to one sub-slot-based HARQ codebook are permitted. In other words, two slot-based HARQ codebooks (two HARQ codebooks within the slot formed by sub-slots 1420A and 1420B) can be constructed simultaneously in the UE to support HARQ codebooks with different priorities. Alternatively, one slot-based HARQ codebook with one sub-slot-based HARQ codebook (for example, one within the slot formed by sub-slots 1420A and 1420B sub-slots, and one within one of the two sub-slots 142AA or 1420B, two HARQ codebooks) can be constructed simultaneously in the UE to support HARQ codebooks with different priorities.

[0129] In comparison, HARQ slot group-based processing depends on HARQ slot group 1430. HARQ slot group 1430 includes a plurality of slots (FIG. 14 shows two minimum sizes, indicating that HARQ slot group 1430 is formed by slot 1432A and slot 1432B). The number of slots included in HARQ slot group 1430 may depend on the subcarrier spacing. Generally, the larger the subcarrier spacing, the larger the number of slots to help mitigate the impact of the increase in subcarrier spacing on HARQ processing time. For example, 2, 4, 8, and 16 slots can form HARQ slot group 1430 for subcarrier spacings of 240 KHz, 480 KHz, 960 KHz, and 1920 KHz, respectively. Additionally or alternatively, a range of slots (e.g., the minimum and maximum number of slots) may be used, where this range depends on the subcarrier spacing.

[0130] HARQ slot group 1430 has a duration that depends on the number of slots and the subcarrier spacing (e.g., the symbol time duration) included therein. For HARQ slot 1410 (used for subcarrier spacings of 120 KHz or less), the duration may be the same, smaller, or longer. For example, FIG. 11 shows a 120 KHz subcarrier spacing for Releases 15 and 16 and a 240 KHz subcarrier spacing for the HARQ slot group approach. Symbols 1434 within slots 1432a and 1432B have half the duration of symbol 1412. However, since HARQ slot group 1430 includes twice the number of symbols 1434 as HARQ slot 1410, the durations of HARQ slot 1410 and HARQ slot group 1430 are the same. Since the durations are the same, the impact of the increase in subcarrier spacing on HARQ processing time can be reduced.

[0131] The HARQ slot group 1430 can support a set of HARQ codebooks. One HARQ codebook can be encoded within the HARQ slot group 1430. However, the size of the set can be two or more to support different priorities in the UE. Up to one HARQ codebook can be encoded within the slots of the HARQ slot group. Or, similar to Release 16, if sub-slots of the slots of the HARQ slot group are given, two or more HARQ codebooks can be encoded. Further, the HARQ slot subgroup can be defined within the HARQ slot group 1430. Each subgroup can include one or more slots, one or more sub-slots within a slot, or one or more sub-slots within multiple slots. In this case, the HARQ codebook within the HARQ slot subgroup can be used.

[0132] In the HARQ slot group-based approach, the scheduling of HARQ feedback transmission (e.g., slot offset (K1) and / or number of OFDM symbols (N1)) can be at the HARQ slot group level instead of the slot level (e.g., instead of indexing candidate slots, the slot offset (K1) indexes candidate slot groups, and similarly, instead of indexing candidate symbols in each slot for encoding, the OFDM symbol (N1) indexes the same symbol positions across different slots of the HARQ slot group). Also, the UE can be configured to use a HARQ slot group of a specific size. Further, an update to the PUCCH resource configuration (e.g., PUCCH resource table) may be required to identify specific slots and symbols within the (slots of the) HARQ slot group for use in encoding the set of HARQ codebooks. An update to the codebook generation may also be required. Next, these and other aspects of HARQ processing are described herein.

[0133] The UE can be configured through RRC messages. For example, the UE can signal to the base station its ability to support subcarrier spacings greater than 120 KHz. Next, the base station can configure the UE, for example, using a HARQ slot group configuration that indicates the number of slots in the HARQ slot group. The slot group configuration can also indicate the number of HARQ codebooks supported by the HARQ slot group (e.g., one HARQ codebook to be encoded within the HARQ slot group, up to one HARQ codebook to be encoded within the slots of the HARQ slot group, up to two HARQ codebooks to be encoded in a given subslot of the slots of the HARQ slot group, or the HARQ codebooks to be encoded within a HARQ slot subgroup of the HARQ slot group). The HARQ slot configuration can be signaled in "dl-DatatoUL-ACK-SLOT-Group" similar to "dl-DatatoUL-ACK" in the PUCCH configuration. However, other options for configuring the UE are also possible. For example, the HARQ slot group configuration can be changed dynamically over time by being indicated within DCI. Additionally or alternatively, the HARQ slot group configuration can be set in a predefined configuration of the UE (e.g., as defined in 3GPP technical specifications).

[0134] Next, the base station transmits DCI (e.g., DCI format 1_0, format 1_1, or format 1_2) to the UE. The DCI schedules HARQ feedback transmission (for each slot offset K1) and indicates specific symbols in the HARQ slot group for encoding an applicable set of HARQ codebooks. In one example, the DCI does not change with respect to the existing structure. Instead, the PUCCH resource table (see, e.g., Table 11 above) is modified (e.g., extended) to include additional indexed rows or a new PUCCH resource table is defined. In either case, the PUCCH resource table includes "first symbol" and "number of symbols" entries to accommodate the additional number of symbols within the HARQ slot group. In another example, the structure of the DCI is changed, but the PUCCH resource table can remain the same (e.g., Table 11 can be used without modification). In this case, the DCI can include one or more bit fields, where the bit values indicate slots, sub-slots, and / or sub-groups within the HARQ slot group. The PUCCH resource table is searched to determine the first symbol and number of symbols applicable to the indicated slots, sub-slots, and / or sub-groups.

[0135] The UE receives the DCI and determines the number of HARQ codebooks to generate, the HARQ slot group to use, and the symbols within the HARQ slot group for encoding the HARQ codebook(s). The UE then processes the downlink data and generates and transmits the HARQ codebook(s) as HARQ feedback using the symbols.

[0136] Different options are possible for generating the HARQ codebook. In a first example, a separate ACK / NAK is assigned to each transport block or each codeblock group (e.g., from the corresponding data reception for which the HARQ codebook is generated). When there are multiple transport blocks or codeblock groups, multiple ACK / NAKs are generated. These ACK / NAKs are multiplexed into a single HARQ codebook. If applicable, a separate HARQ codebook is created for each HARQ slot group, HARQ subgroup, HARQ slot, or HARQ subslot. As a result, a single HARQ codebook is generated for multiple transport blocks or codeblock groups, thereby reducing the total number of HARQ codebooks for using a HARQ codebook per transport block or codeblock group. However, since multiple ACK / NAKs are multiplexed, the HARQ codebook size can be relatively large.

[0137] In a second example, a single ACK / NAK is assigned to multiple transport blocks or code block groups, resulting in a single HARQ codebook. Here, multiple ACK / NAKs are generated and bundled together to result in a single ACK / NAK. The bundling can include the use of an AND operation, where ACK is represented by "1" and NAK is represented by "0". For example, if four ACKs and one NAK are generated, the bundling results in a NAK that is encoded in the HARQ codebook. The bundling results in an ACK that is encoded in the HARQ codebook only if all five are ACKs. This bundling can be performed across multiple sub-slots within a slot of a HARQ slot group, multiple slots of a HARQ group, or multiple HARQ sub-groups of a HARQ slot group, and / or across multiple HARQ groups. Since a single HARQ codebook is used instead of multiple codebooks, the HARQ transmission overhead is reduced. However, the HARQ codebook may not need to be as granular up to the transport block level or code block group level and may require a larger transmission overhead in the case of a NAK.

[0138] As described above, an increase in the sub-carrier spacing results in an increase in the OFDM symbol (N1). Next, the increase in the OFDM symbol (N1) can result in multiple symbols being transmitted before the PDSCH is processed. For example, at a sub-carrier spacing of 960 KHz, up to 160 symbols or 11 slots can be transmitted before processing. Additional embodiments can be used to help mitigate the impact of the increase in sub-carrier spacing on HARQ processing, and these embodiments relate to the underlying HARQ process. These embodiments can be used in conjunction with, or independently of, the above-described HARQ scheduling and HARQ slot group embodiments.

[0139] In some embodiments, the maximum number of HARQ processes is increased. For example, in Release 15 and Release 16 of the 3GPP technical specifications, the maximum number is set to 16. Due to the increase in the number of received symbols, based on the subcarrier spacing being greater than 120 KHz, the maximum number can be increased to be greater than 16. The additional HARQ processes can be synchronous or asynchronous. To track each HARQ process, the UE and the base station need to know the HARQ process number for each HARQ transmission / HARQ reception. To do so, the DCI includes a "HARQ processor number" field. This field is 4 bits long and can accommodate an increase in the maximum number of HARQ processes (e.g., a number exceeding 16).

[0140] In some embodiments, the maximum number of HARQ processes is not increased. Instead, the number of repetitions to prevent the need for HARQ latency, the target BLER for link adaptation, and / or single transmission (without HARQ) or ARQ only for a subset of HAR processes may be permitted.

[0141] For example, on the downlink, the number of repetitions is defined in DL_REPETITION_NUMBER that provides the number of transmissions to the UE repeated within a bundle. On the uplink, the number of repetitions is defined in UL_REPETITION_NUMBER that provides the number of transmission repetitions from the UE within a bundle. In either case, the number of repetitions can be increased based on the subcarrier spacing. For example, the number of repetitions can be an implicit multiplier of the subcarrier spacing. By increasing the number of repetitions, a smaller number of HARQ processes may be required. The number of repetitions can be indicated via the DCI.

[0142] BLER refers to the block error code that depends on the number of transport blocks or code block groups and the NAKs generated for them. The BLER can be changed (e.g., from 10 percent to 15 percent or any other value). When a change is given, different modulation and coding schemes (MCS) can be used (e.g., from QAM modulation to QPSK modulation), where the modulation is adapted to meet the target BLER. Each target BLER can be associated with one or more MCSs in the MCS table. The target BLER and the associated MCS can be based on the subcarrier spacing. For example, assuming an increase in the number of OFDM symbols (N1), the target BLER can be increased along with the increase in subcarrier spacing to allow for a higher BLER and lower retransmissions. The BLER and / or the MCS table can be defined in the RRC configuration of the UE.

[0143] Furthermore, the transmission of data to the UE on the downlink can be permitted without HARQ transmissions coming back from the UE. This technique represents an exception to the HARQ process, and HARQ feedback may not be generated for some of the downlink slots or symbols within them. Additionally or alternatively, only ARQ (instead of HARQ) may be used for a subset of the HARQ processes. Non-HARQ transmissions or ARQ-only transmissions can be defined in the RRC configuration, the media access control (MAC) control element (CE), or the DCI.

[0144] Other embodiments can be used additionally or alternatively to help mitigate the impact of increased sub - carrier spacing on HARQ processing, and these embodiments relate to HARQ codebook design. In some embodiments, a type 1 (semi - static) codebook is used. The time window covered by this type of HARQ codebook can be increased by increasing the maximum number of slots covered by the HARQ codebook. This approach can increase the overhead. As described above, the overhead can be reduced by using HARQ slot groups or HARQ slot subgroups. Yet another approach to reduce the overhead is to generate and transmit HARQ feedback only for slots with valid symbols. The validity of the symbols can be defined in different ways. For example, when a valid base - station - UE beam pair exists, the resulting symbol is valid. In another example, the HARQ feedback is sent on the uplink. Thus, downlink - only slots cannot be used to transmit HARQ feedback, while uplink - only slots and flexible slots can be used. In this case, downlink - only slots are removed from HARQ processing, such as being candidate slots for HARQ feedback transmission. In some embodiments, a type 2 (dynamic) codebook is used. The time window covered by this type of HARQ codebook can be increased by increasing the maximum dynamic allocation (e.g., one or both of cDIA and tDAI). This maximum value can be increased from 2, and the increase can depend on the sub - carrier spacing (e.g., the larger the sub - carrier spacing, the larger the increase).

[0145] FIG. 15 is a diagram illustrating an example of an operation flow / algorithm structure 1500 for HARQ slot group-based processing according to some embodiments. A UE may implement the operation flow / algorithm structure 1500 to generate and transmit HARQ feedback on a physical channel having a frequency greater than 120 GHz, where the HARQ transmission and / or reception of data for which the HARQ feedback is generated uses a subcarrier spacing greater than 52.6 KHz. The operation flow / algorithm structure 1500 may be executed or implemented by a UE, such as UE104, 1700, etc., or a component thereof, such as a processor 1704.

[0146] The operation flow / algorithm structure 1500 may include, at 1502, receiving downlink control information (DCI) from a base station. In some embodiments, the DCI has format 1_0, format 1_1, or format 1_2. The DCI includes a slot offset indicator indicating a base station-signaled slot offset. The slot offset indicator may be, for example, a "time domain resource allocation". In some embodiments, the DCI also includes a slot indicator that can be used to identify a slot, sub-slot, or subgroup within the HARQ slot group.

[0147] The operation flow / algorithm structure 1500 may include, at 1504, determining physical uplink channel resources within a slot of a hybrid automatic repeat request (HARQ) slot group based on DCI, where the HARQ slot group includes a plurality of slots available for transmitting one or more HARQ codebooks on the physical uplink channel, the physical uplink channel has a frequency greater than 52.6 GHz, and transmission on the physical uplink channel uses a subcarrier spacing greater than 150 KHz. In some embodiments, the physical channel resources include a set of symbols within the HARQ slot group, and these symbols are used to encode a set of HARQ codebooks. "Time domain resource allocation" may be used to determine, based on the SLIV, from the PUCCH resource table, a first symbol and the number of symbols, a subgroup of the HARQ slot group, a slot within the HARQ slot group, or a subslot within or across slots of the HARQ slot group. In some embodiments, the slot indicator in the DCI is used to identify a specific slot, subslot, or subgroup within the HARQ slot group, and the PUCCH resource table may be used simply to identify the first symbol and the number of symbols. The received data (e.g., transport block or codeblock group) for which HARQ feedback is scheduled is processed. The UE can use a type 1 or type 2 codebook together with a bundling or multiplexing technique to encode the ACK / NAK corresponding to the data.

[0148] The operation flow / algorithm structure 1500 may include, at 1506, transmitting one or more HARQ codebooks within the physical uplink channel resources on the physical uplink channel. In some embodiments, the determined symbols within the HARQ slot group encode a set of HARQ codebooks (e.g., using OFDM multiplexing).

[0149] In some embodiments, the operation flow / algorithm structure 1500 may include an additional set of operations that can be used with the above operations. These additional sets can be used independently of each other or in relation to each other. When used in combination, the additional sets can be executed sequentially or in parallel. FIG. 15 shows that the additional sets are part of the operation flow / algorithm structure 1500, but each of these sets can be executed in an independent operation flow / algorithm structure.

[0150] In one example of the additional set, the operation flow / algorithm structure 1500 may include, at 1510, generating one or more HARQ codebooks based on the number of HARQ processes. In some embodiments, based on the subcarrier spacing being greater than 120 KHz, the number of HARQ processes is increased to be more than 16 to enable the processing of additional PDSCH symbols, resulting in additional ACK / NAKs that can be fed back in one or more HARQ codebooks.

[0151] In one example of the additional set, the operation flow / algorithm structure 1500 may include, at 1520, determining the number of repetitions based on DCI. In some embodiments, the number of repetitions is increased with an increase in subcarrier spacing, resulting in a smaller amount of HARQ information to be fed back. The operation flow / algorithm structure 1500 may also include, at 1522, generating one or more HARQ codebooks based on the number of repetitions. In some embodiments, the increase in repetitions results in a decrease in the amount of HARQ information encoded in one or more HARQ codebooks.

[0152] In one example of the additional set, the operation flow / algorithm structure 1500 may include, at 1530, determining a block error rate (BLER) for link adaptation based on the radio resource control (RRC) configuration of the UE, where the BLER is related to a modulation and coding scheme (MCS) table defined based on the subcarrier spacing being greater than 120 KHz. In some embodiments, as the subcarrier spacing increases, the target BLER can be increased in order to reduce the number of required retransmissions and the overall hybrid automatic repeat request (HARQ) processing. The operation flow / algorithm structure 1500 may also include, at 1532, decoding a set of transport blocks or a set of code block groups based on the BLER. In some embodiments, an error correction code (ECC) algorithm is applied to decode a set of transport blocks or code block groups and derive the actual BLER. Further, the operation flow / algorithm structure 1500 may include, at 1534, generating one or more HARQ codebooks based on the decoding. In some embodiments, if the actual BLER is better (e.g., smaller) than the target BLER, the amount of HARQ information that needs to be fed back is reduced, and as a result, the amount of HARQ information encoded in one or more HARQ codebooks is decreased.

[0153] Embodiments are described in FIGS. 13-15 in relation to HARQ processing, slot offset (K1), and number of OFDM symbols (N1), but these embodiments are not so limited. Instead, embodiments are equally applicable to downlink data processing and slot offset (K0). Embodiments are also equally applicable to uplink data processing, slot offset (K2), and number of OFDM symbols (N2). For example, a super slot can be defined for downlink data or uplink data. A super slot is a data slot group that includes a plurality of slots. Instead of indexing each slot in the super slot, the slot offset (K0 or K2) can index the super slot. In other words, in the embodiments of FIGS. 13-15, the HARQ slot group can be replaced with a super slot, and the HARQ processing can be replaced with applicable downlink or uplink data processing. Further, some embodiments described in relation to FIGS. 13-15 include DCI format 1_0, format 1_1, or format 1_2, but these formats are provided for illustrative purposes, and embodiments can be equally applicable to other DCI formats including DC format 1_x and the like.

[0154] FIG. 16 shows a receiving component 1600 of UE 104 according to some embodiments. The receiving component 1600 may include an antenna panel 1604 that includes some antenna elements. Panel 1604 is shown with four antenna elements, but other embodiments may include other numbers.

[0155] Antenna panel 1604 may be coupled to an analog beamforming (BF) component that includes a number of phase shifters 1608(1) to 1608(4). Phase shifters 1608(1) to 1608(4) may be coupled to a radio frequency (RF) chain 1612. The RF chain 1612 may amplify a received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to a baseband processor for further processing.

[0156] In various embodiments, control circuitry that may be present within the baseband processor may provide BF weights (e.g., W1 to W4) that may represent phase shift values to phase shifters 1608(1) to 1608(4) to provide a receive beam at antenna panel 1604. These BF weights may be determined based on channel-based beamforming.

[0157] FIG. 17 shows a UE 1700 according to some embodiments. The UE 1700 is similar to the UE 174 of FIG. 1 and may be substantially interchangeable.

[0158] Similar to what was described above for UE 174, the UE 1700 may be any mobile or non-mobile computing device such as a cellular phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter or actuator, etc.), video surveillance / monitoring device (e.g., camera or video camera, etc.), wearable device, relaxed-IoT device, etc. In some embodiments, the UE may be a reduced-capacity UE or an NR-Light UE.

[0159] UE 1700 may include a processor 1704, an RF interface circuit 1708, a memory / storage 1712, a user interface 1716, sensors 1720, a driver circuit 1722, a power management integrated circuit (PMIC) 1724, and a battery 1728. The components of UE 1700 may be implemented as an integrated circuit (IC), a part thereof, an individual electronic device or other module, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 17 is intended to show a high-level diagram of some of the components of UE 1700. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the components shown may occur in other embodiments.

[0160] The components of UE 1700 may be coupled to various other components via one or more interconnects 1732, and the one or more interconnects may represent any type of interface, input / output section, (local, system, or expansion) bus, transmission line, trace, optical connection, etc. that can cause various circuit components (on common or different chips or chip sets) to interact with each other.

[0161] The processor 1704 may include, for example, processor circuits such as a baseband processor circuit (BB) 1704A, a central processing unit circuit (CPU) 1704B, and a graphics processing unit circuit (GPU) 1704C. The processor 1704 may include any type of circuit or processor circuit that executes computer-executable instructions such as program code, software modules, or functional processes from the memory / storage 1712, or operates in other ways to cause UE 1700 to perform the operations described herein.

[0162] In some embodiments, the baseband processor circuit 1704A may access the communication protocol stack 1736 in the memory / storage 1712 to communicate via a 3GPP-compliant network. Generally, the baseband processor circuit 1704A may access the communication protocol stack to perform user plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer, and may also perform control plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access "NAS" layer. In some embodiments, the operation of the PHY layer may additionally or alternatively be performed by components of the RF interface circuit 1708.

[0163] The baseband processor circuit 1704A may generate or process a baseband signal or waveform that conveys information within a 3GPP-compliant network. In some embodiments, the waveform for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0164] The baseband processor circuit 1704A may also access the group information 1724 from the memory / storage 1712 to determine a search space group in which some repetitions of the PDCCH may be transmitted.

[0165] Memory / storage 1712 may include any type of volatile or non-volatile memory that may be distributed throughout UE 1700. In some embodiments, some of memory / storage 1712 may be located in the processor 1704 itself (e.g., L1 and L2 caches), while other memory / storage 1712 is external to the processor 1704 but accessible via a memory interface. Memory / storage 1712 may include, without limitation, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state memory, or any other suitable volatile or non-volatile memory device technology, etc.

[0166] RF interface circuit 1708 may include a transceiver circuit and a radio frequency front-end module (RFEM) that enable UE 1700 to communicate with other devices via a wireless access network. RF interface circuit 1708 may include various elements disposed in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0167] In the receive path, the RFEM may receive a radiated signal from the air interface via antenna 1724 and filter and amplify the signal (using a low noise amplifier). The signal may be provided to the receiver of the transceiver that down-converts the RF signal to a baseband signal provided to the baseband processor of processor 1704.

[0168] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal by a power amplifier before the signal is radiated across the air interface via antenna 1724.

[0169] In various embodiments, the RF interface circuit 1708 may be configured to transmit / receive signals in a manner compliant with NR access technology.

[0170] Antenna 1724 may include several antenna elements that convert an electrical signal into a radio wave to propagate in air and convert each received radio wave into an electrical signal, respectively. The antenna elements may be arranged on one or more antenna panels. Antenna 1724 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multi-input multi-output communication. Antenna 1724 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, and the like. Antenna 1724 may have one or more panels designed for a specific frequency band including bands in FR1 or FR2.

[0171] The user interface circuit 1716 includes various input / output (I / O) devices designed to enable user interaction with the UE 1700. The user interface 1716 includes an input device circuit and an output device circuit. The input device circuit includes any physical or virtual means for receiving inputs, including, among other things, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information such as sensor readings, actuator position(s), or other similar information, or for communicating information in other ways. The output device circuit includes, among other things, any number or combination of audio displays or visual displays, including one or more simple visual outputs / indicators (e.g., binary state indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as a display device or a touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), and the outputs such as characters, graphics, multimedia objects, etc. may be generated or created from the operation of the UE 1700.

[0172] Sensor 1720 may include a device, module, or subsystem that is intended to detect an event or change in the environment and transmit information (sensor data) regarding the detected event to some other device, module, subsystem, etc. Examples of such sensors include, in particular, inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including three-axis accelerometers, three-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or pinhole diaphragms without lenses); light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones, or other similar voice capture devices, and the like.

[0173] Driver circuit 1722 may include software and hardware elements that operate to control a particular device incorporated in, attached to, or otherwise communicatively coupled to UE 1700. Driver circuit 1722 may include individual drivers that enable interaction with or control of various input / output (I / O) devices that other components may be present within or connected to UE 1700. For example, driver circuit 1722 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface, a sensor driver for obtaining sensor readings of sensor circuit 1720 and controlling and enabling access to sensor circuit 1720, a driver for obtaining the actuator position of electromechanical components or for controlling and enabling access to electromechanical components, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0174] The PMIC 1724 can manage the power supplied to various components of the UE 1700. In particular, with respect to the processor 1704, the PMIC 1724 can control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0175] In some embodiments, the PMIC 1724 can control or otherwise be part of various power saving mechanisms of the UE 1700. For example, if the platform UE is in the RRC connected state and is still connected to the RAN node because traffic reception is expected shortly, after a certain inactive period, the platform can enter a state known as discontinuous reception mode (DRX). During this state, the UE 1700 can power down at short intervals and thereby save power. If there is no data traffic activity over a long period, the UE 1700 may transition to the RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback and handover. The UE 1700 enters a very low power state, performs paging, where again it wakes up periodically to listen to the network and then powers down again. The UE 1700 cannot receive data in this state and must transition to the RRC connected state to receive data. In a further power saving mode, the device may be allowed to be unavailable from the network for a period longer than the paging interval (ranging from seconds to hours). During this time, the device cannot reach the network at all and can be completely powered down. Although there will be a significant delay if there is data transmitted during this time, the delay is considered acceptable.

[0176] The battery 1728 may supply power to the UE 1700, but in some examples, the UE 1700 may be mounted and deployed in a fixed position and may have a power source coupled to the power grid. The battery 1728 may be a lithium-ion battery, an air zinc battery, an aluminum air battery, a metal air battery such as a lithium air battery, etc. In some implementation forms such as vehicle-based applications, the battery 1728 may be a typical lead-acid battery for automobiles.

[0177] FIG. 18 shows a gNB 1800 according to some embodiments. The gNB node 1800 is similar to the gNB 108 and may be substantially interchangeable. A base station such as the base station 182 may have the same or similar components as the gNB 1800.

[0178] The gNB 1800 may include a processor 1804, an RF interface circuit 1808, a core network (CN) interface circuit 1812, and a memory / storage circuit 1816.

[0179] The components of the gNB 1800 may be coupled to various other components via one or more interconnects 1828.

[0180] The processor 1804, the RF interface circuit 1808, the memory / storage circuit 1816 (including the communication protocol stack 1810), the antenna 1824, and the interconnect 1828 may be similar to the elements of the same name illustrated and described with respect to FIG. 10.

[0181] The CN interface circuit 1812 may provide connectivity to a core network, such as a 5th Generation Core Network (5GC), using a 5GC compliant network interface protocol such as the Carrier Ethernet protocol or some other suitable protocol. The network connectivity may be provided to / from the gNB 1800 via an optical fiber or a wireless backhaul. The CN interface circuit 1812 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1812 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0182] It should be well understood that the use of personally identifiable information should comply with privacy policies and practices that generally recognize meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of the permitted use should be clearly indicated to the user.

[0183] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the following exemplary sections. For example, the baseband circuit described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples described below. As another example, a circuit associated with a UE, base station, network element, etc., as described above in connection with one or more of the foregoing figures, may be configured to operate in accordance with one or more of the examples described below in the example section. Examples

[0184] The following section presents further exemplary embodiments.

[0185] Example 1 includes a method. The method is implemented by a user equipment (UE), and includes receiving, by the UE from a base station, downlink control information (DCI) indicating a slot offset signaled by the base station; determining a minimum slot offset based on a subcarrier spacing of a physical downlink channel greater than 120 KHz; determining a slot offset (K1) between data reception on the physical downlink channel and hybrid automatic repeat request (HARQ) transmission on the physical uplink channel based on the minimum slot offset and the slot offset signaled by the base station; and transmitting, on the physical uplink channel, HARQ feedback for the data reception based on the slot offset (K1).

[0186] Example 2 includes the method of Example 1, wherein the physical downlink channel has a frequency greater than 52.6 gigahertz (GHz), and the DCI has at least one of format 1_0, format 1_1, format 1_2, or format 1_x.

[0187] Example 3 includes the method of any of the foregoing examples, wherein the minimum slot offset is determined from at least one of a radio resource control (RRC) configuration of the UE, the DCI, or a predefined configuration of the UE.

[0188] Example 4 includes the method of any of the foregoing examples, wherein the minimum slot offset is determined as a ceiling or floor integer equal to a ratio of (i) a number (N1) of OFDM symbols required for UE processing from the end of data reception to the earliest possible start of HARQ transmission, and (ii) a number of symbols in a slot.

[0189] Example 5 includes any of the methods of the foregoing examples, and determining the slot offset (K1) includes selecting the slot offset (K1) from a plurality of discontinuous candidate slots based on a minimum slot offset and a base station-signaled slot offset.

[0190] Example 6 includes any of the methods of Example 5, and further includes determining a slot offset multiplier from at least one of a UE's radio resource control (RRC) configuration, DCI, or a UE's predefined configuration, and selecting the slot offset (K1) from a plurality of discontinuous candidate slots further based on the slot offset multiplier.

[0191] Example 7 includes any of the methods of Example 6, and further includes selecting the slot offset (K1) based on the sum of (i) a minimum slot offset and (ii) a value obtained by multiplying a base station-signaled slot offset by a slot offset multiplier.

[0192] Example 8 includes any of the methods of Example 5, and further includes generating a slot position hash by at least hashing a base station-signaled slot offset, and selecting the slot offset (K1) based on the slot position hash.

[0193] Example 9 includes the method of Example 8, and further includes selecting the slot offset (K1) based on the sum of (i) a minimum slot offset and (ii) a slot position hash.

[0194] Example 10 includes any of the methods of the foregoing examples, and further includes determining a second slot offset (K0) based on a subcarrier spacing being greater than 120 KHz, where the second slot offset (K0) is between DCI reception and data reception, and transmitting HARQ feedback is further based on the second slot offset.

[0195] Example 11 includes a method. The method is implemented by a user equipment (UE) and is for data reception on a physical downlink channel. The method includes signaling, by the UE, to a base station the UE's capabilities for data reception that uses a subcarrier spacing greater than 120 KHz; receiving, from the base station, downlink control information (DCI) including a slot offset indicator; determining, based on the slot offset indicator, a slot offset (K1) between the data reception and hybrid automatic repeat request (HARQ) transmission on a physical uplink channel, where the slot offset (K1) is greater than a minimum number of slots based on a subcarrier spacing greater than 120 KHz; and transmitting, on the uplink physical channel, HARQ feedback for the data reception based on the slot offset (K1).

[0196] Example 12 includes the method of any of the preceding examples, where the physical downlink channel has a frequency greater than 52.6 GHz, the minimum number is 8 slots, the DCI has format 1_0, and includes a physical downlink shared channel (PDSCH)-HARQ_feedback timing indicator field having a bit size that is at least 4 bits based on a subcarrier spacing greater than 120 KHz.

[0197] Example 13 includes the method of any of the preceding examples, where the minimum number is 15 slots, the DCI has format 1_1 or 1_2, and includes a physical downlink shared channel (PDSCH)-HARQ_feedback timing indicator field having a bit size that is at least 5 bits based on a subcarrier spacing greater than 120 KHz.

[0198] Example 14 includes any of the methods of the foregoing examples, the DCI has format 1_1 or 1_2, the slot offset (K1) has a value greater than 15 slots, and the value is defined in the resource control (RRC) configuration field.

[0199] Example 15 includes any of the methods of the foregoing examples, and is a second slot offset (K0) based on the subcarrier spacing being greater than 120 KHz, the second slot offset (K0) further includes determining the second slot offset (K0) that is between DCI reception and data reception, and transmitting HARQ feedback is further based on the second slot offset.

[0200] Example 16 includes a method. The method is implemented by a UE and includes receiving, from a base station, downlink control information (DCI) on a physical channel, and data communication, where the data communication is downlink data reception or uplink data transmission, and the data communication uses a subcarrier spacing greater than 120 KHz, receiving DCI indicating a base station-signaled slot offset between the DCI reception and the data communication, determining a minimum slot offset based on a subcarrier spacing greater than 120 KHz, determining a slot offset based on the minimum slot offset and the base station-signaled slot offset, and when the data communication is downlink data reception, receiving downlink data on the physical channel based on the slot offset, or when the data communication is uplink data transmission, transmitting uplink data on the physical channel based on the slot offset, and performing one of them.

[0201] Example 17 includes the method of any of the foregoing examples, the physical channel has a frequency greater than 52.6 GHz, and the minimum slot offset is determined as the ceiling or floor integer equal to the ratio of (i) the number of OFDM symbols (N2) required for UE processing from the end of DCI reception to the earliest possible start of uplink data transmission, and (ii) the number of symbols in a slot.

[0202] Example 18 includes the method of any of the foregoing examples, and the slot offset indicates a discontinuous slot between DCI reception and data communication.

[0203] Example 19 includes the method of Example 18, and further includes determining a slot offset multiplier from at least one of the UE's radio resource control (RRC) configuration, DCI, or start and length indicator (SLIV) process. The discontinuous slot is indicated based on the slot offset multiplier, and the slot offset is determined based on the sum of (i) the minimum slot offset and (ii) the value obtained by multiplying the base station-signaled slot offset by the slot offset multiplier.

[0204] Example 20 includes the method of any of the foregoing examples, and the minimum slot offset is determined from the UE's radio resource control (RRC) configuration, DCI, or a predetermined configuration of the UE's radio resource control (RRC), DCI, or UE.

[0205] Example 21 includes a UE including means for performing one or more elements of the method described or related to any of Examples 1 to 20.

[0206] Example 22 includes one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the UE, cause the UE to perform one or more elements of the method described in any of Examples 1 to 20 or a method related thereto, or any other method or process described herein.

[0207] Example 23 includes a UE that includes logic, modules, or circuitry for performing one or more elements of a method described or related to any of Examples 1 to 20.

[0208] Example 24 includes a UE that includes one or more processors and one or more computer-readable media that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described or related to any of Examples 1 to 20.

[0209] Example 25 includes a system that includes means for performing one or more elements of a method described or related to any of Examples 1 to 20.

[0210] Example 26 includes one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of a system, cause the system to perform one or more elements of a method described in any of Examples 1 to 20 or related thereto, or any other method or process described herein.

[0211] Example 27 includes a system that includes one or more processors and one or more computer-readable media that, when instructions are executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any of Examples 1 to 20.

[0212] Unless otherwise specified, any of the above examples can be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the exact forms disclosed. Modifications and variations are possible in light of the above teachings or can be acquired from practice of the various embodiments.

[0213] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art upon a complete understanding of the above disclosure. The following claims are intended to be construed to embrace all such variations and modifications.

Claims

1. A method performed by a device, comprising: determining a timing associated with hybrid automatic repeat request (HARQ) transmission on a physical uplink channel for data reception on a physical downlink channel; determining a first number of symbols associated with a time for processing the data reception, wherein the first number of symbols is determined based on a first subcarrier spacing of the physical downlink channel, the first subcarrier spacing is a coefficient times larger than a second subcarrier spacing, the second subcarrier spacing is 120 KHz and is associated with a second number of symbols, and the first number of symbols is the coefficient times larger than the second number of symbols; determining a physical uplink resource of the physical uplink channel for the HARQ transmission based on the timing and the first number of symbols; performing the HARQ transmission using the physical uplink resource.

2. The method according to claim 1, wherein the first subcarrier spacing is 4 times larger than the second subcarrier spacing, and the first number of symbols is 4 times larger than the second number of symbols.

3. The method according to claim 1, wherein the first subcarrier spacing is 8 times larger than the second subcarrier spacing, and the first number of symbols is 8 times larger than the second number of symbols.

4. The method according to claim 1, wherein the first subcarrier spacing has a linear value corresponding to that of the second subcarrier spacing, and the first number of symbols has a linear value corresponding to that of the second number of symbols.

5. The method according to claim 1, wherein the timing is determined based on downlink control information (DCI), and the DCI indicates a timing indicator based on the first subcarrier spacing greater than 120 KHz.

6. The method according to claim 5, wherein the timing indicator is indicated by the "m" bit of the DCI, and "m" is based on the first subcarrier spacing greater than 120 KHz.

7. The method according to claim 6, wherein "m" is 4 or more.

8. The method according to claim 5, wherein the timing indicator has a first value associated with a second value of the first subcarrier spacing, and the second value is greater than 120 KHz.

9. The method according to claim 5, wherein a value of the timing indicator is within a range, and the range is based on the first subcarrier spacing greater than 120 KHz.

10. The method according to claim 1, wherein the timing is determined based on downlink control information (DCI), the DCI indicates a timing indicator associated with a radio resource control (RRC) configuration, and the RRC configuration is based on the first subcarrier spacing greater than 120 KHz.

11. The method according to claim 10, wherein the RRC configuration indicates a number of slots between the data reception and the HARQ transmission, and the number of slots is based on the first subcarrier spacing greater than 120 KHz.

12. The method according to claim 11, wherein the number of slots is indicated by a parameter of the RRC configuration, and a magnitude of the parameter increases as a value of the first subcarrier spacing increases.

13. The method according to claim 1, wherein the time for processing the data reception for the first subcarrier spacing greater than 120 kHz is determined according to a processing capability of a user equipment.

14. A base station, comprising one or more processors, and one or more memories storing instructions, which when executed by the one or more processors configure the base station to send to a user equipment (UE) information indicating a timing associated with a hybrid automatic repeat request (HARQ) transmission on a physical uplink channel for data reception on a physical downlink channel, send data to the UE on the physical downlink channel, receive the HARQ transmission from the UE on a physical uplink resource of the physical uplink channel, wherein the HARQ transmission is received after the data is transmitted based on the timing and a first number of symbols, the first number of symbols is based on a first subcarrier spacing of the physical downlink channel, the first subcarrier spacing is a coefficient multiple larger than a second subcarrier spacing, the second subcarrier spacing is 120 KHz and is associated with a second number of symbols, and the first number of symbols is the coefficient multiple larger than the second number of symbols.

15. The physical downlink channel has a frequency higher than 52.6 gigahertz (GHz), and the information is included in downlink control information (DCI) having at least one of format 1_0, format 1_1, or format 1_2. The base station according to claim 14.

16. The information is included in downlink control information (DCDI) or a radio resource control (RRC) configuration. The base station according to claim 14.

17. The information indicates a slot offset between the data reception and the hybrid automatic repeat request (HARQ) transmission, and the slot offset is based on the first subcarrier spacing greater than 120 kHz. The base station according to claim 14.

18. An apparatus, having a processing circuit, wherein the processing circuit, determines a timing associated with a hybrid automatic repeat request (HARQ) transmission on a physical uplink channel for data reception on a physical downlink channel, determines a first number of symbols associated with a time for processing the data reception, where the first number of symbols is determined based on a first subcarrier spacing of the physical downlink channel, the first subcarrier spacing is a coefficient multiple larger than a second subcarrier spacing, the second subcarrier spacing is 120 kHz and is associated with a second number of symbols, and the first number of symbols is the coefficient multiple larger than the second number of symbols, determines a physical uplink resource of the physical uplink channel for the HARQ transmission based on the timing and the first number of symbols, and is configured to perform the HARQ transmission using the physical uplink resource. An apparatus.

19. The timing is determined from information transmitted by a base station, the information indicates a slot offset between the data reception and the HARQ transmission, and the slot offset is based on the first subcarrier spacing greater than 120 kHz. The apparatus according to claim 18.

20. The slot offset is determined based on downlink control information (DCI) or a radio resource control (RRC) configuration. The apparatus according to claim 19.

Images