Uplink control information processing for sub-slots

By performing PUCCH transmission scheduling and priority management in the sub-time slot in the 3GPP NR standard, the problem of overlapping PUCCH transmission in the sub-time slot is solved, coverage and efficiency are improved, and the reliability of HARQ-ACK feedback is enhanced.

CN114073028BActive Publication Date: 2024-11-08TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080047948.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-03
Filing Date
2020-05-04
Publication Date
2024-11-08
Estimated Expiration
2040-05-04

AI Technical Summary

Technical Problem

In the 3GPP NR standard, there is a problem of time overlap between PUCCH transmission in the sub-time slot, resulting in reduced coverage and conflicts, affecting the efficiency of HARQ-ACK feedback.

Method used

By implementing a scheduling mechanism within the sub-time slot between network nodes and wireless devices, PUCCH transmission is restricted from transmitting within a single sub-time slot, and prioritization and K1 value scheduling rules are adopted when conflicts occur, ensuring that PUCCH transmission does not span multiple sub-times to avoid overlapping time.

Benefits of technology

It effectively avoids the time overlap of PUCCH transmission, improves the efficiency of coverage range and HARQ-ACK feedback, prevents resource conflicts, and enhances the reliability of wireless communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114073028B_ABST
    Figure CN114073028B_ABST
Patent Text Reader

Abstract

A method, a network node and a wireless device for scheduling PUCCH transmissions longer than a sub-slot so that different PUCCH transmissions do not overlap in time are disclosed. According to one aspect, a method in a network node includes: scheduling a physical uplink control channel PUCCH transmission on a per-sub-slot basis. The method also includes: sending a physical downlink channel to a wireless device WD on a per-sub-slot basis, the physical downlink channel having an indication of a sub-slot for sending the PUCCH transmission according to the schedule.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular, to uplink control information (UCI) processing for sub-slots. Background Art

[0002] The New Radio (NR) (also referred to as "5G") standard of the Third Generation Partnership Project (3GPP) is designed to provide services for a variety of use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and machine-type communications (MTC). Each of these services has different technical requirements. For example, the general requirements for eMBB are high data rates with medium latency and medium coverage, while URLLC services require low latency and high reliability transmission for possibly medium data rates.

[0003] One of the solutions for low-latency data transmission is shorter transmission time intervals. In NR, in addition to transmission in time slots, micro-slot transmission is also allowed to reduce latency. Figure 1 is a diagram showing multiple resource elements for NR transmission. A mini-slot can consist of 2, 4, or 7 orthogonal frequency division multiplexing (OFDM) symbols, and in the uplink (UL), a mini-slot can be any number (1 to 14) of OFDM symbols. It should be noted that the concept of slots and mini-slots is not specific to a particular service, which means that mini-slots can be used for eMBB, URLLC, or other services.

[0004] Downlink control information

[0005] In the 3GPP NR standard, downlink control information (DCI) transmitted in a physical downlink control channel (PDCCH) is used to indicate downlink (DL) data related information, UL related information, power control information, slot format indication, etc. There are different formats of DCI associated with each of these control signals, and a wireless device (WD) recognizes these formats based on different radio network temporary identifiers (RNTIs).

[0006] WD is configured by high-layer signaling to use different periods to monitor DCI in different resources, etc. DCI formats 1_0 and 1_1 are used to schedule downlink (DL) data transmitted in the physical downlink shared channel (PDSCH), and include time and frequency resources for DL ​​transmission as well as modulation and coding information, HARQ (Hybrid Automatic Repeat Request) information, etc.

[0007] HARQ Feedback

[0008] The process for receiving downlink transmissions is that the WD first monitors and decodes the PDDCH in time slot "n", which points to the DL data scheduled in time slot n+K0 time slots, where K0 is greater than or equal to 0. The WD then decodes the data in the corresponding PDSCH. Finally, based on the results of the decoding, the WD sends a correctly decoded confirmation (ACK) or negative confirmation (NACK) to the base station (gNB, also referred to as the network node in this article) in time slot n+K0+K1 (in the case of time slot aggregation, n+K0 will be replaced with the time slot where the PDSCH ends). Both K0 and K1 are indicated in the downlink DCI. The resources used to send the confirmation are indicated by the physical uplink control channel (PUCCH) resource indicator (PRI) field in the PDCCH, which points to the PUCCH resources configured by the higher layer in the PUCCH resources.

[0009] Depending on the DL / UL slot configuration, or whether carrier aggregation or code block group (CBG) transmission is used in DL, feedback for multiple PDSCHs may need to be multiplexed in one feedback. This is done by constructing the HARQ-ACK codebook. In NR, the WD can be configured to multiplex the ACK / NACK (A / N) bits using a semi-static codebook or a dynamic codebook.

[0010] A Type 1 or semi-static codebook has a bit sequence in which each element contains a possible allocated A / N bit from a particular timeslot, carrier, or transport block (TB). When the WD is configured with a code block group (CBG) and / or time domain resource allocation (TDRA) table with multiple entries, multiple bits are generated per timeslot and per transport block (TB). It is worth noting that the codebook is derived regardless of the actual PDSCH scheduling. The size and format of the semi-static codebook are pre-configured based on the mentioned parameters. The disadvantage of the semi-static HARQ ACK codebook is that the size is fixed, regardless of whether there is a transmission or whether bits are not reserved in the feedback matrix.

[0011] In the case where the WD has a TDRA table configured with multiple time domain resource allocation entries: the table can be pruned (i.e., entries can be deleted based on a specified algorithm) to derive a TDRA table containing only non-overlapping time domain allocations. Then 1 bit is reserved in the HARQ code block (CB) for each non-overlapping entry (assuming that the WD can support receiving multiple PDSCHs in one time slot).

[0012] To avoid reserving unnecessary bits in the semi-static HARQ codebook, in NR, the WD can be configured to use a type 2 or dynamic HARQ codebook, where the A / N bit is present only when there is a corresponding transmission scheduled. To avoid any confusion between the gNB and the WD about the number of PDSCHs for which the WD should send feedback, there is a counter downlink allocation indicator (DAI) field in the DL allocation. The DAI field represents the cumulative number of (serving cell, PDCCH opportunity) pairs in which PDSCHs were scheduled to the WD until the current PDCCH. In addition, there is another field called the total DAI, which, when present, gives the total number of all PDCCHs for the current PDCCH monitoring opportunity. The timing for sending HARQ feedback is determined based on both the PDSCH transmission slot (K0) of the reference PDCCH slot and the PUCCH slot (K1) containing the HARQ feedback.

[0013] Figure 2 The timeline in a scenario with two PDSCHs and one feedback is shown. In this example, a total of 4 PUCCH resources are configured, and the physical resource indicator (PRI) indicates PUCCH 2 to be used for HARQ feedback. The following explains how to select PUCCH 2 from the 4 PUCCH resources based on the procedures in 3GPP Release 15.

[0014] In NR 3GPP Release 15, a WD can be configured with up to 4 PUCCH resource sets for HARQ-ACK information transmission. Each set is associated with a series of uplink control information (UCI) payload bits including HARQ-ACK bits. The first PUCCH resource set is always associated with 1 or 2 HARQ-ACK bits and therefore includes only PUCCH formats 0 or 1 or both. The payload value range (minimum to maximum) for other PUCCH resource sets (if configured) is provided by the configuration, except for the maximum value of the last PUCCH resource set using the default value and the minimum value of the second set (which is 3). The first PUCCH resource set can include up to 32 PUCCH resources of format 0 or 1. Other sets can include up to 8 bits of format 2, 3 or 4.

[0015] As previously described, the WD may determine the time slot for sending the HARQ-ACK bit in the PUCCH corresponding to the PDSCH scheduled or activated by the DCI via the K1 value provided by the configuration or the field in the corresponding DCI. The WD forms a codebook based on the HARQ-ACK bits with the associated PUCCH in the same time slot via the corresponding K1 value. The WD may determine a PUCCH resource set for which the size of the codebook is within the corresponding range of the payload value associated with the set. In addition, if the set is configured with up to 8 PUCCH resources, the WD may determine the PUCCH resources in the set by the field in the last DCI associated with the corresponding PDSCH. If the set is the first set and is configured with more than 8 resources, the PUCCH resources in the set are determined by the field in the last DCI associated with the corresponding PDSCH and an implicit rule based on the control channel element (CCE).

[0016] PUCCH resources used for HARQ-ACK transmission may overlap in time with other PUCCH resources used for channel state information (CSI) and / or scheduling request (SR) transmission and PUSCH transmission in the time slot. In the case of overlapping PUCCH and / or PUSCH resources, the WD first resolves the overlapping PUCCH resources (if any) by determining the PUCCH resources carrying the total UCI (including HARQ-ACK bits) so that the UCI multiplexing timeline requirement is met. There may be partial or complete discarding of CSI bits (if any) to multiplex UCI in the determined PUCCH resources. Then, if the timeline requirement for UCI multiplexing is met, the WD resolves the overlap of PUCCH and PUSCH resources (if any) by multiplexing UCI on the PUSCH resources.

[0017] 3GPP considered the following:

[0018] Considerations:

[0019] In order to support multiple PUCCHs for HARQ-ACK within a time slot to construct a HARQ-ACK codebook, a sub-slot-based HARQ-ACK feedback process is supported:

[0020] An uplink (UL) time slot includes multiple sub-time slots. No more than one PUCCH carrying HARQ-ACK is sent starting in a sub-time slot;

[0021] PDSCH transmission is not limited by subslots (if any);

[0022] For Future Study (FFS): PDSCH to subslot association; and

[0023] For future study (FFS): whether to allow PUCCH to cross subslot boundaries; and

[0024] At least for Type II HARQ-ACK codebook, Rel-15 HARQ-codebook construction is applied in units of subslots:

[0025] ο Type I HARQ-ACK codebook is for future study;

[0026] Apply Release 15 PUCCH resource coverage procedure in sub-slot units;

[0027] • The number or length of UL sub-slots in a slot is WD-specific and semi-statically configured.

[0028] οFFS: The number of PUCCH transmissions carrying HARQ-ACK in a time slot is limited;

[0029] FFS: K1 definition; and

[0030] FFS: Details of PUCCH resource configuration and determination.

[0031] FFS: Whether to use "codebook-free HARQ" as a supplement.

[0032] FFS: Whether HARQ-ACK can be omitted if the latency requirement cannot be met.

[0033] FFS: PDSCH grouping and PHY identification for separate HARQ-ACK constructions for different service types.

[0034] In order to support multiple PUCCHs for HARQ-ACK within a slot for constructing a HARQ-ACK codebook, K1 is defined following the Release 15 method but in units of subslots.

[0035] When at least two HARQ-ACK codebooks are constructed simultaneously to support different service types for WDs, for both type I (if supported) and type II HARQ-ACK codebooks (if supported), and for dynamically scheduled PDSCHs, the WD may select a PHY identifier for identifying the HARQ-ACK codebook from the following:

[0036] Option 1: via DCI format;

[0037] Option 2: via RNTI

[0038] Option 3: via explicit indication in DCI (FFS: new field or reuse of existing field);

[0039] Option 4: via CORESET / search space;

[0040] FFS: Additional option for Type I HARQ-ACK codebook; and

[0041] FFS: For SPS PDSCH (including SPS release PDCCH).

[0042] There are problems in supporting PUCCH transmissions across sub-slot boundaries. Summary of the invention

[0043] Some embodiments advantageously provide methods, network nodes, and wireless devices for uplink control information (UCI) processing for sub-slots.For example, it should be noted that restricting PUCCH transmissions to be contained within sub-slots reduces coverage compared to allowing longer PUCCH transmissions.

[0044] Some embodiments allow PUCCH resources associated with a subslot to be partially or fully transmitted in a subsequent subslot. When different PUCCH transmissions overlap in time, some embodiments are governed by rules for handling UCI collisions. Some embodiments allow subslot PUCCH transmissions that span more than one subslot.

[0045] According to one aspect, a network node configured to communicate with a wireless device WD is provided. The network node comprises a processing circuit configured to schedule a physical uplink control channel PUCCH transmission on a per sub-slot basis. The network node further comprises a radio interface in communication with the processing circuit, the radio interface being configured to send a physical downlink channel to the WD on a per sub-slot basis, the physical downlink channel having an indication of a sub-slot for sending a PUCCH transmission according to the scheduling.

[0046] According to this aspect, in some embodiments, the network node further configures the WD with a common PUCCH resource set for a sub-time slot in a time slot. In some embodiments, the network node further configures the WD with a different PUCCH resource set for each sub-time slot in a time slot. In some embodiments, the physical downlink channel transmission includes a K1 value for each sub-time slot, the K1 value indicating the number of sub-time slots until the transmission of the corresponding PUCCH. In some embodiments, a K1 value is provided for multiple sub-time slots within a time slot, the K1 value indicating the number of time slots until the transmission of the same PUCCH in the sub-time slot. In some embodiments, the scheduling is performed to prevent the PUCCH resources associated with the sub-time slot from occupying orthogonal frequency division multiplexing OFDM symbols in early sub-time slots.

[0047] According to another aspect, a method in a network node configured to communicate with a wireless device WD is provided. The method comprises: scheduling a physical uplink control channel PUCCH transmission on a per sub-slot basis; and sending a physical downlink channel to the WD on a per sub-slot basis, the physical downlink channel having an indication of a sub-slot for sending the PUCCH transmission according to the scheduling.

[0048] According to this aspect, in some embodiments, the method further includes: configuring the WD with a common PUCCH resource set for a sub-time slot in a time slot. In some embodiments, the method further includes: configuring the WD with a different PUCCH resource set for each sub-time slot in a time slot. In some embodiments, the physical downlink channel transmission includes a K1 value for each sub-time slot, the K1 value indicating the number of sub-time slots until the transmission of the corresponding PUCCH. In some embodiments, a K1 value is provided for multiple sub-time slots within a time slot, the K1 value indicating the number of time slots until the transmission of the same PUCCH in the sub-time slot. In some embodiments, the scheduling is performed to prevent the PUCCH resources associated with the sub-time slot from occupying orthogonal frequency division multiplexing OFDM symbols in early sub-time slots.

[0049] According to yet another aspect, a WD configured to communicate with a network node is provided. The WD comprises: a radio interface configured to receive an indication of a sub-time slot for sending a physical uplink control channel PUCCH transmission. The WD further comprises: a processing circuit in communication with the radio interface, the processing circuit being configured to schedule the PUCCH transmission in the indicated sub-time slot.

[0050] According to this aspect, in some embodiments, if a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is discarded or postponed. In some embodiments, the PUCCH transmission is discarded or postponed based at least in part on the priority of the PUCCH transmission. In some embodiments, the processing circuit is also configured to: when two PUCCH transmissions overlap in time, multiplex hybrid automatic repeat request HARQ bits and schedule the HARQ bits for transmission in the later of the two PUCCH transmissions. In some embodiments, the multiplexing is performed only when there is sufficient time between the start of the earlier of the two PUCCH transmissions and the reception of an indication that triggers the later of the two PUCCH transmissions. In some embodiments, the multiplexing is performed only when the two PUCCH transmissions have the same priority. In some embodiments, the multiplexing is performed only when the two PUCCH transmissions are scheduled with the same type of K1 value indicating the subslot used for the PUCCH transmission. In some embodiments, when the occupied OFDM symbol of a PUCCH resource spans more than one time slot, the PUCCH resource is considered invalid. In some embodiments, the PUCCH resource whose OFDM symbol spans more than one time slot is truncated in time. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource is configured. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot associated with the PUCCH transmission.

[0051] According to another aspect, a method in a wireless device WD configured to communicate with a network node is provided. The method comprises: receiving an indication of a subslot for sending a Physical Uplink Control Channel PUCCH transmission; and scheduling the PUCCH transmission in the indicated subslot.

[0052] According to this aspect, in some embodiments, if a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is discarded or postponed. In some embodiments, the PUCCH transmission is discarded or postponed based at least in part on the priority of the PUCCH transmission. In some embodiments, the method further comprises: when two PUCCH transmissions overlap in time, multiplexing a hybrid automatic repeat request HARQ bit, and scheduling the HARQ bit for transmission in the later of the two PUCCH transmissions. In some embodiments, the multiplexing is performed only when there is sufficient time between the start of the earlier of the two PUCCH transmissions and the receipt of an indication that triggers the later of the two PUCCH transmissions. In some embodiments, the multiplexing is performed only when the two PUCCH transmissions have the same priority. In some embodiments, the multiplexing is performed only when the two PUCCH transmissions are scheduled with the same type of K1 value indicating the subslot used for the PUCCH transmission. In some embodiments, when the occupied orthogonal frequency division multiplexing OFDM symbol of the PUCCH resource spans more than one slot, the PUCCH resource is considered invalid. In some embodiments, orthogonal frequency division multiplexing OFDM symbols spanning PUCCH resources of more than one time slot are truncated in time. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource is configured. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot associated with the PUCCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The present embodiments and attendant advantages and features will be more readily understood and more fully appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, which are:

[0054] Figure 1 is a diagram illustrating a plurality of resource elements for NR transmission;

[0055] Figure 2 shows the timeline in a scenario with two PDSCHs and one feedback;

[0056] Figure 3 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0057] Figure 4is a block diagram of a host computer communicating with a wireless device via a network node over at least a partially wireless connection according to some embodiments of the present disclosure;

[0058] Figure 5 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0059] Figure 6 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0060] Figure 7 is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0061] Figure 8 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0062] Fig. 9 is a flow chart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0063] Fig.10 is a flow chart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

[0064] Fig.11 is a flow chart of an alternative exemplary process for uplink control information (UCI) processing for sub-slots in a network node according to the principles set forth herein;

[0065] Fig.12 is a flow chart of an alternative exemplary process for uplink control information (UCI) processing for sub-slots in a wireless device according to the principles set forth herein; and

[0066] Fig.13 An example is shown in which each PDSCH is associated with a specific subslot for HARQ feedback. DETAILED DESCRIPTION

[0067] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in a combination of apparatus components and processing steps related to uplink control information (UCI) processing for sub-time slots. Therefore, components are represented by conventional symbols in the drawings where appropriate, and only those specific details relevant to understanding the embodiments are shown so as not to obscure the present disclosure with details that are readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0068] As used herein, relational terms such as "first" and "second", "top" and "bottom" may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the concepts described herein. As used herein, the singular forms "one", "an", and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when used herein, the terms "include" and / or "comprise" specify the presence of stated characteristics, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other characteristics, integers, steps, operations, elements, components, and / or combinations thereof.

[0069] In the embodiments described herein, connection terms such as "in communication with..." may be used to indicate electrical communication or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will recognize that multiple components may interoperate, and modifications and variations are possible to achieve electrical communication and data communication.

[0070] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection (although not necessarily a direct one) and may include wired and / or wireless connections.

[0071] The term "network node" used herein may be any type of network node included in a radio network, and may also include any of the following: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a g-node B (gNB), an evolved node B (eNB or eNodeB), a node B, a multi-standard radio (MSR) radio node (e.g., MSRBS), a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. As used herein, the term "radio node" may also be used to denote a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0072] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) may be used interchangeably. The WD herein may be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0073] In addition, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, which can include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU) remote radio head (RRH).

[0074] Note that although terminology from one particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in the present disclosure, this should not be considered to limit the scope of the present disclosure to only the above-mentioned systems. Other wireless systems (including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM)) may also benefit from utilizing the concepts covered within the present disclosure.

[0075] It is also noted that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.

[0076] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will also be understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and will not be interpreted as an idealized or overly formal meaning unless explicitly defined as such herein.

[0077] Embodiments provide uplink control information (UCI) processing for subslots. Some embodiments employ scheduling PUCCH transmissions longer than a subslot so that different PUCCH transmissions do not overlap in time. According to one aspect, a network node is configured to schedule physical uplink control channel transmissions PUCCH to span more than one subslot of a slot according to at least one rule so that different PUCCH transmissions do not overlap in time. The network node is also configured to send the schedule to a WD.

[0078] Referring again to the drawings, wherein like elements are designated by like reference numerals, Figure 3, a schematic diagram of a communication system 10 according to an embodiment is shown, the communication system 10 is, for example, a 3GPP type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network 12 such as a radio access network and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage areas 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to or paged by the corresponding network node 16c. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16a. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is in the coverage area or a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0079] In addition, it is contemplated that the WD 22 may communicate with multiple network nodes 16 and multiple types of network nodes 16 simultaneously and / or be configured to communicate with multiple network nodes 16 and multiple types of network nodes 16, respectively. For example, the WD 22 may have dual connectivity with a network node 16 supporting LTE and the same or different network node 16 supporting NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0080] The communication system 10 itself can be connected to a host computer 24, which can be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 can extend directly from the core network 14 to the host computer 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be one of a public, private, or managed network, or a combination of more than one of them. The intermediate network 30 (if any) can be a backbone network or the Internet. In some embodiments, the intermediate network 30 can include two or more sub-networks (not shown).

[0081] Overall, Figure 3The communication system realizes the connectivity between one of the connected WD 22a, 22b and the host computer 24. The connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, 22b are configured to use the access network 12, the core network 14, any intermediate network 30 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent because at least some of the participating communication devices through which the OTT connection passes do not know the routes of the uplink and downlink communications. For example, the network node 16 may not be notified or does not need to be notified of the past routes of the incoming downlink communications with data from the host computer 24 to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to know the future routes of the outgoing uplink communications from the WD 22a to the host computer 24.

[0082] The network node 16 is configured to include a transmission scheduler unit 32 configured to schedule Physical Uplink Control Channel PUCCH transmissions on a per sub-slot basis. The wireless device 22 is configured to receive an indication of a sub-slot for sending a Physical Uplink Control Channel PUCCH transmission.

[0083] According to one embodiment, reference will now be made to Figure 4 An example implementation of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or in place of a processor (e.g., a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0084] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or cause these methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein for host computer 24. The instructions may be software associated with host computer 24.

[0085] The software 48 may be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 is operable to provide services to remote users such as WD 22 connected via an OTT connection 52 terminated at the WD 22 and the host computer 24. When providing services to remote users, the host application 50 may provide user data sent using the OTT connection 52. "User data" may be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider, and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, send and / or receive from the network node 16 and / or wireless device 22 to the network node 16 and / or wireless device 22.

[0086] The communication system 10 also includes a network node 16 disposed in the communication system 10, and the network node 16 includes hardware 58 that enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to the interface of different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 with the host computer 24. The connection 66 may be direct, or the connection 66 may pass through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0087] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, in addition to or in place of a processor (e.g., a central processing unit) and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0088] Thus, the network node 16 also has software 74, which is stored internally, for example, in the memory 72, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) that can be accessed by the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any method and / or process described herein and / or cause these methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the processes described herein for the network node 16. For example, the processing circuitry 68 of the network node 16 may include a transmission scheduler unit 32 configured to schedule Physical Uplink Control Channel transmissions PUCCH to span more than one subslot of a timeslot according to at least one rule such that different PUCCH transmissions do not overlap in time.

[0089] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0090] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor (e.g., a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 86 may be configured to access (e.g., write and / or read) the memory 88, which may include any kind of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0091] Therefore, WD 22 may also include software 90, which is stored in, for example, a memory 88 at WD 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. Software 90 may be executed by processing circuit 84. Software 90 may include client application 92. Client application 92 is operable to provide services to human or non-human users via WD 22 with the support of host computer 24. In host computer 24, the executing host application 50 may communicate with the executing client application 92 via an OTT connection 52 terminated at WD 22 and host computer 24. When providing services to users, client application 92 may receive request data from host application 50 and provide user data in response to the request data. OTT connection 52 may transmit both request data and user data. Client application 92 may interact with the user to generate the user data it provides.

[0092] The processing circuit 84 may be configured to control any method and / or process described herein and / or cause these methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88, which is configured to store data, programming software codes, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the process described herein for the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a radio interface 82, which is configured to receive a schedule for causing a physical uplink control channel transmission PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time.

[0093] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Figure 4 shown, and independently, the surrounding network topology can be Figure 3 The surrounding network topology.

[0094] exist Figure 4 In the figure, the OTT connection 52 has been abstractly drawn to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicitly referencing any intermediate devices and the exact routing of the messages via these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the WD 22 or from the service provider operating the host computer 24, or both. When the OTT connection 52 is active, the network infrastructure can further make a decision according to which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0095] The wireless connection 64 between WD 22 and network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to WD 22 using OTT connection 52 (wherein the wireless connection 64 can form the final segment). More specifically, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, relaxed file size restrictions, better responsiveness, and extended battery life.

[0096] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22. The measurement process and / or network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 52 passes or is associated with such a communication device; the sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc. The reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be achieved because the software 48, 90 causes the OTT connection 52 to be used to send messages, particularly empty or "dummy" messages, during its monitoring of propagation time, errors, etc.

[0097] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data, and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / end a transmission to the WD 22, and / or to prepare / terminate / maintain / support / end receipt of a transmission from the WD 22.

[0098] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from a transmission from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / end a transmission to network node 16, and / or to prepare / terminate / maintain / support / end receipt of a transmission from network node 16.

[0099] although Figure 3 and 4Various "units" (e.g., transmission scheduler unit 32) are shown as being within respective processors, but it is contemplated that these units may be implemented so that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or in a combination of hardware and software.

[0100] Figure 5 FIG. 1 is a diagram showing a communication system (eg Figure 3 and 4 24, a network node 16, and a WD 22, which may be reference Figure 4 1 and 2. The method of claim 1 further includes a method for transmitting a user data to a network node 16 and a WD 22. In the first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides user data by executing a host application (e.g., host application 50) (block S102). In a second step, the host computer 24 initiates a transmission carrying user data to the WD 22 (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (block S106). In an optional fourth step, the WD 22 executes a client application (e.g., client application 92) associated with the host application 50 executed by the host computer 24 (block S108).

[0101] Figure 6 FIG. 1 is a diagram showing a communication system (eg Figure 3 24, a network node 16, and a WD 22, which may be reference Figure 3 and 4 1 and 2. The method further includes a host computer 24, a network node 16, and a WD 22 as described above. In a first step of the method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides user data by executing a host application (e.g., host application 50). In a second step, the host computer 24 initiates a transmission carrying user data to the WD 22 (block S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission may pass through the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0102] Figure 7 FIG. 1 is a diagram showing a communication system (eg Figure 324, a network node 16, and a WD 22, which may be reference Figure 3 and 4 Those host computers 24, network nodes 16 and WD 22 described above. In the optional first step of the method, WD 22 receives input data provided by the host computer 24 (box S116). In the optional sub-step of the first step, WD 22 executes the client application 92, and the client application 92 provides user data in response to the received input data provided by the host computer 24 (box S118). Additionally or alternatively, in the optional second step, WD 22 provides user data (box S120). In the optional sub-step of the second step, WD provides user data by executing a client application (e.g., client application 92) (box S122). When providing user data, the executed client application 92 can further consider the user input received from the user. Regardless of the specific manner of providing user data, WD 22 can initiate the transmission of user data to the host computer 24 in an optional third sub-step (box S124). In a fourth step of the method, host computer 24 receives user data sent from WD 22 (block S126 ) in accordance with the teachings of the embodiments described throughout this disclosure.

[0103] Figure 8 FIG. 1 is a diagram showing a communication system (eg Figure 3 24, a network node 16, and a WD 22, which may be reference Figure 3 and 4 1 and 2. In an optional first step of the method, the network node 16 receives user data from the WD 22 in accordance with the teachings of the embodiments described throughout the present disclosure (block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0104] Fig. 91 is a flow chart of an exemplary process in a network node 16 according to an embodiment described herein. One or more blocks described herein may be performed by one or more units of the network node 16, for example, by one or more of the processing circuit 68 (including the transmission scheduler unit 32), the processor 70, the radio interface 62 and / or the communication interface 60. The network node 16 is configured, for example, via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60, to schedule physical uplink control channel transmissions PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time (block S134). The process also includes causing the scheduling to be sent to the WD (block S136).

[0105] Fig.10 is a flow chart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more units of the wireless device 22, for example, by one or more of the processing circuit 84, the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured, for example, via the processing circuit 84 and / or the processor 86 and / or the radio interface 82, to receive a schedule for causing a physical uplink control channel transmission PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time (block S138). The process also includes sending a PUCCH transmission according to the schedule (block S140).

[0106] Fig.11 1 is a flow chart of an exemplary process in a network node 16 according to the principles set forth herein. One or more blocks described herein may be performed by one or more units of the network node 16, for example, by one or more of the processing circuit 68 (including the transmission scheduler unit 32), the processor 70, the radio interface 62 and / or the communication interface 60. The network node 16 is configured, for example, via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60, to schedule physical uplink control channel PUCCH transmissions on a per-subslot basis (block S142). The process also includes sending a physical downlink channel to the WD 22 on a per-subslot basis, the physical downlink channel having an indication of a subslot for sending PUCCH transmissions according to the schedule (block S144).

[0107] Fig.12is a flow chart of an exemplary process in WD 22 according to the principles set forth herein. One or more blocks described herein may be performed by one or more units of wireless device 22, such as by one or more of processing circuit 84, processor 86, radio interface 82, and / or communication interface 60. Wireless device 22 is configured, for example, via processing circuit 84 and / or processor 86 and / or radio interface 82, to receive an indication of a sub-slot for transmitting a physical uplink control channel PUCCH transmission (block S146). The process also includes scheduling a PUCCH transmission in the indicated sub-slot (block S148).

[0108] Having described the general process flow of the arrangements of the present disclosure and provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following section provides details and examples of arrangements for uplink control information (UCI) processing of sub-slots.

[0109] Fig.13 An example is shown in which each PDSCH is associated with a specific subslot by using a K1 value in units of subslots for HARQ feedback.

[0110] For power limited WDs, it may be useful to be able to schedule longer PUCCHs to increase coverage. Thus, allowing PUCCH transmissions to span more than one subslot may be useful.

[0111] In one embodiment, WD 22 determines the PUCCH to use based on the UCI payload associated with the subslot, for example, via processing circuitry 84. This payload may exclude UCI corresponding to low priority traffic in UL transmissions that are dropped or deferred for other reasons.

[0112] In one embodiment, different sub-timeslots may be associated with different PUCCH resources. In one embodiment, PUCCH resources associated with a sub-timeslot are not allowed to occupy OFDM symbols in an earlier sub-timeslot. In one embodiment, PUCCH resources associated with a sub-timeslot are allowed to occupy OFDM symbols in a later sub-timeslot within the same time slot. Note that allowing a sub-timeslot to occupy OFDM symbols in a later sub-timeslot can sometimes result in collisions between scheduled PUCCH transmissions.

[0113] In one embodiment, it is undesirable for WD 22 to be scheduled to have PUCCH transmissions that start in different sub-slots that overlap in time. In one embodiment, when two PUCCH transmissions overlap in time, WD 22 may drop or defer one of the two transmissions. In one version of this embodiment, when WD 22 should drop or defer the PUCCH transmission that started earlier, WD 22 does so only if there is sufficient time between when WD 22 should stop sending the earlier PUCCH transmission and when WD 22 receives a schedule that triggers the later PUCCH transmission.

[0114] In one embodiment, when two PUCCH transmissions overlap in time, WD 22 may defer one of the two transmissions and send the deferred transmission at a later time.

[0115] In one embodiment, which of the two PUCCH transmissions to drop or postpone may be based on a priority associated with at least one of the two transmissions. The PUCCH transmission with the lowest priority or no priority may be dropped or postponed. In one embodiment, when two PUCCH transmissions overlap, WD 22 may drop or postpone the earlier scheduled transmission.

[0116] In one embodiment, some services are scheduled by using K1 values ​​of slots rather than subslots. In this case, when determining rules for dropping or deferring due to PUCCH collisions, WD 22 should treat HARQ feedback fed back in a slot as belonging to all subslots of the slot.

[0117] In an embodiment, when two PUCCH transmissions overlap in time, WD 22 multiplexes the HARQ-ACK bits and sends them in the PUCCH resources corresponding to the PUCCH in the later subslot. For example, the HARQ-ACK bits of two PUCCHs may be multiplexed and sent on the PUCCH resources in subslot n+1. The new PUCCH resources may be determined based on the PUCCH resource indicator associated with the last DCI that schedules / activates the PDSCH (which has a corresponding PUCCH in the later subslot). The PUCCH resource indicator points to the PUCCH resource index of the PUCCH resource set determined by the number of aggregated HARQ-ACK bits.

[0118] In one version of the above embodiment, WD 22 may multiplex the HARQ-ACK information only if there is sufficient time between the start of the earlier PUCCH transmission and WD 22 receiving the schedule that triggers the later PUCCH transmission.

[0119] In one embodiment, the multiplexing of HARQ-ACK bits of two PUCCHs overlapping in time (as in the above embodiment) depends on the priorities associated with the two PUCCH transmissions. For example, multiplexing is performed only when the two PUCCH transmissions have the same priority.

[0120] In one embodiment, the multiplexing of HARQ-ACK bits of two PUCCHs that overlap in time (as in the above-described embodiments) may depend on the type of K1 values ​​of the two PUCCH transmissions, i.e., in units of slots or subslots. For example, multiplexing is performed only when two PUCCH transmissions are scheduled using K1 values ​​of the same unit type (e.g., K1 associated with the two PUCCHs is in units of subslots).

[0121] PUCCH resource configuration

[0122] In one embodiment, WD 22 may be configured with a separate PUCCH resource set for each subslot in a time slot. In one embodiment, WD 22 may be configured with a common PUCCH resource set for all subslots in a time slot. In one version of this embodiment, an additional subslot-specific PUCCH resource set is configured for each subslot in a time slot. The PUCCH resources in the subslot-specific PUCCH resource set may or may not be included in the common PUCCH resource set. In one embodiment, when the occupied OFDM symbols of a certain PUCCH resource span more than one time slot, the PUCCH resource may be considered invalid. In another embodiment, the PUCCH resources whose occupied OFDM symbols span more than one time slot are truncated in time so that they do not cross the time slot boundary. In one embodiment, the starting symbol of a PUCCH resource in a time slot may be given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the subslot for which the resource set is configured. In one embodiment, for example, by using a K1 signal, the starting symbol of a PUCCH resource in a time slot may be given by the starting symbol configured in the PUCCH resource plus the starting symbol of the subslot associated with the PUCCH transmission in the time slot.

[0123] Therefore, some embodiments allow PUCCH transmissions spanning more than one subslot while resolving potential collision issues.

[0124] According to one aspect, a network node 16 configured to communicate with a wireless device (WD) 22 is provided. The network node 16 includes a processing circuit 68 configured to schedule a physical uplink control channel PUCCH transmission on a per sub-slot basis. The network node 16 also includes a radio interface 62 in communication with the processing circuit 68, the radio interface configured to send a physical downlink channel to the WD 22 on a per sub-slot basis, the physical downlink channel having an indication of a sub-slot for sending a PUCCH transmission according to the schedule.

[0125] According to this aspect, in some embodiments, the network node 16 also configures the WD 22 via the radio interface 62 a common PUCCH resource set for a sub-time slot in a time slot. In some embodiments, the starting symbol of the PUCCH resource in the time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource set is configured. In some embodiments, the network node 16 also configures the WD 22 via the radio interface 62 a different PUCCH resource set for each sub-time slot in the time slot. In some embodiments, the physical downlink channel transmission includes a K1 value for each sub-time slot, the K1 value indicating the number of sub-time slots until the transmission of the corresponding PUCCH. In some embodiments, a K1 value is provided for multiple sub-time slots within the time slot, the K1 value indicating the number of time slots until the transmission of the same PUCCH in the sub-time slot. In some embodiments, the scheduling is performed to prevent the PUCCH resources associated with the sub-time slot from occupying orthogonal frequency division multiplexing OFDM symbols in early sub-time slots.

[0126] According to another aspect, there is provided a method in a network node 16 configured to communicate with a wireless device (WD) 22. The method includes scheduling, via the processing circuit 68, a physical uplink control channel, PUCCH, transmission on a per sub-slot basis, and sending, via the radio interface 62, to the WD 22, a physical downlink channel, on a per sub-slot basis, the physical downlink channel having an indication of a sub-slot for sending the PUCCH transmission according to the schedule.

[0127] According to this aspect, in some embodiments, the method further comprises configuring WD 22 with a common PUCCH resource set for a sub-time slot in a time slot. In some embodiments, the starting symbol of the PUCCH resource in the time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource set is configured. In some embodiments, the method further comprises configuring WD 22 with a different PUCCH resource set for each sub-time slot in the time slot. In some embodiments, the physical downlink channel transmission includes a K1 value for each sub-time slot, the K1 value indicating the number of sub-time slots until the transmission of the corresponding PUCCH. In some embodiments, a K1 value is provided for multiple sub-time slots within the time slot, the K1 value indicating the number of time slots until the transmission of the same PUCCH in the sub-time slot. In some embodiments, the scheduling is performed to prevent the PUCCH resources associated with the sub-time slot from occupying orthogonal frequency division multiplexing OFDM symbols in early sub-time slots.

[0128] According to yet another aspect, there is provided a WD 22 configured to communicate with a network node 16. The WD 22 comprises a radio interface 82 configured to receive an indication of a sub-slot for transmitting a physical uplink control channel PUCCH transmission. The WD 22 also comprises a processing circuit 84 in communication with the radio interface, the processing circuit being configured to schedule the PUCCH transmission in the indicated sub-slot.

[0129] According to this aspect, in some embodiments, if a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is discarded or postponed. In some embodiments, the PUCCH transmission is discarded or postponed based at least in part on the priority of the PUCCH transmission. In some embodiments, the processing circuit 84 is also configured to: when two PUCCH transmissions overlap in time, multiplex the hybrid automatic repeat request HARQ bit, and schedule the HARQ bit for transmission in the later of the two PUCCH transmissions. In some embodiments, multiplexing is performed only when there is sufficient time between the start of the earlier of the two PUCCH transmissions and the reception of the indication that triggers the later of the two PUCCH transmissions. In some embodiments, multiplexing is performed only when the two PUCCH transmissions have the same priority. In some embodiments, multiplexing is performed only when two PUCCH transmissions are scheduled with the same type of K1 value indicating the sub-slot used for PUCCH transmission. In some embodiments, when the occupied orthogonal frequency division multiplexing OFDM symbol of the PUCCH resource spans more than one time slot, the PUCCH resource is considered invalid. In some embodiments, orthogonal frequency division multiplexing OFDM symbols spanning PUCCH resources of more than one time slot are truncated in time. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource is configured. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot associated with the PUCCH transmission.

[0130] According to another aspect, there is provided a method in a wireless device (WD) 22 configured to communicate with a network node 16. The method comprises receiving, via a radio interface 82, an indication of a sub-slot for sending a physical uplink control channel, PUCCH, transmission, and scheduling, via a processing circuit 84, the PUCCH transmission in the indicated sub-slot.

[0131] According to this aspect, in some embodiments, if a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is discarded or postponed. In some embodiments, the PUCCH transmission is discarded or postponed based at least in part on the priority of the PUCCH transmission. In some embodiments, the method further comprises: when two PUCCH transmissions overlap in time, multiplexing a hybrid automatic repeat request HARQ bit via processing circuit 84, and scheduling the HARQ bit for transmission in the later of the two PUCCH transmissions. In some embodiments, multiplexing is performed only when there is sufficient time between the start of the earlier of the two PUCCH transmissions and the reception of an indication that triggers the later of the two PUCCH transmissions. In some embodiments, multiplexing is performed only when the two PUCCH transmissions have the same priority. In some embodiments, multiplexing is performed only when two PUCCH transmissions are scheduled with the same type of K1 value indicating a subslot for PUCCH transmission. In some embodiments, when the occupied orthogonal frequency division multiplexing OFDM symbol of the PUCCH resource spans more than one slot, the PUCCH resource is considered invalid. In some embodiments, orthogonal frequency division multiplexing OFDM symbols spanning PUCCH resources of more than one time slot are truncated in time. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot for which the PUCCH resource is configured. In some embodiments, the starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the sub-time slot associated with the PUCCH transmission.

[0132] According to one aspect, a network node 16 configured to communicate with a wireless device (WD) 22 is provided. The network node includes a processing circuit 68 configured to schedule a physical uplink control channel transmission PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time. The processing circuit 68 is also configured to cause the scheduling to be sent to the WD 22.

[0133] According to this aspect, in some embodiments, a PUCCH transmission is dropped or postponed if it overlaps in time with another PUCCH transmission.In some embodiments, when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or postponed.

[0134] According to another aspect, a method in a network node 16 is provided. The method comprises scheduling a physical uplink control channel transmission PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time. The method also comprises sending the schedule to a wireless device WD 22.

[0135] According to this aspect, in some embodiments, a PUCCH transmission is dropped or postponed if it overlaps in time with another PUCCH transmission.In some embodiments, when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or postponed.

[0136] According to yet another aspect, a WD 22 configured to communicate with a network node includes a radio interface 82 and a processing circuit 84, the processing circuit 84 being configured to receive a schedule for causing a physical uplink control channel transmission PUCCH to span more than one sub-slot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time. The radio interface 82 is also configured to send the PUCCH transmission according to the schedule.

[0137] According to this aspect, in some embodiments, a PUCCH transmission is dropped or postponed if it overlaps in time with another PUCCH transmission.In some embodiments, when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or postponed.

[0138] According to another aspect, a method implemented in a wireless device (WD) 22 is provided. The method includes receiving a schedule for causing a physical uplink control channel transmission, PUCCH, to span more than one subslot of a time slot according to at least one rule so that different PUCCH transmissions do not overlap in time. The method includes sending the PUCCH transmission according to the schedule.

[0139] According to this aspect, in some embodiments, a PUCCH transmission is dropped or postponed if it overlaps in time with another PUCCH transmission.In some embodiments, when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or postponed.

[0140] Some examples include:

[0141] Embodiment A1. A network node configured to communicate with a wireless device (WD), the network node being configured to and / or comprising a radio interface and / or comprising a processing circuit configured to:

[0142] scheduling a physical uplink control channel transmission, PUCCH, to span more than one sub-slot of a time slot according to at least one rule such that different PUCCH transmissions do not overlap in time; and

[0143] The schedule is sent to WD.

[0144] Embodiment A2. The network node of Embodiment A1, wherein a PUCCH transmission is dropped or postponed if the PUCCH transmission overlaps in time with another PUCCH transmission.

[0145] Embodiment A3. The network node of Embodiment A1, wherein when PUCCH transmissions overlap in time, an earlier one of the PUCCH transmissions is dropped or deferred.

[0146] Embodiment B1. A method implemented in a network node, the method comprising:

[0147] scheduling a physical uplink control channel transmission, PUCCH, to span more than one sub-slot of a time slot according to at least one rule such that different PUCCH transmissions do not overlap in time; and

[0148] The schedule is sent to the wireless device WD.

[0149] Embodiment B2. The method of embodiment B1, wherein a PUCCH transmission is dropped or postponed if the PUCCH transmission overlaps in time with another PUCCH transmission.

[0150] Embodiment B3. The method of embodiment B1, wherein when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or deferred.

[0151] Embodiment C1. A wireless device (WD) configured to communicate with a network node, the WD being configured to and / or comprising a radio interface and / or a processing circuit configured to:

[0152] receiving a schedule for causing a physical uplink control channel transmission, PUCCH, to span more than one subslot of a time slot according to at least one rule such that different PUCCH transmissions do not overlap in time; and

[0153] PUCCH transmissions are sent according to the schedule.

[0154] Embodiment C2. The WD of embodiment C1, wherein a PUCCH transmission is dropped or postponed if the PUCCH transmission overlaps in time with another PUCCH transmission.

[0155] Embodiment C3. The WD of Embodiment C1, wherein when PUCCH transmissions overlap in time, an earlier one of the PUCCH transmissions is dropped or deferred.

[0156] Embodiment D1. A method implemented in a wireless device (WD), the method comprising:

[0157] receiving a schedule for causing a physical uplink control channel transmission, PUCCH, to span more than one subslot of a time slot according to at least one rule such that different PUCCH transmissions do not overlap in time; and

[0158] PUCCH transmissions are sent according to the schedule.

[0159] Embodiment D2. The method of embodiment D1, wherein a PUCCH transmission is dropped or postponed if the PUCCH transmission overlaps in time with another PUCCH transmission.

[0160] Embodiment D3. The method of embodiment D1, wherein when PUCCH transmissions overlap in time, the earlier of the PUCCH transmissions is dropped or deferred.

[0161] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects, all of which are generally referred to herein as "circuits" or "modules." Any process, step, action, and / or function described herein may be performed and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium, which contains a computer program code that may be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0162] Some embodiments are described herein with reference to the flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each square block of the flowchart and / or block diagram, and the combination of square blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (to thereby produce a special-purpose computer), a processor of a special-purpose computer or other programmable data processing device to produce a machine, so that these instructions, when executed via a processor of a computer or other programmable data processing device, produce a device that implements the function / operation specified in one or more square blocks in the flowchart and / or block diagram.

[0163] These computer program instructions may also be stored in a computer-readable memory or storage medium, which may cause a computer or other programmable data processing device to work in a specific manner so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions / operations specified in one or more blocks in the flowchart and / or block diagram.

[0164] Computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps to implement the functions / operations specified in one or more boxes in the flowchart and / or block diagram.

[0165] It will be understood that the functions / actions noted in the blocks may occur in a different order than that noted in the operational diagram. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in the opposite order, depending on the functions / actions involved. Although some figures include arrows on the communication paths to illustrate the primary direction of communication, it will be understood that communication may occur in the opposite direction to the arrows shown.

[0166] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language (e.g. The computer program code for performing the operations of the present disclosure may be written in a conventional procedural programming language (e.g., C++). However, the computer program code for performing the operations of the present disclosure may also be written in a conventional procedural programming language (e.g., the "C" programming language). The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer, partially on a remote computer, or entirely on the remote computer. In the case of a remote computer, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet).

[0167] Many different embodiments have been disclosed herein in conjunction with the above description and accompanying drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be overly repetitive and confusing. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the accompanying drawings will be interpreted as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, as well as the manner and process of making and using them, and will support claims to any such combination or subcombination.

[0168] Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise noted above, it should be noted that not all drawings are to scale. Based on the above teachings, various modifications and variations are possible without departing from the scope of the following claims.

Claims

1. A wireless device WD (22) configured to communicate with a network node (16), the WD (22) include: a radio interface (82) configured to receive an indication of subslots for transmitting a physical uplink control channel (PUCCH) transmission, wherein the physical downlink control channel reception includes a K1 value for each subslot indicating the number of subslots until transmission of the corresponding PUCCH; and A processing circuit (84) in communication with the radio interface, the processing circuit being configured to schedule the PUCCH transmission in the indicated sub-slot by multiplexing hybrid automatic repeat request acknowledgement HARQ-ACK bits of two PUCCH transmissions overlapping in time, the multiplexing depending on the type of K1 values ​​of the two PUCCH transmissions in units of time slots or sub-slots, wherein the multiplexing is performed only when the two PUCCH transmissions are scheduled with K1 values ​​of the same unit type.

2. The WD (22) according to claim 1, in, If a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is dropped or postponed.

3. The WD (22) according to claim 2, in, Based at least in part on the priority of the PUCCH transmission, the PUCCH transmission is dropped or deferred.

4. The WD (22) according to claim 1, in, The processing circuit (84) is further configured to: when two PUCCH transmissions overlap in time, multiplex hybrid automatic repeat request (HARQ) bits and schedule the HARQ bits for transmission in a later one of the two PUCCH transmissions.

5. The WD (22) according to claim 1, in, The multiplexing is performed only if there is sufficient time between the start of the earlier of the two PUCCH transmissions and the receipt of an indication triggering the later of the two PUCCH transmissions.

6. The WD (22) according to claim 1, in, The multiplexing is performed only when the two PUCCH transmissions have the same priority.

7. The WD (22) according to claim 1, in, When the occupied OFDM symbols of a PUCCH resource span more than one slot, the PUCCH resource is considered invalid.

8. The WD (22) according to claim 1, in, PUCCH resources where an OFDM symbol spans more than one slot are truncated in time.

9. The WD (22) according to claim 1, in, The starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the subslot for which the PUCCH resource is configured.

10. The WD (22) according to claim 1, in, The starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol of the sub-time slot associated with the PUCCH transmission in the time slot.

11. A method in a wireless device WD (22) configured to communicate with a network node (16), the method include: receiving an indication of subslots for sending a physical uplink control channel (PUCCH) transmission, wherein the physical downlink control channel reception includes a K1 value for each subslot indicating a number of subslots until transmission of a corresponding PUCCH; and The PUCCH transmission is scheduled in the indicated subslot by multiplexing the hybrid automatic repeat request confirmation HARQ-ACK bits of two PUCCH transmissions overlapping in time, the multiplexing depending on the type of K1 values ​​of the two PUCCH transmissions in units of time slots or subslots, wherein the multiplexing is performed only when the two PUCCH transmissions are scheduled with K1 values ​​of the same unit type.

12. The method according to claim 11, in, If a PUCCH transmission overlaps in time with another PUCCH transmission, the PUCCH transmission is dropped or postponed.

13. The method according to claim 12, in, Based at least in part on the priority of the PUCCH transmission, the PUCCH transmission is dropped or deferred.

14. The method according to claim 11, further comprising: include: When two PUCCH transmissions overlap in time, hybrid automatic repeat request HARQ bits are multiplexed and scheduled for transmission in a later one of the two PUCCH transmissions.

15. The method according to claim 11, in, The multiplexing is performed only if there is sufficient time between the start of the earlier of the two PUCCH transmissions and the receipt of an indication triggering the later of the two PUCCH transmissions.

16. The method according to claim 11, in, The multiplexing is performed only when the two PUCCH transmissions have the same priority.

17. The method according to claim 11, in, When the occupied OFDM symbols of a PUCCH resource span more than one slot, the PUCCH resource is considered invalid.

18. The method according to claim 11, in, PUCCH resources where an OFDM symbol spans more than one slot are truncated in time.

19. The method according to claim 11, in, The starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol in the time slot of the subslot for which the PUCCH resource is configured.

20. The method according to claim 11, in, The starting symbol of a PUCCH resource in a time slot is given by the starting symbol configured in the PUCCH resource plus the starting symbol of the sub-time slot associated with the PUCCH transmission in the time slot.