Patent Description:
Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.

As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

<CIT> describes a user equipment (UE) including a processor and memory in electronic communication with the processor. Instructions stored in the memory are executable to determine a physical uplink control channel (PUCCH) resource and a PUCCH format. The instructions are also executable to transmit uplink control information (UCI) on the PUCCH resource using the PUCCH format. If the PUCCH format is a <NUM>-symbol short PUCCH, <NUM>-symbol PUCCH structure is used in each symbol, and if the UCI is up to <NUM> bits, the UCI is repeated in two symbols using repetition of a <NUM>-symbol PUCCH. If the PUCCH format is a <NUM>-symbol short PUCCH, and if the UCI is more than <NUM> bits, the UCI is jointly encoded, and the encoded UCI bits are distributed across two symbols.

<NPL>, discusses evaluation of reliability and latency aspects of PUCCH, and enhancements. On multiple HARQ sending within a slot, and separate HARQ procedure for URLLC, it is proposed: To avoid double reporting, Type-<NUM> HARQ codebook determination should be amended so as to restrict the set of PDCCH monitoring occasions to disjoint sets in the case where multiple HARQ codebooks are transmitted in the same slot. Type-<NUM> (and possibly Type-<NUM>) HARQ codebook determination should be applicable to sub-slots as an option, and K1 time offset should be interpreted as the number of sub-slot boundaries overlapped by the offset. For indicating the HARQ procedure per each DCI, the use of reserved value(s) should be considered in existing DCI fields, such as the PDSCH-to-HARQ_feedback (i.e., K1 index) field.

<CIT> describes a wireless communication system supporting different transmission time intervals (TTI). User equipment can report user equipment capability information indicating that the user equipment supports a second TTI length that is shorter than a first TTI length. A base station can transmit, to the user equipment, a second piece of TTI information indicating a second TTI having the second TTI length. The user equipment can receive a first downlink channel only through a first TTI having the first TTI length until the second piece of TTI information is received. When the second piece of TTI information is received, the first downlink channel can be received in the first TTI and/or a second downlink channel can be received in the second TTI.

<CIT>, being state of the art under Art. <NUM>(<NUM>) EPC, describes a method including the WTRU receiving a first Physical Downlink Shared Channel (PDSCH) associated with a first type of service or priority level in a first slot or mini slot and a second PDSCH associated with a second type of service or priority level in a second slot or mini-slot and determining a first HARQ codebook acknowledgment index (HCAI) based on a property of the first PDSCH or control information associated with the first PDSCH and a second HCAI based on a property of the second PDSCH or control information associated with the second PDSCH. The method includes generating for a subsequent slot or mini-slot, a first Physical Uplink Control Channel (PUCCH) including first HARQ-ACK information in accordance with the first HCAI and a second PUCCH including second HARQ-ACK information in accordance with the second HCAI and transmitting the first and second PUCCHs.

<CIT>, being state of the art under Art. <NUM>(<NUM>) EPC, describes a method for transmitting an uplink control channel in a wireless communication system. Disclosed in the present specification is a method for transmitting a physical uplink control channel by means of a UE, the method including: a step for generating a first HARQ-ACK codebook related to a first PUCCH; a step for generating a second HARQ-ACK codebook related to a second PUCCH; and a step for transmitting simultaneously the first PUCCH and the second PUCCH or one PUCCH among the first PUCCH and the second PUCCH to a base station in one slot on the basis of a plurality of indicators. According to the present embodiments, the sequence for transmitting a plurality of PUCCHs including respectively different HARQ-ACKs in one slot is clarified, and thus the targeted performance of a <NUM> wireless communication system intended to simultaneously provide various types of traffic (eURLLC, eMBB) can be achieved.

There is provided a user equipment, a base station device and a method performed by a user equipment as defined in the independent claims, respectively.

A user equipment (UE) is described. The UE includes a higher layer processor configured to determine a physical uplink control channel (PUCCH) resource in a slot or a subslot for HARQ-ACK feedback for ultra-reliable low-latency communication (URLLC) physical downlink shared channel (PDSCH) transmissions. The PUCCH resource is specified as an enhanced PUCCH format configured to satisfy URLLC PUCCH reliability requirements. The UE also includes transmitting circuitry configured to transmit the HARQ-ACK feedback for the URLLC PDSCH transmissions based on the determined PUCCH resource.

the enhanced PUCCH format for URLLC may be configured with a higher transmit power than a normal PUCCH format. A PUCCH signal for URLLC may be transmitted using transmit diversity with a multiple antenna transmission. More than one physical resource block (PRB) may be allocated for PUCCH format <NUM>, <NUM>, and <NUM>. The enhanced PUCCH format for URLLC may be configured with a lower maximum code rate compared with PUCCH resources for enhanced mobile broadband (eMBB).

In a case that a subslot structure is configured, a starting symbol index in a PUCCH configuration may be modified to represent a relative position within a subslot instead of a symbol index within a slot. In a case that a subslot structure is configured, a PUCCH resource may always start from the beginning of a subslot or may end at the last symbol of a subslot, and the starting symbol index in a PUCCH configuration is not present or ignored.

One or more PUCCH resource sets may be configured in each subslot of a configured subslot structure. The same PUCCH configurations on PUCCH formats and the PUCCH resource sets may be used in all subslots. In the case of different subslot durations, PUCCH formats and PUCCH resource sets may be determined based on subslots with a shorter duration.

One or more PUCCH resource sets may be configured in a subset of subslots of a configured subslot structure.

One or more PUCCH resource sets may be configured independently in multiple subsets of subslots in the subslot structure for PUCCH resource allocation. Different PUCCH configurations may be applied to different sets of subslots.

A base station (gNB) is also described. The gNB includes a higher layer processor configured to determine a PUCCH resource in a slot or a subslot for HARQ-ACK feedback from a UE for URLLC PDSCH transmissions. The PUCCH resource is specified as an enhanced PUCCH format configured to satisfy URLLC PUCCH reliability requirements. The gNB also includes receiving circuitry configured to receive the HARQ-ACK feedback from the UE for the URLLC PDSCH transmissions based on the determined PUCCH resource.

A method by a UE is also described. The method includes determining a PUCCH resource in a slot or a subslot for HARQ-ACK feedback for URLLC PDSCH transmissions. The PUCCH resource is specified as an enhanced PUCCH format configured to satisfy URLLC PUCCH reliability requirements. The method also includes transmitting the HARQ-ACK feedback for the URLLC PDSCH transmissions based on the determined PUCCH resource.

A method by a gNB is also described. The method includes determining a PUCCH resource in a slot or a subslot for HARQ-ACK feedback from a UE for URLLC PDSCH transmissions. The PUCCH resource is specified as an enhanced PUCCH format configured to satisfy URLLC PUCCH reliability requirements. The method also includes receiving the HARQ-ACK feedback from the UE for the URLLC PDSCH transmissions based on the determined PUCCH resource.

The 3rd Generation Partnership Project, also referred to as "3GPP," is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems and devices.

At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to mean the more general term "wireless communication device. " A UE may also be more generally referred to as a terminal device.

In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms "base station," "Node B," "eNB," "gNB" and/or "HeNB" may be used interchangeably herein to mean the more general term "base station. " Furthermore, the term "base station" may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device.

It should be noted that as used herein, a "cell" may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a "cell" may be defined as "combination of downlink and optionally uplink resources. " The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

"Configured cells" are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. "Configured cell(s)" may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. "Configured cell(s)" for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). "Activated cells" are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). "Deactivated cells" are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a "cell" may be described in terms of differing dimensions. For example, a "cell" may have temporal, spatial (e.g., geographical) and frequency characteristics.

Fifth generation (<NUM>) cellular communications (also referred to as "New Radio," "New Radio Access Technology" or "NR" by 3GPP) envisions the use of time/ frequency/space resources to allow for enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as massive machine type communication (MMTC) like services. A new radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as a base station device.

In <NUM> NR, different services can be supported with different quality of service (QoS) requirements (e.g., reliability and delay tolerance). For example, eMBB may be targeted for high data rate, and URLLC is for ultra-reliability and low latency. To support ultra-low latency, more than one HARQ-ACK feedback in a slot may be configured for URLLC services. A subslot structure in a slot for multiple PUCCH resources for URLLC PDSCH HARQ-ACK feedback is described herein. Additionally, aspects of URLLC PUCCH enhancement with different PUCCH formats, and details of PUCCH resource configuration with slot level and subslot level structures are described herein.

Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.

<FIG> is a block diagram illustrating one implementation of one or more gNBs <NUM> and one or more UEs <NUM> in which systems and methods for low-latency physical uplink control channel (PUCCH) enhancements and resource configuration may be implemented. The one or more UEs <NUM> communicate with one or more gNBs <NUM> using one or more antennas 122a-n. For example, a UE <NUM> transmits electromagnetic signals to the gNB <NUM> and receives electromagnetic signals from the gNB <NUM> using the one or more antennas 122a-n. The gNB <NUM> communicates with the UE <NUM> using one or more antennas 180a-n.

The UE <NUM> and the gNB <NUM> may use one or more channels <NUM>, <NUM> to communicate with each other. For example, a UE <NUM> may transmit information or data to the gNB <NUM> using one or more uplink channels <NUM>. Examples of uplink channels <NUM> include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels <NUM> (e.g., PUSCH) may be used for transmitting UL data (i.e., Transport Block(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).

Here, UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel from PUSCH) may be defined for transmitting the URLLC data. For the sake of simple description, the term "PUSCH" may mean any of (<NUM>) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (<NUM>) PUSCH or URLLC-PUSCH, (<NUM>) PUSCH and URLLC-PUSCH, or (<NUM>) only URLLC-PUSCH (e.g., not regular PUSCH).

Also, for example, uplink channels <NUM> may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR). The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)).

The CSI may include information indicating a channel quality of downlink. The SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. Namely, the SR may be used for requesting UL resources for transmitting UL data.

The one or more gNBs <NUM> may also transmit information or data to the one or more UEs <NUM> using one or more downlink channels <NUM>, for instance. Examples of downlink channels <NUM> include a PDCCH, a PDSCH, etc. Other kinds of channels may be used. The PDCCH may be used for transmitting Downlink Control Information (DCI).

Each of the one or more UEs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a UE operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in the UE <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the UE <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the gNB <NUM> using one or more antennas 122a-n. For example, the receiver <NUM> may receive and downconvert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the gNB <NUM> using one or more antennas 122a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The UE <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce decoded signals <NUM>, which may include a UE-decoded signal <NUM> (also referred to as a first UE-decoded signal <NUM>). For example, the first UE-decoded signal <NUM> may comprise received payload data, which may be stored in a data buffer <NUM>. Another signal included in the decoded signals <NUM> (also referred to as a second UE-decoded signal <NUM>) may comprise overhead data and/ or control data. For example, the second UE-decoded signal <NUM> may provide data that may be used by the UE operations module <NUM> to perform one or more operations.

In general, the UE operations module <NUM> may enable the UE <NUM> to communicate with the one or more gNBs <NUM>. The UE operations module <NUM> may include a UE scheduling module <NUM>.

The UE scheduling module <NUM> may perform PUCCH configuration and resource allocation as described herein. Due to low latency requirements of URLLC, two or more PUCCH resources may need to be configured in a single slot. The current time domain allocation for short PUCCH by configuring a single starting symbol in a slot will not be sufficient.

To configure more than one PUCCH instance in a slot, the UE <NUM> may be configured with a subslot structure for HARQ-ACK PUCCH resource allocation. Different subslot structures can be specified, including at least a <NUM>-symbol structure, a <NUM> and <NUM> symbol structure and/or a <NUM>-symbol structure.

The UE <NUM> may be configured with higher layer signaling for a subslot structure for PUCCH allocation. One or more PUCCH resources may be configured within a configured subslot.

In an approach, the UE <NUM> may be configured with a subset of subslots in a subslot structure, and PUCCH is configured only within the subslots in the subset of the subslot structure. In another approach, the UE <NUM> may be configured with multiple subsets of subslots in the subslot structure for PUCCH resource allocation.

The subsets of subslots in a subslot structure may be specified and the UE <NUM> may be configured by higher layer signaling on the subset of subslots in a subslot structure. The UE <NUM> may be configured with multiple subslot structures for PUCCH resource allocation.

A URLLC HARQ-ACK PUCCH resource in a slot or a subslot may be specified as an enhanced PUCCH format to provide desired reliability requirements. To provide high reliability and low latency, some enhancements to PUCCH formats are described. Transmit diversity (TxD) and enhanced power control for all PUCCH formats are described. More than one Physical Resource Block (PRB) allocation for PUCCH format <NUM>, <NUM>, and <NUM> may be implemented. More PRB allocation and lower maximum code rate by the maxCodeRate parameter for enhanced PUCCH formats for URLLC are also described herein.

In the case that a subslot structure is configured, for a PUCCH resource configuration in a subslot, the starting symbol index in a PUCCH configuration may be modified to represent the relative position within a subslot instead of the symbol index within a slot. The startingSymbolIndex field may be removed or ignored if a PUCCH always starts from the beginning of a subslot or ends at the last symbol of a subslot. Whether a PUCCH always starts from the beginning of a subslot or ends at the last symbol of a subslot may be specified in the standard or may be configured by higher layer signaling to a UE <NUM>.

One or more PUCCH resource sets may be configured in each subslot of a configured subslot structure. The same PUCCH configurations on the PUCCH formats and resources sets may be used in all subslots. In the case of different subslot durations, the PUCCH formats and resource sets may be determined based on the subslots with a shorter duration.

The UE <NUM> may be configured with a subset of subslots in a subslot structure. One or more PUCCH resource sets may be configured only within the subslots in the subset of the subslot structure.

The UE <NUM> may be configured with multiple subsets of subslots in the subslot structure for PUCCH resource allocation. The PUCCH resources may be configured independently in each subset of subslots. Thus, different PUCCH configurations may be applied to different sets of subslots.

The UE <NUM> may be configured with multiple subslot structures for PUCCH resource allocation. The PUCCH resources may be configured independently in each subslot structure, and different PUCCH resource configurations may be applied to different subslot structures.

In the case of a slot-based PUCCH resource, multiple starting symbol locations in a slot may be specified for the enhanced PUCCH formats for URLLC.

The PUCCH resources in a slot should not overlap with each other in time domain. Each PUCCH resource should be contained within the slot, and not cross a slot boundary. Therefore, the number of PUCCH resources that can be configured in a slot depends on the number of symbols in the configured PUCCH format.

Aspects of PUCCH formats in NR are described herein. PUCCH may be used to report important uplink control information (UCI), which includes HARQ-ACK, SR, channel state information (CSI), etc. While NR release-<NUM> is designed mainly for enhanced mobile broadband (eMBB), several physical uplink control channel (PUCCH) formats are specified for different number of bits, as given below.

As used herein, µ represents subcarrier spacing configuration, where Δf = <NUM>µ·<NUM> [kHz]. <MAT> represents the number of slots per subframe for subcarrier spacing configuration µ. <MAT> represents the number of slots per frame for subcarrier spacing configuration µ. <MAT> represents the number of symbols per slot.

Multiple OFDM numerologies are supported as given by Table <NUM> where µ and the cyclic prefix for a bandwidth part may be obtained from the higher-layer parameter subcarrierSpacing and cyclicPrefix, respectively.

For subcarrier spacing configuration µ , slots are numbered <MAT> in increasing order within a subframe and <MAT> in increasing order within a frame. There are <MAT> consecutive symbols (e.g., OFDM symbols) in a slot where <MAT> depends on the cyclic prefix as given by Table <NUM> and Table <NUM>. The start of slot <MAT> in a subframe is aligned in time with the start of symbol <MAT> in the same subframe. Table <NUM> includes the number of OFDM symbols per slot, slots per frame, and slots per subframe for normal cyclic prefix. Table <NUM> includes the number of OFDM symbols per slot, slots per frame, and slots per subframe for extended cyclic prefix.

The physical uplink control channel supports multiple formats as shown in Table <NUM>. In case frequency hopping is configured for PUCCH format <NUM>, <NUM>, or <NUM>, the number of symbols in the first hop is given by <MAT> where <MAT> is the length of the PUCCH transmission in OFDM symbols.

The UE <NUM> may be configured with a separate PUCCH resource set for enhanced PUCCH formats from the "normal" PUCCH format (i.e., the PUCCH resource sets for URLLC traffic may be configured independently and separately from eMBB PUCCH resource sets). The PUCCH resource for URLLC may be configured with different parameters and/or with some different fields from that of eMBB resources.

In NR, multiple PUCCH resource sets may be configured for different payload sizes. In each PUCCH resource set, up to <NUM> PUCCH resources can be configured. If the number of resources is more than <NUM>, subsets are formed. In NR, for a PUCCH reporting, the PUCCH resource set may first be determined based on the UCI payload size. The ARI field may indicate the PUCCH resource subset in a PUCCH resource set. If there are more than <NUM> PUCCH resource in each subset, the PUCCH resource for UCI reporting may be determined implicitly based on CCE index of the scheduling DCI. Namely, the PUCCH resource subset(s) for URLLC or eMBB may be indicated by using the ARI field. Also, the PUCCH resource(s) for URLLC or eMBB may be determined based on CCE index of the scheduling DCI (e.g., the CCE index of PDCCH scheduling PDSCH transmission).

URLLC traffic requires ultra-reliability and low latency. The HARQ-ACK for URLLC packet may be supported to provide the required reliability. Furthermore, the HARQ-ACK feedback should be reported immediately after a URLLC transmission.

To provide desired reliability for DL URLLC transmission, PUCCH resources need to be allocated to allow PDSCH retransmissions. Due to high reliability and low latency requirements, to support re-transmission of URLLC PDSCH, one or more HARQ-ACK feedback needs to be reported within a subframe, and more than one HARQ-ACK reporting PUCCH resources may need to be configured in a subframe or a slot.

The current time domain allocation for a PUCCH resource by configuring a starting symbol and a duration may not be sufficient. In an approach, the UE <NUM> may be configured with a subslot structure, and the PUCCH resources are configured within a subslot structure.

To reduce latency, in LTE, a shortened transmission time interval (sTTI) can be configured besides legacy <NUM> TTI. The sTTI can be configured at the subslot level with <NUM> or <NUM> symbols in a sTTI, or at the slot level with <NUM> symbols in a sTTI. In LTE, the DL and UL shortened TTI duration can be configured separately, and the DL sTTI duration has to be the same or shorter than the UL sTTI duration. Once configured, the sPDSCH, sPUCCH and sPUSCH transmissions all follow the configured sTTI structure.

In NR Rel-<NUM>, the PUCCH resources may be configured at a slot level of <NUM> symbols. Therefore, to have more than one HARQ-ACK feedback in a slot, the granularity of PUCCH reporting should be enhanced. Thus, in this disclosure, the PUCCH allocation methods based on a mini-slot or subslot structure are described.

DL and UL subslot configuration are described herein. In NR, subslot configuration for PUCCH for HARQ-ACK reporting can be separately configured from PDSCH and PUSCH scheduling. If a DL subslot structure is configured for PDSCH scheduling, the UE <NUM> can limit the starting symbols for PDCCH or DCI monitoring in each slot. This can reduce complexity.

In some approaches, the DL and UL subslot structure can be the same. In other approaches, the DL and UL subslot structure can be different. Unlike LTE sTTI, the PUCCH duration can be shorter than a URLLC PDSCH duration.

Furthermore, in NR, the starting symbol and duration can be scheduled for a PDSCH and PUSCH. Thus, NR does not need to follow a subslot structure for PDSCH and PUSCH scheduling. Therefore, NR only needs to define subslot structure for PUCCH of HARQ-ACK reporting.

As described herein, the focus is on UL subslot configuration for HARQ-ACK feedback on PUCCH for ease of explanation. However, the subslot allocation may also be applied on the DL for PDSCH transmissions, and on UL for PUSCH transmissions.

A subslot structure for HARQ-ACK PUCCH configuration in URLLC is described herein. A slot may be partitioned into multiple subslots, and the PUCCH resources for HARQ-ACK may be configured within each subslot. Therefore, the PUCCH resource configuration for URLLC includes a subslot structure and PUCCH resource allocation within a subslot.

There is a tradeoff between the duration of a subslot and the number of PUCCH instances in a slot. A shorter duration may provide more opportunities for HARQ-ACK reporting with reduced latency. But the shorter duration may also bring more overhead on the PUCCH resources. To provide retransmission with desired latency, within <NUM>, <NUM> to <NUM> HARQ-ACK reporting instances are enough.

The minimum subslot may be only one symbol. In this case, all symbols can be used to carry HARQ-ACK. However, with a subslot structure, a PUCCH resource should not cross the subslot boundary. Thus, a <NUM> symbol short PUCCH can be used. To allocate multiple symbols in a subslot, PUCCH resources can be configured with more robustness and flexibility.

Different subslot configurations may be specified for NR. <FIG> illustrates different subslot structures for URLLC PUCCH allocation.

In one case, the PUCCH resources can be configured in each subslot of a configured subslot structure. Multiple sets of PUCCH resources can be configured in each subslot. Each PUCCH resource set may be configured for a payload range. Each resource set may contain PUCCH resources with the same or different formats, with the same or different starting positions in a subslot. A single PUCCH resource should not cross over a subslot boundary.

The same PUCCH configuration can be applied to all subslots, as shown in <FIG>. In the case of the different duration for the subslots (e.g., in the case of <NUM> and <NUM> symbol subslot structure), the same PUCCH configuration may be determined based on the subslot with a shorter duration.

In another case, the PUCCH resources may be configured in a subset of the subslots. The subset pattern and indexes may be configured by higher layer signaling. This reduces the PUCCH resource overhead by limiting the PUCCH resources in a subset of subslots.

The subslot indexes included in the subset may be configured by higher layer signaling. The subslot indexes in the subset may be defined by a table that includes the allowed sets of subslot indexes. And the index in the table is signaled to UE <NUM> by higher layer signaling. <FIG> shows some examples of PUCCH allocation in a subset of subslots.

In yet another case, multiple subsets of subslots may be configured, and PUCCH configuration may be configured independently in each subset of subslots. <FIG> shows several examples of PUCCH configuration in multiple subset of subslots. In the example of <NUM> and <NUM> symbol subslots in <FIG>, different subsets can be formed for subslots with different durations, and the same or different PUCCH resource configurations can be used in the different subsets with different durations.

According to the invention as claimed, the UE <NUM> may be configured with multiple subslot structures. Different PUCCH resource sets can be configured that follow different subslot structure configurations.

Low latency physical uplink control channel (PUCCH) enhancements and resource configuration are also described herein. In a first aspect, PUCCH enhancements for ultra-reliability and low latency are described. Some enhancements are needed to satisfy the URLLC PUCCH reliability requirements (e.g., achieving a BER of <NUM>-<NUM> instead of <NUM><NUM> for regular HARQ-ACK).

For a single PUCCH resource within a slot or subslot, several methods can be implemented. A first method may include transmit power control. One way to increase reliability is to increase the transmit power of PUCCH for URLLC HARQ-ACK feedback. Enhanced PUCCH formats for URLLC may be configured with a higher transmit power than normal PUCCH formats. For example, a separate amplitude scaling factor βPUCCH may be configured and mapped in sequence transmitted on the enhanced PUCCH formats.

A second method may include transmit diversity. For all PUCCH formats <NUM>/<NUM>/<NUM>/<NUM>/<NUM> enhancement, transmit diversity with multiple antenna transmission on multiple PUCCH resources may be configured to enhance the PUCCH performance. Transmit diversity (TxD) can also increase the reliability. With TxD, the PUCCH signal is transmitted on two antenna ports, each using a separate PUCCH Physical Resource Block (PRB) resource.

For HARQ-ACK transmission with sequence based PUCCH format <NUM>, the spatial orthogonal resource transmit diversity (SORTD) scheme may be supported for transmissions with two antenna ports (p ∈ [p<NUM>, p<NUM>]).

The UE <NUM> may use a PUCCH resource for transmission of HARQ-ACK in a slot mapped to antenna port p. For transmission on antenna port p<NUM>, the UE <NUM> may use a PUCCH resource that is configured or implicitly derived based on CCE indexes of the scheduling DCI. For transmission on antenna port p<NUM>, the UE <NUM> may use the next PUCCH resource after the PUCCH resource used for antenna port p<NUM>.

The TxD may be configured to a UE <NUM> by RRC configurations in PUCCH configuration, or a separate information element.

A third method may include more frequency domain allocation. For short PUCCH format <NUM>, <NUM>, and <NUM>, only one PRB is allocated in NR Rel-<NUM>. For URLLC PUCCH, more than <NUM> PRB may be allocated for enhanced PUCCH format <NUM>, <NUM>, and <NUM>. For long PUCCH formats <NUM> and <NUM>, more PRBs may be configured compared with a PUCCH for eMBB HARQ-ACK feedback with the same payload range.

Furthermore, the long PUCCH duration may be limited for URLLC PUCCH configuration. In one case, only PUCCH duration of <NUM> and <NUM> are supported. In another case, PUCCH duration of <NUM> to <NUM> may be supported. The actual allowed PUCCH duration may be determined based on the numerology, the number of PUCCHs for URLLC PDSCH HARQ-ACK feedback in a slot, and/or determined by the subslot duration if a subslot structure is configured and applied for PUCCH resource allocation.

A fourth method may include a lower maximum code rate for PUCCH of URLLC HARQ-ACK feedback. To increase the reliability of PUCCH HARQ-ACK feedback, the maxCodeRate (i.e., the PUCCH-MaxCodeRate parameter for the maximum code rate for UCI on the PUCCH) may be configured with a much lower rate compared with PUCCH resources configured for HARQ-ACK feedback of eMBB PDSCH transmissions. The maxCodeRate may be configured jointly considering more PRB allocations above. In other words, the enhanced PUCCH formats for URLLC may be configured with a lower maxCodeRate compared with PUCCH resources for eMBB. Thus, for the same payload range, the number of PRBs for URLLC PUCCH may be higher than that of an eMBB PUCCH resource.

In a second aspect, PUCCH resource configuration within a slot or subslot is described herein. With at least one of the above-mentioned enhancements on a PUCCH format, the enhanced PUCCH format can be configured for HARQ-ACK feedback of URLLC PDSCH transmissions. The enhanced PUCCH format can be PUCCH format <NUM>/<NUM>/<NUM>/<NUM>/<NUM>. The payload size and duration restrictions may be different from the PUCCH formats for eMBB HARQ-ACK feedback. Since URLLC supports more than one HARQ-ACK feedback in a slot, enhancements on PUCCH format configuration must be specified.

For subslot level configuration, if a subslot structure is configured for PUCCH resource allocation, the starting symbol index may be re-interpreted as the relative index within a subslot instead of the symbol index of a slot. As shown below in Listing <NUM>, the enhanced PUCCH format is noted as PUCCH_format0_e, PUCCH_format1_e, PUCCH_format2_e, PUCCH_format3_e, PUCCH_format4_e, respectively, to show the enhancement over existing PUCCH formats. Other names over existing formats and new PUCCH formats may be defined as well.

Whether a PUCCH format can be supported or not may depend on the duration of a given subslot.

For enhanced PUCCH format <NUM> and enhanced PUCCH format <NUM>, the startingSymbolIndex may be from the beginning of a subslot to the indexes of subslotduration-<NUM> depending on the number of symbols in the subslot. For a given PUCCH duration of nrofSymbols, the startingSymbolIndex may range from <NUM> to (subslotduration-nrofSymbols).

For enhanced PUCCH format <NUM>, <NUM>, and <NUM>, the startingSymbolIndex may be from the beginning of a subslot to the indexes of subslotduration-<NUM> depending on the number of symbols in the subslot. For a given PUCCH duration of nrofSymbols, the startingSymbolIndex may range from <NUM> to (subslotduration- nrofSymbols).

Furthermore, for enhanced PUCCH format <NUM>, <NUM>, and <NUM>, the number of PRBs may be configured with one or multiple PRBs instead of a fixed one PRB allocation.

In the case of subslot PUCCH resource allocation, the Rel-<NUM> slot level PUCCH configuration may be extended to subslot level. The enhanced PUCCH formats may be used in subslot PUCCH configuration.

Depending on the subslot duration, some parameters may be further restricted to the valid ranges. For a subslot duration of <NUM> symbols, only short PUCCH format <NUM> and <NUM> can be configured. For a subslot duration of <NUM> symbols in a <NUM> and <NUM> symbol subslot structure, only short PUCCH format <NUM> and <NUM> can be configured.

For a subslot duration of <NUM> symbols in a <NUM> and <NUM> symbol subslot structure, short PUCCH format <NUM> and <NUM> can be configured. Long PUCCH format <NUM>,<NUM>,<NUM> with <NUM> symbols only can be configured. For long PUCCH format <NUM> and <NUM>, more than one PRB may be allocated for URLLC PUCCH for HARQ-ACK reporting.

For a subslot duration of <NUM> symbols, short PUCCH format <NUM> and <NUM> can be configured. Long PUCCH format <NUM>,<NUM>,<NUM> with <NUM>-<NUM> symbols can be configured provided all symbols of the PUCCH are confined in the <NUM>-symbol subslot.

In a subslot with PUCCH allocation, multiple sets of PUCCH resources can be configured. Each resource set may be defined by a payload range. Each resource set may contain PUCCH resources with the same or different formats, with the same or different starting positions in a subslot. A single PUCCH resource may not cross over a subslot boundary.

In one method, each PUCCH resource may be defined by a PUCCH format with at least the number of symbols, the number of PRBs, the starting PRB index, and the starting symbol index relative to the starting symbol of the subslot.

In another method, a PUCCH resource always starts from the beginning of a subslot to give fast feedback. Thus, the startingSymbolIndex field in the PUCCH format configurations may be ignored or removed. Only the number of symbols and the number of PRBs, etc. may be configured.

In yet another method, a PUCCH resource may always end at last symbol of a subslot. Thus, the startingSymbolIndex field in the PUCCH format configurations may also be ignored or removed. Only the number of symbols and the number of PRBs, etc., are configured.

Whether the PUCCH starts from the beginning of a subslot or ends at last symbol of a subslot may be specified by the standard, or configured by higher layer signaling to the UE <NUM> from a gNB <NUM>. In one case, the PUCCH resources can be configured in each subslot of a configured subslot structure. The same configuration can be applied to all subslots. In the case of a different duration for the subslots (e.g., in a <NUM> and <NUM> symbol subslot structure), the same PUCCH configuration may be determined based on the subslot with shorter duration. In the case that a PUCCH resource always starts from the beginning of a subslot, the last symbol of a <NUM>-symbol subslot is not used for PUCCH. In the case that a PUCCH resource always ends at the last symbol of a subslot, the first symbol of a <NUM>-symbol subslot is not used for PUCCH.

In another case, the PUCCH resources may be configured in a subset of the subslots only. The subset pattern and indexes may be configured by higher layer signaling. This reduces the PUCCH resource overhead by limiting the PUCCH resources in a subset of subslots.

In yet another case, multiple subsets of subslots may be configured, and PUCCH resources may be configured independently in each subset of subslots. Thus, different PUCCH configurations may be applied to different sets of subslots. For example, in the case of <NUM> and <NUM> symbol subslots, a different subset can be formed for subslots with different durations, and the same or different PUCCH resource configurations can be used in the different subsets with different durations. This can optimize the resource allocation in each subslot based on the duration of the subslot.

The UE <NUM> may be configured with multiple subslot structures for PUCCH resource allocation. The PUCCH resources may be configured independently in each subslot structure, and different PUCCH resource configurations may be applied to different subslot structure. For example, an enhanced PUCCH format <NUM> can be configured for <NUM> or <NUM> bits in a <NUM>-symbol subslot structure. An enhanced PUCCH format <NUM> can be configured for more than <NUM> bits in a <NUM> and <NUM> symbol structure. In a <NUM> symbol subslot structure, an enhanced PUCCH format <NUM> or PUCCH format <NUM> can be configured for higher HARQ-ACK payload when PDSCH aggregation is used to report multiple PDSCH transmissions.

The PUCCH resources in different subslot structures may be differentiated by different payload ranges. For example, small payload PUCCH resources can be allocated more frequently in a subslot structure with short subslot duration. Large payload PUCCH resources can be configured in a subslot structure with longer subslot duration.

The PUCCH resources in different subslot structures may be differentiated by different latency requirements. For example, PUCCH resources can be allocated more frequently in a subslot structure with short subslot duration for ultra-low latency traffic. PUCCH resources can be configured in a subslot structure with longer subslot duration for low latency traffic.

In another case, the PUCCH resources in different subslot structures may be configured for different URLLC services based on the reliability and latency requirements.

Slot level configuration is also described herein. If the PUCCH for URLLC HARQ-ACK feedback is configured at slot level, multiple starting symbol positions may be configured for a PUCCH format (e.g., in a given PUCCH format) besides the number of symbols nrofSymbols parameter, the startingSymbolIndex parameter should be enhanced to configure multiple starting symbol positions in a slot as illustrated in Listing <NUM>.

The PUCCH resources in a slot should not overlap with each other in the time domain. Each PUCCH resource should be contained within a slot, and not cross a slot boundary. Therefore, the number of PUCCH resources that can be configured in a slot depends on the number of symbols in the configured PUCCH format. For an enhanced short PUCCH format <NUM> or PUCCH format <NUM> with one symbol duration, up to <NUM> PUCCH resources may be configured in a slot. For an enhanced short PUCCH format <NUM> or PUCCH format <NUM> with two symbol duration, up to <NUM> PUCCH resources may be configured in a slot. For an enhanced long PUCCH format <NUM>,<NUM>,<NUM>, with four symbol durations, up to <NUM> PUCCH resources may be configured in a slot. For an enhanced long PUCCH format <NUM>,<NUM>,<NUM>, with <NUM> to <NUM> symbol durations, up to <NUM> PUCCH resources may be configured in a slot. <FIG> shows several examples of multiple starting positions for PUCCH formats with different durations.

As described above, the UE <NUM> may transmit on the PUCCH for URLLC, HARQ-ACK of URLLC DL data (e.g., URLLC PDSCH transmission). Also, the UE <NUM> may transmit on the PUCCH for eMBB, HARQ-ACK of eMBB DL data (e.g., eMBB PDSCH transmission). Namely, for the HARQ-ACK transmission corresponding to URLLC DL data, the UE <NUM> may use the PUCCH resource for URLLC. Also, for the HARQ-ACK transmission corresponding to eMBB DL data, the UE <NUM> may use the PUCCH resource for eMBB.

Here, the PDSCH corresponding to URLLC DL data and/or the PDSCH corresponding to eMBB DL data may be identified based on a parameter(s) configured by the gNB <NUM>. For example, the gNB <NUM> may transmit by using the RRC message, the parameter(s) used for identifying that the PDSCH transmission is corresponding to URLLC DL data or eMBB DL data.

Also, the PDSCH corresponding to URLLC DL data may be scheduled (e.g., identified) by using the DCI format(s) with CRC scrambled by Y-RNTI different from the C-RNTI. Here, the PDSCH corresponding to eMBB DL data may be scheduled (e.g., identified) by using the DCI format(s) with CRC scrambled by the C-RNTI. Here, the Y-RNTI may be used for identifying a first CQI table and/or a first MCS table. Also, the C-RNTI may be used for identifying a second CQI table and/or a second MCS table. The first and second CQI tables may be used for interpretation of CQI indices for CQI reporting. Also, the first and second MCS tables may be used to determine a modulation order and/or a target error rate. Namely, the PDSCH corresponding to URLLC DL data and/or the PDSCH corresponding to eMBB DL data may be identified based on a corresponding CQI table(s) and/or MCS table(s).

Also, the PDSCH corresponding to URLLC DL data and/or the PDSCH corresponding to eMBB DL data may be identified based on a duration(s) of PDSCH transmission(s). Here, the duration(s) of PDSCH transmission(s) may be configured/ indicated by the gNB <NUM>. For example, the gNB <NUM> may transmit by using the RRC message, information used for configuring (e.g., determining) the duration(s) of the PDSCH transmission(s). Also, the gNB <NUM> may transmit by using the DCI format(s), information used for indicating the duration(s) of the PDSCH transmission(s). For example, the duration(s) for the PDSCH corresponding to URLLC DL data may be a symbol level(s) (e.g., <NUM> symbols, <NUM> symbols, and/or <NUM> symbols). And, the duration for the PDSCH corresponding to eMBB DL data may be a slot level (e.g., <NUM> slot, <NUM> slots, <NUM> slots). Namely, the PDSCH transmission corresponding to URLLC DL data may support a shorter duration(s) than the PDSCH transmission corresponding eMBB DL data.

The UE operations module <NUM> may provide information <NUM> to the one or more receivers <NUM>. For example, the UE operations module <NUM> may inform the receiver(s) <NUM> when to receive retransmissions.

The UE operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the UE operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the UE operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the UE operations module <NUM> may instruct the encoder <NUM> to encode transmission data <NUM> and/or other information <NUM>. The other information <NUM> may include PDSCH HARQ-ACK information.

The UE operations module <NUM> may provide information <NUM> to the modulator <NUM>. For example, the UE operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The UE operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the UE operations module <NUM> may instruct the one or more transmitters <NUM> when to transmit a signal to the gNB <NUM>. For instance, the one or more transmitters <NUM> may transmit during a UL subframe. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more gNBs <NUM>.

Each of the one or more gNBs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a gNB operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in a gNB <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the gNB <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the UE <NUM> using one or more antennas 180a-n. For example, the receiver <NUM> may receive and downconvert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the UE <NUM> using one or more antennas 180a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The gNB <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce one or more decoded signals <NUM>, <NUM>. For example, a first eNB-decoded signal <NUM> may comprise received payload data, which may be stored in a data buffer <NUM>. A second eNB-decoded signal <NUM> may comprise overhead data and/or control data. For example, the second eNB-decoded signal <NUM> may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module <NUM> to perform one or more operations.

In general, the gNB operations module <NUM> may enable the gNB <NUM> to communicate with the one or more UEs <NUM>. The gNB operations module <NUM> may include a gNB scheduling module <NUM>. The gNB scheduling module <NUM> may perform operations for PUCCH configuration and resource allocation as described herein.

The gNB operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the gNB operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the gNB operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the gNB operations module <NUM> may instruct the encoder <NUM> to encode information <NUM>, including transmission data <NUM>.

The encoder <NUM> may encode transmission data <NUM> and/or other information included in the information <NUM> provided by the gNB operations module <NUM>. For example, encoding the data <NUM> and/or other information included in the information <NUM> may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder <NUM> may provide encoded data <NUM> to the modulator <NUM>. The transmission data <NUM> may include network data to be relayed to the UE <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the modulator <NUM>. This information <NUM> may include instructions for the modulator <NUM>. For example, the gNB operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the gNB operations module <NUM> may instruct the one or more transmitters <NUM> when to (or when not to) transmit a signal to the UE(s) <NUM>. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more UEs <NUM>.

It should be noted that a DL subframe may be transmitted from the gNB <NUM> to one or more UEs <NUM> and that a UL subframe may be transmitted from one or more UEs <NUM> to the gNB <NUM>. Furthermore, both the gNB <NUM> and the one or more UEs <NUM> may transmit data in a standard special subframe.

It should also be noted that one or more of the elements or parts thereof included in the eNB(s) <NUM> and UE(s) <NUM> may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

URLLC may coexist with other services (e.g., eMBB). Due to the latency requirement, URLLC may have a highest priority in some approaches. Some examples of URLLC coexistence with other services are given herein (e.g., in one or more of the following Figure descriptions).

<FIG> illustrates examples of subslot structure for URLLC PUCCH allocation. The subslot indexes 204a-d for <NUM>-symbol slots are shown.

Different subslot configurations <NUM> may be specified for NR. As shown in <FIG>, potential subslot structures in a slot of <NUM> symbols may include one or more of the following. A first subslot configuration 202a includes seven <NUM>-symbol subslots (i.e., <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>). A second subslot configuration 202b includes {<NUM>,<NUM>,<NUM>,<NUM>}-symbol subslots. A third subslot configuration 202c includes {<NUM>,<NUM>,<NUM>,<NUM>}-symbol subslots. A fourth subslot configuration 202d includes <NUM>-symbol subslots.

In an example, for the first subslot configuration 202a structure of a <NUM>-symbol subslot, there are potentially <NUM> subslots that can carry HARQ-ACK with PUCCH feedback. However, in most cases, <NUM> to <NUM> HARQ-ACK feedback in a slot is sufficient to ensure the desired low latency requirements.

Different subslot configurations may be configured for different numerologies with different subcarrier spacing (SCS) settings. For example, for SCS with <NUM> kilohertz (kHz), <NUM>-symbol or <NUM> and <NUM> symbol subslots may be used to ensure more re-transmissions occur within <NUM>. For SCS with <NUM>, <NUM>-symbol subslots may be sufficient to ensure re-transmissions within <NUM>.

<FIG> illustrates examples of PUCCH resource configuration in each subslot. The subslot indexes 304a-b for <NUM>-symbol slots are shown.

The same PUCCH configuration can be applied to all subslots, as shown in the first subslot configuration 302a of <FIG>. The same PUCCH resource configuration may be applied in every subslot of the <NUM>-symbol subslots.

In the case of the different duration for the subslots (e.g., in case of <NUM> and <NUM> symbol subslot structure of the second subslot configuration 302b), the same PUCCH configuration may be determined based on the subslot with shorter duration. For example, the same PUCCH resource configuration may be applied in every subslot based on the subslot with the shorter duration. In the case of the example of the second subslot configuration 302b, the <NUM>-symbol subslot is the shorter duration.

<FIG> illustrates examples of PUCCH allocation in a subset of subslots. The subslot indexes 404a-c for <NUM>-symbol slots are shown.

In the example of a first subslot configuration 402a, there is a <NUM>-symbol subslot structure. In this example, the subset may contain only subslot indexes {<NUM>,<NUM>,<NUM>}. Alternatively, the subset may contain only subslot indexes {<NUM>,<NUM>,<NUM>,<NUM>}.

In the example of a second subslot configuration 402b, there is a <NUM>-symbol subslot structure. In this example, the subset may contain only subslot indexes {<NUM>,<NUM>}. Alternatively, the subset may contain only subslot indexes {<NUM>,<NUM>} or {<NUM>,<NUM>} or {<NUM>,<NUM>}, etc. Other combinations are not excluded. For example, subslot indexes set of {<NUM>,<NUM>,<NUM>},{<NUM>,<NUM>,<NUM>}, etc. may be a subset of subslots for PUCCH resource configuration.

In the example of a third subslot configuration 402c, there is a {<NUM>,<NUM>,<NUM>,<NUM>}-symbol subslot pattern. In this case, PUCCH resource configuration may be applied in a subset of subslot indexes {<NUM>,<NUM>}. Alternatively, PUCCH resource configuration may be applied in a subset of subslot indexes {<NUM>,<NUM>}.

<FIG> illustrates examples of PUCCH configuration in multiple subsets of subslots. The subslot indexes 504a-b for <NUM>-symbol slots are shown. In these examples, multiple subsets of subslots may be configured, and PUCCH configuration may be configured independently in each subset of subslots.

In the example of a first subslot configuration 502a, there is a <NUM>-symbol subslot structure. In a <NUM>-symbol subslot structure, a first PUCCH resource configuration 506a is applied to a set with subslot indexes of {<NUM>,<NUM>,<NUM>}. A second PUCCH resource configuration 506b is applied in a separate set of subslots with indexes {<NUM>,<NUM>}.

In the example of a second subslot configuration 502b, there is a {<NUM>,<NUM>,<NUM>,<NUM> }-structure. A first PUCCH resource configuration 506a is applied to a set with subslot indexes of {<NUM>,<NUM>}. A second PUCCH resource configuration 506b is applied in a separate set of subslots with indexes {<NUM>,<NUM>}. It should be noted that the PUCCH configuration in different subsets may be the same or different.

<FIG> illustrates examples of slot-level PUCCH configuration with multiple starting symbol positions. In a first example <NUM>, the slot has three starting symbol positions with a <NUM>-symbol PUCCH <NUM>. In a second example <NUM>, the slot has two starting symbol positions with a <NUM>-symbol PUCCH <NUM>. In a third example <NUM>, the slot has two starting symbol positions with a <NUM>-symbol PUCCH <NUM>.

<FIG> is a diagram illustrating one example of a resource grid for the downlink. The resource grid illustrated in <FIG> may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with <FIG>.

In <FIG>, one downlink subframe <NUM> may include two downlink slots <NUM>. NDLRB is downlink bandwidth configuration of the serving cell, expressed in multiples of NRB sc, where NRBsc is a resource block <NUM> size in the frequency domain expressed as a number of subcarriers, and NDLsymb is the number of OFDM symbols <NUM> in a downlink slot <NUM>. A resource block <NUM> may include a number of resource elements (RE) <NUM>.

For a PCell, NDLRB is broadcast as a part of system information. For an SCell (including an Licensed Assisted Access (LAA) SCell), NDLRB is configured by a RRC message dedicated to a UE <NUM>. For PDSCH mapping, the available RE <NUM> may be the RE <NUM> whose index <NUM> fulfils <NUM>≥ldata,start and/or ldata,end≥<NUM> in a subframe.

In the downlink, the OFDM access scheme with cyclic prefix (CP) may be employed, which may be also referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH and the like may be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) which is also referred to as physical resource blocks (PRBs). The downlink RB pair is a unit for assigning downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The downlink RB pair includes two downlink RBs that are continuous in the time domain.

The downlink RB includes twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in time domain. A region defined by one sub-carrier in frequency domain and one OFDM symbol in time domain is referred to as a resource element (RE) and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains, respectively. While downlink subframes in one component carrier (CC) are discussed herein, downlink subframes are defined for each CC and downlink subframes are substantially in synchronization with each other among CCs.

<FIG> is a diagram illustrating one example of a resource grid for the uplink. The resource grid illustrated in <FIG> may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with <FIG>.

In <FIG>, one uplink subframe <NUM> may include two uplink slots <NUM>. NULRB is uplink bandwidth configuration of the serving cell, expressed in multiples of NRBsc, where NRBsc is a resource block <NUM> size in the frequency domain expressed as a number of subcarriers, and NULsymb is the number of SC-FDMA symbols <NUM> in an uplink slot <NUM>. A resource block <NUM> may include a number of resource elements (RE) <NUM>.

For a PCell, NULRB is broadcast as a part of system information. For an SCell (including an LAA SCell), NULRB is configured by a RRC message dedicated to a UE <NUM>.

In the uplink, in addition to CP-OFDM, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) access scheme may be employed, which is also referred to as Discrete Fourier Transform-Spreading OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH and the like may be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. The uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair includes two uplink RBs that are continuous in the time domain.

The uplink RB may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in time domain. A region defined by one sub-carrier in the frequency domain and one OFDM/ DFT-S-OFDM symbol in the time domain is referred to as a RE and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains respectively. While uplink subframes in one component carrier (CC) are discussed herein, uplink subframes are defined for each CC.

<FIG> shows examples of several numerologies <NUM>. The numerology #<NUM>901a may be a basic numerology (e.g., a reference numerology). For example, a RE 995a of the basic numerology 901a may be defined with subcarrier spacing 905a of <NUM> in frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in time domain (i.e., symbol length #<NUM>903a), where Ts denotes a baseband sampling time unit defined as <NUM>/(<NUM>*<NUM>) seconds. For the i-th numerology, the subcarrier spacing <NUM> may be equal to <NUM>*<NUM>i and the effective OFDM symbol length <NUM>*<NUM>-i*Ts. It may cause the symbol length is <NUM>*<NUM>-i *Ts + CP length (e.g., <NUM>*<NUM>-i *Ts or <NUM>*<NUM>-i *Ts). In other words, the subcarrier spacing of the i+<NUM>-th numerology is a double of the one for the i-th numerology, and the symbol length of the i+<NUM>-th numerology is a half of the one for the i-th numerology. <FIG> shows four numerologies, but the system may support another number of numerologies. Furthermore, the system does not have to support all of the <NUM>-th to the I-th numerologies, i=<NUM>, <NUM>,.

For example, the first UL transmission on the first SPS resource as above mentioned may be performed only on the numerology #<NUM> (e.g., a subcarrier spacing of <NUM>). Here, the UE <NUM> may acquire (detect) the numerology #<NUM> based on a synchronization signal. Also, the UE <NUM> may receive a dedicated RRC signal including information (e.g., a handover command) configuring the numerology #<NUM>. The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on the numerology #<NUM>, the numerology #<NUM> (a subcarrier spacing of <NUM>), and/or the numerology #<NUM> (a subcarrier spacing of <NUM>).

Also, the second UL transmission on the second SPS resource as above mentioned may be performed only on the numerology #<NUM>. Here, for example, the UE <NUM> may receive System Information (e.g., Master Information Block (MIB) and/or System Information Block (SIB)) including information configuring the numerology #<NUM> and/or the numerology #<NUM>.

Also, the UE <NUM> may receive the dedicated RRC signal including information (e.g., the handover command) configuring the numerology #<NUM> and/or the numerology #<NUM>. The System Information (e.g., MIB) may be transmitted on BCH (Broadcast Channel) and/or the dedicated RRC signal. The System Information (e.g., SIB) may contain information relevant when evaluating if a UE <NUM> is allowed to access a cell and/or defines the scheduling of other system information. The System Information (SIB) may contain radio resource configuration information that is common for multiple UEs <NUM>. Namely, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of UL transmissions (e.g., each of UL-SCH transmissions, each of PUSCH transmissions). Also, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of DL transmissions (each of PDCCH transmissions).

<FIG> shows examples of subframe structures for the numerologies <NUM> that are shown in <FIG>. Given that a slot <NUM> includes NDLsymb (or NULsymb) = <NUM> symbols, the slot length of the i+<NUM>-th numerology <NUM> is a half of the one for the i-th numerology <NUM>, and eventually the number of slots <NUM> in a subframe (i.e., <NUM>) becomes double. It may be noted that a radio frame may include <NUM> subframes, and the radio frame length may be equal to <NUM>.

<FIG> shows examples of slots <NUM> and subslots <NUM>. If a subslot <NUM> is not configured by higher layer, the UE <NUM> and the eNB/gNB <NUM> may only use a slot <NUM> as a scheduling unit. More specifically, a given transport block may be allocated to a slot <NUM>. If the subslot <NUM> is configured by higher layer, the UE <NUM> and the eNB/gNB <NUM> may use the subslot <NUM> as well as the slot <NUM>. The subslot <NUM> may include one or more OFDM symbols. The maximum number of OFDM symbols that constitute the subslot <NUM> may be NDLsymb-<NUM> (or NULsymb-<NUM>).

The subslot length may be configured by higher layer signaling. Alternatively, the subslot length may be indicated by a physical layer control channel (e.g., by DCI format).

The subslot <NUM> may start at any symbol within a slot <NUM> unless it collides with a control channel. There could be restrictions of mini-slot length based on restrictions on starting position. For example, the subslot <NUM> with the length of NDLsymb-<NUM> (or NULsymb - <NUM>) may start at the second symbol in a slot <NUM>. The starting position of a subslot <NUM> may be indicated by a physical layer control channel (e.g., by DCI format). Alternatively, the starting position of a subslot <NUM> may be derived from information (e.g., search space index, blind decoding candidate index, frequency and/or time resource indices, PRB index, a control channel element index, control channel element aggregation level, an antenna port index, etc.) of the physical layer control channel which schedules the data in the concerned subslot <NUM>.

In cases when the subslot <NUM> is configured, a given transport block may be allocated to either a slot <NUM>, a subslot <NUM>, aggregated subslots <NUM> or aggregated subslot(s) <NUM> and slot <NUM>. This unit may also be a unit for HARQ-ACK bit generation.

<FIG> shows examples of scheduling timelines <NUM>. For a normal DL scheduling timeline 1209a, DL control channels are mapped the initial part of a slot 1283a. The DL control channels <NUM> schedule DL shared channels 1213a in the same slot 1283a. HARQ-ACKs for the DL shared channels 1213a (i.e., HARQ-ACKs each of which indicates whether or not transport block in each DL shared channel 1213a is detected successfully) are reported via UL control channels 1215a in a later slot 1283b. In this instance, a given slot <NUM> may contain either one of DL transmission and UL transmission.

For a normal UL scheduling timeline 1209b, DL control channels 1211b are mapped the initial part of a slot 1283c. The DL control channels 1211b schedule UL shared channels 1217a in a later slot 1283d. For these cases, the association timing (time shift) between the DL slot 1283c and the UL slot 1283d may be fixed or configured by higher layer signaling. Alternatively, it may be indicated by a physical layer control channel (e.g., the DL assignment DCI format, the UL grant DCI format, or another DCI format such as UE-common signaling DCI format which may be monitored in common search space).

For a self-contained base DL scheduling timeline 1209c, DL control channels 1211c are mapped to the initial part of a slot 1283e. The DL control channels 1211c schedule DL shared channels 1213b in the same slot 1283e. HARQ-ACKs for the DL shared channels 1213b are reported in UL control channels 1215b, which are mapped at the ending part of the slot 1283e.

For a self-contained base UL scheduling timeline 1209d, DL control channels 1211d are mapped to the initial part of a slot 1283f. The DL control channels 1211d schedule UL shared channels 1217b in the same slot 1283f. For these cases, the slot 1283f may contain DL and UL portions, and there may be a guard period between the DL and UL transmissions.

The use of a self-contained slot may be upon a configuration of self-contained slot. Alternatively, the use of a self-contained slot may be upon a configuration of the subslot. Yet alternatively, the use of a self-contained slot may be upon a configuration of shortened physical channel (e.g., PDSCH, PUSCH, PUCCH, etc.).

<FIG> shows examples of DL control channel monitoring regions. In a first example (a), a physical resource block (PRB) 1389a is shown with a symbol length 1301a and frequency 1309a. In a second example (a), a physical resource block (PRB) 1389b is shown with a symbol length 1301b and frequency 1309b. In an implementation, the bandwidth of the PRB 1389a,b.

In the examples of <FIG>, one or more sets of PRB(s) <NUM> may be configured for DL control channel monitoring. In other words, a control resource set 1307a,b is, in the frequency domain, a set of PRBs 1389a,b within which the UE <NUM> attempts to blindly decode downlink control information, where the PRBs 1389a,b may or may not be frequency contiguous. A UE <NUM> may have one or more control resource sets 1307a,b, and one DCI message may be located within one control resource set 1307a,b. In the frequency-domain, a PRB <NUM> is the resource unit size (which may or may not include Demodulation reference signals (DM-RS)) for a control channel 1303a,b. A DL shared channel 1305a,b may start at a later OFDM symbol than the one(s) which carries the detected DL control channel 1303a,b. Alternatively, the DL shared channel 1305a,b may start at (or earlier than) an OFDM symbol than the last OFDM symbol which carries the detected DL control channel 1303a,b. In other words, dynamic reuse of at least part of resources in the control resource sets 1307a,b for data for the same or a different UE <NUM>, at least in the frequency domain may be supported.

<FIG> shows examples of a DL control channel 1403a,b which includes more than one control channel elements. In a first example (a), a physical resource block (PRB) 1489a is shown with a symbol length 1401a and frequency 1409a. In a second example (a), a physical resource block (PRB) 1489b is shown with a symbol length 1401b and frequency 1409b.

When the control resource set 1407a,b spans multiple OFDM symbols, a control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element 1403a,b may be mapped on REs defined by a single PRB 1489a,b and a single OFDM symbol. If more than one DL control channel elements 1403a,b are used for a single DL control channel transmission, DL control channel element aggregation 1411a,b may be performed.

The number of aggregated DL control channel elements 1403a,b is referred to as DL control channel element aggregation level. The DL control channel element aggregation level may be <NUM> or <NUM> to the power of an integer. The gNB <NUM> may inform a UE <NUM> of which control channel candidates are mapped to each subset of OFDM symbols in the control resource set 1407a,b. If one DL control channel 1403a,b is mapped to a single OFDM symbol and does not span multiple OFDM symbols, the DL control channel element aggregation is performed within an OFDM symbol, namely multiple DL control channel elements 1403a,b within an OFDM symbol are aggregated. Otherwise, DL control channel elements 1403a,b in different OFDM symbols can be aggregated.

<FIG> shows examples of UL control channel structures. In the examples of <FIG>, physical resource blocks (PRBs) <NUM> are shown with a symbol length <NUM> and frequency <NUM>.

In a first example (a), the UL control channel 1513a may be mapped on REs which are defined by a PRB <NUM> and a slot in frequency and time domains, respectively. This UL control channel 1513a may be referred to as a long format (or just the 1st format).

In the second example (b) and third example (c), UL control channels 1513b,c may be mapped on REs on a limited OFDM symbols in time domain. This may be referred to as a short format (or just the 2nd format). The UL control channels 1513b,c with a short format may be mapped on REs within a single PRB <NUM>. Alternatively, the UL control channels 1513b,c with a short format may be mapped on REs within multiple PRBs <NUM>. For example, interlaced mapping may be applied, namely the UL control channel 1513b,c may be mapped to every N PRBs (e.g., <NUM> or <NUM>) within a system bandwidth.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM>. The gNB <NUM> may include a higher layer processor <NUM>, a DL transmitter <NUM>, a UL receiver <NUM>, and one or more antenna <NUM>. The DL transmitter <NUM> may include a PDCCH transmitter <NUM> and a PDSCH transmitter <NUM>. The UL receiver <NUM> may include a PUCCH receiver <NUM> and a PUSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the DL transmitter's and the UL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor <NUM> may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.

The DL transmitter <NUM> may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas <NUM>. The UL receiver <NUM> may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas <NUM> and de-multiplex them. The PUCCH receiver <NUM> may provide the higher layer processor <NUM> UCI. The PUSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

<FIG> is a block diagram illustrating one implementation of a UE <NUM>. The UE <NUM> may include a higher layer processor <NUM>, a UL transmitter <NUM>, a DL receiver <NUM>, and one or more antenna <NUM>. The UL transmitter <NUM> may include a PUCCH transmitter <NUM> and a PUSCH transmitter <NUM>. The DL receiver <NUM> may include a PDCCH receiver <NUM> and a PDSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the UL transmitter's and the DL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor <NUM> may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter <NUM> UCI.

The DL receiver <NUM> may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas <NUM> and de-multiplex them. The PDCCH receiver <NUM> may provide the higher layer processor <NUM> DCI. The PDSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

It should be noted that names of physical channels described herein are examples. The other names such as "NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH", "new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH" or the like can be used.

<FIG> illustrates various components that may be utilized in a UE <NUM>. The UE <NUM> described in connection with <FIG> may be implemented in accordance with the UE <NUM> described in connection with <FIG>. The UE <NUM> includes a processor <NUM> that controls operation of the UE <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1807a and data 1809a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random-access memory (NVRAM). Instructions 1807b and data 1809b may also reside in the processor <NUM>. Instructions 1807b and/or data 1809b loaded into the processor <NUM> may also include instructions 1807a and/or data 1809a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1807b may be executed by the processor <NUM> to implement the methods described above.

The UE <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1822a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

<FIG> illustrates various components that may be utilized in a gNB <NUM>. The gNB <NUM> described in connection with <FIG> may be implemented in accordance with the gNB <NUM> described in connection with <FIG>. The gNB <NUM> includes a processor <NUM> that controls operation of the gNB <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1907a and data 1909a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random-access memory (NVRAM). Instructions 1907b and data 1909b may also reside in the processor <NUM>. Instructions 1907b and/or data 1909b loaded into the processor <NUM> may also include instructions 1907a and/or data 1909a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1907b may be executed by the processor <NUM> to implement the methods described above.

The gNB <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1980a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

The various components of the gNB <NUM> are coupled together by a bus system <NUM>, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. The gNB <NUM> may also include a digital signal processor (DSP) <NUM> for use in processing signals. The gNB <NUM> may also include a communications interface <NUM> that provides user access to the functions of the gNB <NUM>. The gNB <NUM> illustrated in <FIG> is a functional block diagram rather than a listing of specific components.

<FIG> is a block diagram illustrating one implementation of a UE <NUM> in which systems and methods for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission may be implemented. The UE <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM> in which systems and methods for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission may be implemented. The gNB <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. The term "computer-readable medium," as used herein, may denote a computer- and/or processor-readable medium that is non-transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

A program running on the gNB <NUM> or the UE <NUM> according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB <NUM> and the UE <NUM> according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB <NUM> and the UE <NUM> may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned implementations may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Claim 1:
A user equipment, UE (<NUM>), comprising:
a higher layer processor (<NUM>) configured to determine a physical uplink control channel, PUCCH, resource in a first subslot for HARQ-ACK feedback for physical downlink shared channel, PDSCH, transmissions that is associated with a highest priority, the first subslot being configured in a slot; and
an UL transmitter (<NUM>) configured to transmit, based on the determined PUCCH resource, the HARQ-ACK feedback for the PDSCH transmissions that is associated with the highest priority, wherein
the UE (<NUM>) is configured with a first PUCCH resource configuration for the HARQ-ACK feedback in the first subslot,
the PUCCH resource is determined based on the first PUCCH resource configuration, characterized in that:
a plurality of possible subslot structures for HARQ-ACK PUCCH resource allocation in the slot is defined, wherein
all subslots in the slot have same duration in one or more of the possible subslot structures, and
the first subslot and another subslot in the slot have different durations in the rest of the possible subslot structures, and
the UE (<NUM>) is configured with a subslot configuration indicating one of the possible subslot structures for the first PUCCH resource configuration.