Methods and apparatuses for communicating uplink and downlink data in wireless communication network

Abstract

Embodiments of present disclosure provide a method (300) performed by a network node (202) for communicating uplink and downlink data in a TDD scheme with a plurality of UEs (204-1 - 204-N) The method comprising determining to schedule and not to schedule an uplink data transmission for a first UE (204-1) and a second UE (204-2), respectively. The method comprising transmitting, to the first UE, uplink DCI, thereby effectuating the uplink data transmission in a subsequent uplink slot and the network node decoding said uplink data transmission from the first UE. The method comprising transmitting, to the second UE, SR-PUCCH reset information, thereby effectuating transmitting a BSR and optionally padding bits in the subsequent uplink slot, said SR-PUCCH reset information being intended to cause the second UE to reset a SR timer, the network node obviating decoding of said transmission from the second UE.

Description

[0001] METHODS AND APPARATUSES FOR COMMUNICATING UPLINK AND DOWNLINK DATA IN WIRELESS COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to the field of wireless communication. More particularly, it relates to method, network node, User Equipment, UE, and computer program products for communicating uplink and downlink data 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, achieving improved network performance. The network performance improvement is achieved by the NR network using a number of advanced techniques, which comprise, for example, beamforming, massive multipleinput multiple-output, MIMO, full dimensional MIMO, FD-MIMO, advanced antenna array techniques, large scale antenna techniques, or the like.

[0006] In NR, a network node controls all uplink and downlink data traffic, with an exception of initial access by User Equipments, UEs, such as, via Random Access procedures. In particular, when the UE has user data to transmit to the network node in an uplink, the UE sends Scheduling Requests, SRs, to the network node indicating for example, a logical channel generating the SR, an amount of user data to be transmitted, or the like. The UE sends the SRs to the network node in a Physical Uplink Control Channel, PUCCH (hereinafter referred to as SR-PUCCH transmission). In response to the received SR-PUCCH, the network node may allocate time-frequency resources to the requesting UE and communicate the allocated resources to the UE in uplink Downlink Control Information, DCI.

[0007] In order to perform the SR-PUCCH transmissions, the UE may be configured with one or multiple SR configurations (up to 8) per cell group. The SR configuration may be configured for the UE via higher layer signaling. The SR comprises information / parameter indicating a PUCCH resource for the SR, which may be referred to as an SR-PUCCH resource.

[0008] Further, the UE always tracks a number of SR-PUCCH transmissions to the network node. When the SR-PUCCH transmissions reach a maximum number of SR transmissions (sr-TransMax SR-PUCCH transmission), the UE releases its SR-PUCCH resource and initiates using Random Access Channel, RACH, procedures to indicate when it has pending user data to transmit to the network node.

[0009] The RACH procedures can be avoided prior to the SR-PUCCH transmissions reaching the sr-TransMax SR-PUCCH transmission if the UE transmits a Physical Uplink Shared Channel, PUSCH, containing a Buffer Status Report, BSR, when a Medium Access Control, MAC, Protocol Data Unit, PDU, contains a buffer status up to (and including) a last event that triggered the BSR prior to the MAC PDU assembly or when the uplink grant(s) can accommodate all pending user data available for transmission. When this is fulfilled, the UE resets its SR counter.

[0010] SR-PUCCH transmissions and subsequent RACH procedures are disclosed in documents 3GPP TS 38.321 V17.6.0 (2023-09), 5.4.4 Scheduling Request.

[0011] SUMMARY

[0012] An object of the present disclosure is to provide a method, a network node, a User Equipment, UE, and a computer program product for communicating uplink and downlink data in a wireless communication network to mitigate, alleviate, or eliminate all or at least some of the drawbacks of presently known solutions.

[0013] This and other objects are achieved by means of a method, a network node, a User Equipment, UE, 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.

[0014] According to a first aspect of the present disclosure, a method performed by a network node for communicating uplink and downlink data in a Time Division Duplex, TDD, scheme with a plurality of User Equipments, UEs, is provided. The TDD scheme comprising a plurality of transmission slots for communicating the uplink and downlink data with the plurality of UEs. The method comprises determining whether or not to schedule uplink data transmissions for at least a first UE and a second UE among the plurality of UEs, wherein it has been determined to schedule an uplink data transmission for the first UE and it has been further determined not to schedule any uplink data transmission for the second UE. For the first UE for which it has been determined to schedule the uplink data transmission, the method comprises transmitting to said first UE, uplink Downlink Control Information, DCI, in a Physical Downlink Control Channel, PDCCH, thereby effectuating the uplink data transmission in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot, the network node decoding said uplink data transmission from the first UE in the uplink slot. For the second UE for which it has been determined not to schedule the uplink data transmission, the method comprises transmitting to said second UE, a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information in the PDCCH. The network node obviating decoding any transmission from the second UE in the uplink slot.

[0015] In some embodiments, for the second UE for which it has been determined not to schedule the uplink data transmission, transmitting to said second UE, the SR-PUCCH reset information in the PDCCH, effectuating transmitting a Buffer Status Report, BSR, and optionally padding bits in the PUSCH in the subsequent uplink slot. The SR-PUCCH reset information is intended to cause the second UE to reset a SR timer corresponding to a maximum number of SR transmissions configured for the second UE. In some embodiments, the step of transmitting, to the second UE, the SR-PUCCH reset information in the PDCCH further comprises determining whether or not to initiate a reset request for each of the plurality of UEs based on a respective network timer for a respective UE, said reset request is intended for transmission of the SR-PUCCH reset information. When it has been determined to initiate the reset request for a UE, the method comprises sending the reset request for said UE into a reset queue. The method further comprises monitoring the reset queue to determine whether or not to transmit the SR-PUCCH reset information in the PDCCH, wherein transmitting to the second UE the SR-PUCCH reset information in the PDCCH is determined when the reset queue comprises a reset request for said second UE.

[0016] In some embodiments, the network timer is managed by the network node for each of the plurality of UEs for monitoring the maximum number of SR transmissions configured for said UE.

[0017] In some embodiments, initiating the reset request for the UE is determined when the network timer for the UE exceeds a first threshold, wherein the first threshold is lower than a time interval taken by the maximum number of SR transmissions configured for the UE.

[0018] In some embodiments, the method further comprises a step of resetting the network timer corresponding to the UE of the plurality of UEs. The step comprises determining whether Hybrid Automatic Repeat Request, HARQ, information comprising a BSR has been decoded for the UE, when there is the PUSCH from the UE in the uplink slot in response to a previous scheduling of the uplink data transmission for the UE. When it has been determined that the HARQ information has been decoded for the UE, the method comprises determining whether the HARQ information has been decoded using a first HARQ transmission from the UE. When it has been determined that the HARQ information has been decoded using the first HARQ transmission from the UE, the method comprises resetting the network timer corresponding to said UE.

[0019] In some embodiments, the method further comprises resetting the network timer corresponding to the UE upon performing at least one of: determining that the network timer corresponding to the UE has exceeded a second threshold and transmitting the SR-PUCCH reset information to the UE.

[0020] In some embodiments, after transmission of the SR-PUCCH reset information to the second UE or after successful decoding of an ongoing HARQ process between the network node and the second UE or prior to initiation of a new HARQ process between the network node and the second UE, the method comprising toggling a New Data Indicator, NDI, for a subsequent transmission of the SR PUCCH reset information to the second UE, wherein the toggled NDI for the second UE identifies that a subsequent transmission from the second UE is to be a new uplink data transmission. The method further comprises selecting a Transport Block Size, TBS, from a pre-defined TBS sequence for the subsequent uplink data transmission from the second UE, wherein the selected TBS for the at least one first UE is different from a previously used TBS. In some embodiments, the method further comprises reserving a fixed HARQ identifier, ID, to be used for transmission of the SR PUCCH reset information to the second UE.

[0021] In some embodiments, the SR-PUCCH reset information transmitted to the second UE refers to a TBS granted for transmission of the BSR and optionally padding bits other than user data from the second UE.

[0022] In some embodiments, the SR-PUCCH reset information is transmitted to the second UE independent of a Connected Mode Discontinuous Reception, CDRX, state and a data traffic of the second UE.

[0023] In some embodiments, the step of determining whether or not to schedule the uplink data transmission for at least the first UE and second UE, when the uplink DCI is available in at least one downlink slot or a special slot for at least the first UE and second UE.

[0024] In some embodiments, the method further comprises determining whether to schedule a downlink data transmission for at least a UE of the plurality of UEs, when a downlink DCI is available in the at least one downlink slot for that UE. When it has been determined to schedule the downlink data transmission, the method comprises transmitting, to said UE, the downlink DCI in the PDCCH indicating a grant of a Physical Data Shared Channel, PDSCH, for reception of the downlink data transmission from the network node.

[0025] In some embodiments, the network node is communicating over a plurality of antennas using an analogue beam forming, wherein the plurality of antennas using the analogue beam forming are associated with respective wide beams (and narrow beams, a plurality of wide beams covering respective areas, whereby for each wide beam at least one narrow beam forms a joint area with a wide beam.

[0026] According to a second aspect of the present disclosure, a method performed by a User Equipment, UE, for communicating uplink and downlink data with a network node in a Time Division Duplex, TDD, scheme is provided. The TDD scheme comprises a plurality of transmission slots for communicating uplink and downlink data with the network node. The method comprises decoding, a Physical Downlink Control Channel, PDCCH, received from the network node. For the case when uplink Downlink Control Information, DCI, is decoded from the PDCCH, the method comprises performing an uplink data transmission with the network node in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot. For the case when Scheduling Request Physical Uplink Control Channel, SR- PUCCH, reset information is decoded from the PDCCH, the method comprises transmitting, to the network node, a Buffer Status Report, BSR, and optionally padding bits in the PUSCH, in the subsequent uplink slot and resetting a SR timer corresponding to a maximum number of SR transmissions configured for the UE.

[0027] According to a third aspect of the present disclosure, an apparatus of a network node for communicating uplink and downlink data in a Time Division Duplex, TDD, scheme with a plurality of User Equipments, UEs, is provided. The TDD scheme comprising a plurality of transmission slots for communicating the uplink and downlink data with the plurality of UEs. The apparatus comprising controlling circuitry configured to cause determination of whether or not to schedule uplink data transmissions for at least a first UE and a second UE among the plurality of UEs, wherein it has been determined to schedule an uplink data transmission for the first UE and it has been further determined not to schedule any uplink data transmission for the second UE. For the first UE for which it has been determined to schedule the uplink data transmission, the controlling circuitry is configured to cause transmission of uplink Downlink Control Information, DCI, to said UE in a Physical Downlink Control Channel, PDCCH, thereby effectuating the uplink data transmission in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot, the network node decoding said uplink data transmission from the first UE in the uplink slot. For the second UE for which it has been determined not to schedule the uplink data transmission, the controlling circuitry is configured to cause transmission of a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information to said second UE in the PDCCH. The network node obviating decoding any transmission from the second UE in the uplink slot.

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

[0029] According to a fifth aspect of the present disclosure, a User Equipment, UE, for communicating uplink and downlink data with a network node in a Time Division Duplex, TDD, scheme is provided. The TDD scheme comprises a plurality of transmission slots for communicating uplink and downlink data with the network node. The UE comprises a controlling circuitry adapted to cause decoding of a Physical Downlink Control Channel, PDCCH, received from the network node. For the case when uplink Downlink Control Information, DCI, is decoded from the PDCCH, the controlling circuitry is adapted to cause performing an uplink data transmission with the network node in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot. For the case when Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information is decoded from the PDCCH, the controlling circuitry is adapted to cause transmission of a Buffer Status Report, BSR, and optionally padding bits to the network node in the PUSCH, in the subsequent uplink slot and resetting a SR timer corresponding to a maximum number of SR transmissions configured for the UE.

[0030] According to a sixth 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 any of the first and second aspects when the computer program is run by the data processing unit.

[0031] 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.

[0032] An advantage of some embodiments is that alternative and / or improved approaches are provided for avoiding occurrence of a maximum number of SR-PUCCH transmissions for a UE. Thereby, interruptions caused for an end user due to release of SR-PUCCH resources by the UE (based on the occurrence of the maximum number of SR- PUCCH transmissions) may be reduced.

[0033] An advantage of some embodiments is that more than one UE may be granted with a same PUSCH / uplink slot, however the network node decodes the PUSCH from the UE for which it is determined to schedule an uplink data transmission. Therefore, more than one UE may run 3GPP PDCCH processes, which prevent occurrence of the maximum number of SR-PUCCH transmissions for that UE.

[0034] An advantage of some embodiment is that transmitting SR-PUCCH reset information in a PDCCH for the UE for which it has been determined not to schedule the uplink data transmission and avoiding decoding of a PUSCH from such UE provides an extra amount of PUSCH / PDCCH. The extra amount of PUSCH / PDCCH may be used to reset a SR timer of the UE.

[0035] An advantage of some embodiments is that the SR-PUCCH reset information uses a TBS, which enables the UE to transmit nothing more than a BSR and padding bits. Thus, transmission of user data from such UE to the network node is avoided.

[0036] An advantage of some embodiments is that selecting, after transmission of the SR-PUCCH reset information, a TBS from a pre-defined TBS sequence for a subsequent uplink data transmission from the UE increases a probability that the SR timer is reset at the UE.

[0037] BRIEF DESCRIPTION OF THE DRAWINGS

[0038] 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.

[0039] Figs 1A, 1 B, and 10 show a non-public reference design.

[0040] 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;

[0041] Fig. 1 B discloses a flowchart illustrating example method steps of a method performed by a network node for communicating uplink and downlink data with at least a User Equipment, of a plurality of UEs;

[0042] Fig. 10 is an example illustration of handling uplink data transmissions for a UE;

[0043] Fig. 2 discloses an example wireless communication network according to some embodiments;

[0044] Fig. 3 is a flowchart illustrating example method steps according to some embodiments;

[0045] Fig. 4 is a flowchart illustrating example method steps according to some embodiments; Fig. 5 is a signaling diagram illustrating example signaling according to some embodiments;

[0046] Fig. 6A is a flowchart illustrating example method steps according to some embodiments;

[0047] Fig. 6B is a flowchart illustrating example method steps according to some embodiments;

[0048] Fig. 7 is a flowchart illustrating example method steps according to some embodiments;

[0049] Fig. 8 is a flowchart illustrating example method steps according to some embodiments;

[0050] Figs. 9 and 10 disclose example illustrations of handling uplink data transmissions for UEs, according to some embodiments;

[0051] Fig. 11 is a schematic block diagram illustrating an example apparatus according to some embodiments;

[0052] Fig. 12 is a schematic block diagram illustrating an example apparatus according to some embodiments;

[0053] Fig. 13 is a block diagram of a telecommunication network connected via an intermediate network to a host computer, according to some embodiments;

[0054] Fig. 14 is a block diagram of a host computer communicating via a base station with a UE over a partially wireless connection, according to some embodiments;

[0055] Fig. 15 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a UE, according to some embodiments;

[0056] Fig. 16 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a UE, according to some embodiments;

[0057] Fig. 17 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a UE, according to some embodiments;

[0058] Fig. 18 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a UE, according to some embodiments; and

[0059] Fig. 19 discloses an example computing environment according to some embodiments.

[0060] DETAILED DESCRIPTION

[0061] Aspects of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. The apparatus and methods 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. 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.

[0062] 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.

[0063] 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 a / an / the 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.

[0064] Furthermore, the following terms are used throughout the description given below:

[0065] - User Equipment: As used herein, a UE is any type of device that has access to (i.e., is served by) a wireless communication 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 a 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, laptopmounted 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”.

[0066] - Network Node: As used herein, a "network node” is any node that is either part of the radio access network or the 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 U E, and / or to perform other functions (e.g., administration) in the cellular communications network.

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

[0068] - 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.

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

[0070] - 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 Acknowledgment, NACK bits, Channel State Information, CSI.

[0071] 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.

[0072] 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.

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

[0074] 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. The TDD scheme comprises a plurality of transmission slots (slot n - slot n+7) for communicating uplink and downlink data with a plurality of User Equipments, 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.

[0075] As disclosed in Fig. 1A, 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 acknowledgment, NACK, in the PUCCH 103. The PDDCH 104 in the slot n+3 comprises a PDCCH that represents an uplink data 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 trailing when the PUCCH 103 will be transmitted.

[0076] 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.

[0077] 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.

[0078] Fig. 1 B discloses a flowchart illustrating example method steps of a method performed by a network node for communicating uplink and downlink data with at least a User Equipment, of a plurality of UEs.

[0079] At step 110, the network node determines whether a new transmission slot is available for communicating with the UE. The transmission slot referred herein may be a downlink slot or a special slot. When it has been determined that the new transmission slot is available, at step 111, the network node determines if uplink Downlink Control Information, DCI, is available in the transmission slot. If the uplink DCI is not available in the transmission slot, the network node performs step 113.

[0080] If the uplink DCI is available in the transmission slot, at step 112, the network node determines whether or not to schedule an uplink data transmission for the UE. Scheduling of the uplink data transmission herein refers to granting of a Physical Uplink Shared Channel, PUSCH, for the UE for transmission of pending user data.

[0081] When it has been determined to schedule the uplink data transmission for the UE, at step 114, the network node transmits a Physical Downlink Control Channel, PDCCH, to the UE for the uplink data transmission. The PDCCH comprises the uplink (UL) DCI indicating a grant of the PUSCH for the UE for the uplink data transmission. When it has been determined not to schedule the uplink data transmission, at step 113, the network node determines if downlink (DL) DCI is available in the transmission slot. Herein, the transmission slot is a downlink slot. If the downlink DCI is not available in the transmission slot, the network node repeats from step 110.

[0082] If the downlink DCI is available in the transmission slot, at step 115, the network node determines whether or not to schedule the downlink data transmission for the UE. Scheduling of the downlink data transmission herein refers to a grant of a Physical Downlink Shared Channel, PDSCH, for reception of the downlink data from the network node. When it has been determined to schedule the downlink data transmission for the UE, at step 116, the network node transmits the PDCCH to the UE for the downlink data transmission. The PDCCH comprises the downlink (DL) DCI.

[0083] If the downlink DCI is not available in the transmission slot or if it has been determined not to schedule the downlink data transmission, the network node repeats from step 110.

[0084] In particular, when the network node is loaded with traffic, the network node may fail to grant the uplink data transmission for the UE for a longer time period due to lack of PUSCH opportunities. This may cause a maximum number of SR-PUCCH transmissions (sr-TransMax SR-PUCCH transmission) to occur for the UE in that network node. Also, the maximum number of SR-PUCCH transmissions (sr-TransMax SR-PUCCH transmission) may occur for the UE, when the network node operates in low Signal-to-lnterference-plus-Noise Ratio, SINR, scenarios.

[0085] When the maximum number of SR-PUCCH transmissions occurs, the UE releases its SR-PUCCH resources. Releasing of the SR-PUCCH resources may cause interruptions for an end user. The interruptions may be that the NR connection is lost and a reestablishment is needed. The reestablishment may take time (for example, 1 -2 seconds) or throughput may be degraded for a shorter timer period.

[0086] Further, a risk of the interruptions may increase with a shorter SR-PUCCH periodicity that is in use. On the other hand, if a longer periodicity is set for the SR-PUCCH transmissions, the longer will be the delay from the UE transmitting the SR-PUCCH until the SR-PUCCH is decoded by the network node. Such a delay affects latency.

[0087] Fig. 1C discloses an example illustration of handling uplink data transmissions for a UE.

[0088] Consider an example scenario, as disclosed in Fig. 1 C, wherein a network node schedules / grants (at step 1) an uplink data transmission for a User Equipment, UE, in a Physical Downlink Control Channel, PDCCH. Upon scheduling the uplink data transmission for the UE, the UE transmits a Physical Uplink Shared Channel, PUSCH, in a subsequent uplink slot. The network node decodes (at step 2) the PUSCH from the UE, wherein the PUSCH may comprise a Buffer Status Report, BSR > ‘O' and optionally user data. The UE resets (at step 3) a Scheduling Request, SR counter / timer (reference time x) after transmission of the PUSCH in the subsequent uplink slot.

[0089] Further, the UE initiates SR Physical Uplink Control Channel, PUCCH (SR-PUCCH) transmissions untill the SR timer reaches a maximum number of SR-PUCCH transmissions configured for the UE, for example, SR timer=n milliseconds, ms. If the network node does not schedule / grant the uplink data transmission for the UE during n ms (step 4), there may be no PUSCH transmission from the UE for the network node. Subsequently, the UE initiates a Random Access Channel, RACH, procedure by releasing SR-PUCCH resources. Releasing of the SR-PUCCH resources may cause interruptions for an end user.

[0090] As briefly mentioned above, the interruptions are troublesome, when the maximum number of SR-PUCCH transmissions occurs for the UE.

[0091] Fig. 2 discloses an example wireless communication network 2000. 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 embodiments, 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.

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

[0093] 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.

[0094] 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.

[0095] It should be understood that in some examples, in particular with the NR network or any other similar next generation network, the network node 202 may schedule more than one UE at a time.

[0096] Further, 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.

[0097] In the wireless communication network 2000, the network node 202 controls the uplink and downlink data transmissions for the plurality of UEs 204-1 - 204-N. In particular, if any of the plurality of UEs 204-1 - 204N, for example, 204-2, has user data to transmit to the network node 202, the UE 204-2 transmits Scheduling Requests, SRs, to the network node 202 at specific times (for example, when a Buffer Status Report, BSR, is triggered) using the PUCCH. The UE 204-2 may transmit the SRs to the network node 202 using SR-PUCCH resources. Upon receiving the SR-PUCCH, the network node 202 schedules an uplink data transmission for the UE 204-2, allocates time-frequency resources (PUSCH resources) for the scheduled uplink data transmission, and communicates the allocated resources to the UE 204-2 in Downlink Control Information, DCI in the PDCCH. However, when the network node 202 fails to schedule the uplink data transmission for the UE 204-2 for a longer time period due to lack of resources, a maximum number of SR-PUCCH transmissions (sr-TransMax SR-PUCCH transmission) may occur for the UE 204-2 in that network node 202.

[0098] On occurrence of the maximum number of SR-PUCCH transmissions, the UE 204-2 releases its SR-PUCCH resources and initiates a Random Access Channel, RACH, procedure. Releasing of the SR-PUCCH resources may cause interruptions for an end user while accessing communication services from the network node 202. For example, the interruptions may include connection lost or a requirement for reestablishment of connection. Thus, the interruptions due to the occurrence of the maximum number of SR-PUCCH transmissions are troublesome and degrades throughput of communication services being accessed by the UE from the network node.

[0099] Therefore, embodiments herein enable the network node 202 for communicating uplink and downlink data with the plurality of UEs 204-1 - 204-N, by avoiding occurrence of the maximum number of SR-PUCCH transmissions for the UEs 204-1 - 204-N.

[0100] The network node 202 determines whether or not to schedule uplink data transmissions for at least a first UE 204-1 and a second UE 204-2 among the plurality of UEs 204-1 - 204-N. Herein, the network node 202 determines to schedule the uplink data transmission for the first UE 204-1 and further determines not to schedule the uplink data transmission for the second UE 204-2.

[0101] For the first UE 204-1 for which it has been determined to schedule the uplink data transmission, the network node 202 transmits, to the first UE 204-1 , uplink DCI in the PDCCH. Thereby, effectuating the uplink data transmission in the PUSCH, in a subsequent uplink slot. The network node 202 decodes the uplink data transmission from the first UE 204-1 in the uplink slot. For the second UE 204-2 for which it has been determined not to schedule the uplink data transmission, the network node 202 transmits, to the second UE 204-2, SR-PUCCH reset information in the PDCCH. The network node obviates decoding of any transmission from the second UE 204-2 in the uplink slot.

[0102] For the second UE 204-2 for which it has been determined not to schedule the uplink data transmission, transmitting the SR-PUCCH reset information to that second UE 204-2 effectuates transmission of a BSR and optionally padding bits in the PUSCH in the subsequent uplink slot. The SR-PUCCH reset information is intended to cause the second UE 204-2 to reset a SR timer corresponding to a maximum number of SR transmissions configured for the second UE 204-2. Therefore, the network node 202 may enable the second UE 204-2 to reset the SR timer before the occurrence of the maximum number of SR-PUCCH transmissions, which avoids releasing of the SR-PUCCH resources and subsequently the associated interruptions.

[0103] Various examples for communicating uplink and downlink data in the wireless communication network 2000 are explained in conjunction with figures in the later parts of the description.

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

[0105] At step 310, the method 300 comprises determining whether or not to schedule uplink data transmissions for at least a first UE and a second UE among the plurality of UEs. In embodiments disclosed herein, scheduling the uplink data transmission for a UE may refer to granting of a Physical Uplink Shared Channel, PUSCH for the UE, so that the UE may transmit user data to the network node in the granted PUSCH. Step 301 may be performed when uplink Downlink Control Information, DCI, is available in at least one downlink slot or a special slot for at least the first UE and the second UE.

[0106] At step 310a, the method 300 comprises determining to schedule the uplink data transmission for the first UE.

[0107] In some examples, the network node may determine to schedule the uplink data transmission for the first UE, when the network node identifies that the first UE has pending user data. The network node may identify that the first UE has pending user data from a Buffer Status Report, BSR, previously received from the first UE and based on decoding of a Scheduling Request, SR, from the first UE in a SR Physical Uplink Control Channel, PUCCH. For example, the network node may identify that the first UE has the pending user data, when the BSR>0 or when it has decoded SR=1 from the SR-PUCCH.

[0108] In some examples, the network node may determine to schedule the uplink data transmission for the first UE blindly, when the network node requests the first UE to signal its control status information (like piggybacking data when the network node determines that the UE will transmit the control status information necessary to determine beams (for example, narrow beams) to be used).

[0109] In some examples, the network node may determine to pre-schedule or schedule the uplink data transmission for the first UE, when there is no need for the PUSCH from any other UE.

[0110] In some examples, the network node may determine to pre-schedule or schedule the uplink data transmission for the first UE, when the network node has recently sent the downlink data to the first UE so that there might be an uplink response pending from the UE, which the network node is not aware of.

[0111] At step 310b, the method 300 further comprises determining not to schedule any uplink data transmission for the second UE.

[0112] In some examples, the network node may determine not to schedule any uplink data transmission for the second UE, when the network node does not receive any SR-PUCCH transmissions from the second UE in an expected time interval.

[0113] In some examples, the network node may determine not to schedule any uplink data transmission for the second UE, when available radio resources / PUSCH are utilized for the first UE (i.e., no availability of radio resource for the second UE).

[0114] For the first UE for which it has been determined to schedule the uplink data transmission, at step 315, the method comprises transmitting, to the first UE, the uplink DCI in a Physical Downlink Control Channel, PDCCH. Thereby effectuating the uplink data transmission in the PUSCH, in a subsequent uplink slot. The network node decodes the uplink data transmission from the first UE in the uplink slot. The uplink data transmission from the first UE comprises user data.

[0115] For the second UE for which it has been determined not to schedule the uplink data transmission, at step 320, the method comprising transmitting to the second UE, SR-PUCCH reset information in the PDCCH. The network node obviates decoding of any transmission from the second UE in the uplink slot.

[0116] In some embodiments, for the second UE for which it has been determined not to schedule the uplink data transmission, transmitting to said second UE, the SR-PUCCH reset information in the PDCCH, effectuates transmitting a BSR and optionally padding bits in the PUSCH in the subsequent uplink slot. The SR-PUCCH reset information is intended to cause the second UE to reset a SR timer corresponding to a maximum number of SR transmissions / SR-PUCCH transmissions configured for the second UE.

[0117] Thus, in embodiments disclosed herein, the SR-PUCCH reset information may be used as a normal PUSCH grant for the second UE with a difference that the network node will not decode the PUSCH from the second UE. In some embodiments, the network node may transmit the SR-PUCCH reset information to the second UE blindly.

[0118] In some embodiments, the step 320 of transmitting, to the second UE, the SR-PUCCH reset information in the PDCCH further comprises determining whether or not to initiate a reset request for each of the plurality of UEs. The reset request may be intended for transmission of the SR-PUCCH reset information. In some examples, the network node may determine whether or not to initiate the reset request for each of the plurality of UEs, based on a respective network timer for a respective UE. It may be determined to initiate the reset request for a UE, when the network timer for the UE exceeds a first threshold. The first threshold is lower than a time interval taken by the maximum number of SR transmissions configured for the UE.

[0119] When it has been determined to initiate the reset request for the UE, the method 300 comprises sending the reset request for that UE into a reset queue and monitoring the reset queue to determine whether or not to transmit the SR- PUCCH reset information in the PDCCH. It may be determined to transmit the SR-PUCCH reset information to the second UE in the PDCCH when the reset queue comprises a reset request for the second UE.

[0120] Transmission of the SR-PUCCH reset information to the second UE by monitoring the reset queue is described in detail in conjunction with Fig. 6B.

[0121] In some embodiments, the SR-PUCCH reset information transmitted to the second UE refers to a Transport Block Size, TBS, granted for transmission of the BSR and optionally padding bits other than user data from the second UE. Thereby, the granted TBS may not support transmission of the user data from the second UE to the network node. The network node may set the TBS herein small, so that the UE can send its BSR and possible padding bits excluding the user data.

[0122] Consider an example scenario, wherein the network node sets the TBS as 3 bytes. In such a scenario, the UE may transmit only the BSR to the network node, as the BSR requires 3 bytes. Consider another example scenario, wherein the network node sets the TBS as 4 bytes. In such a scenario, the UE may transmit the BSR of 3 bytes and padding bits of 1 byte to the network node. Thereby, by setting the TBS small, transmission of the user data from the second UE may be avoided. If the user data is transmitted and the network node has obviated reception of such data, it may lead to retransmission of the user data from a higher layer of the second UE by causing unnecessary end user delay. Such problems may be avoided by preventing the second UE from transmitting the user data to the network node.

[0123] In some embodiments, the network node may keep track of channel conditions of the UE to set the TBS. The channel conditions of the UE may include, but is not limited to, Signal-to-l nterference-plus-Noise Ratio, SINR, or the like.

[0124] Optionally, the SR-PUCCH reset information may be transmitted to the second UE independent of a Connected Discontinuous Reception, CDRX, state and a data traffic of the second UE. In some examples, the CDRX state of the second UE may include a cdrxlnactive state or a cdrxActive state. The network node may transmit the SR-PUCCH reset information to the second UE independent of the CDRX state, since the network node may not always know whether or not the second UE has pending user data and has transmitted the SR-PUCCH. For instance, in a first case, the second UE may have transmitted the SR-PUCCH, but the network node fails to decode the SR-PUCCH due to low SI NR. In a second case, the second UE is in the cdrxActive state and not sending any SR-PUCCH for the network node. In a third case that is in loaded scenario, the network node may observe that the SR-PUCCH is decoded as SR=1 multiple times, but the network node may not have an opportunity to schedule the uplink data transmission for the second UE. However, irrespective of the first, second, and third cases, the network node transmits the SR-PUCCH reset information to the second UE.

[0125] In some embodiments, after transmission (at step 320) of the SR-PUCCH reset information to the second UE or after successful decoding of an ongoing HARQ process between the network node and the second UE or prior to initiation of a new HARQ process between the network node and the second UE, the method 300 further comprises toggling a New Data Indicator, NDI, for a subsequent transmission of the SR PUCCH reset information to the second UE. The toggled NDI for the second UE may identify that a subsequent transmission from the second UE is to be a new uplink data transmission. The method 300 further comprises selecting a TBS from a pre-defined TBS sequence for the subsequent uplink data transmission from the second UE. The selected TBS for the second UE is different from a previously used TBS.

[0126] In some embodiments, the method 300 further comprises reserving a fixed HARQ identifier, ID, to be used for transmission of the SR-PUCCH reset information to the second UE.

[0127] Steps of toggling the NDI and selecting the TBS are described in detail in conjunction with Fig. 8.

[0128] Fig. 4 is a flowchart illustrating example method steps of a method 400 performed by a User Equipment, UE, for communicating uplink and downlink data with a network node in a Time Division Duplex, TDD, scheme. The TDD scheme comprises a plurality of transmission slots for communicating uplink and downlink data with the network node.

[0129] At step 410, the method 400 comprises decoding, a Physical Downlink Control Channel, PDCCH, received from the network node.

[0130] For the case when uplink Downlink Control Information, DCI, has been decoded from the PDCCH, at step 415, the method 400 comprises performing an uplink data transmission with the network node in a Physical Uplink Shared Channel, PUSCH, in a subsequent uplink slot.

[0131] For the case when a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information has been decoded from the PDCCH, at step 420, the method 400 comprises transmitting, to the network node, a Buffer Status Report, BSR, and optionally padding bits in the PUSCH, in a subsequent uplink slot and resetting a SR timer corresponding to a maximum number of SR transmissions configured for the UE on the PUCCH. Fig. 5 is a sequence diagram illustrating example signaling for handling scheduling of uplink data transmissions for User Equipments, UEs in a wireless communication network. The network node 202 communicates uplink and downlink data with at least first and second UEs 204-1 and 204-2 of a plurality of UEs in a Time Division Duplex, TDD, scheme.

[0132] The network node 202 determines 510 whether or not to schedule uplink data transmissions for the first and second UEs 204-1 and 204-2, when there is uplink Downlink Control Information, DCI, in at least one downlink slot for the first and second UEs 204-1 and 204-2.

[0133] In some examples, the network node may determine whether or not to schedule the uplink data transmissions for at least the first UE 204-1 and the second UE 204-2 independent of at least one Scheduling Request, SR, received from each of the first UE and the second UE in a SR Physical Uplink Control Channel, PUCCH.

[0134] In some examples, the network node may determine whether or not schedule the uplink data transmissions for at least the first UE 204-1 and the second UE 204-2 based on one or more metrics. Examples of the metrics may include, but are not limited to, a number of SR-PUCCH transmissions received from such UEs in an expected time interval, availability of one or more radio resources (including a Physical Uplink Shared Channel, PUSCH) at the network node for scheduling the uplink data transmission, a status of a network timer associated with such UEs, and so on. The network timer may be managed by the network node for each of the plurality of UEs for monitoring a maximum number of SR transmissions (also be referred to as SR-PUCCH transmissions) configured for that UE.

[0135] In an example herein, the network node 202 determines 510a to schedule the uplink data transmission for the first UE 204-1 and further determines 510b not to schedule the uplink data transmission for the second UE 204-2.

[0136] Upon determining to schedule the uplink data transmission for the first UE 204-1 , the network node 202 transmits 515 the uplink DCI (UL DCI) to the first UE 204-1 in a Physical Downlink Control Channel, PDCCH. The UL DCI indicates a grant of the PUSCH for the first UE 204-1 to perform the uplink data transmission in the subsequent uplink slot.

[0137] Upon determining not to schedule the uplink data transmission for the second UE 204-2, the network node 202 monitors 517 a reset queue 550 to determine if there is any reset request for the second UE 204-2. The reset queue 550 stores the reset requests initiated for different UEs, based on a status of respective network timers managed for the respective different UEs. In some embodiments, the reset request may be initiated for a UE when a network timer associated with that exceeds a first threshold. The first threshold may be less than a time interval taken for a maximum number of SR- PUCCH transmissions configured for the UE. If there is a reset request for the second UE 204-2, the network node 202 transmits 520 SR-PUCCH reset information to the second UE 204-2. After transmitting the SR-PUCCH reset information, the network node 202 resets 525 a network timer associated with the second UE 204-2.

[0138] Meanwhile, the first UE 204-1 decodes the PDCCH received from the network node 202. Based on the decoding of the PDCCH, the first UE 204-1 transmits 526 the uplink data transmission to the network node 202 in the subsequent uplink slot, in the PUSCH. The uplink data transmission comprises user data. The network node 202 decodes 527 the PUSCH / uplink data transmission from the first UE 204-1 to obtain the user data of the first UE 204-1 .

[0139] The second UE 204-2 decodes the PDCCH received from the network node 202. Based on the decoding of the PDCCH, the second UE 204-2 transmits 528a a Buffer Status Report, BSR, and padding bits (optional) without including any user data to the network node 202 in the subsequent uplink slot, in the PUSCH. Upon the transmission, the second UE 204-2 resets 528b a SR timer managed to track a maximum number of SRs configured for the second UE 204-2. The network node 202 obviates 529 decoding of the PUSCH from the second UE 204-2. Thereby, a fake PUSCH grant may be provided for the second UE using the SR-PUCCH reset information. With this fake PUSCH grant, the second UE resets its SR timer before reaching a maximum number of SR-PUCCH transmissions configured for that UE.

[0140] In view of the above, it is evident that with the normal and fake PUSCH grants, more than one UE may be granted with a same PUSCH / uplink slot, however the network node decodes the PUSCH from only one UE for which it is determined to schedule the uplink data transmission. Other UEs may execute a PDCCH process, which prevent occurrence of the maximum number of SR-PUCCH transmissions for the UEs.

[0141] In some examples, if the wireless communication network supports scheduling of more than one UE at a time, the network node may grant the normal PUSCH for one or more UEs (for example, by splitting transmissions in one downlink slot) along with granting the fake PUSCH for one or more other UEs. In such a scenario, the network node may decode the respective PUSCH from the one or more UEs for which the normal PUSCH is granted.

[0142] Fig. 6A is an example flow diagram illustrating method steps 600 performed by a network node for communicating uplink and downlink data in a Time Division Duplex, TDD, with a plurality of User Equipments, UEs. The TDD comprises a plurality of transmission slots for communication the uplink and downlink data with the plurality of UEs.

[0143] At step 601, the network node checks for at least one new transmission slot. When the at least one new transmission slot has been arrived, at step 605, the network node identifies if uplink Downlink Control Information, DCI, is available in the at least one transmission slot for the plurality of UEs. The at least one transmission slot herein refers to a downlink slot or a special slot. If the uplink DCI is not available in the at least one transmission slot, the network node performs step 601.

[0144] If the uplink DCI is available in the at least one transmission slot, at step 610, the network node 202 determines whether or not to schedule an uplink data transmission for the plurality of UEs. At steps 610a and 610b, the network node determines to schedule the uplink data transmission for a first UE among the plurality of UEs and not to schedule the uplink data transmission for a second UE among the plurality of UEs, respectively.

[0145] Upon determining (at step 610a) to schedule the uplink data transmission, at step 615, the network node transmits the uplink DCI to the first UE in a Physical Downlink Control Channel, PDCCH. Thereby, a Physical Uplink Shared Channel, PUSCH is granted for the first UE for the uplink data transmission. The uplink DCI instructs the first UE to perform the uplink data transmission in a subsequent uplink slot, in the granted PUSCH. The uplink data transmission comprises user data. Upon granting the PUSCH for the first UE, the network node receives and decodes the PUSCH from the first UE. Thereby, a regular / normal PUSCH grant may be provided for the first UE from the network node.

[0146] Upon determining (at step 610b) not to schedule the uplink data transmission, at step 620, the network node transmits a Scheduling Request, SR, Physical Uplink Control Channel, PUCCH (SR-PUCCH) reset information in the PDCCH. The SR-PUCCH reset information refers to a Transport Block Size, TBS, which enables the second UE 204-2 to transmit nothing more than a BSR and optionally padding bits to the network node in the PUSCH in the uplink slot (excluding transmission of the user data). Thereby, the SR-PUCCH reset information may appear as the normal PUSCH grant for the second UE. However, the network node obviates decoding of the PUSCH from the second UE.

[0147] In some examples, the PUSCH from the second UE may cause interference for the first UE. In order to avoid such interference, the network node may allocate very few Physical Resource Blocks, PRBs, compared to the first UE, or enable the second UE to transmit PUSCH with a low transmit power, or avoid transmitting the SR-PUCCH reset information to the second UE which narrow beam overlaps with the first UE (in such a case, the network node may select another second UE).

[0148] Upon transmitting the SR-PUCCH reset information to the second UE, at step 625, the network node resets a network timer associated with the second UE.

[0149] Fig. 6B is an example flow diagram illustrating method steps 600 performed by a network node for transmission of Scheduling Request, SR, Physical Uplink Control Channel, PUCCH (SR-PUCCH), reset information.

[0150] As disclosed in Fig. 6B, upon detecting start of at least one new transmission slot, steps 607, 608, and 609 are performed in parallel with steps 605, 610, and 615. As the steps 605, 610, and 615 have already been described in detail in conjunction with Fig. 6A, repeated description is omitted herein.

[0151] At step 607, the network node determines whether or not to initiate a reset request for any of a plurality of UEs. The reset request is initiated for transmission of the SR-PUCCH reset information. In some embodiments, the network node may determine whether or not to initiate a reset request for any of a plurality of UEs based on a respective network timer associated with a respective UE. The network timer may be managed for each of the plurality of UEs to monitor a maximum number of Scheduling Request, SR, transmissions configured for that UE. The network timer may be set to a first threshold, which is shorter than a shortest time to perform a maximum number of SR-PUCCH transmissions configured for the UE. Thus, the network timer for the UE runs from ‘O' to the first threshold. In some embodiments, the network node may count a time from the first transmission of the PDCCH until PUSCH was successfully decoded and use that counted time as a start of the network timer for the UE. When it has been determined that the network timer for at least a UE of the plurality of UEs exceeds the first threshold, at step 608, the network node initiates the reset request. Thus, the network node may use a timer based solution to determine when the maximum number of SR-PUCCH transmissions configured for the UE is about to happen and accordingly initiate the reset request for transmission of the SR-PUCCH reset information for that UE.

[0152] At step 609, the network node sends the reset request initiated for the UE into the queue.

[0153] Meanwhile, when it has been determined (at step 610) not to schedule an uplink data transmission for a second UE among the plurality of UEs, at step 617, the network node identifies if there is any reset request for the second UE in the reset queue. If there is a reset request for the second UE in the reset queue, at step 620, the network node transmits the SR-PUCCH reset information to the second UE in a Physical Downlink Control Channel, PDCCH. Thereafter, the network node performs step 625, as described in detail in conjunction with Fig. 6A.

[0154] Fig. 7 is an example flowchart illustrating method steps 710 performed by a network node for resetting a network timer associated with a User Equipment. The network node manages the network timer for each of the plurality of UEs to monitor a maximum number of Scheduling Request, SR, transmissions configured for that UE on a SR Physical Uplink Control Channel, PUCCH (SR-PUCCH). Although the method steps 710 disclosed herein may be equally applicable for the plurality of UEs, the embodiments herein are described by considering a single UE for ease of understanding.

[0155] At step 601 , the network node identifies if there is any new transmission slot for a UE. If there is any new transmission slot for the UE, at step 703, the network node increments network timer associated with the UE.

[0156] Upon incrementing the network timer, at step 705, the network node identifies whether Hybrid Automatic Repeat Request, HARQ, information comprising a Buffer Status Report, BSR, has been decoded for the UE, when there is a Physical Uplink Shared Channel, PUSCH from the UE in an uplink slot in response to a previous scheduling of the uplink data transmission for the UE.

[0157] When it has been determined that the HARQ information has been decoded for the UE, at step 707, the network node determines whether the HARQ information has been decoded using a first HARQ transmission from the UE. When it has been determined that the HARQ information has not been decoded or it has been determined that the HARQ information has been not decoded using the first HARQ transmission, the network node repeats from step 601.

[0158] When it has been determined that the HARQ information has been decoded using the first HARQ transmission from the UE, at step 709, the network node resets the network timer associated with the UE. Resetting the network timer based upon the first HARQ transmission from the UE guarantees that the time when the UE resets its SR timer (at a Physical Downlink Control Channel, PDCCH) and when the network node resets the network timer for the UE (at the PUSCH) is kept small to avoid long HARQ retransmissions. In some embodiments, the network node may also reset the network timer associated with the UE upon determining that the network timer associated with the UE has exceeded a second threshold. The second threshold is a general threshold defined for operability of the network timer.

[0159] In some embodiments, the network node may also reset the network timer associated with the UE upon transmitting the SR-PUCCH reset information to the UE.

[0160] Fig. 8 is an example flowchart illustrating method steps performed by a network node for assigning a New Data Indicator, NDI, and a Transport Block Size, TBS, for a UE. Although the method steps disclosed in Fig. 8 may be equally applicable for the plurality of UEs, the embodiments herein are described by considering a single UE for ease of understanding.

[0161] At step 800, the network node sets a start value of NDI and TBS.

[0162] At step 620, the network node determines if a Scheduling Request, SR, Physical Uplink Control Channel, PUCCH (SR- PUCCH) reset information has been transmitted to the UE. The UE referred in Fig. 8 may be the UE for which it has been determined not to schedule an uplink data transmission.

[0163] If the SR-PUCCH reset information has been transmitted to the UE, at step 802, the network node toggles the NDI for the UE for a subsequent transmission of the SR PUCCH reset information to the UE. The toggled NDI for the UE may identify that a subsequent transmission from the UE is to be a new uplink data transmission. The NDI referred herein may be a NDI associated with a reset queue comprising at least one reset request for transmission of the SR-PUCCH reset information for at least one UE.

[0164] At step 803, the network node selects the TBS from a pre-defined TBS sequence for the subsequent uplink data transmission from the UE. The selected TBS for the at least one first UE is different from a previously used TBS. In some embodiments, the network node may select the TBS based on a round robin approach. Consider an example, wherein the pre-defined TBS sequence comprises a TBS 1 , a TBS 2, and a TBS 3 and the TBS 1 has been used previously. In such a scenario, the network node selects the TBS 2 from the pre-defined TBS sequence for the subsequent uplink data transmission from the UE.

[0165] The toggled NDI and the changed TBS may indicate that the UE shall reset its SR timer.

[0166] In some embodiments, the steps 802 and 803 may be performed after successful decoding of an ongoing HARQ process between the network node and the UE or prior to initiation of a new HARQ process between the network node and the second UE.

[0167] In some embodiments, the network node may further reserve a fixed HARQ ID for transmission of the SR-PUCCH reset information to the UE. In an example, the network node may reserve a HARQ ID 15 from HARQ IDs 1-16 for transmission of the SR-PUCCH reset information. The NDI may control the HARQ ID for which it refers to (for example herein, HARQ ID 15).

[0168] The network node may use any of the HARQ IDs for transmission of the SR-PUCCH reset information. However, using any of the HARQ IDs may not be optimal since the SR-PUCCH reset information is transmitted blindly to the UE irrespective of one or more SRs received from the UE in the PUCCH. For example, the UE in a sleep state may not decode the SR-PUCCH reset information received from the network node. Hence, if any random HARQ ID (for example, an HARQ ID 3) is assigned for the transmission of the SR-PUCCH reset information, the UE may use that HARQ ID for transmission of user data when the UE wakes up. Thus, the HARQ ID 15 is fixed for transmission of the SR-PUCCH reset information, which prevents the UE from transmitting the user data to the network node in response to the SR-PUCCH reset information.

[0169] It should be understood that the HARQ ID 15 may also be used for the actual user data transmission, when the transmission of SR-PUCCH reset information is not required for any of the plurality of UEs.

[0170] Fig. 9 discloses an example illustration of handling uplink and downlink data communication in a wireless communication network. In the wireless communication network, a network node 202 communicates uplink and downlink data in a Time Duplex Division, TDD, scheme with a plurality of UEs. The TDD scheme comprises a plurality of transmission slots 901-910, which may be used by the network node 202 for communicating uplink and downlink data with the plurality of UEs. The TDD scheme with DDDSUDDDSU pattern is disclosed in Fig. 9, wherein the transmission slots may comprise downlink slots (D901 , D902, D903, D906, D907, and D908), special slots (S904 and S909), and uplink slots (U905 and U910)

[0171] Consider an example scenario, wherein the network node 202 identifies a start of downlink slots D901 , D902, and D903 having uplink Downlink Control Information, DCI, available for User Equipments, UEs 204-1 , 204-2, and 204-3. In such a scenario, the network node 202 determines to schedule an uplink data transmission for the UE 204-1 and further determines not to schedule any uplink data transmission for the UEs 204-2 and 204-3. Upon the determination, the network node 202 transmits uplink DCI to the UE 204-1 in a Physical Downlink Control Channel, PDCCH, in the D901. The network node 202 further transmits a Scheduling Request, SR, Physical Uplink Control Channel, PUCCH (SR-PUCCH) reset information to the UEs 204-2 and 204-3 in the PDCCH, in the D902 and D903, respectively.

[0172] Upon receiving the PDCCH from the network node 202, the UE 204-1 performs the uplink data transmission in a Physical Uplink Shared Channel, PUSCH, in the subsequent uplink slot U905. The uplink data transmission comprises user data. The network node decodes the PUSCH from the UE 204-1 to obtain the user data.

[0173] Upon receiving the PDCCH from the network node 202, the UE 204-2 / 204-3 transmits a Buffer Status Report, BSR, and optionally padding bits to the network node in the PUSCH in the subsequent uplink slot U905. However, the network node obviates decoding of the PUSCH from the UE 204-2 / 204-3. Thus, the network node may provide a normal PUSCH grant for the UE for which it has been determined to schedule the uplink data transmission and fake PUSCH grants for multiple UEs for which it has been determined not to schedule the uplink data transmission. Such fake PUSCH grants allow the UEs to reset their SR timers before reaching a maximum number of SR-PUCCH transmissions.

[0174] Fig. 10 discloses an example illustration of handling uplink data transmission for a User Equipment, UE.

[0175] Consider an example scenario as depicted in Fig. 10, wherein the network node schedules / grants (step 1) the uplink data transmission (i.e., a Physical Uplink Shared Channel, PUSCH) for a UE in a Physical Downlink Control Channel, PDCCH. Upon scheduling the uplink data transmission for the UE, the UE transmits the PUSCH in a subsequent uplink slot. The PUSCH may comprise a Buffer Status Report, BSR > ‘O' and optionally user data. The network node decodes (at step 2) the PUSCH from the UE. The UE resets a SR counter / timer (reference time x) after transmission of the PUSCH in the subsequent uplink slot.

[0176] Further, when the UE has pending user data, the UE initiates Scheduling Request, SR, Physical Uplink Control Channel, PUCCH (SR-PUCCH) transmissions for a grant of the PUSCH from the network node. The UE may perform the SR-PUCCH transmissions till the SR counter / timer reaches a maximum number of SR transmissions configured for the UE, for example, SR counter / timer='n' milliseconds, ms. During ‘n’ ms, the network node may not schedule the uplink data transmission / grant the PUSCH for the UE due to lack of PUSCH resources, as disclosed in Fig. 1C. In contrast to such a process as disclosed in Fig. 1C, embodiments herein enable the network node to provide a fake PUSCH grant for the UE before ‘n’ ms, when the network node is not able to schedule / grant any uplink data transmission / PUSCH for that UE.

[0177] For instance, as disclosed in Fig. 10, the network node may not schedule any uplink data transmission for the UE during ‘m’ ms, wherein m<n. After ‘m’ ms (i.e., in between ‘m’ and ‘n’ ms), the network node may provide (at step 4) the fake PUSCH grant for the UE by transmitting SR-PUCCH reset information to the UE in the PDCCH. The SR- PUCCH reset information enables the UE to transmit a Buffer Status Report, BSR, and optionally padding bits to the network node in the granted PUSCH. However, the network node does not decode (at step 5) the PUSCH from the UE, which provides an extra amount of PDCCH / PUSCH to the UE for resetting its SR timer. Thus, the SR timer may be reset (at step 6) before reaching the maximum number of SR transmissions configured for the UE on the SR- PUCCH, which avoids releasing of SR-PUCCH resources by the UE. Hence no troublesome interruption for an end user.

[0178] Fig. 11 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 uplink and downlink data in a Time Division Duplex, TDD, with a plurality of User Equipments, UEs, and may be configured to cause performance of the method 300 for communicating the uplink and downlink data in the TDD with the plurality of UEs. According to at least some embodiments of the present invention, the apparatus 202 in Fig. 11 comprises one or more modules. These modules may e.g. be a memory 1102, a processor 1104, a controlling circuitry 1106, a transceiver 1108, a determination module 1110, and a decoding module 1112. The controlling circuitry 1106, may in some embodiments be adapted to control the above mentioned modules.

[0179] The memory 1102, the processor 1104, the transceiver 1108, the determination module 1110, and the decoding module 1112, as well as the controlling circuitry 1106, may be operatively connected to each other.

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

[0181] The determination module 1110 may be adapted to determine whether or not to schedule uplink data transmissions for at least a first UE and a second UE among the plurality of UEs.

[0182] When it has been determined to schedule an uplink data transmission for the first UE, the transceiver 1108 may be adapted to transmit uplink Downlink Control Information, DCI, to the first UE in a Physical Downlink Control Channel, PDCCH.

[0183] When it has been determined not to schedule any uplink data transmission for the second UE, the transceiver 1108 may be adapted to transmit Scheduling Request, SR, Physical Uplink Control Channel, SR-PUCCH, reset information to the second UE in the PDCCH. The SR-PUCCH reset information is intended to cause the second UE to reset a SR timer corresponding to a maximum number of transmissions configured for the second UE.

[0184] The decoding module 1112 may be configured to decode the uplink data transmission received from the first UE in a Physical Uplink Shared Channel, PUSCH, in a subsequent uplink slot. The decoding module 1112 may be further configured to obviate any transmission from the second UE in the PUSCH in the subsequent uplink slot.

[0185] The processor 1104 may be adapted to manage a network timer for each of the plurality of UEs for monitoring a maximum number of SR transmissions configured for said UE. In some embodiments, a status of the network timer associated with a UE may be used to initiate a reset request for that UE. The reset request may be for transmission of the SR-PUCCH reset information. The reset request initiated for any UEs may be stored in a reset queue.

[0186] Further, the memory 1102 is adapted to store the network timer, the reset queue, the uplink data transmission decoded from the UE, or the like.

[0187] Fig. 12 is an example schematic diagram showing an apparatus 204. The apparatus 204 may e.g. be comprised in any of a plurality of User Equipment, UEs (for example, UEs 204-1 - 204N as depicted in Fig. 2). The apparatus 204 is capable of communicating uplink and downlink data with a network node in a Time Division Duplex, TDD, and may be configured to cause performance of the method 400 for communicating with the network node in the TDD.

[0188] According to at least some embodiments of the present invention, the apparatus 204 in Fig. 12 comprises one or more modules. These modules may e.g. be a memory 1202, a processor 1204, a controlling circuitry 1206, a transceiver 1208, and a reset module 1212. The controlling circuitry 1206, may in some embodiments be adapted to control the above mentioned modules.

[0189] The memory 1202, the processor 1204, the transceiver 1208, and the reset module 1212 as well as the controlling circuitry 1206, may be operatively connected to each other.

[0190] The transceiver 1208 may be adapted to receive a Physical Downlink Control Channel, PDCCH from the network node.

[0191] The reset module 1212 may be adapted to decode the PDCCH from the network node. When uplink downlink control information, DCI, has been decoded from the PDCCH, the reset module 1212 may be adapted to enable the transceiver 1208 to transmit user data to the network node in a Physical Uplink Shared Channel, PUSCH, in a subsequent uplink slot.

[0192] When Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information has been decoded from the PDCCH, the reset module 1212 may be adapted to enable the transceiver 1208 to transmit a Buffer Status Report, BSR, and padding bits (optional) to the network node in the PUSCH in the subsequent uplink slot and to reset a SR timer corresponding to a maximum number of SR transmissions configured for the UE.

[0193] Further, the processor 1204 is adapted to manage the SR timer for the UE.

[0194] Further, the memory 1202 is adapted to store the SR timer, the maximum number of SR transmissions configured for the UE, or the like.

[0195] Fig. 13 is a block diagram of a telecommunication network connected via an intermediate network to a host computer according to some embodiments. With reference to Fig. 13, in accordance with an embodiment, a communication system includes telecommunication network 4410, such as a 3GPP-type cellular network, which comprises access network 4411, such as a radio access network, and core network 4414. Access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to, or be paged by, the corresponding base station 4412c. A second UE 4492 in coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491 , 4492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 4412. Telecommunication network 4410 is itself connected to host computer 4430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 4430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 4421 and 4422 between telecommunication network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430 or may go via an optional intermediate network 4420. Intermediate network 4420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 4420, if any, may be a backbone network or the Internet; in particular, intermediate network 4420 may comprise two or more sub-networks (not shown).

[0196] The communication system of Fig. 13 as a whole enables connectivity between the connected UEs 4491, 4492 and host computer 4430. The connectivity may be described as an over-the-top, OTT connection 4450. Host computer 4430 and the connected UEs 4491 , 4492 are configured to communicate data and / or signaling via OTT connection 4450, using access network 4411 , core network 4414, any intermediate network 4420 and possible further infrastructure (not shown) as intermediaries. OTT connection 4450 may be transparent in the sense that the participating communication devices through which OTT connection 4450 passes are unaware of routing of uplink and downlink communications. For example, base station 4412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 4430 to be forwarded (e.g., handed over) to a connected UE 4491. Similarly, base station 4412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 4491 towards the host computer 4430.

[0197] Fig. 14 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection. Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Fig. 14. In communication system 4500, host computer 4510 comprises hardware 4515 including communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 4500. Host computer 4510 further comprises processing circuitry 4518, which may have storage and / or processing capabilities.

[0198] In particular, processing circuitry 4518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 4510 further comprises software 4511 , which is stored in or accessible by host computer 4510 and executable by processing circuitry 4518. Software 4511 includes host application 4512. Host application 4512 may be operable to provide a service to a remote user, such as UE 4530 connecting via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the remote user, host application 4512 may provide user data which is transmitted using OTT connection 4550. Communication system 4500 further includes base station 4520 provided in a telecommunication system and comprising hardware 4525 enabling it to communicate with host computer 4510 and with UE 4530. Hardware 4525 may include communication interface 4526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 4500, as well as radio interface 4527 for setting up and maintaining at least wireless connection 4570 with UE 4530 located in a coverage area (not shown in Fig. 14) served by base station 4520. Communication interface 4526 may be configured to facilitate connection 4560 to host computer 4510. Connection 4560 may be direct or it may pass through a core network (not shown in Fig. 14) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 4525 of base station 4520 further includes processing circuitry 4528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 4520 further has software 4521 stored internally or accessible via an external connection.

[0199] Communication system 4500 further includes UE 4530 already referred to. Its hardware 4535 may include radio interface 4537 configured to set up and maintain wireless connection 4570 with a base station serving a coverage area in which UE 4530 is currently located. Hardware 4535 of UE 4530 further includes processing circuitry 4538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 4530 further comprises software 4531, which is stored in or accessible by UE 4530 and executable by processing circuitry 4538. Software 4531 includes client application 4532. Client application 4532 may be operable to provide a service to a human or non-human user via UE 4530, with the support of host computer 4510. In host computer 4510, an executing host application 4512 may communicate with the executing client application 4532 via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the user, client application 4532 may receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 may transfer both the request data and the user data. Client application 4532 may interact with the user to generate the user data that it provides.

[0200] It is noted that host computer 4510, base station 4520 and UE 4530 illustrated in Fig. 14 may be similar or identical to host computer 4430, one of base stations 4412a, 4412b, 4412c and one of UEs 4491 , 4492 respectively. This is to say, the inner workings of these entities may be as shown in Fig. 19 and independently, the surrounding network topology may be that of Fig. 14.

[0201] In Fig. 14, OTT connection 4550 has been drawn abstractly to illustrate the communication between host computer 4510 and UE 4530 via base station 4520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 4530 or from the service provider operating host computer 4510, or both. While OTT connection 4550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0202] Wireless connection 4570 between UE 4530 and base station 4520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE 4530 using OTT connection 4550, in which wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and / or reduce random access failure rates and thereby provide benefits such as faster and / or more reliable random access.

[0203] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 4550 between host computer 4510 and UE 4530, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring OTT connection 4550 may be implemented in software 4511 and hardware 4515 of host computer 4510 or in software 4531 and hardware 4535 of UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 4550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 4511 , 4531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 4550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 4520, and it may be unknown or imperceptible to base station 4520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 4510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 4511 and 4531 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 4550 while it monitors propagation times, errors or the like.

[0204] Fig. 15 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. For simplicity of the present disclosure, only drawing references to Fig. 15 will be included in this section. In step 4610, the host computer provides user data. In substep 4611 (which may be optional) of step 4610, the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. Fig. 16 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. For simplicity of the present disclosure, only drawing references to Fig. 16 will be included in this section. In step 4710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 4720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0205] Fig. 17 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. For simplicity of the present disclosure, only drawing references to Fig. 17 will be included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In substep 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In substep 4811 (which may be optional) of step 4810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 4830 (which may be optional), transmission of the user data to the host computer. In step 4840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0206] Fig. 18 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. Fig. 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE. For simplicity of the present disclosure, only drawing references to Fig. 18 will be included in this section. In step 4910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0207] 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.

[0208] 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.

[0209] Fig. 19 illustrates an example computing environment 1900 implementing methods and a network node and a UE, as described in Figs. 3, 4, 11 , and 12. As depicted in Fig. 19, the computing environment 1900 comprises at least one data processing module 1906 that is equipped with a control module 1902 and an Arithmetic Logic Unit, ALU, 1904, a plurality of networking devices 1908 and a plurality Input output, I / O devices 1910, a memory 1912, a storage 1914. The data processing module 1906 may be responsible for implementing the methods described in Figs.3 and 4. For example, the data processing module 1906 may in some embodiments be equivalent to the controlling circuitry of the network node / UE described above in conjunction with the Fig. 11 / 12. The data processing module 1906 is capable of executing software instructions stored in memory 1912. The data processing module 1906 receives commands from the control module 1902 in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU 1904.

[0210] The computer program is loadable into the data processing module 1906, which may, for example, be comprised in an electronic apparatus (such as a network node / UE). When loaded into the data processing module 1206, the computer program may be stored in the memory 1912 associated with or comprised in the data processing module 1906. According to some embodiments, the computer program may, when loaded into and run by the data processing module 1906, cause execution of method steps according to, for example, any of the methods illustrated in Figs. 3 and 4 or otherwise described herein.

[0211] The overall computing environment 1900 may be composed of multiple homogeneous and / or heterogeneous cores, multiple CPUs of different kinds, special media and other accelerators. Further, the plurality of data processing modules 1906 may be located on a single chip or over multiple chips. The algorithm comprising of instructions and codes required for the implementation are stored in either the memory 1912 or the storage 1914 or both. At the time of execution, the instructions may be fetched from the corresponding memory 1912 and / or storage 1914, and executed by the data processing module 1906.

[0212] In case of any hardware implementations various networking devices 1908 or external I / O devices 1910 may be connected to the computing environment to support the implementation through the networking devices 1908 and the I / O devices 1910.

[0213] 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. 19 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

Claims

CLAIMS1. A method (300) performed by a network node (202) for communicating uplink and downlink data in a Time Division Duplex, TDD, scheme with a plurality of User Equipments, UEs (204-1 - 204-N), the TDD scheme comprising a plurality of transmission slots (901-910) for communicating the uplink and downlink data with the plurality of UEs (204-1 - 204-N), the method (300) comprising:- determining (310, 510, 610) whether or not to schedule uplink data transmissions for at least a first UE and a second UE (204-1 - 204-2) among the plurality of UEs (204-1 - 204-N); wherein- for the case it has been determined to schedule (310a, 510a, 610a) an uplink data transmission for the first UE (204-1) and it has been further determined not to schedule (310b, 510b, 610b) any uplink data transmission for the second UE (204-2),- for the first UE (204-1) for which it has been determined to schedule the uplink data transmission, transmitting (315, 515, 615) to said first UE (204-1) uplink Downlink Control Information, DCI, in a Physical Downlink Control Channel, PDCCH, thereby effectuating the uplink data transmission in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot (905), the network node (202) decoding said uplink data transmission from the first UE (204-1) in the uplink slot (905); and- for the second UE (204-2) for which it has been determined not to schedule the uplink data transmission, transmitting (320, 520, 620) to said second UE (204-2), a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information in the PDCCH, the network node (202) obviating decoding any transmission from the second UE (204-2) in the uplink slot (905).

2. The method (300) according to claim 1 , wherein for the second UE (204-2) for which it has been determined not to schedule the uplink data transmission, transmitting (320, 520, 620) to said second UE (204-2), the SR- PUCCH reset information in the PDCCH, effectuating transmitting a Buffer Status Report, BSR, and optionally padding bits in the PUSCH in the subsequent uplink slot (905), said SR-PUCCH reset information being intended to cause the second UE (204-2) to reset a SR timer corresponding to a maximum number of SR transmissions configured for the second UE (204-2).

3. The method (300) according to any of the preceding claims, wherein the step (320, 520, 620) of transmitting, to the second UE (204-2), the SR-PUCCH reset information in the PDCCH further comprising:- determining (607) whether or not to initiate a reset request for each of the plurality of UEs (204-1 - 204- N) based on a respective network timer for a respective UE, said reset request is intended for transmission of the SR-PUCCH reset information; and- when it has been determined (608) to initiate the reset request for a UE, sending (609) the reset request for said UE into a reset queue (550); and- monitoring (617) the reset queue (550) to determine whether or not to transmit the SR-PUCCH reset information in the PDCCH, wherein transmitting (320, 520, 620) to the second UE (204-2) the SR-PUCCH reset information in the PDCCH is determined when the reset queue comprises a reset request for said second UE (204-2).

4. The method (300) according to claim 3, wherein the network timer is managed by the network node (202) for each of the plurality of UEs (204-1 -204-N) for monitoring the maximum number of SR transmissions configured for said UE.

5. The method (300) according to any of claims 3-4, wherein initiating the reset request for the UE is determined (608) when the network timer for the UE exceeds a first threshold, wherein the first threshold is lower than a time interval taken by the maximum number of SR transmissions configured for the UE.

6. The method (300) according to any of claims 3-5, further comprising a step (710) of resetting the network timer corresponding to the UE of the plurality of UEs (204-1 - 204-N), said step comprising:- determining (705) whether Hybrid Automatic Repeat Request, HARQ, information comprising a BSR has been decoded for the UE, when there is the PUSCH from the UE in the uplink slot in response to a previous scheduling of the uplink data transmission for the UE;- when it has been determined that the HARQ information has been decoded for the UE, determining (707) whether the HARQ information has been decoded using a first HARQ transmission from the UE; and- when it has been determined that the HARQ information has been decoded using the first HARQ transmission from the UE, resetting (709) the network timer corresponding to said UE.

7. The method (300) according to any of claims 3-6, further comprising resetting the network timer corresponding to the UE upon performing at least one of the following steps:- determining that the network timer corresponding to the UE has exceeded a second threshold; and- transmitting the SR-PUCCH reset information to the UE.

8. The method (300) according to any of the preceding claims, wherein after transmission (620) of the SR- PUCCH reset information to the second UE (204-2) or after successful decoding of an ongoing HARQ processbetween the network node (202) and the second UE (204-2) or prior to initiation of a new HARQ process between the network node (202) and the second UE (204-2), the method (300) further comprising:- toggling (802) a New Data Indicator, NDI, for a subsequent transmission of the SR PUCCH reset information to the second UE (204-2), wherein the toggled NDI for the second UE (204-2) identifies that a subsequent transmission from the second UE (204-2) is to be a new uplink data transmission; and- selecting (803) a Transport Block Size, TBS, from a pre-defined TBS sequence for the subsequent uplink data transmission from the second UE (204-2), wherein the selected TBS for the second UE (204-2) is different from a previously used TBS.

9. The method (300) according to any of the preceding claims, further comprising:- reserving a fixed HARQ identifier, ID, to be used for transmission of the SR PUCCH reset information to the second UE (204-2).

10. The method (300) according to any of the preceding claims, wherein the SR-PUCCH reset information transmitted to the second UE (204-2) refers to a TBS granted for transmission of the BSR and optionally padding bits other than user data from the second UE (204-2).

11. The method (300) according to any of the preceding claims, wherein the SR-PUCCH reset information is transmitted to the second UE (204-2) independent of a Connected Mode Discontinuous Reception, CDRX, state and a data traffic of the second UE (204-2).

12. The method (300) according to any of the preceding claims, wherein determining (310, 510, 610) whether or not to schedule the uplink data transmission for at least the first UE and second UE (204-1 - 204-2), when the uplink DCI is available (605) in at least one downlink slot (901 -903) or a special slot (904) for at least the first UE and second UE (204-1 - 204-2).

13. The method (300) according to any of the preceding claims, further comprising:- determining whether to schedule a downlink data transmission for at least a UE of the plurality of UEs (204-1 -204-N), when a downlink DCI is available in at least one downlink slot (901-903) for that UE; and- when it has been determined to schedule the downlink data transmission, transmitting, to said UE, the DL DCI in the PDCCH indicating a grant of a Physical Data Shared Channel, PDSCH, for reception of the downlink data transmission from the network node (202).

14. The method (300) according to any of the preceding claims, wherein the network node (202) is communicating over a plurality of antennas using an analogue beam forming, wherein the plurality of antennas using the analogue beam forming are associated with respective wide beams (WB1-WBn) and narrow beams, a plurality of wide beams (WB1-WBn) covering respective areas, whereby for each wide beam (WB2) at least one narrow beam (NB) forms a joint area with a wide beam (WB2).

15. A method (400) performed by a User Equipment, UE (204) for communicating uplink and downlink data with a network node (202) in a Time Division Duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (901-910) for communicating uplink and downlink data with the network node (202), the method (400) comprising:- decoding (410), a Physical Downlink Control Channel, PDCCH, received from the network node (202), wherein- for the case when uplink Downlink Control Information, DCI, is decoded from the PDCCH, performing (415) an uplink data transmission with the network node (202) in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot (905); and- for the case when a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information is decoded from the PDCCH, transmitting (420), to the network node (202), a Buffer Status Report, BSR, and optionally padding bits in the PUSCH, in the subsequent uplink slot (905) and resetting a SR timer corresponding to a maximum number of SR transmissions configured for the UE (204).

16. An apparatus of a network node (202) for communicating uplink and downlink data in a Time Division Duplex, TDD, scheme with a plurality of User Equipments, UEs (204-1 - 204-N), the TDD scheme comprising a plurality of transmission slots (901-910) for communicating the uplink and downlink data with the plurality of UEs (204-1 - 204-N), the apparatus comprising controlling circuitry (1106) configured to cause:- determination of whether or not to schedule uplink data transmissions for at least a first UE and a second UE (204-1 - 204-2) among the plurality of UEs (204-1 - 204-N); wherein- for the case it has been determined to schedule an uplink data transmission for the first UE (204-1) and it has been further determined not to schedule (610b) any uplink data transmission for the second UE (204-2),- for the first UE (204-1) for which it has been determined to schedule the uplink data transmission, transmission, to said first UE (204-1) uplink Downlink Control Information, DCI, in a Physical Downlink Control Channel, PDCCH, thereby effectuating the uplink data transmission in a Physical UplinkScheduling Channel, PUSCH, in a subsequent uplink slot (905), the network node (202) decoding said uplink data transmission from the first UE (204-1) in the uplink slot (905); and- for the second UE (204-2) for which it has been determined not to schedule the uplink data transmission, transmission, to said second UE (204-2), a Scheduling Request Physical Uplink Control Channel, SR- PUCCH, reset information in the PDCCH the network node (202) obviating decoding any transmission from the second UE (204-2) in the uplink slot (905).

17. The apparatus according to claim 16, wherein for the second UE (204-2) for which it has been determined not to schedule the uplink data transmission, transmitting (320, 520, 620) to said second UE (204-2), the SR- PUCCH reset information in the PDCCH, effectuating transmitting a Buffer Status Report, BSR, and optionally padding bits in the PUSCH in the subsequent uplink slot (905), said SR-PUCCH reset information being intended to cause the second UE (204-2) to reset a SR timer corresponding to a maximum number of SR transmissions configured for the second UE (204-2).

18. The apparatus according to any of claims 16-17, wherein the controlling circuitry (1106) is configured to cause the step of transmitting, to the second UE (204-2), the SR-PUCCH reset information in the PDCCH by causing:- determination of whether or not to initiate a reset request for each of the plurality of UEs (204-1 - 204- N) based on a respective network timer for a respective UE, said reset request is intended for transmission of the SR-PUCCH reset information; and- when it has been determined to initiate the reset request for a UE, sending of the reset request for said UE into a reset queue (550); and- monitoring of the reset queue (550) to determine whether or not to transmit the SR-PUCCH reset information in the PDCCH, wherein transmitting to the second UE (204-2) the SR-PUCCH reset information in the PDCCH is determined when the reset queue comprises a reset request for said second UE (204-2).

19. The apparatus according to claim 18, wherein the network timer is managed by the network node (202) for each of the plurality of UEs (204-1 -204-N) for monitoring the maximum number of SR transmissions configured for said UE.

20. The apparatus according to any of claims 18-19, wherein initiating the reset request for the UE is determined when the network timer for the UE exceeds a first threshold, wherein the first threshold is lower than a time interval taken by the maximum number of SR transmissions configured for the UE.

21. The apparatus according to any of claims 18-20, wherein the controlling circuitry (1106) is further configured to cause a step of resetting the network timer corresponding to the UE of the plurality of UEs (204-1 - 204-N) by causing:- determination of whether Hybrid Automatic Repeat Request, HARQ, information comprising a BSR has been decoded for the UE, when there is the PUSCH from the UE in the uplink slot in response to a previous scheduling of the uplink data transmission for the UE;- when it has been determined that the HARQ information has been decoded for the UE, determination of whether the HARQ information has been decoded using a first HARQ transmission from the UE; and- when it has been determined that the HARQ information has been decoded using the first HARQ transmission from the UE, resetting of the network timer corresponding to said UE.

22. The apparatus according to any of claims 18-21 , wherein the controlling circuitry (1106) is further configured to cause resetting of the network timer corresponding to the UE upon performing at least one of the following steps:- determining that the network timer corresponding to the UE has exceeded a second threshold; and- transmitting the SR-PUCCH reset information to the UE.

23. The apparatus according to any of claims 16-22, wherein after transmission of the SR-PUCCH reset information to the second UE (204-2) or after successful decoding of an ongoing HARQ process between the network node (202) and the second UE (204-2) or prior to initiation of a new HARQ process between the network node (202) and the second UE (204-2), the controlling circuitry is further configured to cause:- toggling of a New Data Indicator, NDI, for a subsequent transmission of the SR PUCCH reset information to the second UE (204-2), wherein the toggled NDI for the second UE (204-2) identifies that a subsequent transmission from the second UE (204-2) is to be a new uplink data transmission; and- selection of a Transport Block Size, TBS, from a pre-defined TBS sequence for the subsequent uplink data transmission from the second UE (204-2), wherein the selected TBS for the at least one first UE is different from a previously used TBS.

24. The apparatus according to any of claims 16-23, wherein the controlling circuitry (1106) is further configured to cause:- reservation of a fixed HARQ identifier, ID, to be used for transmission of the SR PUCCH reset information to the second UE (204-2).

25. The apparatus according to any of claims 16-24, wherein the SR-PUCCH reset information transmitted to the second UE (204-2) refers to a TBS granted for transmission of the BSR and optionally padding bits other than user data from the second UE (204-2).

26. The apparatus according to any of claims 16-25, wherein the SR-PUCCH reset information is transmitted to the second UE (204-2) independent of a Connected Mode Discontinuous Reception, CDRX, state and a data traffic of the second UE (204-2).

27. The apparatus according to any of claims 16-26, wherein the controlling circuitry (1106) is further configured to cause the step of determination of whether or not to schedule the uplink data transmission for at least the first UE and second UE (204-1 - 204-2), when the uplink DCI is available in at least one downlink slot (901 - 903) or a special slot (904) for at least the first UE and second UE (204-1 - 204-2).

28. The apparatus according to any of claims 16-27, wherein the controlling circuitry is further configured to cause:- determination of whether to schedule a downlink data transmission for at least a UE of the plurality of UEs (204-1-204-N), when a downlink DCI is available in the downlink slot (901-903) for that UE; and- when it has been determined to schedule the downlink data transmission, transmission, to said UE, the downlink DCI in the PDCCH indicating a grant of a Physical Data Shared Channel, PDSCH, for reception of the downlink data transmission from the network node (202).

29. The apparatus according to any of claims 16-28, wherein the network node (202) is communicating over a plurality of antennas using an analogue beam forming, wherein the plurality of antennas using the analogue beam forming are associated with respective wide beams (WB1 -WBn) and narrow beams, a plurality of wide beams (WB1-WBn) covering respective areas, whereby for each wide beam (WB2) at least one narrow beam (NB) forms a joint area with a wide beam (WB2).

30. A network node (202) comprising the apparatus of any of the claims 16 through 29.31 . A User Equipment, UE (204) for communicating uplink and downlink data with a network node (202) in a time division duplex, TDD, scheme, the TDD scheme comprising a plurality of transmission slots (901 -910) for communicating the uplink and downlink data with the network node (202), the UE (204) comprising a controlling circuitry (1206) configured to cause:- decoding of a Physical Downlink Control Channel, PDCCH, received from the network node (202), wherein- for the case uplink Downlink Control Information, DCI, is decoded from the PDCCH, performing of an uplink data transmission with the network node (202) in a Physical Uplink Scheduling Channel, PUSCH, in a subsequent uplink slot (905); and- for the case a Scheduling Request Physical Uplink Control Channel, SR-PUCCH, reset information is decoded from the PDCCH, transmission of a Buffer Status Report, BSR, and optionally padding bits to the network node in the PUSCH, in a subsequent uplink slot (905) and resetting a SR timer corresponding to a maximum number of SR transmissions configured for the UE (204).

32. 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 15 when the computer program is run by the data processing unit.

Images