Low-Intensity Physical Uplink Control Channel (PUCCH) Enhancement and Resource Allocation

Abstract

The present invention describes a user equipment (UE). The UE includes a high-layer processor configured to determine a physical uplink control channel (PUCCH) resource in a time slot or a sub-time slot for HARQ-ACK feedback of a physical downlink shared channel (PDSCH) transmission for ultra-reliable low-latency communication (URLLC). The PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirements. The UE further includes a transmitting circuit configured to transmit the HARQ-ACK feedback for the URLLC PDSCH transmission based on the determined PUCCH resource.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to low latency Physical Uplink Control Channel (PUCCH) enhancements and resource allocation. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable services, extended coverage areas, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, each of which can be served by a base station. A base station can be a device that communicates with wireless communication devices.

[0003] With the development of wireless communication devices, there has been a continuous search for ways to improve communication capacity, speed, flexibility, and / or efficiency. However, improving communication capacity, speed, flexibility, and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device can communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] A user equipment (UE) includes: a higher layer processor configured to determine a Physical Uplink Control Channel (PUCCH) resource in a time slot or a sub - slot for HARQ - ACK feedback of a Ultra - Reliable Low - Latency Communication (URLLC) Physical Downlink Shared Channel (PDSCH) transmission, wherein the PUCCH resource is designated as an enhanced PUCCH format configured to meet URLLC PUCCH reliability requirements; and a transmitting circuit configured to transmit the HARQ - ACK feedback for the URLLC PDSCH transmission based on the determined PUCCH resource.

[0006] In one example, a base station (gNB) includes: a high-layer processor configured to determine a physical uplink control channel (PUCCH) resource in a time slot or sub-slot for HARQ-ACK feedback of a physical downlink shared channel (PDSCH) transmission for ultra-reliable low-latency communication (URLLC) from a user equipment (UE), wherein the PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirement; and a receiving circuit configured to receive, based on the determined PUCCH resource, the HARQ-ACK feedback for the URLLC PDSCH transmission from the UE.

[0007] In one example, a method performed by a user equipment (UE) includes: determining a physical uplink control channel (PUCCH) resource in a time slot or sub-slot for HARQ-ACK feedback of a physical downlink shared channel (PDSCH) transmission for ultra-reliable low-latency communication (URLLC), wherein the PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirement; and transmitting, based on the determined PUCCH resource, the HARQ-ACK feedback for the URLLC PDSCH transmission.

[0008] In one example, a method performed by a base station (gNB) includes: determining a physical uplink control channel (PUCCH) resource in a time slot or sub-slot for HARQ-ACK feedback of a physical downlink shared channel (PDSCH) transmission for ultra-reliable low-latency communication (URLLC) from a user equipment (UE), wherein the PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirement; and receiving, based on the determined PUCCH resource, the HARQ-ACK feedback for the URLLC PDSCH transmission from the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Figure 1 is a block diagram illustrating one particular implementation of one or more base stations (gNBs) and one or more user equipments (UEs) in which systems and methods for low-latency physical uplink control channel (PUCCH) enhancement and resource allocation may be implemented.

[0010] Figure 2 Figure 2 illustrates an example of a sub-slot structure for URLLC PUCCH allocation.

[0011] Figure 3 Figure 3 ​​​​​​Shows an example of PUCCH resource configuration in each sub - slot.

[0012] Figure 4 Figure 4 Shows an example of PUCCH allocation in a subset of sub - slots.

[0013] Figure 5 Figure 5 Shows an example of PUCCH configuration in multiple subsets of sub - slots.

[0014] Figure 6 Figure 6 Shows an example of slot - level PUCCH configuration with multiple starting symbol positions.

[0015] Figure 7 Figure 7 Is a diagram showing an example of a resource grid for the downlink.

[0016] Figure 8 Figure 8 Is a diagram showing an example of a resource grid for the uplink.

[0017] Figure 9 Figure 9 Shows examples of several parameters.

[0018] Figure 10 Figure 10 Shows for Figure 9 An example of the sub - frame structure of the parameters shown in.

[0019] Figure 11 Figure 11 Shows examples of slots and sub - slots.

[0020] Figure 12 Figure 12 Shows an example of a scheduling timeline.

[0021] Figure 13 Figure 13 Shows an example of a DL control channel monitoring area.

[0022] Figure 14 Figure 14 Shows an example of a DL control channel including more than one control channel element.

[0023] Figure 15 Figure 15 Shows an example of a UL control channel structure.

[0024] Figure 16 Figure 16 Is a block diagram showing a specific implementation of a gNB. ​​​​​​​​​​​​​​​​​​​​​​​​​​

[0025] Figure 17 Figure 17 is a block diagram showing a specific implementation of a UE.

[0026] Figure 18 Figure 18 shows various components that can be utilized in the UE.

[0027] Figure 19 Figure 19 shows various components that can be utilized in the gNB.

[0028] Figure 20 Figure 20 is a block diagram showing a specific implementation of a UE in which a system and method for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission can be implemented.

[0029] Figure 21 Figure 21 is a block diagram showing a specific implementation of a gNB in which a system and method for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission can be implemented. Detailed Description

[0030] The present invention describes a user equipment (UE). The UE includes a high-layer processor configured to: determine a physical uplink control channel (PUCCH) resource in a time slot or sub-slot for HARQ-ACK feedback for a physical downlink shared channel (PDSCH) transmission for ultra-reliable low-latency communication (URLLC). The PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirements. The UE further includes a transmission circuit configured to transmit the HARQ-ACK feedback for the URLLC PDSCH transmission based on the determined PUCCH resource.

[0031] The enhanced PUCCH format for URLLC can be configured with a higher transmit power than the normal PUCCH format. Transmit diversity with multi-antenna transmission can be used to transmit the PUCCH signal for URLLC. More than one physical resource block (PRB) can be allocated for PUCCH formats 0, 1, and 4. The enhanced PUCCH format for URLLC can be configured with a lower maximum code rate compared to the PUCCH resources for enhanced mobile broadband (eMBB).

[0032] ​​​​​​​​​​In the case where a sub-slot structure is configured, the starting symbol index in the PUCCH configuration can be modified to represent the relative position within the sub-slot, rather than the symbol index within the slot. In the case where a sub-slot structure is configured, the PUCCH resource can always start from the beginning of the sub-slot, or can end at the last symbol of the sub-slot, and the starting symbol index in the PUCCH configuration does not exist or is ignored.

[0033] One or more PUCCH resource sets can be configured in each sub-slot of the configured sub-slot structure. The same PUCCH configuration regarding PUCCH format and PUCCH resource set can be used in all sub-slots. In the case of different sub-slot durations, the PUCCH format and PUCCH resource set can be determined based on the sub-slot with the shorter duration.

[0034] One or more PUCCH resource sets can be configured in a subset of sub-slots of the configured sub-slot structure.

[0035] One or more PUCCH resource sets can be independently configured in multiple subsets of sub-slots in the sub-slot structure for PUCCH resource allocation. Different PUCCH configurations can be applied to different sets of sub-slots.

[0036] The present invention also describes a base station (gNB). The gNB includes a high-layer processor configured to determine a PUCCH resource in a slot or sub-slot for HARQ-ACK feedback of an URLLC PDSCH transmission from a UE. The PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirement. The gNB also includes a receiving circuit configured to receive the HARQ-ACK feedback of the URLLC PDSCH transmission from the UE based on the determined PUCCH resource.

[0037] A method performed by a UE is also described. The method includes determining a PUCCH resource in a slot or sub-slot for HARQ-ACK feedback of an URLLC PDSCH transmission. The PUCCH resource is designated as an enhanced PUCCH format configured to meet the URLLC PUCCH reliability requirement. The method also includes transmitting the HARQ-ACK feedback of the URLLC PDSCH transmission based on the determined PUCCH resource.

[0038] A method performed by a gNB is also described. The method includes determining a PUCCH resource in a time slot or a sub - slot for HARQ - ACK feedback for a URLLC PDSCH transmission from a UE. The PUCCH resource is designated as an enhanced PUCCH format configured to meet URLLC PUCCH reliability requirements. The method further includes receiving, from the UE, the HARQ - ACK feedback for the URLLC PDSCH transmission based on the determined PUCCH resource.

[0039] The 3rd Generation Partnership Project (also known as "3GPP") is a cooperation agreement aimed at formulating globally applicable technical specifications and technical reports for third - and fourth - generation wireless communication systems. 3GPP can formulate specifications for next - generation mobile networks, systems, and devices.

[0040] 3GPP Long - Term Evolution (LTE) is the name given to a project that awards the improvement of the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to meet future requirements. In one aspect, UMTS has been modified to provide support and specifications for the Evolved Universal Terrestrial Radio Access (E - UTRA) and the Evolved Universal Terrestrial Radio Access Network (E - UTRAN).

[0041] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE - A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, and / or 12). 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 used in other types of wireless communication systems.

[0042] A wireless communication device can be an electronic device that is used to transmit voice and / or data to a base station, which in turn can communicate with the device's network (e.g., the Public Switched Telephone Network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptop computers, netbooks, e - readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device". A UE may also be more generally referred to as a terminal device.

[0043] In 3GPP specifications, a base station is typically referred to as Node B, evolved Node B (eNB), Home eNode B (HeNB), or some other similar terms. Since the scope of this 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 represent the more general term "base station". Additionally, the term "base station" may be used to represent an access point. An access point can be an electronic device that provides access to a network (e.g., local area network (LAN), Internet, etc.) for wireless communication devices. The term "communication device" may be used to represent wireless communication devices and / or base stations. An eNB may also more generally be referred to as a base station device.

[0044] It should be noted that, as used herein, a "cell" can be any such communication channel: which is designated by a standardization or regulatory body for use in International Mobile Telecommunications - Advanced (IMT - Advanced) and all or a subset thereof, such that it is adopted by 3GPP as an authorized frequency band (e.g., frequency band) for communication between an eNB and a UE. It should also be pointed out that in the overall description of E - UTRA and E - UTRAN, as used herein, a "cell" can be defined as "a combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in the system information transmitted on the downlink resources.

[0045] "Configured cells" are those cells that the UE is aware of and has been granted permission by the eNB to transmit or receive information on. "Configured cells" can be serving cells. The UE can receive system information and perform required measurements on all configured cells. The "configured cells" for a radio connection can include a primary cell and / or zero, one, or more secondary cells. "Active cells" are those configured cells on which the UE is transmitting and receiving. That is, active cells are those cells on which the UE monitors its Physical Downlink Control Channel (PDCCH), and in the case of downlink transmission, are those cells on which the UE decodes its Physical Downlink Shared Channel (PDSCH). "De - activated cells" are those configured cells on which the UE does not monitor the transmission of PDCCH. It should be noted that "cells" can be described in different dimensions. For example, a "cell" can have time, space (e.g., geographical), and frequency characteristics.

[0046] The fifth generation (5G) cellular communication (also known as "New Radio", "New Radio Access Technology", or "NR" by 3GPP) envisions using time / frequency / spatial resources to enable enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as services such as massive machine type communication (MMTC). A New Radio (NR) base station may be referred to as a gNB. A gNB may also more generally be referred to as base station equipment.

[0047] In 5G NR, different services can be supported through different quality of service (QoS) requirements (e.g., reliability and latency tolerance). For example, eMBB can target high data rates, and URLLC is used to achieve ultra-reliability and low latency. To support ultra-low latency, more than one HARQ-ACK feedback in a time slot can be configured for URLLC services. This document describes the sub-slot structure in a time slot of multiple PUCCH resources for URLLC PDSCH HARQ-ACK feedback. Additionally, this document describes aspects of URLLC PUCCH enhancements with different PUCCH formats, as well as details of PUCCH resource configurations with time-slot level and sub-slot level structures.

[0048] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, where like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Thus, the more detailed description below of several specific implementations presented in the drawings is not intended to limit the scope of the claimed subject matter, but merely represents the described systems and methods.

[0049] Figure 1 is a block diagram showing one specific implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for low-latency physical uplink control channel (PUCCH) enhancement and resource configuration can be implemented. One or more UEs 102 use one or more antennas 122a-n to communicate with one or more gNBs 160. For example, UE102 uses one or more antennas 122a-n to transmit electromagnetic signals to gNB 160 and receive electromagnetic signals from gNB 160. gNB 160 uses one or more antennas 180a-n to communicate with UE 102.

[0050] UE 102 and gNB 160 may communicate with each other using one or more channels 119, 121. For example, UE 102 may use one or more uplink channels 121 to transmit information or data to gNB 160. Examples of the uplink channel 121 include PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, the uplink channel 121 (e.g., PUSCH) may be used to transmit UL data (i.e., transport block), MAC PDU, and / or UL-SCH (Uplink Shared Channel).

[0051] Here, the UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, a URLLC-PUSCH (i.e., a different physical uplink shared channel from PUSCH) may be defined to transmit URLLC data. For simplicity of description, the term "PUSCH" may represent any one of the following: (1) only PUSCH (e.g., conventional PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not conventional PUSCH).

[0052] Moreover, for example, the uplink channel 121 may be used to transmit Hybrid Automatic Repeat reQuest ACKnowledgment (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ-ACK may include information indicating an ACK (ACKnowledgment) or NACK (Negative ACKnowledgment) of DL data (i.e., transport block), Media Access Control Protocol Data Unit (MAC PDU), and / or DL-SCH (Downlink Shared Channel).

[0053] The CSI may include information indicating the channel quality of the downlink. The SR may be used to request UL-SCH (Uplink Shared Channel) resources for new transmissions and / or retransmissions. That is, the SR may be used to request UL resources for transmitting UL data.

[0054] For example, one or more gNB 160 may also use one or more downlink channels 119 to transmit information or data to one or more UE 102. Examples of the downlink channel 119 include PDCCH, PDSCH, etc. Other types of channels may be used. The PDCCH may be used to transmit Downlink Control Information (DCI).

[0055] Each of one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0056] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and down-convert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. One or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, one or more transmitters 158 may up-convert and transmit one or more modulated signals 156.

[0057] The demodulator 114 may demodulate one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signals. The decoder 108 may produce a decoded signal 110, which may include a UE decoded signal 106 (also referred to as a first UE decoded signal 106). For example, the first UE decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as a second UE decoded signal 110) may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0058] Generally, the UE operation module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.

[0059] The UE scheduling module 126 may perform PUCCH configuration and resource allocation as described herein. According to the low latency requirements of URLLC, it may be necessary to configure two or more PUCCH resources in a single time slot. The current practice of allocating the time domain for short PUCCH by configuring a single starting symbol in the time slot will not meet the requirements.

[0060] To configure more than one PUCCH instance in a time slot, the UE 102 may be configured with a sub - time - slot structure for HARQ - ACK PUCCH resource allocation. Different sub - time - slot structures may be specified, including at least a 2 - symbol structure, a 3 - symbol structure, a 4 - symbol structure, and / or a 7 - symbol structure.

[0061] The UE 102 may be configured with higher - layer signaling of the sub - time - slot structure for PUCCH allocation. One or more PUCCH resources may be configured within the configured sub - time - slot.

[0062] In one method, the UE 102 may be configured with a subset of sub - time - slots in the sub - time - slot structure and configure PUCCH only within the sub - time - slots of the subset of the sub - time - slot structure. In another method, the UE 102 may be configured with multiple subsets of sub - time - slots in the sub - time - slot structure for PUCCH resource allocation.

[0063] A subset of sub - time - slots in the sub - time - slot structure may be specified and the UE 102 may be configured through higher - layer signaling on the subset of sub - time - slots in the sub - time - slot structure. The UE 102 may be configured with multiple sub - time - slot structures for PUCCH resource allocation.

[0064] The URLLC HARQ - ACK PUCCH resources in a time slot or sub - time - slot may be specified as enhanced PUCCH formats to provide the desired reliability requirements. To provide high reliability and low latency, some enhancements to the 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 formats 0, 1, and 4 may be implemented. More PRB allocations for enhanced PUCCH formats for URLLC and a reduced maximum code rate through the maxCodeRate parameter are also described herein.

[0065] In the case where a sub-slot structure is configured, for the PUCCH resource configuration in a sub-slot, the starting symbol index in the PUCCH configuration can be modified to represent the relative position within the sub-slot, rather than the symbol index within the slot. If the PUCCH always starts from the beginning of the sub-slot or ends at the last symbol of the sub-slot, the startingSymbolIndex field can be removed or ignored. Whether the PUCCH always starts from the beginning of the sub-slot or ends at the last symbol of the sub-slot can be specified in the standard or can be configured via higher layer signaling to the UE 102.

[0066] One or more PUCCH resource sets can be configured in each sub-slot of the configured sub-slot structure. The same PUCCH configuration regarding the PUCCH format and resource set can be used in all sub-slots. In the case of different sub-slot durations, the PUCCH format and resource set can be determined based on the sub-slot with the shorter duration.

[0067] The UE 102 can be configured with a subset of the sub-slots in the sub-slot structure. One or more PUCCH resource sets can be configured only within the sub-slots in the subset of the sub-slot structure.

[0068] The UE 102 can be configured with multiple subsets of the sub-slots in the sub-slot structure for PUCCH resource allocation. The PUCCH resources can be configured independently in each subset of the sub-slots. Therefore, different PUCCH configurations can be applied to different sets of sub-slots.

[0069] The UE 102 can be configured with multiple sub-slot structures for PUCCH resource allocation. The PUCCH resources can be configured independently in each sub-slot structure, and different PUCCH resource configurations can be applied to different sub-slot structures.

[0070] In the case of time-slot based PUCCH resources, multiple starting symbol positions in the time-slot can be specified for the enhanced PUCCH format for URLLC.

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

[0072] This document describes aspects of PUCCH formats in NR. The PUCCH can be used to report important uplink control information (UCI), including HARQ-ACK, SR, channel state information (CSI), etc. Although NR Release 15 is mainly designed for enhanced mobile broadband (eMBB), multiple physical uplink control channel (PUCCH) formats are specified for different bit numbers, as described below.

[0073] As used herein, μ represents the subcarrier spacing configuration, where Δf = 2 μ ·15 [kHz]. represents the number of time slots per subframe for the subcarrier spacing configuration μ. represents the number of time slots per frame for the subcarrier spacing configuration μ. represents the number of symbols per time slot.

[0074] As given in Table 1, multiple OFDM parameters are supported, where μ and the cyclic prefix of the bandwidth part can be obtained from the higher layer parameters subcarrierSpacing and cyclicPrefix, respectively.

[0075]

[0076]

[0077] Table 1

[0078] For the subcarrier spacing configuration μ, the time slots are numbered in ascending order within a subframe as and in ascending order within a frame as There are consecutive symbols (e.g., OFDM symbols) in a time slot, where depends on the cyclic prefix given in Tables 2 and 3. The start time of time slot in a subframe is aligned with the start time of symbols in the same subframe. Table 2 includes the number of OFDM symbols per time slot, the number of time slots per frame, and the number of time slots per subframe for the normal cyclic prefix. Table 3 includes the number of OFDM symbols per time slot, the number of time slots per frame, and the number of time slots per subframe for the extended cyclic prefix.

[0079]

[0080] Table 2

[0081]

[0082] Table 3

[0083] The physical uplink control channel supports multiple formats as shown in Table 4. In the case where frequency hopping is configured for PUCCH format 1, 3, or 4, the number of symbols in the first hop is given by as follows, where is the length of PUCCH transmission in terms of OFDM symbols.

[0084]

[0085]

[0086] Table 4

[0087] UE 102 can be configured with a separate PUCCH resource set for enhanced PUCCH formats from the "normal" PUCCH formats (i.e., the PUCCH resource set for URLLC traffic can be configured independently and separately from the eMBB PUCCH resource set). The PUCCH resources for URLLC can be configured with parameters different from those of the eMBB resources and / or some different fields.

[0088] In NR, multiple PUCCH resource sets can be configured for different payload sizes. In each PUCCH resource set, up to 16 PUCCH resources can be configured. If the number of resources is greater than 4, subsets are formed. In NR, for PUCCH reporting, the PUCCH resource set can be determined first based on the UCI payload size. The ARI field can indicate the PUCCH resource subset within the PUCCH resource set. If there are more than 1 PUCCH resources in each subset, the PUCCH resource for UCI reporting can be implicitly determined based on the CCE index of the scheduling DCI. That is, the PUCCH resource subset for URLLC or eMBB can be indicated by using the ARI field. Additionally, the PUCCH resource for URLLC or eMBB can be determined based on the CCE index of the scheduling DCI (e.g., the CCE index of the PDCCH scheduling the PDSCH transmission).

[0089] URLLC traffic requires ultra-high reliability and low latency. HARQ-ACK for URLLC packets can be supported to provide the required reliability. In addition, the HARQ-ACK feedback should be reported immediately after the URLLC transmission.

[0090] To provide the desired reliability for DL URLLC transmission, PUCCH resources need to be allocated to allow PDSCH retransmission. Due to the high reliability and low latency requirements, to support the retransmission of URLLC PDSCH, one or more HARQ-ACK feedbacks need to be reported within a subframe, and it may be necessary to configure more than one HARQ-ACK reporting PUCCH resource within a subframe or a slot.

[0091] Currently, the practice of allocating the time domain for PUCCH resources by configuring the starting symbol and duration may not be able to meet the requirements. In one method, the UE 102 can be configured with a sub-slot structure, and the PUCCH resources are configured within the sub-slot structure.

[0092] To reduce latency, in LTE, in addition to the traditional 1 ms TTI, shortened transmission time intervals (sTTIs) can also be configured. The sTTI can be configured with 2 or 3 symbols in the sTTI at the sub-slot level, or 7 symbols in the sTTI at the slot level. In LTE, the DL and UL shortened TTI durations can be configured separately, and the DL sTTI duration must be the same as or shorter than the UL sTTI duration. Once configured, sPDSCH, sPUCCH, and sPUSCH transmissions all follow the configured sTTI structure.

[0093] In NR Rel-15, PUCCH resources can be configured at the slot level with 14 symbols. Therefore, in order to have more than one HARQ-ACK feedback in a slot, the granularity of PUCCH reporting should be enhanced. Therefore, in the present disclosure, a PUCCH allocation method based on a micro-slot or sub-slot structure is described.

[0094] This document describes DL and UL sub-slot configurations. In NR, the sub-slot configuration of the PUCCH for HARQ-ACK reporting can be configured separately from the PDSCH and PUSCH scheduling. If the DL sub-slot structure is configured for PDSCH scheduling, the UE 102 can limit the starting symbol for PDCCH or DCI monitoring in each slot. This can reduce complexity.

[0095] In some methods, the DL and UL sub-slot structures can be the same. In other methods, the DL and UL sub-slot structures can be different. Different from the LTE sTTI, the PUCCH duration can be shorter than the URLLC PDSCH duration.

[0096] In addition, in NR, the starting symbol and duration can be scheduled for PDSCH and PUSCH. Therefore, NR does not need to follow the sub-slot structure of PDSCH and PUSCH scheduling. Therefore, NR only needs to define the sub-slot structure for the PUCCH of HARQ-ACK reporting.

[0097] As described herein, for ease of explanation, the focus is on the UL sub-slot configuration of HARQ-ACK feedback on the PUCCH. However, sub-slot allocation can also be applied to the DL for PDSCH transmission and to the UL for PUSCH transmission.

[0098] This document describes a sub-slot structure for HARQ-ACK PUCCH configuration in URLLC. A time slot can be divided into multiple sub-slots, and PUCCH resources for HARQ-ACK can be configured within each sub-slot. Therefore, the PUCCH resource configuration for URLLC includes the sub-slot structure and the PUCCH resource allocation within the sub-slot.

[0099] There is a trade-off between the duration of the sub-slot and the number of PUCCH instances in a time slot. A shorter duration can provide more opportunities for HARQ-ACK reporting with reduced latency. However, a shorter duration may also bring more overhead to the PUCCH resources. To provide retransmissions with a desired latency, 2 to 4 HARQ-ACK reporting instances are sufficient within 1 ms.

[0100] The minimum sub-slot can be just one symbol. In this case, all symbols can be used to carry HARQ-ACK. However, for the sub-slot structure, the PUCCH resources should not cross the sub-slot boundary. Therefore, a 1-symbol short PUCCH can be used. To allocate multiple symbols within a sub-slot, the PUCCH resources can be configured with higher robustness and flexibility.

[0101] Different sub-slot configurations can be specified for NR. Figure 2 Different sub-slot structures for URLLC PUCCH allocation are shown.

[0102] In one case, PUCCH resources can be configured in each sub-slot of the configured sub-slot structure. Multiple PUCCH resource sets can be configured in each sub-slot. Each PUCCH resource set can be configured for a payload range. Each resource set can contain PUCCH resources with the same or different formats and the same or different starting positions within the sub-slot. A single PUCCH resource should not cross the sub-slot boundary.

[0103] The same PUCCH configuration can be applied to all sub-slots, as Figure 3 shown. In the case of different durations of sub-slots (e.g., in the case of 3-symbol and 4-symbol sub-slot structures), the same PUCCH configuration can be determined based on the sub-slot with the shorter duration.

[0104] In another case, PUCCH resources can be configured in a subset of sub-slots. The subset pattern and index can be configured by higher layer signaling. This reduces the PUCCH resource overhead by restricting the PUCCH resources in a subset of sub-slots.

[0105] The sub-slot indices included in the subset can be configured by higher layer signaling. The sub-slot indices in the subset can be defined by a table including a set of allowed sub-slot indices. And the indices in the table are signaled to the UE 102 by higher layer signaling. Figure 4 Some examples of PUCCH allocations in a sub-slot subset are shown.

[0106] In yet another case, multiple subsets of sub-slots can be configured, and PUCCH configurations can be configured independently in each subset of sub-slots. Figure 5 Some examples of PUCCH configurations in multiple subsets of sub-slots are shown. In Figure 5 the examples of 3-symbol and 4-symbol sub-slots, different subsets can be formed for sub-slots with different durations, and the same or different PUCCH resource configurations can be used in different subsets with different durations.

[0107] In another case, the UE 102 can be configured with multiple sub-slot structures. Different PUCCH resource sets following different sub-slot structure configurations can be configured.

[0108] Low latency physical uplink control channel (PUCCH) enhancements and resource configurations are also described herein. In a first aspect, PUCCH enhancements for ultra-reliability and low latency are described. Some enhancements are needed to meet the URLLC PUCCH reliability requirements (e.g., for conventional HARQ-ACK, achieving 10 -6 instead of 10 -2 BER).

[0109] For a single PUCCH resource within a slot or sub-slot, several methods can be implemented. The first method can include transmit power control. One way to improve reliability is to increase the transmit power of the PUCCH for URLLC HARQ-ACK feedback. The enhanced PUCCH format for URLLC can be configured with a higher transmit power than the normal PUCCH format. For example, a separate amplitude scaling factor β PUCCH can be configured and mapped in the order of transmission on the enhanced PUCCH format.

[0110] The second method can include transmit diversity. For all PUCCH format 0 / 1 / 2 / 3 / 4 enhancements, transmit diversity with multi-antenna transmission on multiple PUCCH resources can be configured for enhanced PUCCH performance. Transmit diversity (TxD) can also improve reliability. For TxD, the PUCCH signal is transmitted on two antenna ports, and each antenna port uses a separate PUCCH physical resource block (PRB) resource.

[0111] For HARQ-ACK transmission with sequence-based PUCCH format 0, a Spatial Orthogonal Resource Transmit Diversity (SORTD) scheme for transmission with two antenna ports (p ∈ [p0, p1]) can be supported.

[0112] UE 102 can use PUCCH resources to transmit HARQ-ACK in a time slot mapped to antenna port p. For transmission on antenna port p0, UE 102 can use a scheduling DCI-based CCE index configuration or an implicitly derived PUCCH resource. For transmission on antenna port p1, UE 102 can use the next PUCCH resource after the PUCCH resource for antenna port p0.

[0113] TxD can be configured for UE 102 through RRC configuration in the PUCCH configuration or a separate information element configuration.

[0114] A third method can include more frequency domain allocations. For short PUCCH formats 0, 1, and 4, only one PRB is allocated in NR Rel-15. For URLLC PUCCH, more than 1 PRB can be allocated for enhanced PUCCH formats 0, 1, and 4. For long PUCCH formats 2 and 3, more PRBs can be configured compared to the PUCCH for eMBB HARQ-ACK feedback with the same payload range.

[0115] In addition, for URLLC PUCCH configuration, the long PUCCH duration may be restricted. In one case, only PUCCH durations of 4 and 7 are supported. In another case, PUCCH durations from 4 to 7 can be supported. The actually allowed PUCCH duration can be determined based on parameters, the number of PUCCHs for URLLC PDSCH HARQ-ACK feedback in a time slot, and / or if a sub-slot structure is configured and applied to PUCCH resource allocation, by the sub-slot duration.

[0116] The fourth method may include a lower maximum code rate for PUCCH for URLLC HARQ-ACK feedback. To improve the reliability of PUCCH HARQ-ACK feedback, the maxCoderate (i.e., the PUCCH-MaxCodeRate parameter of the maximum code rate of UCI on PUCCH) may be configured with a much lower rate compared to the PUCCH resources configured for HARQ-ACK feedback of eMBB PDSCH transmission. The above-mentioned more PRB allocations may be considered for jointly configuring the maxCoderate. In other words, compared to the PUCCH resources for eMBB, the enhanced PUCCH format for URLLC may be configured with a lower maxCodeRate. Therefore, for the same payload range, the number of PRBs of URLLC PUCCH may be higher than that of eMBB PUCCH resources.

[0117] In a second aspect, PUCCH resource configuration within a time slot or sub-slot is described herein. For at least one of the above enhancements on a PUCCH format, the enhanced PUCCH format may be configured for HARQ-ACK feedback of URLLC PDSCH transmission. The enhanced PUCCH format may be PUCCH format 0 / 1 / 2 / 3 / 4. The payload size and duration limits may be different from the PUCCH formats for eMBB HARQ-ACK feedback. Since URLLC supports more than one HARQ-ACK feedback in a time slot, the enhancements to the PUCCH format configuration must be specified.

[0118] For sub-slot level configuration, if the sub-slot structure is configured for PUCCH resource allocation, the starting symbol index may be reinterpreted as a relative index within the sub-slot rather than the symbol index of the time slot. As shown in List 1 below, the enhanced PUCCH formats are respectively labeled as PUCCH_format0_e, PUCCH_format1_e, PUCCH_format2_e, PUCCH_format3_e, PUCCH_format4_e to indicate the enhancements to the existing PUCCH formats. Other names for the existing formats and new PUCCH formats may also be defined.

[0119] Whether a PUCCH format is supported may depend on the duration of a given sub-slot.

[0120] For enhanced PUCCH format 0 and enhanced PUCCH format 2, startingSymbolIndex can be the index from the start of the sub-slot to subslotduration-1 according to the number of symbols in the sub-slot. For a given PUCCH duration of nrofSymbols, startingSymbolIndex can be in the range of 0 to (subslotduration - nrofSymbols).

[0121] For enhanced PUCCH formats 1, 3, and 4, startingSymbolIndex can be the index from the start of the sub-slot to subslotduration-4 according to the number of symbols in the sub-slot. For a given PUCCH duration of nrofSymbols, startingSymbolIndex can be in the range of 0 to (subslotduration - nrofSymbols).

[0122] In addition, for enhanced PUCCH formats 0, 1, and 4, the number of configured PRBs can be allocated with one or more PRBs instead of a fixed one PRB.

[0123]

[0124]

[0125] List 1

[0126] In the case of sub-slot PUCCH resource allocation, the Rel-15 slot-level PUCCH configuration can be extended to the sub-slot level. Enhanced PUCCH formats can be used for sub-slot PUCCH configuration.

[0127] According to the sub-slot duration, some parameters can be further restricted within a valid range. For a sub-slot duration of 2 symbols, only short PUCCH formats 0 and 2 can be configured. For a sub-slot duration of 3 symbols in 3-symbol and 4-symbol sub-slot structures, only short PUCCH formats 0 and 2 can be configured.

[0128] For a sub-slot duration of 4 symbols in 3-symbol and 4-symbol sub-slot structures, short PUCCH formats 0 and 2 can be configured. Only long PUCCH formats 1, 3, 4 with 4 symbols can be configured. For long PUCCH formats 1 and 4, more than one PRB can be allocated for URLLC PUCCH used for HARQ-ACK reporting.

[0129] For a 7-symbol subslot duration, short PUCCH formats 0 and 2 can be configured. Long PUCCH formats 1, 3, and 4 with 4 to 7 symbols can be configured, provided that all symbols of the PUCCH are restricted within the 7-symbol subslot.

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

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

[0132] In another method, the PUCCH resource always starts from the beginning of the subslot to give fast feedback. Therefore, the startingSymbolIndex field in the PUCCH format configuration can be ignored or removed. Only the number of symbols and the number of PRBs, etc., can be configured.

[0133] In yet another method, the PUCCH resource can always end at the last symbol of the subslot. Therefore, the startingSymbolIndex field in the PUCCH format configuration can also be ignored or removed. Only the number of symbols and the number of PRBs, etc., are configured.

[0134] Whether the PUCCH starts from the beginning of the subslot or ends at the last symbol of the subslot can be specified by the standard or configured by higher layer signaling from gNB 160 to UE 102. In one case, PUCCH resources can be configured in each subslot of the configured subslot structure. The same configuration can be applied to all subslots. In the case of different subslot durations (e.g., in 3-symbol and 4-symbol subslot structures), the same PUCCH configuration can be determined based on the subslot with the shorter duration. In the case where the PUCCH resource always starts from the beginning of the subslot, the last symbol of the 4-symbol subslot is not used for the PUCCH. In the case where the PUCCH resource always ends at the last symbol of the subslot, the first symbol of the 4-symbol subslot is not used for the PUCCH.

[0135] In another case, PUCCH resources can be configured only in a subset of subslots. The subset pattern and index can be configured by higher layer signaling. This reduces the PUCCH resource overhead by restricting the PUCCH resources in the subset of subslots.

[0136] In yet another scenario, multiple subsets of sub - slots can be configured, and PUCCH resources can be configured independently in each subset of sub - slots. Thus, different PUCCH configurations can be applied to different sets of sub - slots. For example, in the case of 3 - symbol and 4 - symbol sub - slots, different subsets can be formed for sub - slots with different durations, and the same or different PUCCH resource configurations can be used in different subsets with different durations. This can optimize the resource allocation in each sub - slot based on the duration of the sub - slot.

[0137] UE 102 can be configured with multiple sub - slot structures for PUCCH resource allocation. PUCCH resources can be configured independently in each sub - slot structure, and different PUCCH resource configurations can be applied to different sub - slot structures. For example, enhanced PUCCH format 0 can be configured for 1 or 2 bits in a 2 - symbol sub - slot structure. Enhanced PUCCH format 2 can be configured for more than 2 bits in 3 - symbol and 4 - symbol structures. In a 7 - symbol sub - slot structure, when PDSCH aggregation is used to report multiple PDSCH transmissions, enhanced PUCCH format 3 or PUCCH format 4 can be configured for a higher HARQ - ACK payload.

[0138] PUCCH resources in different sub - slot structures can be distinguished by different payload ranges. For example, small - payload PUCCH resources can be allocated more frequently in sub - slot structures with short sub - slot durations. Large - payload PUCCH resources can be configured in sub - slot structures with longer sub - slot durations.

[0139] PUCCH resources in different sub - slot structures can be distinguished by different latency requirements. For example, PUCCH resources can be allocated more frequently in sub - slot structures with short sub - slot durations for ultra - low - latency traffic. PUCCH resources can be configured in sub - slot structures with longer sub - slot durations for low - latency traffic.

[0140] In another case, PUCCH resources in different sub - slot structures can be configured for different URLLC services based on reliability and latency requirements.

[0141] Slot - level configurations are also described herein. If PUCCH for URLLC HARQ - ACK feedback is configured at the slot level, in addition to the number of the nrofSymbols parameter of the symbols, multiple starting symbol positions can be configured for a PUCCH format (e.g., for a given PUCCH format), and the startingSymbolIndex parameter should be enhanced to configure multiple starting symbol positions in the slot, as shown in List 2.

[0142]

[0143] List 2

[0144] PUCCH resources in a time slot shall not overlap with each other in the time domain. Each PUCCH resource shall be contained within a time slot and shall not cross the time slot boundary. Therefore, the number of PUCCH resources that can be configured in a time slot depends on the number of symbols in the configured PUCCH format. For the enhanced short PUCCH format 0 or PUCCH format 2 with a symbol duration of one, up to 14 PUCCH resources can be configured in a time slot. For the enhanced short PUCCH format 0 or PUCCH format 2 with a symbol duration of two, up to 7 PUCCH resources can be configured in a time slot. For the enhanced long PUCCH formats 1, 3, 4 with a symbol duration of four, up to 3 PUCCH resources can be configured in a time slot. For the enhanced long PUCCH formats 1, 3, 4 with a symbol duration of 5 to 7, up to 2 PUCCH resources can be configured in a time slot. Figure 6 Several examples showing multiple starting positions of PUCCH formats with different durations are presented.

[0145] As described above, the UE 102 may transmit HARQ-ACK for URLLC DL data (e.g., URLLC PDSCH transmission) on the PUCCH for URLLC. Additionally, the UE 102 may transmit HARQ-ACK for eMBB DL data (e.g., eMBB PDSCH transmission) on the PUCCH for eMBB. That is, for HARQ-ACK transmission corresponding to URLLC DL data, the UE 102 may use the PUCCH resources for URLLC. Additionally, for HARQ-ACK transmission corresponding to eMBB DL data, the UE 102 may use the PUCCH resources for eMBB.

[0146] Here, the PDSCH corresponding to URLLC DL data and / or the PDSCH corresponding to eMBB DL data can be identified based on parameters configured by the gNB 160. For example, the gNB 160 may transmit, via an RRC message, parameters for identifying whether a PDSCH transmission corresponds to URLLC DL data or eMBB DL data.

[0147] Additionally, the PDSCH corresponding to URLLC DL data can be scheduled (e.g., identified) by using a DCI format with a CRC scrambled by a Y-RNTI different from the C-RNTI. Here, the PDSCH corresponding to eMBB DL data can be scheduled (e.g., identified) by using a DCI format with a CRC scrambled by the C-RNTI. Here, the Y-RNTI can be used to identify the first CQI table and / or the first MCS table. Additionally, the C-RNTI can be used to identify the second CQI table and / or the second MCS table. The first CQI table and the second CQI table can be used to interpret the CQI index of the CQI report. Additionally, the first MCS table and the second MCS table can be used to determine the modulation order and / or the target error rate. That is, the PDSCH corresponding to URLLC DL data and / or the PDSCH corresponding to eMBB DL data can be identified based on the corresponding CQI table and / or MCS table.

[0148] Additionally, the PDSCH corresponding to URLLC DL data and / or the PDSCH corresponding to eMBB DL data can be identified based on the duration of the PDSCH transmission. Here, the duration of the PDSCH transmission can be configured / indicated by the gNB 160. That is, the gNB 160 can transmit a message for configuring (e.g., determining) the duration of the PUSCH transmission by using an RRC message. Additionally, the gNB 160 can transmit information for indicating the duration of the PDSCH transmission by using a DCI format. For example, the duration of the PDSCH corresponding to URLLC DL data can be at the symbol level (e.g., 2 symbols, 3 symbols, and / or 5 symbols). And, the duration of the PDSCH corresponding to eMBB DL data can be at the slot level (e.g., 1 slot, 2 slots, 5 slots). That is, the PDSCH transmission corresponding to URLLC DL data can support a shorter duration than the PDSCH transmission corresponding to eMBB DL data.

[0149] The UE operation module 124 can provide the information 148 to one or more receivers 120. For example, the UE operation module 124 can notify one or more receivers 120 when to receive a retransmission.

[0150] The UE operation module 124 can provide the information 138 to the demodulator 114. For example, the UE operation module 124 can notify the demodulator 114 of the modulation pattern expected for the transmission from the gNB 160.

[0151] The UE operation module 124 can provide the information 136 to the decoder 108. For example, the UE operation module 124 can notify the decoder 108 of the coding expected for the transmission from the gNB 160.

[0152] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0153] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operation module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to the modulator 154.

[0154] The UE operation module 124 may provide information 144 to the modulator 154. For example, the UE operation module 124 may notify the modulator 154 of the modulation type (e.g., constellation mapping) for transmission to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0155] The UE operation module 124 may provide information 140 to one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operation module 124 may instruct the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during the UL subframe. The one or more transmitters 158 may up-convert the one or more modulated signals 156 and transmit the one or more modulated signals to one or more gNBs 160.

[0156] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive paths and / or transmission paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0157] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. One or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n. For example, the receiver 178 may receive and down-convert the signals to generate one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. One or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n. For example, one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

[0158] The demodulator 172 may demodulate one or more received signals 174 to generate one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may use the decoder 166 to decode the signals. The decoder 166 may generate one or more decoded signals 164, 168. For example, the first eNB decoded signal 164 may include received payload data, which may be stored in the data buffer 162. The second eNB decoded signal 168 may include overhead data and / or control data. For example, the second eNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operation module 182 may use to perform one or more operations.

[0159] Generally, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operation module 182 may include a gNB scheduling module 194. The gNB scheduling module 194 may perform operations for PUCCH configuration and resource allocation as described herein.

[0160] The gNB operation module 182 may provide information 188 to the demodulator 172. For example, the gNB operation module 182 may notify the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0161] The gNB operation module 182 may provide information 186 to the decoder 166. For example, the gNB operation module 182 may notify the decoder 166 of the coding expected for transmissions from one or more UEs 102.

[0162] The gNB operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.

[0163] The encoder 109 may encode the transmission data 105 included in the information 101 provided by the gNB operation module 182 and / or other information. For example, encoding the transmission data 105 included in the information 101 and / or other information may involve error detection and / or correction coding, mapping the data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0164] The gNB operation module 182 may provide the information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operation module 182 may notify the modulator 113 of the modulation type (e.g., constellation mapping) for one or more transmissions to the UE 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0165] The gNB operation module 182 may provide the information 192 to one or more transmitters 117. The information 192 may include instructions for one or more transmitters 117. For example, the gNB operation module 182 may instruct one or more transmitters 117 when (when not) to transmit signals to one or more UEs 102. One or more transmitters 117 may up-convert one or more modulated signals 115 and transmit the one or more modulated signals to one or more UEs 102.

[0166] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0167] It should also be noted that one or more of the elements or their components included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or their components may be implemented as chips, circuits, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0168] URLLC can coexist with other services (e.g., eMBB). Due to latency requirements, in some methods, URLLC may have the highest priority. Some examples of URLLC coexisting with other services are given herein (e.g., in one or more of the following figure descriptions).

[0169] Figure 2 An example of a sub-slot structure for URLLC PUCCH allocation is shown. Sub-slot indices 204a-d of a 14-symbol slot are shown.

[0170] Different sub-slot configurations 202 can be specified for NR. As Figure 2 shown, the possible sub-slot structures in a 14-symbol slot may include one or more of the following. The first sub-slot configuration 202a includes seven 2-symbol sub-slots (i.e., 2, 2, 2, 2, 2, 2, 2). The second sub-slot configuration 202b includes {4, 3, 4, 3}-symbol sub-slots. The third sub-slot configuration 202c includes {4, 3, 3, 4}-symbol sub-slots. The fourth sub-slot configuration 202d includes 7-symbol sub-slots.

[0171] In one example, for the first sub-slot configuration 202a of a 2-symbol sub-slot structure, there may be 7 sub-slots capable of carrying HARQ-ACK with PUCCH feedback. However, in most cases, 2 to 4 HARQ-ACK feedbacks in a slot are sufficient to ensure the desired low latency requirements.

[0172] Different sub-slot configurations can be configured for different parameters with different subcarrier spacing (SCS) settings. For example, for an SCS of 15 kilohertz (kHz), 2-symbol or 3-symbol and 4-symbol sub-slots can be used to ensure more retransmissions occur within 1 ms. For an SCS of 60 kHz, 7-symbol sub-slots may be sufficient to ensure retransmissions within 1 ms.

[0173] Figure 3 An example of PUCCH resource configuration in each sub-slot is shown. Sub-slot indices 304a-b of a 14-symbol slot are shown.

[0174] The same PUCCH configuration can be applied to all sub-slots, as Figure 3 shown in the first sub-slot configuration 302a. The same PUCCH resource configuration can be applied to each sub-slot of 2-symbol sub-slots.

[0175] In the case of different durations of sub - slots (e.g., in the case of the 3 - symbol and 4 - symbol sub - slot structures of the second sub - slot configuration 302b), the same PUCCH configuration can be determined based on the sub - slot with the shorter duration. For example, the same PUCCH resource configuration can be applied in each sub - slot based on the sub - slot with the shorter duration. In the example of the second sub - slot configuration 302b, the 3 - symbol sub - slot has the shorter duration.

[0176] Figure 4 An example of PUCCH allocation in a subset of sub - slots is shown. Sub - slot indices 404a - c of a 14 - symbol time slot are shown.

[0177] In the example of the first sub - slot configuration 402a, there is a 2 - symbol sub - slot structure. In this example, the subset may only contain sub - slot indices {1, 3, 5}. Alternatively, the subset may only contain sub - slot indices {0, 2, 4, 6}.

[0178] In the example of the second sub - slot configuration 402b, there is a 2 - symbol sub - slot structure. In this example, the subset may only contain sub - slot indices {3, 6}. Alternatively, the subset may only contain sub - slot indices {2, 5} or {1, 4} or {0, 3}, etc. Other combinations are not excluded. For example, sets of sub - slot indices such as {2, 4, 6}, {0, 3, 6}, etc. can be subsets of sub - slots for PUCCH resource configuration.

[0179] In the example of the third sub - slot configuration 402c, there is a {4, 3, 4, 3} symbol sub - slot pattern. In this case, the PUCCH resource configuration can be applied to the subset of sub - slot indices {0, 2}. Alternatively, the PUCCH resource configuration can be applied to the subset of sub - slot indices {1, 3}.

[0180] Figure 5 Examples of PUCCH configurations in multiple subsets of sub - slots are shown. Sub - slot indices 504a - b of a 14 - symbol time slot are shown. In these examples, multiple subsets of sub - slots can be configured, and PUCCH configurations can be independently configured in each subset of sub - slots.

[0181] In the example of the first sub - slot configuration 502a, there is a 2 - symbol sub - slot structure. In the 2 - symbol sub - slot structure, the first PUCCH resource configuration 506a is applied to the set of sub - slot indices {1, 3, 5}. The second PUCCH resource configuration 506b is applied to a separate set of sub - slots with indices {0, 4}.

[0182] In the example of the second sub-slot configuration 502b, there is a {4, 3, 4, 3} structure. The first PUCCH resource configuration 506a is applied to the set of sub-slot indices {0, 2}. The second PUCCH resource configuration 506b is applied to a separate set of sub-slots with indices {1, 3}. It should be noted that the PUCCH configurations in different subsets can be the same or different.

[0183] Figure 6 Examples of slot-level PUCCH configurations with multiple starting symbol positions are shown. In the first example 601, the slot has three starting symbol positions with a 1-symbol PUCCH 606. In the second example 603, the slot has two starting symbol positions with a 2-symbol PUCCH 606. In the third example 605, the slot has two starting symbol positions with a 4-symbol PUCCH 606.

[0184] Figure 7 is a diagram showing an example of a resource grid for the downlink. Figure 7 The shown resource grid can be used in some specific implementations of the systems and methods disclosed herein. In conjunction with Figure 1 More details about the resource grid are given.

[0185] In Figure 7 one downlink subframe 769 may include two downlink slots 783. N DL RB is the downlink bandwidth configuration for the serving cell, represented as a multiple of N RB sc where N RB sc is the size of a resource block 789 in the frequency domain, represented as the number of subcarriers, and N DL symb is the number of OFDM symbols 787 in the downlink slot 783. A resource block 789 may include multiple resource elements (REs) 791.

[0186] For the PCell, N DL RB is broadcast as part of the system information. For SCell (including licensed-assisted access (LAA) SCell), N DL RB is configured via an RRC message dedicated to the UE 102. For PDSCH mapping, the available REs 791 can be the REs 791 whose index 1 in the subframe satisfies 1 ≥ 1 data,start and / or 1 data,end ≥ 1.

[0187] In the downlink, an OFDM access scheme with a cyclic prefix (CP) can be adopted, which can also be referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH, etc. can be transmitted. A downlink radio frame can include multiple pairs of downlink resource blocks (RBs), which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair includes two consecutive downlink RBs in the time domain.

[0188] A downlink RB includes twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE), and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and time domain respectively. Although the downlink subframes in one component carrier (CC) are discussed herein, downlink subframes are defined for each CC and are substantially synchronized with each other between CCs.

[0189] Figure 8 is a diagram illustrating an example of a resource grid for the uplink. Figure 8 The shown resource grid can be used in some specific implementations of the systems and methods disclosed herein. More details about the resource grid are given in Figure 1 in conjunction with

[0190] In Figure 8 , an uplink subframe 869 can include two uplink time slots 883. N UL RB is the uplink bandwidth configuration for the serving cell, expressed as a multiple of N RB sc , where N RB sc is the size of the resource block 889 in the frequency domain, expressed as the number of subcarriers, and N UL symb is the number of SC-FDMA symbols 893 in the uplink time slot 883. The resource block 889 can include multiple resource elements (REs) 891.

[0191] For the PCell, N UL RB is broadcast as part of the system information. For the SCell (including the LAA SCell), N UL RB is configured via an RRC message dedicated to the UE 102.

[0192] In the uplink, in addition to CP - OFDM, a single - carrier frequency - division multiple access (SC - FDMA) access scheme can also be adopted, which is also known as discrete Fourier transform - spread OFDM (DFT - S - OFDM). In the uplink, PUCCH, PUSCH, PRACH, etc. can be transmitted. The uplink radio frame can include multiple pairs of uplink resource blocks. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slots. An uplink RB pair includes two uplink RBs that are consecutive in the time domain.

[0193] An uplink RB can include twelve sub - carriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT - S - OFDM symbols in the time domain. The region defined by one sub - carrier in the frequency domain and one OFDM / DFT - S - OFDM symbol in the time domain is called a RE and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and time domain respectively. Although the uplink sub - frame in one component carrier (CC) is discussed herein, the uplink sub - frame is defined for each CC.

[0194] Figure 9 Examples of several parameters 901 are shown. Parameter #1 901a can be a basic parameter (e.g., a reference parameter). For example, the RE 995a of the basic parameter 901a can be defined as having a sub - carrier spacing 905a of 15 kHz in the frequency domain and a length of 2048Ts + CP (e.g., 160Ts or 144Ts) in the time domain (i.e., symbol length #1 903a), where Ts represents the base - band sampling time unit defined as 1 / (15000 * 2048) seconds. For the i - th parameter, the sub - carrier spacing 905 can be equal to 15 * 2 i and the effective OFDM symbol length 2048 * 2 -i *Ts. This can make the symbol length 2048 * 2 -i *Ts+CP length (e.g., 160 * 2 -i *Ts or 144 * 2 -i *Ts). In other words, the sub - carrier spacing of the (i + 1) - th parameter is twice that of the i - th parameter, and the symbol length of the (i + 1) - th parameter is half that of the i - th parameter. Figure 9 Four parameters are shown, but the system can support another number of parameters. In addition, the system does not have to support all of the 0 - th parameter to the I - th parameter (i = 0, 1,..., I).

[0195] For example, the first UL transmission on the first SPS resource as described above may be performed only on parameter #1 (e.g., the subcarrier spacing is 15 kHz). Here, the UE 102 may obtain (detect) parameter #1 based on the synchronization signal. In addition, the UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) of configuration parameter #1. The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on parameter #1, parameter #2 (subcarrier spacing is 30 kHz), and / or parameter #3 (subcarrier spacing is 60 kHz).

[0196] In addition, the second UL transmission on the second SPS resource as described above may be performed only on parameter #3. Here, for example, the UE 102 may receive system information (e.g., the master information block (MIB) and / or the system information block (SIB)) including information of configuration parameter #2 and / or parameter #3.

[0197] In addition, the UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) of configuration parameter #2 and / or parameter #3. System information (e.g., MIB) may be transmitted on the BCH (broadcast channel) and / or the dedicated RRC signal. System information (e.g., SIB) may contain information on when to evaluate whether the UE 102 is allowed to access the cell and / or information when defining the scheduling of other system information. The system information (SIB) may contain radio resource configuration information shared by multiple UEs 102. That is, the dedicated RRC signal may include each of multiple parameter configurations (the first parameter, the second parameter, and / or the third parameter) for each UL transmission (e.g., each UL-SCH transmission, each PUSCH transmission). In addition, the dedicated RRC signal may include each of multiple parameter configurations (the first parameter, the second parameter, and / or the third parameter) for each DL transmission (e.g., each PDCCH transmission).

[0198] Figure 10 is shown Figure 9 An example of the subframe structure of parameter 1001 shown in DL Symb (or N UL Symb ) = 7 symbols, the slot length of the (i + 1)-th parameter 1001 is half of the slot length of the i-th parameter 1001, and the number of slots 1083 in a subframe (e.g., 1 ms) will eventually double. It should be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

[0199] Figure 11An example of time slot 1183 and sub - time slot 1107 is shown. If the sub - time slot 1107 is not configured by the higher layer, the UE 102 and the eNB / gNB 160 may use only the time slot 1183 as the scheduling unit. More specifically, a given transport block may be allocated to the time slot 1183. If the sub - time slot 1107 is configured by the higher layer, the UE 102 and the eNB / gNB 160 may use the sub - time slot 1107 as well as the time slot 1183. The sub - time slot 1107 may include one or more OFDM symbols. The maximum number of OFDM symbols that make up the sub - time slot 1107 may be N DL symb - 1 (or N UL symb - 1).

[0200] The sub - time slot length may be configured by higher layer signaling. Alternatively, the sub - time slot length may be indicated by a physical layer control channel (e.g., via DCI format).

[0201] The sub - time slot 1107 may start from any symbol within the time slot 1183, unless it conflicts with a control channel. Based on the restrictions on the starting position, there may be restrictions on the micro - time slot length. For example, a sub - time slot 1107 with a length of N DL symb - 1 (or N UL symb - 1) may start from the second symbol in the time slot 1183. The starting position of the sub - time slot 1107 may be indicated by a physical layer control channel (e.g., via DCI format). Alternatively, the starting position of the sub - time slot 1107 may be derived from the information of the physical layer control channel scheduling the data in the sub - time slot 1107 (e.g., search space index, blind decoding candidate index, frequency and / or time resource index, PRB index, control channel element index, control channel element aggregation level, antenna port index, etc.).

[0202] In the case where the sub - time slot 1107 is configured, a given transport block may be allocated to the time slot 1183, the sub - time slot 1107, the aggregated sub - time slot 1107, or the aggregated sub - time slot 1107 and the time slot 1183. This unit may also be a unit for HARQ - ACK bit generation.

[0203] Figure 12An example of the scheduling timeline 1209 is shown. For the normal DL scheduling timeline 1209a, the DL control channel is mapped to the initial part of slot 1283a. The DL control channel 1211 schedules the DL shared channel 1213a in the same slot 1283a. The HARQ-ACK for the DL shared channel 1213a (i.e., each indicating whether the transport block in each DL shared channel 1213a is successfully detected) is reported via the UL control channel 1215a in the subsequent slot 1283b. In this case, a given slot 1283 may contain either a DL transmission or a UL transmission.

[0204] For the normal UL scheduling timeline 1209b, the DL control channel 1211b is mapped to the initial part of slot 1283c. The DL control channel 1211b schedules the UL shared channel 1217a in the subsequent slot 1283d. For these cases, the associated timing (time offset) 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., a DL allocation DCI format, a UL grant DCI format, or another DCI format, such as a UE common signaling DCI format that can be monitored in a common search space).

[0205] For the self-contained basic DL scheduling timeline 1209c, the DL control channel 1211c is mapped to the initial part of slot 1283e. The DL control channel 1211c schedules the DL shared channel 1213b in the same slot 1283e. The HARQ-ACK for the DL shared channel 1213b is reported in the UL control channel 1215b, which is mapped to the end part of slot 1283e.

[0206] For the self-contained basic UL scheduling timeline 1209d, the DL control channel 1211d is mapped to the initial part of slot 1283f. The DL control channel 1211d schedules the UL shared channel 1217b in the same slot 1283f. For these cases, slot 1283f may contain a DL part and a UL part, and there may be a guard period between the DL transmission and the UL transmission.

[0207] The use of self-contained slots may be based on the configuration of self-contained slots. Alternatively, the use of self-contained slots may be based on the configuration of sub-slots. Still alternatively, the use of self-contained slots may be based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0208] Figure 13An example of a DL control channel monitoring region is shown. In the first example (a), physical resource block (PRB) 1389a is shown as having a symbol length 1301a and a frequency 1309a. In the second example (a), physical resource block (PRB) 1389b is shown as having a symbol length 1301b and a frequency 1309b. In a specific implementation, the bandwidths of PRBs 1389a and 1389b.

[0209] In Figure 13 the example of, one or more sets of PRBs 1389 may be configured for DL control channel monitoring. In other words, control resource sets 1307a and 1307b are a set of PRBs 1389a and 1389b in the frequency domain, and UE 102 attempts to blindly decode downlink control information within this set of PRBs, where PRBs 1389a and 1389b may or may not be frequency-contiguous. UE 102 may have one or more control resource sets 1307a and 1307b, and one DCI message may be located within one control resource set 1307a or 1307b. In the frequency domain, PRB 1389 is the resource unit size for control channels 1303a and 1303b (which may or may not include demodulation reference signals (DM-RS)). DL shared channels 1305a and 1305b may start at an OFDM symbol later than the symbol carrying the detected DL control channels 1303a and 1303b. Alternatively, DL shared channels 1305a and 1305b may start at (or start at a symbol earlier than) the last OFDM symbol carrying the detected DL control channels 1303a and 1303b. In other words, at least dynamic reuse of at least a portion of the resources in control resource sets 1307a and 1307b for data of the same or different UEs 102 is supported at least in the frequency domain.

[0210] Figure 14 An example of DL control channels 1403a and 1403b including more than one control channel element is shown. In the first example (a), physical resource block (PRB) 1489a is shown as having a symbol length 1401a and a frequency 1409a. In the second example (a), physical resource block (PRB) 1489b is shown as having a symbol length 1401b and a frequency 1409b.

[0211] When the control resource sets 1407a, 1407b span multiple OFDM symbols, a control channel candidate can be mapped to multiple OFDM symbols or can be mapped to a single OFDM symbol. A DL control channel element 1403a, 1403b can be mapped on the REs defined by a single PRB 1489a, 1489b and a single OFDM symbol. If more than one DL control channel element 1403a, 1403b is used for a single DL control channel transmission, DL control channel element aggregation 1411a, 1411b can be performed.

[0212] The number of aggregated DL control channel elements 1403a, 1403b is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level can be 1 or a power of 2 up to an integer. The gNB 160 can notify the UE 102 which control channel candidates are mapped to each subset of the OFDM symbols in the control resource sets 1407a, 1407b. If a DL control channel 1403a, 1403b is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, that is, multiple DL control channel elements 1403a, 1403b are aggregated within one OFDM symbol. Otherwise, DL control channel elements 1403a, 1403b can be aggregated in different OFDM symbols.

[0213] Figure 15 An example of the UL control channel structure is shown. In Figure 15 the example, the physical resource block (PRB) 1589 is shown as having a symbol length 1501 and a frequency 1509.

[0214] In the first example (a), the UL control channel 1513a can be mapped on the REs defined by the PRB 1589 and the time slots in the frequency domain and the time domain respectively. This UL control channel 1513a can be referred to as the long format (or simply referred to as the first format).

[0215] In the second example (b) and the third example (c), the UL control channels 1513b, 1513c can be mapped on the REs on a limited number of OFDM symbols in the time domain. This can be referred to as the short format (or simply referred to as the second format). The UL control channels 1513b, 1513c with the short format can be mapped on the REs within a single PRB 1589. Alternatively, the UL control channels 1513b, 1513c with the short format can be mapped on the REs within multiple PRBs 1589. For example, an interleaved mapping can be applied, that is, the UL control channels 1513b, 1513c can be mapped to every Nth PRB (e.g., 5 or 10) within the system bandwidth.

[0216] Figure 16It is a block diagram showing a specific implementation of gNB 1660. gNB 1660 may include a high-layer processor 1623, a DL transmitter 1625, a UL receiver 1633, and one or more antennas 1631. The DL transmitter 1625 may include a PDCCH transmitter 1627 and a PDSCH transmitter 1629. The UL receiver 1633 may include a PUCCH receiver 1635 and a PUSCH receiver 1637.

[0217] The high-layer processor 1623 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1623 may obtain transport blocks from the physical layer. The high-layer processor 1623 may send to / obtain from the high layer of the UE high-layer messages such as RRC messages and MAC messages. The high-layer processor 1623 may provide a transport block to the PDSCH transmitter and provide transmission parameters related to the transport block to the PDCCH transmitter.

[0218] The DL transmitter 1625 may multiplex downlink physical channels and downlink physical signals (including reservation signals) and transmit them via the transmit antenna 1631. The Ul receiver 1633 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1631. The PUCCH receiver 1635 may provide UCI to the high-layer processor 1623. The PUSCH receiver 1637 may provide the received transport block to the high-layer processor 1623.

[0219] Figure 17 It is a block diagram showing a specific implementation of UE 1702. UE 1702 may include a high-layer processor 1723, a UL transmitter 1751, a DL receiver 1743, and one or more antennas 1731. The UL transmitter 1751 may include a PUCCH transmitter 1753 and a PUSCH transmitter 1755. The DL receiver 1743 may include a PDCCH receiver 1745 and a PDSCH receiver 1747.

[0220] The high-layer processor 1723 may manage the behavior of the physical layer (the behavior of the UL transmitter and the DL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1723 may obtain transport blocks from the physical layer. The high-layer processor 1723 may send to / obtain from the high layer of the UE high-layer messages such as RRC messages and MAC messages. The high-layer processor 1723 may provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1753.

[0221] The DL receiver 1743 can receive and demultiplex multiplexed downlink physical channels and downlink physical signals via the receiving antenna 1731. The PDCCH receiver 1745 can provide DCI to the higher layer processor 1723. The PDSCH receiver 1747 can provide the received transport block to the higher layer processor 1723.

[0222] It should be noted that the names of the physical channels described herein are examples. Other names can be used, such as "NR PDCCH, NR PDSCH, NR PUCCH, and NR PUSCH", "New Generation-(G)PDCCH, GPDSCH, GPUCCH, and GPUSCH", etc.

[0223] Figure 18 Various components that can be utilized in the UE 1802 are shown. In connection with Figure 18 the described UE 1802 can be implemented according to the UE 102 described in connection with Figure 1 The UE 1802 includes a processor 1803 that controls the operation of the UE 1802. The processor 1803 can also be referred to as a central processing unit (CPU). The memory 1805 (which can include read-only memory (ROM), random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 1807a and data 1809a to the processor 1803. A part of the memory 1805 can also include non-volatile random access memory (NVRAM). The instructions 1807b and data 1809b can also reside in the processor 1803. The instructions 1807b and / or data 1809b loaded into the processor 1803 can also include the instructions 1807a and / or data 1809a from the memory 1805, which are loaded for the processor 1803 to execute or process. The instructions 1807b can be executed by the processor 1803 to implement the above-described method.

[0224] The UE 1802 can also include a housing that houses one or more transmitters 1858 and one or more receivers 1820 to allow for sending and receiving data. The transmitter 1858 and the receiver 1820 can be combined into one or more transceivers 1818. One or more antennas 1822a-n are attached to the housing and electrically coupled to the transceiver 1818.

[0225] The various components of the UE 1802 are coupled together by a bus system 1811 (which can include a power bus, a control signal bus, and a status signal bus in addition to the data bus). However, for clarity, the various buses are shown in Figure 18is shown as bus system 1811 in. The UE 1802 may also include a digital signal processor (DSP) 1813 for processing signals. The UE 1802 may also include a communication interface 1815 that provides user access to the functions of the UE 1802. Figure 18 The UE 1802 shown is a functional block diagram rather than a list of specific components.

[0226] Figure 19 Various components that can be utilized in the gNB 1960 are shown. In conjunction with Figure 19 The gNB 1960 described can be implemented according to the gNB 160 described in conjunction with Figure 1 The gNB 1960 includes a processor 1903 that controls the operation of the gNB 1960. The processor 1903 may also be referred to as a central processing unit (CPU). A memory 1905 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 1907a and data 1909a to the processor 1903. A portion of the memory 1905 may also include non-volatile random access memory (NVRAM). Instructions 1907b and data 1909b may also reside in the processor 1903. The instructions 1907b and / or data 1909b loaded into the processor 1903 may also include instructions 1907a and / or data 1909a from the memory 1905, which are loaded for the processor 1903 to execute or process. The instructions 1907b may be executed by the processor 1903 to implement the above-described method.

[0227] The gNB 1960 may also include a housing that houses one or more transmitters 1917 and one or more receivers 1978 to allow for sending and receiving data. The transmitters 1917 and receivers 1978 may be combined into one or more transceivers 1976. One or more antennas 1980a-n are attached to the housing and electrically coupled to the transceivers 1976.

[0228] The various components of the gNB 1960 are coupled together by a bus system 1911 (in addition to the data bus, this bus system may also include a power bus, a control signal bus, and a status signal bus). However, for clarity, the various buses are shown as bus system 1911 in Figure 19 The gNB 1960 may also include a digital signal processor (DSP) 1913 for processing signals. The gNB 1960 may also include a communication interface 1915 that provides user access to the functions of the gNB 1960. Figure 19 The gNB1960 shown is a functional block diagram rather than a list of specific components.

[0229] Figure 20FIG. 0 is a block diagram illustrating a particular implementation of a UE 2002 in which systems and methods for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission can be implemented. The UE 2002 includes a transmitting device 2058, a receiving device 2020, and a control device 2024. The transmitting device 2058, the receiving device 2020, and the control device 2024 can be configured to perform one or more of the functions described above Figure 1 above Figure 18 illustrates Figure 20 an example of the specific device structure of Figure 1 One or more of the functions of

[0230] Figure 21 FIG. 12 is a block diagram illustrating a particular implementation of a gNB 2160 in which systems and methods for HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission can be implemented. The gNB 2160 includes a transmitting device 2123, a receiving device 2178, and a control device 2182. The transmitting device 2123, the receiving device 2178, and the control device 2182 can be configured to perform one or more of the functions described above Figure 1 above Figure 19 illustrates Figure 21 an example of the specific device structure of Figure 1 One or more of the functions of

[0231] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" can refer to non-transitory and tangible computer-readable media and / or processor-readable media. By way of example and not limitation, computer-readable media or processor-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices 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. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and optical disk, where disks typically reproduce data magnetically, while optical disks use lasers to reproduce data optically.

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

[0233] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, these method steps and / or actions can be interchanged with each other and / or combined into a single step. In other words, unless the correct operation of the method requires steps or actions in a specific order, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0234] It should be understood that the claims are not limited to the exact configurations and components shown above. Without departing from the scope of the claims, various modifications, changes, and alterations can be made to the arrangements, operations, and details of the systems, methods, and apparatuses described herein.

[0235] The program running on the gNB 160 or the UE 102 according to the system and method is a program that controls a CPU, etc. in a manner to implement the functions according to the system and method (a program for computer operation). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, this information is stored in various ROMs or HDDs and read by the CPU whenever needed for modification or writing. As a recording medium on which the program is stored, any one of a semiconductor (e.g., ROM, non-volatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., magnetic tape, floppy disk, etc.), etc. is possible. In addition, in some cases, the functions according to the above system and method are implemented by running the loaded program. Additionally, the functions according to the system and method are implemented based on instructions from the program in combination with an operating system or other application programs.

[0236] In addition, when the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transmitted to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. Further, some or all of the gNB 160 and the UE 102 according to the above-described system and method may be implemented as an LSI which is a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 may be individually built into a chip, and some or all of the functional blocks may be integrated into a chip. Further, the technology of the integrated circuit is not limited to the LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. Further, if an integrated circuit technology alternative to the LSI appears with the continuous progress of semiconductor technology, the integrated circuit applying such technology may also be used.

[0237] In addition, each functional block or various features of the base station device and the terminal device used in each of the above-described specific embodiments may be implemented or executed by a circuit (usually one integrated circuit or a plurality of integrated circuits). The circuit designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, 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 of the above circuits may be configured by a digital circuit or may be configured by an analog circuit. Further, when an integrated circuit technology for manufacturing an integrated circuit replacing the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by such technology can also be used.

[0238] As used herein, the term "and / or" shall be construed to mean one or more items. For example, the phrase "A, B, and / or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be construed to mean one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" shall be understood to mean one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

[0239] <Cross-reference>

[0240] This non-provisional application claims the priority of Provisional Application No. 62 / 790,909, filed on January 10, 2019, under 35 U.S.C. § 119, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment UE, characterized in that, Comprising: A high-layer processor configured to determine a Physical Uplink Control Channel (PUCCH) resource in a first sub-slot for Hybrid Automatic Repeat reQuest - Acknowledgement (HARQ-ACK) feedback corresponding to a Physical Downlink Shared Channel (PDSCH) transmission of Ultra-Reliable Low-Latency Communication (URLLC), the HARQ-ACK feedback corresponding to the PDSCH transmission being associated with the highest priority, the first sub-slot being configured within a time slot; And A transmitting circuit configured to transmit, based on the determined PUCCH resource, the HARQ-ACK feedback corresponding to the PDSCH transmission associated with the highest priority, wherein The User Equipment (UE) is configured with a first PUCCH resource configuration for the HARQ-ACK feedback in the first sub-slot, The PUCCH resource is determined based on the first PUCCH resource configuration, Multiple possible sub-slot structures for HARQ-ACK PUCCH resource allocation within the time slot are defined, wherein All sub-slots within the time slot have the same duration in one or more of the possible sub-slot structures, and The first sub-slot and other sub-slots within the time slot have different durations in the remaining possible sub-slot structures, and The UE is configured with a sub-slot configuration indicating one of the multiple possible sub-slot structures.

2. The UE according to claim 1, wherein The starting symbol index in the first PUCCH resource configuration represents the relative position within the first sub-slot rather than the symbol index within the time slot.

3. A base station device, characterized in that, Comprising A high-layer processor configured to determine a Physical Uplink Control Channel (PUCCH) resource in a first sub-slot for HARQ-ACK feedback corresponding to a Physical Downlink Shared Channel (PDSCH) transmission of Ultra-Reliable Low-Latency Communication (URLLC), the HARQ-ACK feedback corresponding to the PDSCH transmission being associated with the highest priority, the first sub-slot being configured within a time slot; And A receiving circuit configured to receive, based on the determined PUCCH resource, the HARQ-ACK feedback corresponding to the PDSCH transmission associated with the highest priority, wherein The PUCCH resource is determined based on a first PUCCH resource configuration, Multiple possible sub-slot structures for HARQ-ACK PUCCH resource allocation within the time slot are defined, wherein All sub-slots within the time slot have the same duration in one or more of the possible sub-slot structures, and The first sub-slot and other sub-slots within the time slot have different durations in the remaining possible sub-slot structures, and The base station device is configured with a sub-slot configuration indicating one of the multiple possible sub-slot structures.

4. The base station device according to claim 3, wherein The starting symbol index in the first PUCCH resource configuration represents the relative position within the first sub-slot rather than the symbol index within the time slot.

5. A method performed by a user equipment UE, the method comprising: Determining a physical uplink control channel PUCCH resource in a first sub-slot for HARQ-ACK feedback corresponding to a physical downlink shared channel PDSCH transmission of ultra-reliable low-latency communication URLLC, the HARQ-ACK feedback corresponding to the PDSCH transmission being associated with the highest priority, the first sub-slot being configured in a time slot; And Transmitting, based on the determined PUCCH resource, the HARQ-ACK feedback corresponding to the PDSCH transmission associated with the highest priority, wherein, The UE is configured with a first PUCCH resource configuration for the HARQ-ACK feedback in the first sub-slot, The PUCCH resource is determined based on the first PUCCH resource configuration, A plurality of possible sub-slot structures for HARQ-ACK PUCCH resource allocation in the time slot are defined, wherein, All sub-slots in the time slot have the same duration in one or more of the possible sub-slot structures, and The first sub-slot and other sub-slots in the time slot have different durations in the remaining possible sub-slot structures, and The UE is configured with a sub-slot configuration indicating one of the plurality of possible sub-slot structures.

6. A method performed by a base station device, the method comprising: Determining a physical uplink control channel PUCCH resource in a first sub-slot for HARQ-ACK feedback, the HARQ-ACK feedback corresponding to a physical downlink shared channel PDSCH transmission of ultra-reliable low-latency communication URLLC and the HARQ-ACK feedback being associated with the highest priority, the first sub-slot being configured in a time slot; And Receiving, based on the determined PUCCH resource, the HARQ-ACK feedback corresponding to the PDSCH transmission associated with the highest priority, wherein, The PUCCH resource is determined based on a first PUCCH resource configuration, A plurality of possible sub-slot structures for HARQ-ACK PUCCH resource allocation in the time slot are defined, wherein, All sub-slots in the time slot have the same duration in one or more of the possible sub-slot structures, and The first sub-slot and other sub-slots in the time slot have different durations in the remaining possible sub-slot structures, and The base station device is configured with a sub-slot configuration indicating one of the plurality of possible sub-slot structures.

Images