Handling resource assignment for feedback reception in wireless communication network

Abstract

Embodiments of present disclosure provide a method (300) performed by a network node (202) for communicating with a plurality of User Equipments, UEs (204-1 - 204-N) in a Time Division Duplex, TDD, scheme. The method (300) comprises establishing that first UE (204-1) is scheduled for first downlink data (D1) on first downlink slot (D601) associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback, scheduling, for first UE (204-1), second downlink data (D2) on a second downlink slot (D602), scheduling PUCCH resource for ACK / NACK feedback; and transmitting second downlink data (D2) to first UE (204-1) on second downlink slot (D602) while instructing the first UE (204-1) to send ACK / NACK feedback pertaining the second downlink data (D2) on pending uplink slot (U605) using the PUCCH resource associated with second downlink data (D2).

Description

[0001] HANDLING RESOURCE ASSIGNMENT FOR FEEDBACK RECEPTION IN WIRELESS COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to the field of wireless communication. More particularly, it relates to a method, a network node, and computer program products for communicating with a plurality of User Equipments, UEs, in a wireless communication network.

[0004] BACKGROUND

[0005] Fifth generation or 5G New Radio, NR, network overcomes limitations of existing cellular networks by allowing for higher data rates, higher throughput, less latency, and less energy consumption and satisfying ever increasing traffic demand. Thereby, improved network performance can be achieved. The network performance improvement is achieved by the NR network using a number of advanced techniques, which comprise, for example, beamforming, massive multiple-input multiple-output, MIMO, full dimensional MIMO, FD-MIMO, advanced antenna array techniques, large-scale antenna techniques, Time Division Duplex, TDD, scheme, or the like.

[0006] In the NR network, a Physical Uplink Control Channel, PUCCH, is used to carry Uplink Control Information, UCI, from a User Equipment, UE, to a network node. The UCI comprises one or more of: an acknowledgement, ACK, or Negative ACK, NACK, information / bits, Scheduling Requests, SRs, and Channel State Information, CSI. All combinations of the above-described UCI can be sent in the PUCCH. UCI is described in 3GPP TS 38.212 V18.3.0 (2024-06) and is dealt with in item 6.3.

[0007] Further, the NR network supports five different PUCCH formats, PFs, for example, PFO, PF1, PF2, PF3, and PF4. Each PF is classified in terms of factors like physical resource allocation, a number of bits it can carry, or the like. Specifically, the PFO, and PF1 are used to carry the UCI of a size of 1 or 2 bits. The PF2, the PF3, and the PF4 are used to carry the UCI of a size of more than 2 bits. The PFO and the PF2 are short PUCCH, since the PFO and the PF2 can only be 1~2 Orthogonal Frequency Division Multiplexing, OFDM, symbols in length. The PF1, the PF3, and the PF4 are long PUCCH, sine the PF1, the PF3, and the PF4 can be 4—14 OFDM symbols in length.

[0008] The PUSCH (Physical Uplink Shared Channel) is used to transfer uplink user data and UCI.

[0009] Details of PUSCH can be found in TS 38.211 V18.3.0 (2024-06), 38.212 V18.3.0 (2024-06), 38.214 V18.3.0 (2024- 06), and 38.331 18.2.0 (2024-06).

[0010] SUMMARY An object of the present disclosure is to provide a method, a network node, and a computer program product for communicating with a plurality of User Equipments, UEs, in a wireless communication network to mitigate, alleviate, or eliminate all or at least some of the above-discussed drawbacks of presently known solutions.

[0011] This and other objects are achieved by means of a method, a network node, and a computer program product as defined in the appended claims. The term exemplary is in the present context to be understood as serving as an instance, example or illustration.

[0012] According to a first aspect of the present disclosure, a method performed by a network node for communicating with a plurality of User Equipments, UEs, in a Time Division Duplex, TDD, scheme is provided. The TDD scheme comprising a plurality of transmission slots for communicating with the plurality of UEs. The method comprises establishing that a first UE of the plurality of UEs is scheduled for first downlink data (D1) on a first downlink slot of the plurality of transmission slots and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot of the plurality of transmission slots, for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format. The method further comprises scheduling, for the first UE, second downlink data (D2) on a second downlink slot of the plurality of transmission slots; scheduling, for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE pertaining the second downlink data (D2) on the pending uplink slot and transmitting the second downlink data (D2) to the first UE on the second downlink slot while instructing the first UE to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot using the PUCCH resource associated with the second downlink data (D2). The scheduling the PUCCH resource associated with the second downlink data (D2) comprises selecting a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled, the method comprises scheduling the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

[0013] In some embodiments, when it is determined that the one or more conditions are fulfilled, the method further comprises changing the PUCCH resource associated with the first downlink data (D1) to the scheduled PUCCH resource associated with the second downlink data (D2).

[0014] In some embodiments, the PUCCH format of the PUCCH resource associated with the first and / or second downlink data (D1, D2) is indicative of any of: a number of bits of information the corresponding PUCCH resource can carry; a number symbols for assignment to the corresponding PUCCH resource; and a number of Physical Resource Blocks, PRBs, for assignment to the corresponding PUCCH resource.

[0015] In some embodiments, the selection of PUCCH format for the PUCCH resource associated with the second downlink data (D2) is selected based on required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2).

[0016] In some embodiments, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of bits of information of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of bits of information is less than a first threshold.

[0017] In some embodiments, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of symbols of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of symbols is less than a second threshold.

[0018] In some embodiments, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of PRBs of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of PRBs is less than a third threshold.

[0019] In some embodiments, the one or more conditions are fulfilled if, in addition, the selected PUCCH format is a predetermined PUCCH format of any of the PUCCH formats according to 3GPP TS 38.331 v17.2. Release 17.

[0020] In some embodiments, the predetermined format is any of PUCCH format 0 and PUCCH format 1.

[0021] In some embodiments, the one or more conditions are fulfilled if, in addition, a signal quality metric of a signal between the network node and first UE is less than a fourth threshold and / or when the signal quality metric is above a fifth threshold.

[0022] In some embodiments, the one or more conditions are fulfilled if, in addition, the first UE is configured with a PUCCH resource set comprising a PUCCH resource, different from the PUCCH resource associated with first downlink data (D1), that is not scheduled for ACK / NACK feedback from any UE of the plurality of UEs.

[0023] In some embodiments, when it is determined that the one or more conditions are not fulfilled, scheduling the PUCCH resource associated with the second downlink data (D2) as the same PUCCH resource as the PUCCH resource associated with first downlink data (D1). In some embodiments, transmitting the first downlink data (D1) to the first UE on the first downlink slot while instructing the first UE to send the ACK / NACK feedback pertaining the first downlink data (D1) on the pending uplink slot using the PUCCH resource associated with the first downlink data (D1).

[0024] In some embodiments, the first downlink slot precedes the second downlink slot.

[0025] In some embodiments, the second downlink slot and the first downlink slot are simultaneous.

[0026] In some embodiments, the network node is configured to perform digital beam forming.

[0027] According to a second aspect of the present disclosure, an apparatus of a network node for communicating with a plurality of User Equipments, UEs, in a Time Division Duplex, TDD, scheme. The TDD scheme comprises a plurality of transmission slots for communicating with the plurality of UEs. The apparatus comprises a controlling circuitry configured to cause establishing that a first UE of the plurality of UEs is scheduled for first downlink data (D1) on a first downlink slot of the plurality of transmission slots and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot of the plurality of transmission slots, for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format. The method further comprises scheduling, for the first UE, second downlink data (D2) on a second downlink slot of the plurality of transmission slots; scheduling, for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE pertaining the second downlink data (D2) on the pending uplink slot and transmitting the second downlink data (D2) to the first UE on the second downlink slot while instructing the first UE to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot using the PUCCH resource associated with the second downlink data (D2). The scheduling the PUCCH resource associated with the second downlink data (D2) comprises selecting a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled. The method comprises scheduling the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

[0028] A third aspect is a network node comprising the apparatus of the second aspect.

[0029] According to a fourth aspect of the present disclosure, there is provided a computer program product comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions. The computer program is loadable into a data processing unit and configured to cause execution of the method according to the first aspect when the computer program is run by the data processing unit. In some embodiments, any of the above aspects may additionally have features identical with or corresponding to any of the various features as explained above for any of the other aspects.

[0030] An advantage of some embodiments is that the network node may not decode a PUCCH received from the UE using a number of bits other than the number of bits being assigned for that PUCCH. The UE may send the PUCCH using a wrong number of bits when the UE has failed to decode a last PDCCH. Thus, incorrect decoding of the PUCCH (i.e., ACK / NACK feedback) may be avoided at the network node.

[0031] An advantage of some embodiments is that unnecessary retransmissions at a higher layer of the network node and any other risks that may cause due to the false decoding of the PUCCH at the network node may be avoided. Hence, data transmissions may be not delayed for an end user.

[0032] BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The foregoing will be apparent from the following more particular description of the example embodiments, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the example embodiments.

[0034] Figs 1A, I Bshow a non-public reference design.

[0035] Fig. 1 A discloses a concept of a Time Division Duplex, TDD, scheme for a 3 / 1 pattern using with an Analogue Beam Forming, ABF;

[0036] Fig. 1 B discloses a flowchart illustrating example method steps of a method performed by a network node for communicating with at least a User Equipment, of a plurality of UEs in a TDD scheme according to a nonpublic reference design;

[0037] Fig. 2 discloses an example wireless communication network used for illustrating an example operation according to the present disclosure in relation to operation in a reference example scenario;

[0038] Fig. 3 is a flowchart illustrating example method steps of a method performed by a network node for communicating with a plurality of UEs according to an embodiment of the invention;

[0039] Figs. 4A and 4B disclose example illustrations of handling assignment of PUCCH resources for feedback reception according to a non-public reference design;

[0040] Fig. 5 is a signalling diagram illustrating example signalling for assigning PUCCH resources for feedback reception according to an embodiment of the invention; Figs. 6A and 6B disclose example illustrations of handling assignment of PUCCH resources for feedback reception according to an embodiment of the invention;

[0041] Fig. 7 is a flowchart illustrating example method steps according to an embodiment of the invention performed by a network node for communicating with a plurality of User Equipments; and

[0042] Fig. 8 is a schematic block diagram illustrating an example apparatus according to an embodiment of the invention.

[0043] DETAILED DESCRIPTION

[0044] Aspects of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. The method and apparatus disclosed herein can, however, be realized in many different forms and should not be construed as being limited to the aspects set forth herein. Like numbers in the drawings refer to like elements throughout.

[0045] Embodiments of the present disclosure will be described and exemplified more fully hereinafter with reference to the accompanying drawings. The solutions disclosed herein can, however, be realized in many different forms and should not be construed as being limited to the embodiments set forth herein.

[0046] It will be appreciated that when the present disclosure is described in terms of a method, it may also be embodied in one or more processors and one or more memories coupled to the one or more processors, wherein the one or more memories store one or more programs that perform the steps, services and functions disclosed herein when executed by the one or more processors.

[0047] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods and / or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0048] Furthermore, the following terms are used throughout the description given below: - User Equipment: As used herein, a UE is any type of device that has access to (i.e., is served by) a wireless communication system / network by communicating wirelessly with network nodes and / or other wireless devices. Communicating wirelessly can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through air. Some examples of the UE include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP, VoIP, phones, wireless local loop phones, desktop computers, personal digital assistants, PDAs, wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop-embedded equipment, LEE, laptop-mounted equipment, LME, smart devices, wireless customer-premise equipment, CPE, mobile-type communication, MTC, devices, Internet-of-Things, loT, devices, vehicle-mounted wireless terminal devices, D2D UEs, V2X UEs, etc. Unless otherwise noted, the term "UE” is used interchangeably herein with the term "wireless device”.

[0049] - Network Node: As used herein, a "network node” is any node that is either part of a radio access network or a core network of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in the cellular communications network, to enable and / or provide wireless access to the UE, and / or to perform other functions (e.g., administration) in the cellular communications network.

[0050] - Physical Downlink Control Channel, PDCCH: As used herein, a "PDCCH” is a physical channel that carries Downlink Control Information, DCI, for downlink or uplink.

[0051] - Physical Downlink Shared Channel, PDSCH: As used herein, a "PDSCH” is a downlink physical channel that delivers user data from the network node to the UE.

[0052] - Physical Uplink Shared Channel, PUSCH: As used herein, "PUSCH” is a physical uplink channel that delivers user data and optionally Uplink Control Information, UCI, from the UE to the network node.

[0053] - Physical Uplink Control Channel, PUCCH: As used herein, "PUCCH” is a physical channel that carries a set of information referred as Uplink Control Information, UCI. The UCI comprises Scheduling Requests, SRs, Acknowledgment, ACK / Negative ACK, NACK bits, Channel State Information, CSI.

[0054] - PUCCH format 0, PFO: As used herein, "PFO” can be one or more two symbols long (with or without frequency hopping) and can carry one or two ACK / NACK bits together with at most one SR bit. The PFO may be always one Physical Resource Block, PRB, wide.

[0055] - PF1 : As used herein, “PF1” can be four to fourteen symbols long (with or without frequency hopping) and can carry one or two ACK / NACK bits. If the one or two ACK / NACK bits to be transmitted simultaneously with a SR, the PUCCH transmissions may not occur and instead SR content is multiplexed into the PUCCH resource being used for transmission of the ACK / NACK. The PF1 may always be one PRB wide.

[0056] - PF2: As used herein, "PF2” can be one or two symbols long (with or without frequency hopping) and can carry three or more (up to several tens) ACK / NACK bits, together with CSI and SR, if configured. The PF2 encodes the UCI information and transmits the encoded UCI over subcarriers of one or two OFDM symbols. To accommodate larger payloads, the PF2 may extend over multiple PRBs.

[0057] - PF3: As used herein, "PF3” can be four to fourteen symbols long (with or without frequency hopping) and can carry three to a few hundred bits, together with CSI and SR, if configured. The PF3 offers the largest payloads size across all the PFs. To accommodate larger payloads, the PF3 may extend over multiple PRBs.

[0058] - PF4: As used herein, "PF4” can be four to fourteen symbols long (with or without frequency hopping) and can carry three to a several tens of bits, together with CSI and SR, if configured.

[0059] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is generally used. However, the concepts disclosed herein are not limited to a 3GPP system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access, WCDMA, Worldwide Interoperability for Microwave Access, WIMax, Ultra Mobile Broadband, UMB, and Global System for Mobile Communications, GSM, may also benefit from the concepts, principles, and / or embodiments described herein.

[0060] In addition, functions and / or operations described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. Furthermore, although the term "cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

[0061] In general, a UE may be configured with a number of PUCCH resource sets, where a PUCCH resource set is a set of PUCCH resources used by the UE. According to 38.331 V18.2.0 (2024-06) , a UE is configured with up to four PUCCH resource sets, where a PUCCH resource set is denoted PUCCH-ResourceSet. One PUCCH-ResourceSet is specified by the following fields: pucch-ResourceSetld, resourceList, and maxPayloadSize. The field pucch- ResourceSeM is specified by the value PUCCH-ResourceSetld, which is an integer. The field resourceList is specified by a sequence of PUCCH-Resourceld, where each PUCCH-Resourceld is a value in the form of an integer. The field maxPayloadSize is specified by an integer and describes the maximum number of UCI information bits that the UE may transmit using a particular PUCCH resource set.

[0062] As an example, a PUCCH-ResourceSet can be specified as:

[0063] PUCCH-ResourceSet = SEQUENCE { pucch-ResourceSetld PUCCH-ResourceSetld, resourceList SEQUENCE (SIZE (8..maxNrofPUCCH-ResourcesPerSet))

[0064] OF PUCCH-Resourceld, maxPayloadSize INTEGER (4..25S) OPTIONAL - Need R

[0065] } In general, a PUCCH resource describes how to transmit the CSI information. According to TS 38.331 V18.2.0 (2024-06), a PUCCH resource is denoted PUCCH-Resource and and is specified by the following fields: pucch- Resourceld, startingPRB, intraSlotFreguencyHopping, secondHopPRB, and format. The field pucch-Resourceld is specified by the integer value PUCCH-Resourceld. The field startingPRB is specified by the value PRB-ld, which identifies a Physical Resource Block (PRB) position within a carrier. The field intraSlotFreguencyHopping is an optional field used when frequency hopping is activated. The field secondHopPRB is specified by the value PRB-ld, and identifies a PRB position within a carrier used when the optional frequency hopping is activated.

[0066] As an example, a PUCCH-Resource can be specified as:

[0067] PUCCH-Resource ::= SEQUENCE { pucch-Resourceld PUCCH-Resourceld, startingPRB PRB-ld, intraSlotFreguencyHopping ENUMERATED {enabled } OPTIONAL, - Need R secondHopPRB PRB-ld OPTIONAL, - Need R format CHOICE { formatO PUCCH-formatO, formatl PUCCH-formatl, format2 PUCCH-format2, formats PUCCH-format3, format4 PUCCH-format4

[0068] }

[0069] }

[0070] In general, a particular PUCCH resource is specified by a particular format. Each format may be classified in terms of factors like physical resource allocation, a number of bits of information the corresponding PUCCH resource can carry, a number symbols for assignment to the corresponding PUCCH resource, and more.

[0071] As can be seen from the example PUCCH-Resource above, the NR network supports five different formats according to to TS 38.331 V18.2.0 (2024-06). The field format can be any one of the following five child fields: formatO, formatl, formats, formats, and format4, which are specified by the fields PUCCH-formatO, PUCCH-formatl , PUCCH- format2, PUCCH-format3, and PUCCH-format4, respectively. Specifically, the formatO and formatl are used to carry the UCI of a size of 1 or 2 bits. The formats, the formats, and the format4 are used to carry the UCI of a size of more than 2 bits. The formatO and the formats may said to be short PUCCH formats, since the formatO and the formats can only be 1 or 2 Orthogonal Frequency Division Multiplexing (OFDM) symbols in length. The formatl, the formats, and the format4 may be said to be long PUCCH formats, since the formatl, the formats, and the format4 can be 4 to 14 OFDM symbols in length. According to to TS 38.331 V18.2.0 (2024-06), each of the fields PUCCH-formatO, 1,2, 3, 4 are specified by the fields nrofSymbols and startingSymbollndex. The field nrofSymbols is specified by an integer and is indicative of the amount of symbols used by the PUCCH-Resource. The field startingSymbollndex is specified by an integer and is indicative of the start symbol for the PUCCH-resource.

[0072] The field PUCCH-formatO can be specified as:

[0073] PUCCH-formatO = SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (1..2), startingSymbollndex INTEGER(0..13) }

[0074] The field initialCyclicShift is specified by an integer and is indicative of cyclic shift configuration.

[0075] The field PUCCH-formatl can be specified as:

[0076] PUCCH-formatl = SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (4..14), startingSymbollndex INTEGER(0..10), timeDomainOCC INTEGER(0..6) }

[0077] The field timeDomainOCC is specified by an integer value and is indicative of time-domain orthogonal cover code.

[0078] The field PUCCH-format2 can be specified as:

[0079] PUCCH-format2 = SEQUENCE { nrofPRBs INTEGER (1.. 16), nrofSymbols INTEGER (1..2), startingSymbollndex INTEGER(0..13) }

[0080] The field nrofPRBs is specified by an integer value and is indicative of the number of PRB used by the PUCCH resource. The field PUCCH-format3 can be specified as:

[0081] PUCCH-format3 = SEQUENCE { nrofPRBs INTEGER (1.. 16), nrofSymbols INTEGER (4.. 14), startingSymbollndex INTEGER(O..1O) }

[0082] The field PUCCH-format4 can be specified as:

[0083] PUCCH-format4 = SEQUENCE { nrofSymbols INTEGER (4..14), occ-Length ENUMERATED {n2,n4}, occ-lndex ENUMERATED {n0,n1,n2,n3}, startingSymbollndex INTEGER(0..10)

[0084] The field occ-Length is specified by an enumerated value and is indicative of the orthogonal cover code length. The field occ-lndex is specified by an enumerated value and is indicative of the orthogonal cover code index.

[0085] Although PUCCH-formatO, PUCCH-formatl, and PUCCH-format4 are not specified by the field nrofPRBs, the number of PRBs is implicit for these formats since they always use 1 PRB.

[0086] In general, a network node in the NR network configures the UE with a list of PUCCH resource sets (i ,e. , multiple PUCCH-ResourceSet:s), where each PUCCH resource set is provided with a list of PUCCH resources (i.e., multiple PUCCH-Resource:s). The network node transmits the configured list of PUCCH resource sets and the list of PUCCH resources for each PUCCH resource set to the UE beforehand in Radio Resource Control (RRC) setup signals. Furthermore, the list of PUCCH resource sets and the PUCCH resources configured for the UE can be modified during a call / data transfer.

[0087] As mentioned above, Figs. 1A, and 1 B, show a non-public internal reference implementation by the applicant.

[0088] Fig. 1 A discloses a concept of a Time Division Duplex, TDD scheme for a 3 / 1 pattern using with an Analogue Beam Forming, ABF. In New Radio, NR, network, a network node communicates uplink and downlink data with a plurality of User Equipments, UEs, in accordance with the TDD scheme. The TDD scheme comprises a plurality of transmission slots (slot n - slot n+7) for communicating uplink and downlink data with the plurality of UEs, in suitable channels. The channels comprise a Physical Downlink Control Channel, PDCCH 100, for downlink (DL), a Physical Downlink Shared Channel, PDSCH 101, a PDCCH 104 for uplink (UL), a Physical Uplink Shared Channel, PUSCH 102, and a Physical Uplink Control Channel, PUCCH 103. As disclosed in Fig. 1 A, among the transmission slots n - n+7, slots n, n+1, n+2, n+4, n+5, and n+6 represent downlink slots and slots n+3 and n+7 represent uplink slots. A slot n represents a downlink slot, where the UE when decoding the PDCCH 100 receives the downlink data in the PDSCH 101. The UE reports feedback of decoded result, for example, acknowledgment, ACK, or Negative ACK, NACK, in the PUCCH 103. The PDDCH 104 in the slot n+3 comprises a PDCCH that represents an uplink transmission. The PDCCH 104 comprises a delay field 107, which indicates when the PUSCH 102 transmission will start in slot n+7. Further, a field 105 illustrates the PDCCH 100, which contains a field representing where the downlink data (PDSCH data) will be received. A field 106 illustrates the PDCCH 100, which contains a second field icon representing when the PUCCH 103 will be transmitted.

[0089] Further, for the ABF, a phased array antenna may be used to define a number of wide and narrow beams. A plurality of narrow beams is arranged within each respective wide beam such that a wide beam serves a larger geographical area compared to a narrow beam. A narrow beam has a larger antenna gain compared to a wide beam. The wide beams and the narrow beams are typically fixed after the phased array antenna has been mounted and adjusted.

[0090] With respect to the ABF, it is seen that in the slot n, a beam may point at a certain direction towards the UE, wherein the PDCCH 100 and the PDSCH 101 are aimed for. While in the slot n+1 and the slot n+2, the beam may be in the same direction or other direction dependent on which the UE data is aimed for in that particular slot. In the slot n+3, the beam may be first set against the UE which may send the uplink data in the PUSCH 102 and then possibly the direction may be switched to a part in the slot n+3 to receive data from the UE that was scheduled for transmission at the slot n+3 (not shown in Fig. 1A). Further, in the PUCCH 103, symbols denoted ‘O' and T indicates a beam, which may be set to receive PUCCH data from the slot n, the slot n+1, and the slot n+2. If the slot n, the slot n+1, and the slot n+2 represent data from different UEs, the beam may be changed between the symbols in the PUCCH 103.

[0091] Fig. 1 B is an example flowchart illustrating method steps performed by a network node for communicating with a plurality of User Equipments, UEs, in a TDD.

[0092] At step 110, the network node determines if there is any pending downlink data (DL data) for a UE among the plurality of UEs. If there is any pending downlink data for the UE, at step 111, the network node determines whether there is any downlink slot for transmission of the pending downlink data to the UE. When it has been determined there is no downlink slot, the network node repeats from step 110.

[0093] When it has been determined that there is a downlink slot for the pending downlink data to the UE, at step 112, the network node assigns a Physical Uplink Control Channel, PUCCH, format, PF, for respective Acknowledgement, ACK / Negative ACK, NACK, feedback from the UE on a subsequent uplink slot pertaining to the respective downlink data. In some examples, the ACK / NACK feedback may comprise ACK or NACK bits. In some examples, the ACK / NACK feedback may comprise ACK or NACK bits and a possible Scheduling Request, SR, bit. At step 113, the network node determines if the assigned PF has already been used for a previous ACK / NACK from the same UE on the same uplink slot.

[0094] If the assigned PUCCH format has already been used for a previous ACK / NACK from the same UE on the same uplink slot, at step 114, the network node, for the ACK / NACK feedback from the UE on the subsequent uplink slot, assigns the same PUCCH resource that has been used for the previous ACK / NACK from the UE.

[0095] If on the other hand the assigned PUCCH format has not been used for a previous ACK / NACK from the same UE, at step 115, the network node, for ACK / NACK feedback from the UE on the subsequent uplink slot, assigns a PUCCH resource with the assigned PUCCH format, from step 112.

[0096] At step 116, the network node transmits the downlink data to the UE in the downlink slot, while instructing the UE to send the ACK / NACK on the subsequent uplink slot with the assigned PUCCH resource, from step 114 or 115. The network node transmits the downlink data to the UE in a Physical Downlink Shared Channel, PDSCH. The network node transmits Downlink Control Information, DCI, in a Physical Downlink Control Channel, PDCCH, which indicates the assigned PUCCH resource for the ACK / NACK pertaining to the transmitted PDSCH including all previous sent PDSCH that utilise the same UL slot for its feedback.

[0097] Fig. 2 discloses an example wireless communication network 2000. In the below, the operation in such wireless communication network 200 according to an example reference scenario is compared to operation according to an example of the present disclosure.

[0098] The wireless communication network 2000 may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some examples, the wireless communication system 2000 may be configured to operate according to specific standards or other types of predefined rules of procedures. Examples of the wireless communication network 2000 may include, but are not limited to, a fifth generation, 5G, new radio, NR network, or any other similar next generation network.

[0099] The wireless communication network 2000 comprises a network node 202 and a plurality of User Equipments, UEs, 204-1 - 204-N.

[0100] The network node 202 may be a radio node / base station, BS. In an example, the network node 202 may be a gNodeB, gNB. The UE (204-1 - 204-N) may be a wireless device that is stationary or mobile and may also be referred to as a remote station, a mobile station, mobile equipment, a terminal, a remote terminal, an access terminal, or the like. Examples of the wireless device may include, but are not limited to, a cellular phone, a personal digital assistant, PDA, a wireless modem, a wireless communication device, a handheld device, a subscriber unit, a laptop computer, and so on. In some examples, as disclosed in FIG. 2, the network node 202 communicates with the plurality of UEs 204-1 - 204- N over a plurality of antennas using an analogue beam forming, ABF, wherein only UE can be scheduled at a time. The plurality of antennas using the ABF are associated with respective wide beams WB1-WBN and narrow beams, NB (only a single narrow beam is indicated for clarity of illustration). The wide beams WB1-WBN may be arranged into contiguous substantially non-overlapping areas. Moreover, each wide beam may be further subdivided into a number of narrow beam areas. For each wide beam for example, WB2, at least one narrow beam (NB) forms a joint area with the WB2. The plurality of UEs 204-1 - 204-N may appear under any of these areas corresponding to the wide beams and the narrow beams.

[0101] Specifically, the network node 202 communicates uplink and downlink data in a Time Division Duplex, TDD, scheme with a plurality of UEs 204-1 - 204-N. The TDD scheme comprising a plurality of transmission slots for communicating the uplink and downlink data with the plurality of UEs in respective physical channels. The transmission slots may comprise downlink slots, uplink slots, and special slots. The physical channels may comprise a Physical Downlink Control Channel, PDCCH, a Physical Downlink Shared Channel, PDSCH, a Physical Uplink Shared Channel, PUSCH, and a Physical Uplink Control Channel, PUCCH. In the context of this disclosure, the wireless communication network 2000 may support five different PUCCH formats, PFs, for example, PF0, PF1, PF2, PF3, and PF4.

[0102] In the wireless communication system 2000, the network node 202 transmits downlink data to a UE, for example, UE 204-1, in the PDSCH. Meanwhile, via Downlink Control Information, DCI, in the PDCCH, the network node 202 instructs the UE 204-1 to send respective Acknowledgment, ACK / Negative ACK, NACK, feedback for the PDSCH on an uplink slot using a PUCCH resource assigned by the network node 202 for that ACK / NACK feedback. The UE decodes the PDSCH and transmits the ACK / NACK feedback for the PDSCH to the network node on the uplink slot. The UE transmits the ACK / NACK feedback to the network node in the PUCCH using the PUCCH resource decoded from the PDCCH.

[0103] Consider an example reference scenario, wherein the network node 202 establishes that pending first and second downlink data appear in first and second downlink slots, respectively, to the UE 204-1. In such a scenario, the network node 202 assigns a one and the same PF for respective ACK / NACK feedback from the UE on a one and the same subsequent uplink slot pertaining to the pending first and second downlink data. The network node 202 thereafter may assign a one and the same PUCCH resource (for example, ID1 or ID2) for each ACK / NACK feedback on the subsequent uplink slot.

[0104] Upon assigning the PUCCH resource, the network node 202 transmits the first and second downlink data to the UE 204-1 in the first and second downlink slots using first and second PDSCH, respectively. Along with the first and second PDSCH, the network node 202 transmits first and second PDCCH pertaining to the first and second PDSCH to the UE 204-1. The first and second PDCCH instruct the UE 204-1 to send ACK / NACK feedback to the network node 202 on the uplink slot pertaining to the first and second PDSCH. The first and second PDCCH also provide an indication of the assigned PUCCH resource for the ACK / NACK feedback. In some examples, the ACK / NACK feedback may comprise ACK or NACK bits and a possible Scheduling Request, SR, bit.

[0105] In the above-described example reference scenario, if the UE 204-1 has decoded the first PDCCH and the first PDSCH and has failed to decode the second PDCCH, the UE 204-1 transmits the ACK / NACK feedback pertaining to the first PDSCH to the network node 202 in the PUCCH using the PUCCH resource decoded from the first PDCCH. Thereby, the UE 204-1 may send the wrong ACK / NACK feedback. However, the network node 202 may decode the PUCCH comprising the wrong ACK / NACK feedback from the UE 204-1, due to the usage of the same PUCCH resource for the first and second PDCCH. Due to the false decoding of the PUCCH, the network node 202 determines that both the first and second PDSCH / PDCCH have been correctly decoded by the UE 204-1 and the UE 204-1 has transmitted the PUCCH according to the second PDCCH. Such a false determination may lead to unnecessary retransmissions at a higher layer of the network node 202 and cause a delay for an end user.

[0106] The above-described problem may particularly occur with the assignment of the PF0 or the PF1 .

[0107] Therefore, the network node 202 implements a method for communicating with the plurality of UEs 204-1 - 204-N, by avoiding a false decoding of the PUCCH from any UE (at the network node 202). Although the method implemented by the network node 202 may be equally applicable for the plurality of UEs 204-1 - 204-N, the examples herein are described by considering a UE 204-1 for ease of understanding.

[0108] Upon establishing that the pending downlink data appears in at least two downlink slots to the UE 204-1, the network node 202 assigns a PF for the respective ACK / NACK feedback from the UE 204-1 on a one and the same subsequent uplink slot pertaining to respective downlink data in at least two downlink slots. Upon assigning the PF, the network node 202 assigns a PUCCH resource for each respective ACK / NACK feedback on the subsequent uplink slot.

[0109] For assigning the PUCCH resource, the network node 202 determines if the PF0 or the PF1 is assigned for each respective ACK / NACK feedback on the subsequent uplink slot. If the PF0 or the PF1 is assigned, the network node 202 assigns different PUCCH resources for the respective ACK / NACK feedback from the UE on the subsequent uplink slot. If the PF0 or the PF1 is not assigned, the network node 202 assigns the same PUCCH resource for the respective ACK / NACK feedback from the UE on the subsequent uplink slot. The network node 202 thereafter transmits the downlink data to the UE in the at least two respective downlink slots, while instructing the UE 204-1 to send the ACK / NACK feedback on the subsequent uplink. The network node may transmit DCI to the UE 204-1 in the PDCCH in order to instruct the UE 204-1 to send the ACK / NACK feedback on the subsequent uplink with the assigned PUCCH resource. Advantageously, with the proposed method, the first PDCCH indicates a resource only for the ACK / NACK feedback for the first PDSCH, since the second slot has not yet been planned. However, the second PDCCH actually indicate a resource that shall carry the ACK / NACK feedback for both the first and second PDSCH. Therefore, the network node 202 may only decode the PUCCH comprising the ACK / NACK feedback from the UE 204-1 according to the second PDCCH. Thus, there may be no false decoding of the PUCCH at the network node 202. If decoding fails, the network node 202 may retransmit both the first and second PDCCH.

[0110] In addition, the network node 202 may decode the first and second PUCCH (comprising respective first and second ACK / NACK feedback) from the UE 204-1 in parallel, for example, the first PUCCH with the first PDCCH and the second PUCCH with the second PDCCH. If decoding of the first PUCCH with the first PDCCH is successful, the network node 202 may determine that the UE 204-1 has failed to decode the second PDCCH but has correctly decoded the first PDCCH.

[0111] Various examples for communicating with the UEs 204-1 - 204-N in the wireless communication network 2000 are explained in conjunction with figures in the later parts of the description.

[0112] Fig. 3 is a flowchart illustrating example method steps of a method 300 performed by a network node for communicating with a plurality of UEs in a Time Division Duplex, TDD, scheme. The TDD scheme comprises a plurality of transmission slots for communicating with the plurality of UEs. The transmission slots comprise downlink slots, uplink slots and special slots.

[0113] For simplicity, it is throughout the disclosure assumed that the UEs are be awake and not in a Continuous Discontinuous Reception, cDRX state.

[0114] At step 310, the method 300 establishes that a first UE (204-1) of the plurality of UEs (204-1 -204-N) is scheduled for first downlink data (D1) on a first downlink slot (D601) of the plurality of transmission slots (601-610) and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) of the plurality of transmission slots (601-610), for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format.

[0115] In an example, the first downlink data (along with ACK / NACK instructions) may have already been transmitted to the first UE (204-1). In another example, the first downlink data (together with ACK / NACK instructions) may be planned to be transmitted to the first UE (204-1). The uplink transmission pertaining the first downlink data may not have happened during the establishment that the first UE (204-1) is scheduled for the first downlink slot (D601).

[0116] In another example, the pending uplink slot is following the first and the second downlink slots (D601, D602). At step 320, the method 300 schedules, for the first UE (204-1), the second downlink data (D2) on a second downlink slot (D602) of the plurality of transmission slots (601-610).

[0117] At step 330, the method 300 schedules, for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE (204-1) pertaining the second downlink data (D2) on the pending uplink slot U605.

[0118] The step 330 of scheduling the PUCCH resource associated with the second downlink data (D2) comprises step 331 of selecting a PUCCH format for the PUCCH resource associated with the second downlink data (D2).

[0119] At step 332, the method 300 determines whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled.

[0120] At step 333, the method 300 comprises the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

[0121] Optionally, when it is determined that the one or more conditions are fulfilled, the method further comprises step 333- 1, which comprises changing the PUCCH resource associated with the first downlink data (D1) to the scheduled PUCCH resource associated with the second downlink data (D2). In other words, a rescheduling occurs, wherein the ACK / NACK feedback from the first UE (204-1) pertaining the first and the second downlink data (D1, D2) are merged and assigned to the PUCCH resource selected at step 333.

[0122] Table I below shows two examples of the method disclosed herein. In the table, "RSID” represent the resource ID of the assigned PUCCH resource and "PF” is PUCCH format. In Example #1, it is initially established the first UE is scheduled for first downlink data (D1) on the first downlink slot (D601) and that the first downlink data (D1) is associated with a PUCCH resource scheduled on a pending uplink slot (U605) for ACK / NACK feedback pertaining the first downlink data (D1). In Example #1, for this initial scheduling, the PUCCH resource has RSID 4 and PF 1. At a subsequent step, it determined that ACK / NACK feedback pertaining second downlink data (D2) requires PF 1 as well. Therefore, a new PUCCH resource (with RSID 5) is selected for the ACK / NACK feedback pertaining the first downlink data (D1) and for the ACK / NACK feedback pertaining the second downlink data (D2). In Example #2, it is initially established the first UE is scheduled for first downlink data (D1) on the first downlink slot (D601) and that the first downlink data (D1) is associated with a PUCCH resource scheduled on a pending uplink slot (U605) for ACK / NACK feedback pertaining the first downlink data (D1). In Example #2, for this initial scheduling, the PUCCH resource has RSID 6 and PF 3. At a subsequent step, it determined that ACK / NACK feedback pertaining second downlink data (D2) requires PF 3 as well. Therefore, a new PUCCH resource (with RSID 7) is selected for the ACK / NACK feedback pertaining the first downlink data (D1) and for the ACK / NACK feedback pertaining the second downlink data (D2).

[0123] Table I

[0124] Table II below shows two examples of a non-public reference method. In Example #1, it is initially established the first UE is scheduled for first downlink data (D1) on the first downlink slot (D601 ) and that the first downlink data (D1) is associated with a PUCCH resource scheduled on a pending uplink slot (U605) for ACK / NACK feedback pertaining the first downlink data (D1). In Example #1, for this initial scheduling, the PUCCH resource has RSID 4 and PF 1. At a subsequent step, it determined that ACK / NACK feedback pertaining second downlink data (D2) requires PF 1 as well. However, the initially scheduled PUCCH resource (with RSID 4) is kept and selected for the ACK / NACK feedback pertaining the first downlink data (D1) and for the ACK / NACK feedback pertaining the second downlink data (D2).

[0125] In Example #2, it is initially established the first UE is scheduled for first downlink data (D1) on the first downlink slot (D601) and that the first downlink data (D1) is associated with a PUCCH resource scheduled on a pending uplink slot (U605) for ACK / NACK feedback pertaining the first downlink data (D1). In Example #2, for this initial scheduling, the PUCCH resource has RSID 6 and PF 3. At a subsequent step, it determined that ACK / NACK feedback pertaining second downlink data (D2) requires PF 3 as well. However, the initially scheduled PUCCH resource (with RSID 6) is kept and selected for the ACK / NACK feedback pertaining the first downlink data (D1) and for the ACK / NACK feedback pertaining the second downlink data (D2).

[0126] Table II

[0127] At step 340, the method 300 transmits the second downlink data (D2) to the first UE (204-1) on the second downlink slot (D602) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot (U605) using the PUCCH resource associated with the second downlink data (D2).

[0128] Optionally, the PUCCH format of the PUCCH resource associated with the first and / or second downlink data (D1, D2) is indicative of any of: a number of bits of information the corresponding PUCCH resource can carry; a number symbols for assignment to the corresponding PUCCH resource; and a number of Physical Resource Blocks, PRBs, for assignment to the corresponding PUCCH resource.

[0129] Optionally, the step 331 of the selection of PUCCH format for the PUCCH resource associated with the second downlink data (D2) is selected (331-1) based on required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2).

[0130] In an example, the selection is based on first downlink data (D1) and the second downlink data (D2) and is based on all downlink slots that has HARO feedback to be sent in the used uplink slot.

[0131] Optionally, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of bits of information of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of bits of information is less than a first threshold.

[0132] In an example, the first threshold comprises less than 3 bits.

[0133] Optionally, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of symbols of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of symbols is less than a second threshold.

[0134] In an example, the second threshold comprises less than 4 symbols.

[0135] Optionally, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of PRBs of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of PRBs is less than a third threshold.

[0136] In an example, the third threshold comprises less than 2 or 3 PRBs.

[0137] Optionally, the one or more conditions are fulfilled if, in addition, the selected PUCCH format is a predetermined PUCCH format of any of the PUCCH formats according to 3GPP TS 38.331 V18.2.0 (2024-06).

[0138] Optionally, the predetermined format is any of PUCCH format 0 and PUCCH format 1 . Optionally, the one or more conditions are fulfilled if, in addition, a signal quality metric of a signal between the network node (202) and first UE (204-1) is less than a fourth threshold and / or when the signal quality metric is above a fifth threshold.

[0139] In an example, the signal quality refers to quality of service. The signal quality metric of the signal comprises the signal quality from gNB to UE and from UE to gNB (i.e. UL and DL).

[0140] Optionally, the one or more conditions are fulfilled if, in addition, the first UE (204-1) is configured with a PUCCH resource set comprising a PUCCH resource, different from the PUCCH resource associated with first downlink data (D1), that is not scheduled for ACK / NACK feedback from any UE of the plurality of UEs first UE (204-1 -204-N).

[0141] Optionally, when it is determined that the one or more conditions are not fulfilled, scheduling 334 the PUCCH resource associated with the second downlink data (D2) as the same PUCCH resource as the PUCCH resource associated with first downlink data (D1).

[0142] Optionally, transmitting (340) the first downlink data (D1) to the first UE (204-1) on the first downlink slot (D601) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the first downlink data (D1) on the pending uplink slot (U605) using the PUCCH resource associated with the first downlink data (D1).

[0143] In the illustrated example of FIG. 3, timewise, action "340" occurs after action "330” and before action "350”. However, action "340” can occur earlier such as before step "310” or before action "320” or before action "330”. Alternatively, action "340” may occur at the same time as action "350”..

[0144] Optionally, the second downlink slot (D602) and the first downlink slot (D601) are simultaneous.

[0145] Optionally, the network node (202) is configured to perform digital beam forming.

[0146] Figs. 4A and 4B disclose example illustrations of handling assignment of Physical Uplink Control Channel, PUCCH, format, PF, resources for a User Equipment, UE, according to a reference example.

[0147] Consider an example scenario, as disclosed in Fig. 4A, wherein a network node grants a first Physical Downlink Shared Channel, PDSCH and a second PDSCH for a UE for reception of downlink data D1 and D2 in downlink slots D601 and D602. In such a scenario, if the network node assigns a PF (for example, PF1) for the second PDCCH, that is the same as the PF assigned for the first PDCCH, then the network node also assigns same PUCCH resource (for example, ID1) for the second PDCCH.

[0148] Upon the assignment, at step 1, the network node transmits the first PDSCH comprising the downlink data D1 to the UE in the downlink slot D601. Along with the first PDSCH, the network node transmits a Downlink Control Information, DCI, to the UE in a Physical Downlink Control Channel, PDCCH. The network node via the DCI, instructs the UE to send the ACK / NACK feedback for the first PDSCH on the uplink slot U605 using the ID1 .

[0149] At step 2, the network node transmits the second PDSCH comprising the downlink data D2 to the UE in the downlink slot D602 and via the DCI in the PDCCH, the network node instructs the UE to send the ACK / NACK feedback for the first and second PDSCH on the uplink slot U605 using the ID1.

[0150] Consider another example scenario, as disclosed in FIG. 4B, wherein a carrier aggregation is activated for configuring the UE with a Secondary Cell, SCell, along with a serving cell that is a Primary Cell, PCell. The PCell and the SCell are associated with a network node. Further, the PCell and the SCell grant a first PDSCH and a second PDSCH respectively for the UE. The first and second PDSCH are granted for the UE for reception of downlink data D1 in a downlink slot D1 corresponding to the PCell and downlink data D2 in a downlink slot D2 corresponding to the SCell, respectively. If the PCell and the SCell assigns the same PUCCH format (for example, PF1) for the first and second PDCCH pertaining to the first and second PDSCH, respectively, then PCell and the SCell further assign the same PUCCH resource (for example, ID1) for the ACK / NACK feedback on the uplink slot U605 corresponding to the PCell.

[0151] Upon the assignment, at step 1, the PCell transmits the first PDSCH comprising the downlink data D1 to the UE in the downlink slot D601 and via a DCI in the PDCCH, the PCell instructs the UE to send the ACK / NACK feedback for the first PDSCH on the uplink slot U605 using the ID1.

[0152] At step 2, the SCell transmits the second PDSCH comprising the downlink data D2 to the UE in the downlink slot D601 and via the DCI in the PDCCH, the SCell instructs the UE to send the ACK / NACK feedback for the first and second PDSCH on the uplink slot (corresponding to the PCell) using the ID1.

[0153] In the above described scenarios (FIGs. 4A and 4B), if the UE has failed to decode the PDCCH transmitted at the step 2 and if the UE has decoded the PDCCH transmitted at step 1 and further decoded the PDSCH transmitted at step 1 as "ACK”, then the UE transmits the ACK / NACK feedback comprising ACK bits to the network node on the uplink slot U605 in a PUCCH according to the first PDCCH. However, the network node decodes the PUCCH from the UE according to the second PDCCH and interprets that the ACK / NACK feedback received from the UE for both the PDSCH transmitted at steps 1 and 2 comprise ACK bits ("ACK ACK”). Due to this, the network node falsely determines that the PDSCH transmitted at the step 2 was correct. Such a false determination may lead to unnecessary retransmissions at a higher layer of the network node and may cause delay for an end user.

[0154] In some examples, the UE may use a Downlink Assignment Index (a 2 bit field) transmitted in the PDCCH to realize that it has failed to decode the PDCCH such that it can signal a NACK for corresponding PDSCH at a bundled PUCCH UCI report. However, the DAI may not always aid the UE in preventing ACK / NACK reporting error. The above-described problem occurs when a PUCCH format, PFO or PF1 is used, since the UE uses the same feedback transmission for an "ACK” as used for "ACK ACK” and also "NACK” is identical to "NACK NACK”.

[0155] A mapping of values for an ACK feedback (i.e., Hybrid Automatic Repeat Request, HARQ-ACK information bit) to sequences for the PFO is shown below in Table III:

[0156] Table III (Mapping of values for one HARQ-ACK information bit to sequences for PFO)

[0157] -urther, a mapping of values for two HARQ-ACK information bits to sequences for the PFO is shown below in Table IV:

[0158] Table IV (Mapping of values for two HARQ-ACK information bits to sequences for PFO)

[0159] However, in general, when the network node assumes that ‘n’ bits shall be decoded in the PUCCH and the UE transmits less than ‘n’ bits, then exceptional cases may occur. For cases when ‘n >1 T, then a Cyclic Redundancy Check, CRC is used. However, a probability of falsely decoding correct bits using the CRC decoding is relatively high (for example, 8%) due to which an amount of bits for the CRC is low. Therefore, the ACK / NACK feedback can be decoded wrong and Channel State Information, CSI, can be wrong.

[0160] Thus, as described above, assigning of the same PUCCH resource for example, for first and second PDCCH for ACK / NACK feedback from the UE on the same uplink slot with respect to PFO or PF1 may cause the UE to send the wrong ACK / NACK feedback, for the later PDSCH, in the PUCCH. The wrong ACK / NACK feedback may further cause the network node to falsely determine that the later PDSCH was correct.

[0161] Thus, a false decoding of the PUCCH comprising the ACK / NACK feedback from the UE at the network node may harm other related processes, for example, by causing unnecessary retransmissions at the higher layer of the network node.

[0162] Fig. 5 is a sequence diagram illustrating example signalling for communicating with a User Equipment, UE 204-1 of a plurality of User Equipments, UEs, in a wireless communication network. In the wireless communication network, a network node 202 communicates with the UE 204-1 in a Time Division Duplex, TDD. The TDD comprises a plurality of transmission slots for communicating with the UE 204-1 . The TDD with a DDDSU pattern is disclosed in Fig. 5, wherein the transmission slots comprise downlink slots D601, D602, and D603, a special slot 604, and an uplink slot 605. The DDDSU refers to a frame structure most suitable in 5G, in the wireless network communication. In the illustrated example, the network node 202 detects start of a downlink slot D602. The network node establishes 505 that pending downlink data D2 exists for a UE 204-1 and that a previous slot D601 scheduled with Downlink data D1 exists for the same UE 204-1,2. Accordingly the network node decides to schedules in this example the same UE 204-1 in the second downlink slot

[0163] The network node 202 assigns, in this scenario, 515 the same PUCCH format, PF, for slot D601 and D602, for ACK / NACK feedback from the UE on a one and the same subsequent uplink slot U605. The first and second ACK / NACK feedback pertains to the feedback for downlink data D1 and D2 in the downlink slots D601 and D602, respectively. In an example herein, consider that the assigned PF may be a PF0 or a PF1.

[0164] When the same PUCCH format, PF0 or PF1, is assigned for the first and second ACK / NACK feedback, the network node 202 assigns 530 a different PUCCH resources for the ACK / NACK feedback in the second downlink slot D602 from the UE 204-1. For example, a first PUCCH resource (ID1) is previously assigned then a second PUCCH resource (ID2) may be assigned for second downlink slot D602, for ACK / NACK feedback from the UE 204-1 .

[0165] Upon assigning the PUCCH resources, the network node 202 transmits 535a the downlink data D1 to the UE 204-1 in the downlink slot D601, using a Physical Downlink Shared Channel, PDSCH. Along with the downlink data D1, the network node 202 transmits Downlink Control Information, DCI, to the UE 204-1 in a Physical Downlink Control Channel, PDCCH. The DCI instructs the UE 204-1 to send the ACK / NACK feedback for the D1 on the subsequent uplink slot U605 using the PUCCH resource with to ID1 .

[0166] The network node 202 transmits 535b the downlink data D2 to the UE 204-1 in the downlink slot D602, using the PDSCH. Along with the downlink data D2, the network node 202 transmits the DCI to the UE 204-1 in the PDCCH. The DCI instructs the UE 204-1 to send the ACK / NACK feedback for the D2 on the subsequent uplink slot U605 using the PUCCH resource with to ID2. Upon decoding the PDSCH and the PDCCH, the UE 204-1 sends 537b the ACK / NACK feedback for both downlink data D1 and D2 on the subsequent uplink slot 605, in the PUCCH, by replacing the ID1 with the ID2.

[0167] Assigning the new PUCCH resource for each PDCCH may avoid the network node 202 from falsely decoding the PUCCH from the UE, which is illustrated in detail in conjunction with Figs. 6A and 6B.

[0168] Figs. 6A and 6B disclose illustration of handling assignment of Physical Uplink Control Channel, PUCCH resources in a wireless communication network. In the wireless communication network, a network node communicates with at least a User Equipment, UE, of a plurality of UEs, in a Time Division Duplex, TDD, scheme. The TDD with a DDDSU pattern is disclosed in Figs. 6A and 6B. In particular, the network node transmits downlink data to the UE in a Physical Downlink Shared Channel, PDSCH and receives a PUCCH from the UE comprising an Acknowledgement, ACK / Negative ACK, NACK, feedback pertaining to the downlink data. The network node may assign PUCCH format, PF, and PUCCH resource for each ACK / NACK feedback from the UE. Consider an example scenario, as disclosed in Fig. 6A, wherein the network node grants a first and second PDSCH for a UE for reception of downlink data D1 and D2 in downlink slots D601 and D602. In such a scenario, if the network node same PF, for example, PF1 for the first and second PDCCH, then the network node assigns two different PUCCH resources (for example, ID1 and ID2) for the first and second For example, the network node may assign a first PUCCH resource (ID 1 ) for the first PDCCH and then a second PUCCH resource (ID2) for the second PDCCH for ACK / NACK feedback from the UE on the uplink slot U605.

[0169] Upon the assignment, at step 1, the network node transmits the first PDSCH comprising the downlink data D1 to the UE in the downlink slot D601 and via Downlink Control Information, DCI in a Physical Downlink Control Channel, PDCCH, the network node instructs the UE to send the ACK / NACK feedback for the first PDSCH on the uplink slot U605 using the ID1.

[0170] At step 2, the network node transmits the second PDSCH comprising the downlink data D2 to the UE in the downlink slot D602 and via the DCI in the PDCCH, the network node instructs the UE to send the ACK / NACK feedback for the first and second PDSCH on the uplink slot U605 using the ID2, ID2 being different from ID1.

[0171] Consider another example scenario, as disclosed in Fig. 6B, a carrier aggregation, CA, is activated for configuring the UE with a Secondary Cell, SCell, along with a serving cell that is a Primary Cell, Pcell, wherein the Pcell and the Scell may be provided by the network node. In case of the CA, the Pcell and the Scell grant a first PDSCH and a second PDSCH respectively for the UE. The first and second PDSCH are granted for the UE for reception of downlink data D1 in a downlink slot D1 corresponding to the PCell and downlink data D2 in a downlink slot D2 corresponding to the Scell, respectively. If the Pcell and the Scell assigns the same PUCCH format (for example, PF1) for the first and second PDCCH pertaining to the first and second PDSCH, respectively, then Pcell and the Scell assign a different PUCCH resource (For example ID2), on the second PDCCH, for ACK / NACK feedback from the UE on an uplink slot U605 corresponding to the Pcell. For example, the Pcell may assign PUCCH resource, ID1, on the first PDCCH and the Scell then assigs a different PUCCH resource, ID2 for the second PDCCH.

[0172] Upon the assignment, at step 1, the Pcell transmits the first PDSCH comprising the downlink data D1 to the UE in the downlink slot D601 and via DCI in the PDCCH, the Pcell instructs the UE to send the ACK / NACK feedback for the first PDSCH on the uplink slot U605 (corresponding to the Pcell) using the ID1.

[0173] At step 2, the Scell transmits the second PDSCH comprising the downlink data D2 to the UE in the downlink slot D602 and via the DCI in the PDCCH, the Scell instructs the UE to send ACK / NACK feedback for the first and second PDSCH on the uplink slot U605 (corresponding to the Pcell) using the ID2, ID2 being different from ID1.

[0174] In both the above-described scenarios, the UE shall send the ACK / NACK feedback to the respective network node / Pcell in the PUCCH with the ID2, on the subsequent uplink slot U605. Further, in both the above-described scenarios, if the UE has successfully decoded the first PDSCH as "ACK” and consequently also decoded the first PDCCH for the first PDSCH and if the UE has not decoded the second PDCCH, the UE sends the "ACK” as the ACK / NACK feedback to the network node / Pcell in the PUCCH using the PF1 from the ID1. In such a scenario, the network node may decide to decode the PUCCH from the UE according to the second PDCCH. However, the network node may not able to decode the PUCCH from the UE, since the UE has not transmitted the PUCCH according to the second PDCCH.

[0175] Thus, the network node may not falsely decode the PUCCH from the UE when there is a change in the PUCCH resource for each PDCCH.

[0176] Furthermore, the network node may, when failing to decode the PUCCH according to the second PDCCH, PUCCH resource with ID2, decode the PUCCH according to the first PDCCH, PUCCH resource with ID1, to possibly decode only the ACK / NACK feedback for the first PDSCH.

[0177] For cases as described above, when UE do not decode the last PDCCH, the network node will have a lower probability to falsely decode the PUCCH if it decodes according to the last PDCCH.

[0178] Fig. 7 is a flowchart illustrating method steps performed by a network node for communicating with a plurality of User Equipments, UEs, in a Time Division Duplex, TDD, scheme. The TDD comprises a plurality of transmission slots for communicating with the plurality of UEs. Although the method steps disclosed in Fig. 7 may be equally applicable for the plurality of UEs, the examples herein are described by considering a single UE for ease of understanding.

[0179] At step 700, the network node checks if there is any pending downlink data for the UE. If there is any pending downlink data, at step 705, the network node determines whether a current available transmission slot is a downlink slot. When it has been determined that the current available transmission slot is not the downlink slot, the network node repeats from step 700.

[0180] When it has been determined that the current available transmission slot is the downlink slot to the UE, the network node performs the following steps. At step 710, the network node assigns a Physical Uplink Control Channel, PUCCH, format, PF for respective Acknowledgement, ACK / Negative ACK, NACK, feedback from the UE on a subsequent slot, pertaining to the downlink data in the downlink slot.

[0181] In some examples, the network node may assign the PF based on a number of ACK or NACK bits to be carried in the ACK / NACK feedback from the UE. The assigned PF may be one of: a PF0, PF1, PF2, PF3, and PF4.

[0182] The network node may be configured to use two PFs for reception of the ACK / NACK feedback from each of the plurality of UEs. In such a scenario, the network node may assign the PF from the two PFs for the respective ACK / NACK feedback from the UE on the subsequent uplink slot. In an example, the two PFs may include the PF0 and the PF2. In another example, the two PFs may include the PF1 and the PF3. Upon assigning the PF, at step 712, the network node determines if the assigned PF has already been used by the UE pertaining to a previous transmission of the downlink data in a Physical Downlink Shared Channel, PDSCH and thus whether a scheduled PUCCH resource is already present.

[0183] If the assigned PF has already been used by the UE, at step 715, the network node determines if a list of conditions is met.

[0184] If there is no previous PUCCH resource already present, at step 720, the network node assigns a new PUCCH resource (for example, ID2) for the respective ACK / NACK feedback from the UE,

[0185] If the list of conditions is met then, at step 720, the network node assigns a PUCCH resource (for example, ID2) for the respective ACK / NACK feedback from the UE, wherein the assigned PUCCH resource (for example, ID2) is different from the previous PUCCH resource (for example, ID 1) used by the UE, associated with first downlink data (D1), that is not scheduled for ACK / NACK feedback from any UE of the plurality of UEs (204-1 -204-N).

[0186] If there is a previous PUCCH resource already present but the list of conditions are not met, at step 725, the network node assigns the same PUCCH resource (for example, ID 1 ) for the feedback. Thereby, the PUCCH resource is be reused.

[0187] Upon assigning the PUCCH resource, at step 735, the network node transmits the PDSCH to the UE in the downlink slot, wherein the PDSCH comprises the pending downlink data. Meanwhile, the network node transmits the PDCCH to the UE, wherein the PDCCH comprises a Downlink Control Information, DCI. Through the DCI, the network node instructs the UE to send the ACK / NACK feedback for the PDSCH. The DCI may indicate the uplink slot and a resource ID of the assigned PUCCH resource.

[0188] At step 737, the network node receives the ACK / NACK feedback from the UE in the PUCCH using the assigned PUCCH resource.

[0189] It should be understood that the various actions, acts, blocks, steps, or the like (for example, steps 712, 715, and 720) in the flow chart disclosed in Fig. 7 may be performed in the order presented, in a different order or simultaneously. Further, in some examples, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0190] In the following some general considerations are noted for alternative non-published solutions to the present invention, and which illustrates various effects.

[0191] In some examples, the set of PUCCH resources selected for the UE comprises two or more PUCCH resources from the reserved plurality of PUCCH resources. Some of the PUCCH resources in the set of PUCCH resources selected for the UE may be associated with one of the one or more PFs. Alternatively, all the PUCCH resources in the set of PUCCH resources selected for the UE may be associated with only one PF, wherein the PF is the PFO or the PF1 .

[0192] Fig. 8 is an example schematic diagram showing an apparatus 202. The apparatus 202 may e.g., be comprised in a network node. The apparatus 202 is capable of communicating with a plurality of User Equipments, UEs, in a Time Division Duplex, TDD, and may be configured to cause performance of the method 300 for communicating with the plurality of UEs in the TDD.

[0193] According to at least some examples of the present invention, the apparatus 202 in Fig. 8 comprises one or more modules. These modules may e.g., be a memory 802, a processor 804, a controlling circuitry 806, a transceiver 808, a Physical Uplink Control Channel, PUCCH, assignment module 810, and a PUCCH resource schedule module 812, a PUCCH determination module 814. The controlling circuitry 806, may in some examples be adapted to control the above-mentioned modules.

[0194] The memory 802, the processor 804, the transceiver 808, the PUCCH assignment module 810, and the PUCCH resource assignment module 812, as well as the controlling circuitry 806, may be operatively connected to each other.

[0195] The controlling circuitry 806 may be adapted to control the steps as executed by the network node. For example, the controlling circuitry 806 may be adapted to communicate with the plurality of UEs in the TDD scheme (as described above in conjunction with the method 300 and Fig. 3).

[0196] The PUCCH assignment module 810 may be adapted to establish (310) that the first UE of the plurality of UEs is scheduled for first downlink data on the first downlink slot of the plurality of transmission slots and that the first downlink data is associated with the Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot of the plurality of transmission slots, for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1). The PUCCH resource associated with the first downlink data is associated with a PUCCH format.

[0197] The PUCCH resource schedule module 812 may be adapted to scheduling (320), for the first UE, the second downlink data on the second downlink slot of the plurality of transmission slots and schedules (330), for association with the second downlink data, the PUCCH resource for ACK / NACK feedback from the first UE pertaining the second downlink data on the pending uplink slot.

[0198] The transceiver 808 may be adapted to transmit (350) the second downlink data to the first UE on the second downlink slot while instructing the first UE to send the ACK / NACK feedback pertaining the second downlink data on the pending uplink slot using the PUCCH resource associated with the second downlink data. The PUCCH resource schedule module 812 schedules the PUCCH resource associated with the second downlink data comprises selecting

[0199] (331) the PUCCH format for the PUCCH resource associated with the second downlink data.

[0200] The PUCCH determination module 814 may be adapted to determine whether one or more conditions are fulfilled

[0201] (332) if the selected PUCCH format for the PUCCH resource associated with the second downlink data is the same as the PUCCH format of the PUCCH resource associated with the first downlink data, and when it is determined that the one or more conditions are fulfilled, the PUCCH resource associated with the second downlink data is scheduled

[0202] (333) as the different PUCCH resource from the PUCCH resource associated with first downlink data.

[0203] Further, the memory 802 is adapted to store information about PUCCHs, PUCCH resources, the assigned PUCCH resource for each ACK / NACK feedback, or the like.

[0204] In summary, there has been provided various embodiments of the invention according to which:

[0205] A method (300) performed by a network node (202) for communicating with a plurality of User Equipments, UEs (204-1 -204-N) in a Time Division Duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (601-610) for communicating with the plurality of UEs (204-1 -204-N), the method (300) comprising: establishing (310) that a first UE (204-1) of the plurality of UEs (204-1-204-N) is scheduled for first downlink data (D1) on a first downlink slot (D601) of the plurality of transmission slots (601-610) and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) of the plurality of transmission slots (601-610), for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format; scheduling (320), for the first UE (204-1), second downlink data (D2) on a second downlink slot (D602) of the plurality of transmission slots (601-610); scheduling (330), for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE (204-1) pertaining the second downlink data (D2) on the pending uplink slot (U605); and transmitting (350) the second downlink data (D2) to the first UE (204-1) on the second downlink slot (D602) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot (U605) using the PUCCH resource associated with the second downlink data (D2), wherein scheduling (330) the PUCCH resource associated with the second downlink data (D2) comprises selecting (331) a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining (332) whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled, the method comprises scheduling (333) the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1). According to an embodiment when it is determined that the one or more conditions are fulfilled, the method further comprises changing (333-1) the PUCCH resource associated with the first downlink data (D1) to the scheduled PUCCH resource associated with the second downlink data (D2).

[0206] The PUCCH format of the PUCCH resource associated with the first and / or second downlink data (D1, D2) may be indicative of any of: a number of bits of information the corresponding PUCCH resource can carry; a number of symbols for assignment to the corresponding PUCCH resource; and a number of Physical Resource Blocks, PRBs, for assignment to the corresponding PUCCH resource.

[0207] The selection (331) of PUCCH format for the PUCCH resource associated with the second downlink data (D2) may be selected (331-1) based on required ACK / NACK feedback pertaining to the first downlink data (D1) and the second downlink data (D2).

[0208] According to an embodiment, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of bits of information of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of bits of information is less than a first threshold.

[0209] According to an embodiment, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of symbols of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of symbols is less than a second threshold.

[0210] According to an embodiment, the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of PRBs of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of PRBs is less than a third threshold.

[0211] According to an embodiment, the one or more conditions are fulfilled if, in addition, the selected PUCCH format is a predetermined PUCCH format of any of the PUCCH formats according to 3GPP TS 38.331 v17.2. Release 17.

[0212] For example, the predetermined format is any of PUCCH format 0 and PUCCH format 1 .

[0213] According to an embodiment, the one or more conditions are fulfilled if, in addition, a signal quality metric of a signal between the network node (202) and first UE (204-1) is less than a fourth threshold and / or when the signal quality metric is above a fifth threshold. According to an embodiment, the one or more conditions are fulfilled if, in addition, the first UE (204-1) is configured with a PUCCH resource set comprising a PUCCH resource, different from the PUCCH resource associated with first downlink data (D1), that is not scheduled for ACK / NACK feedback from any UE of the plurality of UEs (204-1 -204-N).

[0214] According to an embodiment, when it is determined that the one or more conditions are not fulfilled, scheduling (334) the PUCCH resource associated with the second downlink data (D2) as the same PUCCH resource as the PUCCH resource associated with first downlink data (D1).

[0215] It may apply that transmitting (340) the first downlink data (D1) to the first UE (204-1) on the first downlink slot (D601) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the first downlink data (D1) on the pending uplink slot (U605) using the PUCCH resource associated with the first downlink data (D1).

[0216] For instance, the first downlink slot (D601) precedes the second downlink slot (D602).

[0217] It may apply that the second downlink slot (D602) and the first downlink slot (D601) are simultaneous.

[0218] For example, the network node (202) is configured to perform digital beam forming.

[0219] There is moreover provided a network node (202) for communicating with a plurality of User Equipments, UEs (204- 1 -204-N) in a Time Division Duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (601 - 610) for communicating with the plurality of UEs (204-1 -204-N), the apparatus comprising a controlling circuitry (906) configured to cause: establishing (310) that a first UE (204-1) of the plurality of UEs (204-1 -204-N) is scheduled for first downlink data (D1) on a first downlink slot (D601) of the plurality of transmission slots (601-610) and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) of the plurality of transmission slots (601-610), for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format; scheduling (320), for the first UE (204-1), second downlink data (D2) on a second downlink slot (D602) of the plurality of transmission slots (601-610); scheduling (330), for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE (204-1) pertaining the second downlink data (D2) on the pending uplink slot (U605); and transmitting (350) the second downlink data (D2) to the first UE (204-1) on the second downlink slot (D602) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot (U605) using the PUCCH resource associated with the second downlink data (D2), wherein scheduling (330) the PUCCH resource associated with the second downlink data (D2) comprises selecting (331) a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining (332) whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D 1), and when it is determined that the one or more conditions are fulfilled, the method comprises scheduling (333) the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

[0220] A computer program product is provided comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions, wherein the computer program is loadable into a data processing unit and configured to cause execution of the method described when the computer program is run by the data processing unit.

[0221] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors, DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0222] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the disclosure.

[0223] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in FIG. 8 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

Claims

1. CLAIMS1 . A method (300) performed by a network node (202) for communicating with a plurality of User Equipments, UEs (204-1 -204-N) in a Time Division Duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (601-610) for communicating with the plurality of UEs (204-1 -204-N), the method (300) comprising: establishing (310) that a first UE (204-1) of the plurality of UEs (204-1 -204-N) is scheduled for first downlink data (D1) on a first downlink slot (D601) of the plurality of transmission slots (601-610) and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) of the plurality of transmission slots (601-610), for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format; scheduling (320), for the first UE (204-1), second downlink data (D2) on a second downlink slot (D602) of the plurality of transmission slots (601-610); scheduling (330), for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE (204-1) pertaining the second downlink data (D2) on the pending uplink slot (U605); and transmitting (350) the second downlink data (D2) to the first UE (204-1) on the second downlink slot (D602) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot (U605) using the PUCCH resource associated with the second downlink data (D2), wherein scheduling (330) the PUCCH resource associated with the second downlink data (D2) comprises selecting (331) a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining (332) whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled, the method comprises scheduling (333) the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

2. The method according to claim 1 , when it is determined that the one or more conditions are fulfilled, the method further comprises changing (333-1) the PUCCH resource associated with the first downlink data (D1) to the scheduled PUCCH resource associated with the second downlink data (D2).

3. The method according to claim 1 or 2, wherein the PUCCH format of the PUCCH resource associated with the first and / or second downlink data (D1 , D2) is indicative of any of: a number of bits of information the corresponding PUCCH resource can carry; a number symbols for assignment to the corresponding PUCCH resource; and a number of Physical Resource Blocks, PRBs, for assignment to the corresponding PUCCH resource.

4. The method (300) according to any previous claim, wherein the selection (331) of PUCCH format for the PUCCH resource associated with the second downlink data (D2) is selected (331-1) based on required ACK / NACK feedback pertaining to the first downlink data (D1) and the second downlink data (D2).

5. The method (300) according to claim 4, wherein the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of bits of information of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of bits of information is less than a first threshold.

6. The method (300) according to claim 4 or 5, wherein the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of symbols of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of symbols is less than a second threshold.

7. The method (300) according to any of claims 4-6, wherein the required ACK / NACK feedback pertaining the first downlink data (D1) and the second downlink data (D2) is associated with a required number of PRBs of the PUCCH resource associated with the second downlink data (D2), and wherein the one or more conditions are fulfilled if, in addition, the required number of PRBs is less than a third threshold.

8. The method (300) according to any previous claim, wherein the one or more conditions are fulfilled if, in addition, the selected PUCCH format is a predetermined PUCCH format of any of the PUCCH formats according to 3GPP TS 38.331 v17.

2. Release 17.

9. The method (300) according to claim 8, wherein the predetermined format is any of PUCCH format 0 and PUCCH format 1.

10. The method according to any previous claim, wherein the one or more conditions are fulfilled if, in addition, a signal quality metric of a signal between the network node (202) and first UE (204-1) is less than a fourth threshold and / or when the signal quality metric is above a fifth threshold.11 . The method according to any previous claim, wherein the one or more conditions are fulfilled if, in addition, the first UE (204-1) is configured with a PUCCH resource set comprising a PUCCH resource, different from the PUCCH resource associated with first downlink data (D1), that is not scheduled for ACK / NACK feedback from any UE of the plurality of UEs (204-1 -204-N).

12. The method (300) according to any previous claim, comprising, when it is determined that the one or more conditions are not fulfilled, scheduling (334) the PUCCH resource associated with the second downlink data (D2) as the same PUCCH resource as the PUCCH resource associated with first downlink data (D1).

13. The method (300) according to any previous claim, comprising transmitting (340) the first downlink data (D1) to the first UE (204-1) on the first downlink slot (D601) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the first downlink data (D1) on the pending uplink slot (U605) using the PUCCH resource associated with the first downlink data (D1).

14. The method according to any previous claim, wherein the first downlink slot (D601) precedes the second downlink slot (D602).

15. The method according to any of claims 1-13, wherein the second downlink slot (D602) and the first downlink slot (D601) are simultaneous.

16. The method (300) according to any previous claim, wherein the network node (202) is configured to perform digital beam forming.

17. A network node (202) for communicating with a plurality of User Equipments, UEs (204-1-204-N) in a Time Division Duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (601-610) for communicating with the plurality of UEs (204-1-204-N), the apparatus comprising a controlling circuitry (906) configured to cause: establishing (310) that a first UE (204-1) of the plurality of UEs (204-1-204-N) is scheduled for first downlink data (D1) on a first downlink slot (D601) of the plurality of transmission slots (601-610) and that the first downlink data (D1) is associated with a Physical Uplink Control Channel, PUCCH, resource, scheduled on a pending uplink slot (U605) of the plurality of transmission slots (601-610), for Acknowledgement, ACK, I Negative Acknowledgement, NACK, feedback pertaining the first downlink data (D1), wherein the PUCCH resource associated with the first downlink data (D1) is associated with a PUCCH format; scheduling (320), for the first UE (204-1), second downlink data (D2) on a second downlink slot (D602) of the plurality of transmission slots (601-610); scheduling (330), for association with the second downlink data (D2), a PUCCH resource for ACK / NACK feedback from the first UE (204-1) pertaining the second downlink data (D2) on the pending uplink slot (U605); and transmitting (350) the second downlink data (D2) to the first UE (204-1) on the second downlink slot (D602) while instructing the first UE (204-1) to send the ACK / NACK feedback pertaining the second downlink data (D2) on the pending uplink slot (U605) using the PUCCH resource associated with the second downlink data (D2), wherein scheduling (330) the PUCCH resource associated with the second downlink data (D2) comprises selecting (331) a PUCCH format for the PUCCH resource associated with the second downlink data (D2), determining (332) whether one or more conditions are fulfilled, wherein the one or more conditions are fulfilled if the selected PUCCH format for the PUCCH resource associated with the second downlink data (D2) is the same as the PUCCH format of the PUCCH resource associated with the first downlink data (D1), and when it is determined that the one or more conditions are fulfilled, the method comprises scheduling (333) the PUCCH resource associated with the second downlink data (D2) as a different PUCCH resource from the PUCCH resource associated with first downlink data (D1).

18. A computer program product comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions, wherein the computer program is loadable into a data processing unit and configured to cause execution of the method according to any of claims 1 through 16 when the computer program is run by the data processing unit.

Images