Solving physical uplink control channel collision in sub-slot

Abstract

A method, network node, and wireless device for resolving physical uplink control channel (PUCCH) collisions in sub-slots. According to one aspect, a wireless device (WD) is configured to remove candidate physical uplink control channel, PUCCH, resources from a sub-slot to resolve overlap of PUCCH resources in a slot. According to another aspect, a network node is configured to receive a physical uplink control channel, PUCCH, transmission, the PUCCH resources for the PUCCH transmission based at least in part on removing candidate PUCCH resources from a sub-slot to resolve overlap of PUCCH resources in a slot.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and in particular, to resolving Physical Uplink Control Channel (PUCCH) collisions in sub-time slots. Background Technology

[0002] The New Radio (NR) standard (also known as "5G"), defined by the 3rd Generation Partnership Project (3GPP), is designed to provide services for multiple 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 requirement for eMBB is high data rates under medium latency and medium coverage conditions, while URLLC services require low latency and high reliability transmission but may be geared towards medium data rates.

[0003] One solution for low-latency data transmission is shorter transmission intervals. In NR, in addition to transmission in time slots, microslot transmission is also allowed to reduce latency. Microslots are a concept used in scheduling, and in the downlink (DL), microslots can consist of 2, 4, or 7 segments, while in the uplink (UL), microslots can be any number of orthogonal frequency division multiplexing (OFDM) symbols from 1 to 14. It should be noted that the concepts of time slots and microslots are not specific to any particular service, meaning that microslots can be used for eMBB, URLLC, or other services. Figure 1 An exemplary radio resource with a subcarrier spacing of 15 kHz in NR is shown.

[0004] Uplink control information (UCI) is carried either by the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). It contains one or more uplink control information fields, namely DL acknowledgment (ACK / NACK), channel quality indicator (CQI), or scheduling request (SR).

[0005] If WD transmits user data in UL, then UCI is either transmitted on PUSCH or PUSCH. In this case, PUCCH transmission is not allowed. When there is no user data to transmit, UCI is carried on PUCCH.

[0006] The process for receiving downlink transmissions involves the WD first monitoring and decoding the PDCCH in slot n, which points to the DL data units scheduled in slots n+K0 (K0 is greater than or equal to 0). The WD then decodes the data in the corresponding Physical Downlink Shared Channel (PDSCH). Finally, based on the decoding result, the WD sends a correctly decoded acknowledgment (ACK) or negative acknowledgment (NACK) to the network node, such as the gNB, at slot n+K0+K1. Both K0 and K1 are indicated in the Downlink Control Information (DCI). The resource used for sending the acknowledgment is indicated by the PUCCH Resource Indicator (PRI) field in the PDCCH, which points to one of the PUCCH resources configured by a higher layer. Depending on the DL / UL slot configuration, or whether it is carrier aggregation or per-block group (CBG) transmission used in the DL, it may be necessary to multiplex the feedback of several PDSCHs in a single feedback. This is accomplished by constructing a HARQ-ACK codebook.

[0007] In 3GPP Release 16 (Rel-16), to allow for faster HARQ-ACK feedback, multiple PUCCHs carrying Hybrid Automatic Repeat Request (HARQ)-ACKs are allowed within a time slot. Each time slot is divided into multiple sub-slots, and at most, one PUCCH carrying a HARQ ACK can begin within each sub-slot. Figure 2 An example of a HARQ-ACK transmission sub-slot is shown.

[0008] Conflicts can occur between two PUCCHs or between a PUCCH and a PUSCH within a time slot. In 3GPP Release 15 Rel-15, there are predefined rules for resolving conflicts between multiple PUCCHs or between a PUCCH and a PUSCH. These rules are typically based on the multiplexing of UCIs within a single PUCCH or PUSCH resource. Timeline requirements for UCI multiplexing that should be met for the multiplexing desired by the WD are defined. However, 3GPP Rel-15 generally does not support different priorities in physical (PHY) channels for different UCI types. In 3GPP Rel-16, physical channels (e.g., PUSCH, PUCCH) can have different priority levels due to the different types of services they carry.

[0009] As explained above, when two PUCCHs overlap in time, the general solution in 3GPP Rel-15 is to multiplex the PUCCH into a new PUCCH. However, in 3GPP Rel-16, because multiple sub-slots can exist, each containing HARQ-ACK, it's possible that after the 3GPP Rel-15 process for resolving overlaps between PUCCH resources, multiplexing the PUCCH into a new PUCCH in the sub-slot might conflict with another PUCCH in the next sub-slot (if the selected PUCCH resource extends into the next sub-slot). Figure 3 To illustrate this, PUCCH1 and PUCCH2 overlap and are reused to form a new PUCCH1+PUCCH2, but this then conflicts with PUCCH3 in the next sub-slot. Summary of the Invention

[0010] Some embodiments advantageously provide methods, systems, and apparatus for resolving Physical Uplink Control Channel (PUCCH) conflicts in sub-time slots.

[0011] Methods for resolving conflicts between PUCCHs in different sub-slots are presented. More specifically, some embodiments provide at least:

[0012] a) Configure PUCCH resources so that they do not overlap;

[0013] b) Used for resolving overlapping PUCCHs in the first sub-slot. In this way, PUCCH resources from the next sub-slot that conflict with the PUCCH selected in the first sub-slot will not be considered from the candidate PUCCHs that can be used to resolve overlaps in the next sub-slot.

[0014] Some of the methods presented in this paper allow the transmission of multiple PUCCHs in a time slot without the risk of overlapping with PUCCHs from the next sub-time slot.

[0015] According to an aspect of this disclosure, a method implemented in a wireless device (WD) is provided. The method includes removing candidate Physical Uplink Control Channel (PUCCH) resources from a sub-slot to resolve overlap of PUCCH resources within the slot.

[0016] In some embodiments of this aspect, the candidate PUCCH resource extends from the sub-time slot to the next sub-time slot, and removing the candidate PUCCH resource includes removing the candidate PUCCH resource extending from the sub-time slot to the next sub-time slot. In some embodiments of this aspect, the candidate PUCCH resource extends from the next sub-time slot and overlaps with a PUCCH extending from the first sub-time slot to the next sub-time slot, and removing the candidate PUCCH resource includes removing the candidate PUCCH resource extending from the next sub-time slot that overlaps with a PUCCH extending from the first sub-time slot to the next sub-time slot.

[0017] In some embodiments of this aspect, the method further includes: selecting a PUCCH resource to transmit at least one uplink control information (UCI) message in a first sub-time slot; and extending the candidate PUCCH resource from the next sub-time slot; and removing the candidate PUCCH resource includes removing the candidate PUCCH resource extending from the next sub-time slot based at least in part on the PUCCH resource selected in the first sub-time slot. In some embodiments of this aspect, removing the candidate PUCCH resource includes removing candidate PUCCH resources extending from the next sub-time slot that overlap with the PUCCH resource selected in the first sub-time slot. In some embodiments of this aspect, each PUCCH resource is configured to reside within a single sub-time slot.

[0018] In some embodiments of this invention, the method further includes determining whether the WD processing timeline of uplink control information (UCI) messages multiplexed with the Physical Uplink Shared Channel (PUSCH) is satisfied, with overlapping resolution based at least in part on the determination. In some embodiments of this invention, the method includes multiplexing UCI messages on the Physical Uplink Shared Channel (PUSCH) at least in part on the determination. In some embodiments of this invention, the method includes reserving the later of the PUSCH and UCI messages for transmission and discarding the earlier of the PUSCH and UCI messages at least in part on the determination. In some embodiments of this invention, the method includes reserving the PUSCH and UCI messages with a first priority for transmission and discarding the other of the PUSCH and UCI messages with a lower priority than the first priority at least in part on the determination.

[0019] In some embodiments of this aspect, uplink control information (UCI) messages with a first priority are reserved for transmission, and UCI messages with a lower priority than the first priority are discarded. In some embodiments of this aspect, overlap resolution is based at least in part on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in the overlapping PUCCH resources in the time slot.

[0020] According to another aspect of this disclosure, a method implemented in a network node is provided. The method includes receiving Physical Uplink Control Channel (PUCCH) transmissions, wherein PUCCH resources for PUCCH transmissions are at least partially based on the removal of candidate PUCCH resources from sub-slots to resolve overlap of PUCCH resources in the slots.

[0021] In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot that overlap with PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot based at least partially on the selection of PUCCH resources in the first sub-time slot.

[0022] In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are based at least in part on the removal of candidate PUCCH resources that overlap with the selected PUCCH resources in the first sub-slot, extending from the next sub-slot. In some embodiments of this aspect, each PUCCH resource is configured to reside within a single sub-slot.

[0023] In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the radio device WD processing timeline of uplink control information (UCI) messages multiplexed with the Physical Uplink Shared Channel (PUSCH). In some embodiments of this aspect, PUCCH transmission is received when a UCI message is multiplexed on the Physical Uplink Shared Channel (PUSCH), based at least partially on the WD processing timeline of UCI messages multiplexed with the PUSCH. In some embodiments of this aspect, PUCCH transmission is received when the later of the PUSCH and UCI messages is reserved for transmission and the earlier of the PUSCH and UCI messages is discarded, based at least partially on the WD processing timeline of UCI messages multiplexed with the PUSCH. In some embodiments of this aspect, PUCCH transmission is received when the one with a first priority among the PUSCH and UCI messages is reserved for transmission and the other of the PUSCH and UCI messages with a lower priority than the first priority is discarded, based at least partially on the WD processing timeline of UCI messages multiplexed with the PUSCH.

[0024] In some embodiments of this aspect, uplink control information (UCI) messages with a first priority are retained for PUCCH transmission and UCI messages with a lower priority than the first priority are discarded. In some embodiments of this aspect, receiving PUCCH transmissions is based at least in part on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in overlapping PUCCH resources within a time slot.

[0025] According to another aspect of this disclosure, a wireless device WD configured to communicate with a network node is provided. The wireless device includes processing circuitry. The processing circuitry is configured to cause the wireless device to remove candidate Physical Uplink Control Channel (PUCCH) resources from a sub-time slot to resolve overlap of PUCCH resources within the time slot.

[0026] In some embodiments of this aspect, the candidate PUCCH resource extends from a sub-time slot to the next sub-time slot, and the processing circuitry is configured to cause the radio device to remove the candidate PUCCH resource by being configured to cause the radio device to remove the candidate PUCCH resource extending from the sub-time slot to the next sub-time slot. In some embodiments of this aspect, the candidate PUCCH resource extends from the next sub-time slot and overlaps with a PUCCH extending from the first sub-time slot to the next sub-time slot, and the processing circuitry is configured to cause the radio device to remove the candidate PUCCH resource by being configured to cause the radio device to remove the candidate PUCCH resource extending from the next sub-time slot that overlaps with the PUCCH extending from the first sub-time slot to the next sub-time slot.

[0027] In some embodiments of this aspect, the processing circuitry is further configured to select a PUCCH resource to transmit at least one uplink control information (UCI) message in a first sub-time slot; and the candidate PUCCH resource extends from the next sub-time slot; and the processing circuitry is configured to cause the radio device to remove the candidate PUCCH resource by removing the candidate PUCCH resource extending from the next sub-time slot, which is configured to cause the radio device to remove the candidate PUCCH resource at least in part based on the PUCCH resource selected in the first sub-time slot.

[0028] In some embodiments of this aspect, the processing circuitry is further configured to cause the wireless device to remove candidate PUCCH resources that extend from the next sub-slot and overlap with the selected PUCCH resources in the first sub-slot. In some embodiments of this aspect, each PUCCH resource is configured to reside within a single sub-slot.

[0029] In some embodiments of this aspect, the processing circuitry is further configured to cause the wireless device to determine whether the WD processing timeline of an uplink control information (UCI) message multiplexed with the Physical Uplink Shared Channel (PUSCH) is satisfied, with overlapping resolution based at least in part on the determination. In some embodiments of this aspect, the processing circuitry is further configured to cause the wireless device to multiplex the UCI message on the PUSCH at least in part on the determination. In some embodiments of this aspect, the later of the PUSCH and UCI messages is reserved for transmission and the earlier of the PUSCH and UCI messages is discarded, at least in part on the determination. In some embodiments of this aspect, the one with a first priority among the PUSCH and UCI messages is reserved for transmission and the other with a lower priority than the first priority is discarded, at least in part on the determination.

[0030] In some embodiments of this aspect, uplink control information (UCI) messages with a first priority are reserved for transmission, and UCI messages with a lower priority than the first priority are discarded. In some embodiments of this aspect, overlap resolution is based at least in part on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in the overlapping PUCCH resources in the time slot.

[0031] According to another aspect of this disclosure, a network node configured to communicate with a wireless device WD is provided. The network node includes processing circuitry. The processing circuitry is configured to cause the network node to receive Physical Uplink Control Channel (PUCCH) transmissions, wherein the PUCCH resources used for PUCCH transmissions are at least partially based on removing candidate PUCCH resources from sub-slots to resolve overlap of PUCCH resources within the slots.

[0032] In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot that overlap with PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot based at least partially on the selection of PUCCH resources in the first sub-time slot. In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot that overlap with selected PUCCH resources in the first sub-time slot. In some embodiments of this aspect, each PUCCH resource is configured to reside within a single sub-time slot.

[0033] In some embodiments of this aspect, the PUCCH resources used for PUCCH transmission are based at least in part on the radio device WD processing timeline for uplink control information (UCI) messages multiplexed with the Physical Uplink Shared Channel (PUSCH). In some embodiments of this aspect, based at least in part on the WD processing timeline for UCI messages multiplexed with the PUSCH, the processing circuitry is configured to cause a network node to receive a PUCCH transmission when one of the following occurs: multiplexing a UCI message on the Physical Uplink Shared Channel (PUSCH); reserving the later of the PUSCH and UCI messages for transmission and discarding the earlier of the PUSCH and UCI messages; and reserving the PUSCH and UCI messages with a first priority for transmission and discarding the other of the PUSCH and UCI messages with a lower priority than the first priority.

[0034] In some embodiments of this aspect, uplink control information (UCI) messages with a first priority are retained for PUCCH transmission and UCI messages with a lower priority than the first priority are discarded. In some embodiments of this aspect, the processing circuitry is configured to cause network nodes to receive PUCCH transmissions at least in part based on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in the overlapping PUCCH resources in the time slot. Attached Figure Description

[0035] A more comprehensive understanding of this embodiment and its accompanying advantages and features will be more readily available when considered in conjunction with the accompanying drawings, and by referring to the following detailed description, wherein:

[0036] Figure 1It is an exemplary radio resource in NR with a subcarrier spacing of 15 kHz;

[0037] Figure 2 This is an example of a HARQ-ACK transmission sub-slot;

[0038] Figure 3 This indicates a conflict with the PUCCH in the next sub-slot;

[0039] Figure 4 This is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host via an intermediate network, based on the principles of this disclosure.

[0040] Figure 5 This is a block diagram of a host communicating with a wireless device via a network node through at least a partial wireless connection, according to some embodiments of the present disclosure.

[0041] Figure 6 This is a flowchart illustrating an exemplary method for executing a client application at a wireless device, implemented in a communication system including a host, network node, and wireless device, according to some embodiments of the present disclosure.

[0042] Figure 7 This is a flowchart illustrating an exemplary method for receiving user data at a wireless device, implemented in a communication system including a host, network node, and wireless device, according to some embodiments of the present disclosure.

[0043] Figure 8 This is a flowchart illustrating an exemplary method for receiving user data from a wireless device at a host, implemented in a communication system including a host, a network node, and a wireless device, according to some embodiments of the present disclosure.

[0044] Figure 9 This is a flowchart illustrating an exemplary method for receiving user data at a host, implemented in a communication system including a host, network node, and wireless device, according to some embodiments of the present disclosure.

[0045] Figure 10 This is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0046] Figure 11 This is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

[0047] Figure 12 This explains the removal of candidate PUCCH resources from an earlier sub-slot that extend into the next sub-slot and conflict with another candidate PUCCH resource;

[0048] Figure 13This explains the removal of candidate PUCCH resources in the next sub-slot that overlap with PUCCH resources extending from an earlier sub-slot;

[0049] Figure 14 This illustrates an example of a time slot having two sub-time slots;

[0050] Figure 15 This paper describes a framework for resolving overlapping PUCCH / PUSCH in sub-slots;

[0051] Figure 16 This describes the process for checking the timeline used for UCI multiplexing in a sub-slot;

[0052] Figure 17 These are examples of timing standards used to implement some embodiments;

[0053] Figure 18 This is another example of a timing standard used to implement some embodiments; and

[0054] Figure 19 This is an example of how WD resolves conflicts between messages. Detailed Implementation

[0055] Before describing the exemplary embodiments in detail, it is noted that the embodiments primarily consist of a combination of device components and processing steps related to resolving Physical Uplink Control Channel (PUCCH) collisions in sub-time slots. Therefore, components have been represented appropriately in the figures using conventional symbols, which only illustrate those specific details relevant to understanding the embodiments, so as not to obscure disclosure with details that would be readily apparent to those of ordinary skill in the art who would benefit from the description herein. Throughout the description, the same numbers refer to the same elements.

[0056] As used herein, relational terms such as “first” and “second,” “top” and “bottom,” etc., may be used simply to distinguish one entity or element from another, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein are intended to include the plural forms as well. It will be further understood that, when used herein, the terms “comprises,” “comprising,” “includes,” and / or “including” specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0057] In the embodiments described herein, the connection term "communicating with," etc., can be used to indicate electrical or data communication that can be achieved, for example, through physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will recognize that multiple components can interoperate and that modifications and variations are possible to achieve electrical and data communication.

[0058] In some embodiments described herein, the terms “coupled,” “connected,” etc., may be used herein to indicate a connection (though not necessarily directly) and may include wired and / or wireless connections.

[0059] As used herein, the term "network node" can refer to any type of network node included in a radio network, which may further include any of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, integrated access and backhaul (IAB) node, donor node of control relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio headend (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, location node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. Network nodes may also include test equipment. The term “radio node” as used in this article can also be used to refer to a wireless device (WD) or a radio network node, such as a wireless device (WD).

[0060] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) may be used interchangeably. A WD as used herein can be any type of wireless device, such as a wireless device (WD), capable of communicating with a network node or another WD via radio signals. A WD can 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 (M2M) communication, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0061] Furthermore, in some embodiments, the generic term "radio network node" is used. It can be any kind of radio network node, which may 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), and remote radio headend (RRH).

[0062] It should be noted that while terms from a specific wireless system such as, for example, 3GPP LTE and / or New Radio (NR) may be used in this disclosure, this should not be construed as limiting the scope of the disclosure to only the systems mentioned above. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Global Microwave Access Interoperability (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas included in this disclosure.

[0063] It should be further noted that functions described herein as being performed by wireless devices or network nodes can be distributed among multiple wireless devices and / or network nodes. In other words, it is not anticipated that the functions of the network nodes and wireless devices described herein will be limited to being performed by a single physical device, and in fact, the functions of the network nodes and wireless devices described herein can be distributed among several physical devices.

[0064] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms used herein should be interpreted as having the same meaning as they have in the context of this specification and the relevant field, and will not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0065] Some embodiments provide solutions for resolving Physical Uplink Control Channel (PUCCH) collisions within sub-slots. In some embodiments, it may be assumed that overlap intentions between PUCCH resources with earlier start symbols are resolved first, until there are no overlapping PUCCH resources in the slot. In some embodiments below, two sub-slots are considered for simplicity. However, the process may be applicable to more sub-slots (if any).

[0066] Now returning to the accompanying drawings, the same elements are referred to by the same reference numerals. Figure 4 The diagram illustrates a communication system 10 according to an embodiment, such as a 3GPP-type cellular network capable of supporting standards such as LTE and / or NR (5G). The communication system 10 includes an access network 12, such as a radio access network, and a core network 14. The access network 12 includes multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16) such as NBs, eNBs, gNBs, or other types of radio access points. Each network node defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first radio device (WD) 22a located in coverage area 18a is configured to wirelessly connect to or be paged by the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one WD is in the coverage area or where only one WD is connected to the 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.

[0067] Furthermore, WD 22 is expected to be able to communicate simultaneously with more than one network node 16 and more than one type of network node 16, and / or be configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, WD 22 may have dual connectivity with LTE-enabled network nodes 16 and with the same or different network nodes 16 that support NR. As an example, WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0068] The communication system 10 itself can be connected to the host 24, which can be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or a processing resource in a server farm. The host 24 can be under the ownership or control of a service provider, or can be operated by or on behalf of the service provider. Connections 26, 28 between the communication system 10 and the host 24 can extend directly from the core network 14 to the host 24 or can extend via an optional intermediate network 30. The intermediate network 30 can be one or more public, private, or hosted networks. The intermediate network 30 (if any) can be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0069] Figure 4 The communication system as a whole enables connectivity between one of the connected WDs 22a and 22b and the host 24. This connectivity can be described as an over-the-top (OTT) connection. The host 24 and the connected WDs 22a and 22b are configured to transmit data and / or signaling via the OTT connection using the access network 12, core network 14, any intermediate network 30, and possible additional infrastructure (not shown) as intermediaries. The OTT connection can be transparent in the sense that at least some of the participating communication devices traversing the OTT connection are unaware of the routing of uplink and downlink communications. For example, network node 16 may not be notified, or need not be notified, of past routing of incoming downlink communications, where data originating from host 24 is to be forwarded (e.g., switched) to the connected WD 22a. Similarly, network node 16 does not need to know the future routing of outgoing uplink communications originating from WD 22a toward host 24.

[0070] Network node 16 is configured to include a PUCCH indicator unit 32, which is configured to receive Physical Uplink Control Channel (PUCCH) transmissions. The PUCCH resources used for PUCCH transmissions are at least partially based on removing candidate PUCCH resources from sub-slots to resolve overlap of PUCCH resources within a slot. In some embodiments, the PUCCH indicator unit 32 is configured to signal a PUCCH resource indicator in a Downlink Control Information (DCI) message such that new PUCCH resources do not overlap with other PUCCH resources.

[0071] The wireless device 22 is configured to include a PUCCH removal unit 34, which is configured to remove candidate physical uplink control channel (PUCCH) resources from a sub-time slot to resolve overlap of PUCCH resources in the time slot. In some embodiments, the PUCCH removal unit 34 is configured to remove candidate PUCCH resources extending from a first sub-time slot to a next sub-time slot, or alternatively, to remove candidate PUCCH resources that overlap with PUCCH resources extending from the first sub-time slot to the next sub-time slot from the next sub-time slot.

[0072] Now refer to Figure 5 This section describes an example implementation of the WD 22, network node 16, and host 24 discussed in the preceding paragraphs, according to an embodiment. In the communication system 10, host 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain wired or wireless connections to various communication devices of the communication system 10. Host 24 further includes processing circuitry 42, which may have storage and / or processing capabilities. Processing circuitry 42 may include a processor 44 and memory 46. Specifically, in addition to or in lieu of processors and memory such as a central processing unit, processing circuitry 42 may also include, for example, one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions, for processing and / or control. Processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may include any kind of volatile and / or non-volatile memory, such as cache memory 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).

[0073] Processing circuitry 42 may be configured to control any and / or process described herein and to cause such methods and / or processes to be executed, for example, by host 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host 24 described herein. Host 24 includes memory 46 configured to store data, programmed 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 with respect to host 24. The instructions may be software associated with host 24.

[0074] Software 48 may be executable by processing circuitry 42. Software 48 includes a host application 50. Host application 50 may be operable to provide services to a remote user of WD 22, such as a device connected via an OTT connection 52 terminated at WD 22 and host 24. In providing services to a remote user, host application 50 may provide user data transmitted using OTT connection 52. “User data” may be data and information described herein for implementing the described functionality. In one embodiment, host 24 may be configured to provide control and functionality to a service provider, and host 24 may be operated by or on behalf of the service provider. Processing circuitry 42 of host 24 may enable host 24 to observe, monitor, control, transmit to and / or receive from network node 16 and / or wireless device 22.

[0075] The communication system 10 further includes a network node 16 disposed within the communication system 10 and comprising hardware 58, which enables the network node 16 to communicate with the host 24 and with the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections to 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 within the coverage area 18 served by the network node 16. The radio interface 62 may be configured 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 to the host 24. The connection 66 may be direct, or it may be via the core network 14 of the communication system 10 and / or via one or more intermediate networks 30 outside the communication system 10.

[0076] In the illustrated embodiment, the hardware 58 of network node 16 further includes processing circuitry 68. Processing circuitry 68 may include a processor 70 and memory 72. Specifically, in addition to or in lieu of processors and memory such as a central processing unit, processing circuitry 68 may also include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions. Processor 70 may be configured to access (e.g., write to and / or read from) memory 72, which may include any kind of volatile and / or non-volatile memory, such as cache memory 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).

[0077] Therefore, network node 16 further includes software 74, which is internally stored, for example, in memory 72, or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 may be executable by processing circuitry 68. Processing circuitry 68 may be configured to control any and / or cause any of the methods and / or processes described herein to be executed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. Memory 72 is configured to store data, programmed software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, the processing circuitry 68 of network node 16 may include a PUCCH indicator unit 32, which is configured to signal a PUCCH resource indicator in a downlink control information (DCI) message so that a new PUCCH resource does not overlap with another PUCCH resource.

[0078] The communication system 10 further includes the previously mentioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain wireless connections 64 with network nodes 16 serving the coverage area 18 where the WD 22 is currently located. The radio interface 82 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0079] The hardware 80 of the WD 22 further includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. Specifically, in addition to or in lieu of processors and memory such as a central processing unit, processing circuitry 84 may also include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions. Processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any kind of volatile and / or non-volatile memory, such as cache memory 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).

[0080] Therefore, WD 22 may further include software 90, which is stored, for example, in memory 88 at WD 22 or in external memory accessible by WD 22 (e.g., a database, storage array, network storage device, etc.). Software 90 may be executable by processing circuitry 84. Software 90 may include a client application 92. With the support of host 24, client application 92 may be operable to provide services to human or non-human users via WD 22. In host 24, a executing host application 50 may communicate with the executing client application 92 via an OTT connection 52 terminated at WD 22 and host 24. When providing services to a user, 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.

[0081] Processing circuitry 84 may be configured to control any and / or cause such methods and / or processes described herein to be performed, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD 22 described herein. WD 22 includes memory 88 configured to store data, programmed software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, processing circuitry 84 of wireless device 22 may include a PUCCH removal unit 34 configured to remove candidate physical uplink control channel (PUCCH) resources extending from a first sub-time slot to a next sub-time slot, or alternatively, remove candidate PUCCH resources overlapping with PUCCHs extending from the first sub-time slot to the next sub-time slot from the next sub-time slot.

[0082] In some embodiments, the internal operations of network node 16, WD 22, and host 24 can be as follows: Figure 5 As shown, and independently, the surrounding network topology can be Figure 4 The surrounding network topology.

[0083] exist Figure 5In this diagram, OTT connection 52 is abstractly depicted to illustrate communication between host 24 and wireless device 22 via network node 16, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from WD 22, the service provider of operating host 24, or both. When OTT connection 52 is active, the network infrastructure can further make decisions, dynamically altering the routing based on factors such as network reconfiguration or load balancing considerations.

[0084] The wireless connection 64 between WD 22 and network node 16 is based on the teachings of embodiments described throughout this disclosure. One or more of the various embodiments utilize OTT connection 52 to improve the performance of OTT services provided to WD 22, wherein wireless connection 64 can form the final segment. More precisely, the teachings of some embodiments in these embodiments can improve data rates, latency, and / or power consumption, and thus provide benefits such as reduced user wait times, less stringent file size limits, better responsiveness, extended battery life, etc.

[0085] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. In response to changes in the measurement results, optional network functionality for reconfiguring the OTT connection 52 between host 24 and WD 22 may further exist. The measurement process and / or network functionality for reconfiguring the OTT connection 52 may be implemented in software 48 of host 24, software 90 of WD 22, or both. In embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software 48, 90 may calculate or estimate the monitored quantities from. Reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect network node 16, and may be unknown or imperceptible to network node 16. Some such processes and functionalities may be known and implemented in the art. In some embodiments, the measurement may involve proprietary WD signaling for host 24 to facilitate the measurement of throughput, propagation count, latency, etc. In some embodiments, the measurement can be implemented because software 48, 90 uses OTT connection 52 to facilitate the transmission of messages, particularly empty or 'dumb' messages, while monitoring propagation count, errors, etc.

[0086] Therefore, in some embodiments, host 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward user data to a cellular network for transmission to WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, network node 16 is configured and / or processing circuitry 68 of network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22, and / or the functions and / or methods described herein for preparing / terminating / maintaining / supporting / terminating reception of transmissions from WD 22.

[0087] In some embodiments, host 24 includes processing circuitry 42 and a communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or the functions and / or methods described herein for preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16, and / or WD 22 includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or the functions and / or methods described herein for preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16.

[0088] although Figure 4 and Figure 5 Various “units” such as PUCCH indicator unit 32 and PUCCH removal unit 34 within the corresponding processor are shown, but it is anticipated that these units can be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units can be implemented in hardware or a combination of hardware and software within the processing circuitry.

[0089] Figure 6 This describes an embodiment of a situation, such as... Figure 4 and Figure 5 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include, or may be a reference... Figure 5The described components are host 24, network node 16, and WD 22. In a first step of the method, host 24 provides user data (block S100). In an optional sub-step of the first step, host 24 provides user data by executing a host application such as, for example, host application 50 (block S102). In a second step, host 24 initiates a transmission carrying user data to WD 22 (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout this disclosure, network node 16 transmits the user data carried in the transmission initiated by host 24 to WD 22 (block S106). In an optional fourth step, WD 22 executes a client application such as, for example, a client application 92 associated with host application 50 executed by host 24 (block S108).

[0090] Figure 7 This describes an embodiment of a situation, such as... Figure 4 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include, or may be a reference... Figure 4 and Figure 5 The described components are host 24, network node 16, and WD 22. In a first step of the method, host 24 provides user data (block S110). In an optional sub-step (not shown), host 24 provides user data by executing a host application, such as host application 50. In a second step, host 24 initiates a transmission carrying user data to WD 22 (block S112). According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried via network node 16. In an optional third step, WD 22 receives the user data carried in the transmission (block S114).

[0091] Figure 8 This describes an embodiment of a situation, such as... Figure 4 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include, or may be a reference... Figure 4 and Figure 5The described components are host 24, network node 16, and WD 22. In an optional first step of the method, WD 22 receives input data provided by host 24 (block S116). In an optional sub-step of the first step, WD 22 executes client application 92, which provides user data as a response to the received input data provided by host 24 (block S118). Alternatively, in an optional second step, WD 22 provides user data (block S120). In an optional sub-step of the second step, WD provides user data by executing a client application such as, for example, client application 92 (block S122). When providing user data, the executed client application 92 may further consider user input received from a user. Regardless of the specific manner in which user data is provided, WD 22 may initiate the transmission of user data to host 24 in an optional third sub-step (block S124). In a fourth step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, host 24 receives user data transmitted from WD 22 (block S126).

[0092] Figure 9 This describes an embodiment of a situation, such as... Figure 4 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include, or may be a reference... Figure 4 and Figure 5 The described components are host 24, network node 16, and WD 22. In an optional first step of the method, network node 16 receives user data from WD 22, according to the teachings throughout the embodiments described herein (block S128). In an optional second step, network node 16 initiates a transmission of the received user data to host 24 (block S130). In a third step, host 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0093] Figure 10 This is a flowchart illustrating exemplary processes in network node 16 according to some embodiments presented herein. One or more blocks described herein may be executed by one or more elements of network node 16, such as processing circuitry 68 (including PUCCH indicator unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, such as by means of processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to receive (block S134) Physical Uplink Control Channel (PUCCH) transmissions, with PUCCH resources for PUCCH transmission based at least in part on removing candidate PUCCH resources from sub-slots to resolve overlap of PUCCH resources in the slots.

[0094] In some embodiments, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot that overlap with the PUCCH resources extending from the first sub-time slot to the next sub-time slot. In some embodiments, the PUCCH resources used for PUCCH transmission are at least partially based on the removal of candidate PUCCH resources extending from the next sub-time slot based at least partially on the selection of PUCCH resources in the first sub-time slot.

[0095] In some embodiments, the PUCCH resources used for PUCCH transmission are based at least in part on the removal of candidate PUCCH resources that overlap with the selected PUCCH resources in the first sub-slot, extending from the next sub-slot. In some embodiments, each PUCCH resource is configured to be within a single sub-slot. In some embodiments, the PUCCH resources used for PUCCH transmission are based at least in part on the radio device WD processing timeline for uplink control information (UCI) messages multiplexed with the Physical Uplink Shared Channel (PUSCH).

[0096] In some embodiments, network node 16 is configured, such as by means of processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to perform one of the following: receiving PUCCH transmission when UCI messages are multiplexed on the Physical Uplink Shared Channel PUSCH, based at least in part on whether the WD processing timeline of UCI messages multiplexed with PUSCH is satisfied; receiving PUCCH transmission when the later of the PUSCH and UCI messages is reserved for transmission and the earlier of the PUSCH and UCI messages is discarded, based at least in part on whether the WD processing timeline of UCI messages multiplexed with PUSCH is satisfied; and receiving PUCCH transmission when the one with a first priority of the PUSCH and UCI messages is reserved for transmission and the other of the PUSCH and UCI messages with a lower priority than the first priority is discarded, based at least in part on whether the WD processing timeline of UCI messages multiplexed with PUSCH is satisfied.

[0097] In some embodiments, uplink control information (UCI) messages with a first priority are retained for PUCCH transmission, and UCI messages with a lower priority than the first priority are discarded. In some embodiments, the processing circuitry is configured to cause network nodes to receive PUCCH transmissions based at least in part on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in the overlapping PUCCH resources in the time slot.

[0098] In some embodiments, network node 16 is configured, such as by means of processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to receive PUCCH resources from WD 22. The process includes signaling a PUCCH resource indicator in a downlink control information (DCI) message such that a new PUCCH resource does not overlap with another PUCCH resource.

[0099] Figure 11 This is a flowchart illustrating exemplary processes in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be executed by one or more elements of the wireless device 22, such as processing circuitry 84 (including PUCCH removal unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 is configured, for example by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to remove (block S136) candidate Physical Uplink Control Channel (PUCCH) resources from sub-slots to resolve overlap of PUCCH resources in the slots.

[0100] In some embodiments, candidate PUCCH resources extend from a sub-time slot to the next sub-time slot, and the wireless device 22 is configured, for example by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to cause the wireless device 22 to remove candidate PUCCH resources by means of processing circuitry 84 and / or processor 86 and / or radio interface 82. In some embodiments, candidate PUCCH resources extend from the next sub-time slot and overlap with PUCCHs extending from the first sub-time slot to the next sub-time slot, and the wireless device 22 is configured, for example by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to cause the wireless device 22 to remove candidate PUCCH resources by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to remove candidate PUCCH resources that extend from the next sub-time slot and overlap with PUCCHs extending from the first sub-time slot to the next sub-time slot.

[0101] In some embodiments, the wireless device 22 is further configured, for example by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to cause the wireless device 22 to select a PUCCH resource to transmit at least one uplink control information (UCI) message in a first sub-time slot; and the candidate PUCCH resource extends from the next sub-time slot; and the wireless device 22 is configured, for example by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, to cause the wireless device 22 to remove the candidate PUCCH resource extending from the next sub-time slot by being configured to cause the wireless device 22 to remove the candidate PUCCH resource extending from the next sub-time slot at least in part based on the PUCCH resource selected in the first sub-time slot.

[0102] In some embodiments, the wireless device 22, such as by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, is configured to cause the wireless device 22 to remove candidate PUCCH resources that extend from the next sub-time slot and overlap with the selected PUCCH resources in the first sub-time slot. In some embodiments, each PUCCH resource is configured to reside within a single sub-time slot.

[0103] In some embodiments, the wireless device 22, such as by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, is configured to cause the wireless device 22 to determine whether the WD processing timeline of uplink control information (UCI) messages multiplexed with the Physical Uplink Shared Channel (PUSCH) is satisfied, with overlapping resolution based at least in part on the determination. In some embodiments, the wireless device 22, such as by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, is configured to cause the wireless device 22 to perform one of the following: multiplexing the UCI message on the Physical Uplink Shared Channel (PUSCH) at least in part on the determination; reserving the later of the PUSCH and UCI messages for transmission and discarding the earlier of the PUSCH and UCI messages at least in part on the determination; and reserving the PUSCH and UCI messages with a first priority for transmission and discarding the other of the PUSCH and UCI messages with a lower priority than the first priority at least in part on the determination.

[0104] In some embodiments, uplink control information (UCI) messages with a first priority are reserved for transmission, and UCI messages with a lower priority than the first priority are discarded. In some embodiments, overlap resolution is based at least in part on a relative priority and utility maximization function associated with each uplink control information (UCI) message to be transmitted in the overlapping PUCCH resources in the time slot.

[0105] In some embodiments, the wireless device 22, such as by means of processing circuitry 84 and / or processor 86 and / or radio interface 82, is configured to remove candidate physical uplink control channel (PUCCH) resources extending from a first sub-time slot to a next sub-time slot. Alternatively, the process may include removing candidate PUCCH resources that overlap with the PUCCH extending from the first sub-time slot to the next sub-time slot from the next sub-time slot.

[0106] The general process flow of the publicly disclosed arrangement has been described and examples of hardware and software arrangements for implementing the publicly disclosed process and functions have been provided. The following sections provide details and examples of arrangements for resolving Physical Uplink Control Channel (PUCCH) conflicts in sub-slots.

[0107] In some embodiments, PUCCH resources configured in different sub-slots for HARQ ACK transmission are configured such that they do not overlap. This can be accomplished, for example, by either of the following:

[0108] c) Remove candidate PUCCH resources from earlier sub-slots that extend into the next sub-slot and conflict with another candidate PUCCH resource (see [link]). Figure 12 );or

[0109] d) Remove candidate PUCCH resources in the next sub-slot that overlap with PUCCH resources extending from an earlier sub-slot (see [link]). Figure 13 ).

[0110] Note that in some embodiments, PUCCH resources are limited to sub-slots, meaning they must start and stop within the same sub-slot. In other words, each PUCCH resource is configured / expected to exist within a single sub-slot.

[0111] According to another method, overlapping PUCCHs in the first sub-slot can be resolved, and then, based on the PUCCH resources(s) used for the transmission of UCI in the first sub-slot, all candidate PUCCH resources(s) in subsequent sub-slots that overlap with the selected PUCCH resources in the first sub-slot are removed from the set of candidate PUCCH resources(s) in those sub-slots(s) (e.g., via WD 22). Figure 14 This illustrates an example with two sub-time slots within a time slot. In this example, resolving the overlap between PUCCH1 and PUCCH2 results in the content of both being multiplexed into PUCCH3. Based on this, in the next sub-time slot, PUCCH9 and PUCCH11, which overlap with PUCCH3, are removed from the candidate PUCCH resources in the next sub-time slot (e.g., via WD 22).

[0112] In another embodiment, when resolving PUCCH conflicts, for example via WD 22 and / or network node 16, not only overlapping PUCCH transmissions in the first sub-slot are considered, but also planned PUCCH transmissions in (one or more) subsequent sub-slots that overlap with planned PUCCH transmissions in the first sub-slot. Once all conflicts are resolved, the PUCCH resource in the first sub-slot is selected, for example via WD 22.

[0113] In another embodiment, a signal can be sent to the PUCCH resource indicator in the DCI corresponding to the overlapping PUCCH resource so that the new determined PUCCH resource for multiplexing UCI corresponding to the overlapping PUCCH resource in the sub-slot will not overlap with the PUCCH resource intended for UCI transmission in the next sub-slot (if any).

[0114] Figure 15 An example framework for resolving overlapping PUCCH / PUSCH in a sub-slot is described. In step S138, WD22, for example by means of processing circuitry 84, determines one or more PUCCH and / or one or more PUSCH resources configured or scheduled in the sub-slot. In step S140, WD22 may, for example by means of processing circuitry 84, determine whether there are any Channel State Information (CSI) PUCCHs that overlap with each other. If the answer is yes, the process can proceed to step S142, where WD22 can resolve the overlap to multiplex the CSI in one or more non-overlapping CSI PUCCHs.

[0115] In step S144, WD 22 may, for example by means of processing circuitry 84, determine whether there are any overlapping PUCCH(one or more) PUCCH / (one or more) PUCCH / (one or more) PUSCH in the sub-time slot, at least one of which is permitted by downlink control information (DCI). If the answer is no, WD 22 performs transmissions, for example via radio interface 82, from non-overlapping PUCCH(one or more) and / or PUSCH(one or more) resources (if any). If the answer is yes, the process proceeds to step S148, where WD 22 may determine whether at least one of the overlapping resources is permitted by DCI. If yes, the process proceeds to step S150, where WD 22 checks the UCI multiplexing timeline. If the answer is no, the process proceeds to step S152, where WD determines whether there are any overlapping PUCCH in the sub-time slot. If there are, in step S154, WD 22 may find the earliest overlapping PUCCH in the sub-time slot (e.g., the set X of PUCCHs).

[0116] In step S156, WD 22 can determine the UCI for multiplexing the PUCCH in X and a new PUCCH resource to replace the PUCCH in X. In step S158, WD 22 can determine whether there is any PUSCH overlapping with PUCCH(one or more) in the sub-slot. In step S160, WD 22 can determine whether there is a new PUCCH that does not satisfy the UCI timeline. If the answer is yes (i.e., there is a new PUCCH that does not satisfy the UCI timeline), then in step S162, WD 22 can process the new PUCCH and its corresponding UCI. In step S162, WD 22 can determine whether at least one of them is permitted by DCI. If so, the process can proceed to step S166, where WD 22 checks the UCI multiplexing timeline, for example, by means of processing circuitry 84. In step S168, WD 22 can multiplex the UCI on the PUSCH and discard the overlapping PUCCH.

[0117] Figure 16 Explained for use in, for example, in Figure 15 The process of checking the timeline of UCI multiplexing in the sub-slot in step S150 or S168. Figure 16 In step S170, WD 22 can determine, for example by means of processing circuit 84, whether there are overlapping groups of timelines in which UCI multiplexing has not been checked. If the answer is yes, then in step S172, WD 22 can determine, for example by means of processing circuit 84, whether the group satisfies the timeline. If the answer is no, i.e., the group does not satisfy the timeline, then in step S174, WD 22 can process the UCI / data that does not satisfy the timeline. If the answer is yes, i.e., the group does satisfy the timeline, then the process can return to step S170.

[0118] In some embodiments, when the WD 22 processing timeline for UCI multiplexing is not met:

[0119] e) In one embodiment, the PUCCH and / or PUSCH in the group may be an error condition and are discarded by WD 22 along with the corresponding UCI / data.

[0120] f) Alternatively, in another embodiment, higher priority UCI and / or data may be reserved for transmission, while lower priority UCI and / or data may be discarded by WD 22. Figure 17 An example is provided. For example... Figure 17As shown, in step S176, WD 22 can determine, for example by means of processing circuitry 84, the timeline of a PUCCH that does not meet the requirement of carrying HARQ-ACK. In step S178, WD 22 can then discard the lower priority signal (PUCCH in this example) and, for example, transmit the higher priority signal (PUSCH in this example) via radio interface 82.

[0121] (g) Alternatively, in another embodiment, later UCI and / or data may be retained for transmission while earlier UCI and / or data may be discarded. The timing criteria for discarding enable successful multiplexing of later UCI and / or data with UCI processing time. Figure 18 An example is provided. For example... Figure 18 As shown, in step S180, WD 22 can determine the timeline that does not meet the PUSCH schedule. In step S182, WD 22 can then discard the earlier signal (PUCCH in this example) and transmit the later signal (PUSCH in this example) via radio interface 82.

[0122] In some embodiments, priority-based resolution may also be considered. In some embodiments, messages can be of any control or data type, in addition to the HARQ / PUCCH messages just mentioned. Whenever a collision occurs, WD 22 can, for example by means of processing circuitry 84, check the priority of the interfering messages and can select, for example, to transmit the interfering message(s) with the highest priority via radio interface 82 and discard relatively low-priority messages, i.e., messages with a priority below a predetermined threshold. There may be situations where three or more messages interfere simultaneously or at different times, such that the resolution of the last message may depend on the initial collision pair. See, for example, Figure 19 Three outcomes (shown as a tree) can be implemented depending on their priorities. These interfering messages can be referred to as conflict groups, where the resolution of the last message depends on the resolution of the first message over time. Figure 19 In the example shown, WD 22 first resolves the conflict between messages A and B by means of, for example, processing circuitry 84, and then WD 22 resolves the conflict between the resulting message and message C. Table 1 details various example results of following message priority.

[0123] Table 1

[0124] .

[0125] In Table 1, all messages have different priorities, but there may be cases where messages have the same priority. In such cases, conflict resolution may be applied randomly among messages with the same priority, or WD 22 may prioritize messages on its own (e.g., independently and not based on predetermined / predefined rules known to WD 22 and network node 16) based on one or more parameters or conditions (such as signal-to-interference-plus-noise ratio (SINR), message success probability, capacity, message size, etc.) if no explicit priority is assigned.

[0126] Priorities can be explicitly delivered (when allocating resources), or they can be evaluated based on message resource mappings, and so on. Network node 16 can establish service categories and associate priorities based on the required success rate or reliability of a given message belonging to a service category. For example, this could be for URLLC services with the highest priority of 99.99% and eMBB services with the lowest priority of 90% block error rate (BLER).

[0127] Another embodiment of conflict resolution may include considering the maximization of the utility of the conflict group. Figure 19 For example, message A has a medium priority, message B has a high priority (i.e., a priority higher than message A and / or a priority based on a predetermined priority level), and message C has a medium priority (i.e., a priority lower than message B and / or a priority based on a predetermined priority level). These priorities can be transformed into a utility function; see Table 2 for example. Table 3 shows the opposite results to Table 1, where messages that maximize the utility of the conflict group are advantageous.

[0128] Table 2

[0129] .

[0130] Table 3

[0131] .

[0132] Furthermore, the resolution time (or conflict) window can be static or dynamic. Its size can be, for example:

[0133] • For example, the following fixed windows:

[0134] ° Sub-time slot;

[0135] °Time slot;

[0136] °Superframe; or

[0137] ° A fixed number of x time slots or a fixed time window t.

[0138] • It has dynamic windows such as the following:

[0139] ° The first n conflicts (e.g., in Figure 19 In the context of messages A and B, there are two conflicts; and in the context of messages B and C, there are two conflicts.

[0140] ° is equivalent to the time window of the time cycle of the conflict group (which can span a large number of sub-slots or time slots).

[0141] In addition, conflict resolution can be applied in the following areas:

[0142] • Uplink (UL);

[0143] For example, WD 22 may perform conflict resolution for its interfering UL messages according to any embodiment described herein, such as by means of processing circuitry 84 and / or radio interface 82 (and network node 16 receives such messages accordingly).

[0144] Downlink;

[0145] For example, network node 17 (e.g., gNB) may perform conflict resolution for its interfering DL messages by means of processing circuitry 68 and / or radio interface 62, according to any embodiment described herein (and WD 22 receives such messages accordingly).

[0146] • Straight-through link;

[0147] For example, in device-to-device (D2D) communication, WD 22 performs conflict resolution for its interfering pass-through link messages;

[0148] The above combinations;

[0149] For example, WD 22 has both conflicting pass-through links and UL messages within a certain time window.

[0150] Furthermore, the intended recipient of the message can be a single node or multiple nodes, for example:

[0151] • For UL, different messages may be intended for different network nodes 16 (acting as network node 16 of, for example, gNB), or network node 16 and (one or more) other WD 22 (as D2D links), or relay nodes (network node 16 acting as relay nodes), etc.

[0152] • In the case of DL, different messages can be used for the same WD 22, or different WD 22, or any type of participating node;

[0153] Similarly, D2D WD 22 can have expected (conflicting) messages for use by multiple WD 22 and network node 16 (e.g., gNB).

[0154] In addition, the message can be a control message (e.g., PUCCH or PDCCH or direct link control channel / SLCCH) or a data channel (e.g., PUSCH or PDSCH or direct link shared channel / SLSCH) or a combination of both (data and control, e.g., SLSCH resources are interfering with PUCCH resources, or PUCCH resources are interfering with PUSCH resources in UL).

[0155] According to one aspect, a network node configured to communicate with a wireless device (WD) 22 is provided. The network node has processing circuitry 68 configured to: receive PUCCH resources from the WD 22; and signal a PUCCH resource indicator in a downlink control information (DCI) message such that a new PUCCH resource does not overlap with another PUCCH resource. According to another aspect, a method implemented in a network node is provided. The method includes: receiving PUCCH resources from the WD 22; and signaling a PUCCH resource indicator in a downlink control information (DCI) message such that a new PUCCH resource does not overlap with another PUCCH resource.

[0156] According to another aspect, the wireless device (WD 22) is configured to communicate with network node 16. WD 22 has processing circuitry 84 configured to: remove candidate physical uplink control channel (PUCCH) resources extending from a first sub-time slot to a next sub-time slot; or remove candidate PUCCH resources that overlap with the PUCCH extending from the first sub-time slot to the next sub-time slot from the next sub-time slot.

[0157] Accordingly, in some embodiments, during removal, PUCCH resources in the first sub-slot are selected. In some embodiments, uplink control information (UCI) messages with a first priority are reserved for transmission, and UCI messages with a lower priority than the first priority are discarded.

[0158] According to another aspect, a method implemented in a wireless device (WD 22). The method includes: removing candidate physical uplink control channel (PUCCH) resources extending from a first sub-time slot to a next sub-time slot; or, removing candidate physical uplink control channel (PUCCH) resources that overlap with the PUCCH extending from the first sub-time slot to the next sub-time slot from the next sub-time slot.

[0159] Accordingly, in some embodiments, during removal, PUCCH resources in the first sub-slot are selected. In some embodiments, uplink control information (UCI) messages with a first priority are reserved for transmission, and UCI messages with a lower priority than the first priority are discarded.

[0160] Example A1. A network node configured to communicate with a wireless device (WD), the network node being configured and / or including a radio interface and / or including processing circuitry configured to:

[0161] Receive PUCCH resources from the WD; and

[0162] The downlink control information (DCI) message signals the PUCCH resource indicator to ensure that the new PUCCH resource does not overlap with another PUCCH resource.

[0163] Example B1. A method implemented in a network node, the method comprising:

[0164] Receive PUCCH resources from the WD; and

[0165] The downlink control information (DCI) message signals the PUCCH resource indicator to ensure that the new PUCCH resource does not overlap with another PUCCH resource.

[0166] Example C1. A wireless device (WD) configured to communicate with a network node, the WD being configured and / or the WD including a radio interface and / or processing circuitry, the processing circuitry being configured to:

[0167] Remove candidate Physical Uplink Control Channel (PUCCH) resources extending to the next sub-slot from the first sub-slot; or

[0168] Remove candidate physical uplink control channel (PUCCH) resources from the next sub-slot that overlap with the PUCCH extending from the first sub-slot to the next sub-slot.

[0169] Example C2. WD as described in Example C1, wherein, upon removal, the PUCCH resource in the first sub-slot is selected.

[0170] Example C3. WD as described in Example C1, wherein uplink control information (UCI) messages with a first priority are retained for transmission and UCI messages with a lower priority than the first priority are discarded.

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

[0172] Remove candidate Physical Uplink Control Channel (PUCCH) resources extending to the next sub-slot from the first sub-slot; or

[0173] Remove candidate physical uplink control channel (PUCCH) resources from the next sub-slot that overlap with the PUCCH extending from the first sub-slot to the next sub-slot.

[0174] Example D2. The method as described in Example D1, wherein, upon removal, the PUCCH resource in the first sub-slot is selected.

[0175] Example D3. The method as described in Example D1, wherein uplink control information (UCI) messages with a first priority are retained for transmission and UCI messages with a lower priority than the first priority are discarded.

[0176] As those skilled in the art will recognize, the concepts described herein can be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining all software and hardware aspects generally referred to herein as “circuit” or “module.” Any process, step, action, and / or functionality described herein can be performed by a corresponding module and / or any process, step, action, and / or functionality described herein can be associated with a corresponding module, which can be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure can take the form of a computer program product on a tangible computer-usable storage medium having computer-executable computer program code included in the medium. Any suitable tangible computer-readable medium, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices, can be utilized.

[0177] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, as well as combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thus creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute by means of the computer's processor or other programmable data processing apparatus, create components for implementing the functions / actions specified in the flowchart and / or block diagram blocks or multiple flowchart and / or block diagram blocks.

[0178] These computer program instructions, which can direct a computer or other programmable data processing apparatus to operate in a particular manner, may also be stored in a computer-readable storage medium, such that the instructions stored in the computer-readable storage medium produce an article of writing comprising instruction components that implement the functions / actions specified in flowchart and / or block diagram blocks or multiple flowchart and / or block diagram blocks.

[0179] Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be executed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions / actions specified in flowchart and / or block diagram frames or multiple flowchart and / or block diagram frames.

[0180] It should be understood that the functions / actions annotated in the boxes may occur in a different order than those annotated in the operating instructions. For example, depending on the functions / actions involved, two boxes shown consecutively may actually be performed substantially simultaneously, or sometimes they may be performed in reverse order. Although some diagrams include arrows on the communication path to indicate the main direction of communication, it should be understood that communication may occur in the opposite direction to the depicted arrows.

[0181] Computer program code for performing the operations described herein can be written using object-oriented programming languages ​​such as Java® or C++. However, computer program code for performing the exposed operations can also be written using conventional procedural programming languages ​​such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or (e.g., via the Internet using an Internet service provider) can be made to connect to the external computer.

[0182] Numerous different embodiments have been disclosed herein in conjunction with the foregoing description and figures. It will be understood that literally describing and illustrating every combination and sub-combination of these embodiments would be excessively repetitive and obscure. Therefore, all embodiments may be combined in any manner and / or combination, and this specification, including the figures, should be construed as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein, as well as the ways and processes of making and using them, and this specification, including the figures, should support the claims for any such combination or sub-combination.

[0183] The abbreviations that may be used in the preceding description include:

[0184] Explanation of abbreviations

[0185] eMBB Enhanced Mobile Broadband

[0186] LTE Long Term Evolution

[0187] NR Next Radio

[0188] PUCCH (Physical Uplink Control Channel)

[0189] PUSCH Physical Uplink Shared Channel

[0190] SR scheduling request

[0191] URLLC Ultra-Reliable Low-Latency Communication

[0192] Those skilled in the art will recognize that the embodiments described herein are not limited to those specifically shown and described above. Furthermore, unless otherwise stated above, it should be noted that all figures in the accompanying drawings are not drawn to scale. Various modifications and variations are possible in accordance with the teachings above without departing from the scope of the following claims.

Claims

1. A method implemented in a user equipment (UE) (22), the method comprising: In response to the overlap of PUCCH resources in a time slot, candidate physical uplink control channel (PUCCH) resources are removed from the sub-time slot (S136), wherein the candidate PUCCH resources extend from the sub-time slot to the next sub-time slot, thereby causing the overlap; and Transmit a first uplink control information (UCI) message with a first priority for transmission within overlapping PUCCH resources, wherein a second UCI message with a second priority lower than the first priority for transmission within the overlapping PUCCH resources is discarded to resolve the overlap.

2. The method as described in claim 1, wherein, Each PUCCH resource must be configured in a single sub-slot.

3. The method of claim 1, further comprising: Determine whether the UE processing timeline of any of the UCI messages shared with the Physical Uplink Channel (PUSCH) is satisfied, and the overlapping resolution is at least in part based on the determination.

4. The method of claim 3, further comprising one of the following: Based at least in part on the determination, the UCI message is multiplexed on the Physical Uplink Shared Channel (PUSCH); Based at least in part on the determination, the later of the PUSCH and the UCI messages is reserved for transmission and the earlier of the PUSCH and the UCI messages is discarded.

5. The method of claim 1, wherein, The overlapping solutions are at least partially based on utility maximization functions.

6. A method implemented in a network node (16), the method comprising: Receive (S134) Physical Uplink Control Channel (PUCCH) transmission, wherein the PUCCH resources for the PUCCH transmission are at least partially removed from the sub-slot based on the overlap of PUCCH resources in the time slot, wherein the PUCCH resources for the PUCCH transmission are at least partially removed based on the extension from the sub-slot to the next sub-slot, thereby causing the removal of the overlapping candidate PUCCH resources, wherein a first uplink control information (UCI) message for transmission within the overlapping PUCCH resources and allocated with a first priority is transmitted, and a second UCI message for transmission within the overlapping PUCCH resources and allocated with a second priority lower than the first priority is discarded to resolve the overlap.

7. The method of claim 6, wherein, Each PUCCH resource must be configured in a single sub-slot.

8. The method of claim 6 or 7, wherein, The PUCCH resources used for the transmission of the PUCCH are based at least in part on the user equipment (UE) (22) processing timeline for whether the multiplexing of any uplink control information (UCI) messages and the physical uplink shared channel (PUSCH) is satisfied.

9. The method of claim 8, wherein, Receiving the PUCCH transmission further includes one of the following: Based at least in part on whether the UE processing timeline of multiplexing one of the UCI messages and the PUSCH is satisfied, when the UCI message is multiplexed on the Physical Uplink Shared Channel (PUSCH), the PUCCH transmission is received; and The PUCCH transmission is received when the UE processing timeline of the UCI message multiplexed with the PUSCH is satisfied, at least in part based on whether the PUSCH and the UCI message are retained for the transmission and the earlier PUSCH and the UCI message are discarded.

10. The method of claim 6, wherein, Receiving the PUCCH transmission is at least partially based on a utility maximization function.

11. A user equipment (UE) (22) configured to communicate with a network node (16), the UE (22) including processing circuitry (84) configured to cause the UE (22) to: In response to the overlap of PUCCH resources in the time slot, candidate physical uplink control channel (PUCCH) resources are removed from the sub-time slot (S136), whereby... The candidate PUCCH resource extends from the sub-slot to the next sub-slot, thereby causing the overlap; and Transmit a first uplink control information (UCI) message with a first priority for transmission within overlapping PUCCH resources, wherein a second UCI message with a second priority lower than the first priority for transmission within the overlapping PUCCH resources is discarded to resolve the overlap.

12. The user equipment (22) as claimed in claim 11, wherein, Each PUCCH resource must be configured in a single sub-slot.

13. The user equipment (22) as claimed in claim 11, wherein, The processing circuit (84) is further configured to cause the user equipment (22): Determine whether the UE processing timeline of any of the UCI messages shared with the Physical Uplink Channel (PUSCH) is satisfied, and the overlapping resolution is at least in part based on the determination.

14. The user equipment (22) as claimed in claim 13, wherein, The processing circuit (84) is further configured to cause the user equipment (22) to perform one of the following: Based at least in part on the determination, one of the UCI messages is multiplexed on the Physical Uplink Shared Channel (PUSCH); and Based at least in part on the determination, the later of the PUSCH and the UCI messages is reserved for transmission and the earlier of the PUSCH and the UCI messages is discarded.

15. The user equipment (22) as claimed in claim 11, wherein, The overlapping solutions are at least partially based on utility maximization functions.

16. A network node (16) configured to communicate with a user equipment (UE) (22), the network node (16) including processing circuitry (68) configured to cause the network node (16) to: Receive (S134) Physical Uplink Control Channel (PUCCH) transmission, wherein the PUCCH resources used for the PUCCH transmission are at least partially removed from the sub-slots based on the overlap of PUCCH resources in the slots, wherein, The PUCCH resources used for the PUCCH transmission are at least partially based on the removal of the overlapping candidate PUCCH resources caused by extending from the sub-slot to the next sub-slot, wherein a first uplink control information (UCI) message with a first priority is transmitted within the overlapping PUCCH resources, and a second UCI message with a second priority lower than the first priority is discarded within the overlapping PUCCH resources to resolve the overlap.

17. The network node (16) as claimed in claim 16, wherein, Each PUCCH resource must be configured in a single sub-slot.

18. The network node (16) as described in claim 16 or 17, wherein, The PUCCH resources used for the transmission of the PUCCH are based at least in part on the user equipment (UE) (22) processing timeline for whether the multiplexing of any uplink control information (UCI) messages and the physical uplink shared channel (PUSCH) is satisfied.

19. The network node (16) as described in claim 18, wherein, The processing circuit (68) is configured to cause the network node (16) to receive the PUCCH transmission by performing one of the following: The PUCCH transmission is received when the UCI message is multiplexed on the Physical Uplink Shared Channel (PUSCH), based at least in part on whether the UE processing timeline of multiplexing one of the UCI messages and the PUSCH is satisfied. The PUCCH transmission is received when the UE processing timeline of the UCI message multiplexed with the PUSCH is satisfied, at least in part based on whether the PUSCH and the UCI message are retained for the transmission and the earlier PUSCH and the UCI message are discarded.

20. The network node (16) as claimed in claim 16, wherein, The processing circuit (68) is configured to cause the network node (16) to receive the PUCCH transmission at least in part based on the utility maximization function.

Images