WO2020088761A1

WO2020088761A1 - Client device and network access node for re-scheduling uplink transmissions

Info

Publication number: WO2020088761A1
Application number: PCT/EP2018/079883
Authority: WO
Inventors: Bengt Lindoff; Thorsten Schier; Gustaf Claeson; Wenquan HU; Panayiotis Papadimitriou
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2018-10-31
Filing date: 2018-10-31
Publication date: 2020-05-07

Abstract

The invention relates to relates to re-scheduling of uplink data transmissions. A client device (100) is connected to a network access node (300) and scheduled to perform an uplink data transmission (510) according to a first scheduling information (502). The client device (100) obtains second scheduling information (504) from network access node (300) indicating rescheduling information for the uplink data transmission (510). Based on the obtained second scheduling information (504), the client device (100) perform the uplink data transmission (510) according to the first scheduling information (502) and the second scheduling information (504). Furthermore, the invention also relates to corresponding methods and a computer program.

Description

CLIENT DEVICE AND NETWORK ACCESS NODE FOR RE-SCHEDULING UPLINK TRANSMISSIONS

Technical Field

The invention relates to a client device and a network access node for re-scheduling uplink transmissions. Furthermore, the invention also relates to corresponding methods and a computer program.

Background

A critical requirement of 5G, also known as new radio (NR), is support for ultra-low latency services, such as ultra reliable and low latency communication (URLLC) services. The requirement, one way over the radio access network, for URLLC services has been set to a latency of 1 ms combined with a packet error rate (PER) of 10e-5. The latency expresses the time required for transmitting a data packet through the network.

URLLC traffic thus requires higher reliability and lower latency than enhanced mobile broadband (eMBB) traffic. Hence, when URLLC traffic is multiplexed with eMBB traffic, the URLLC traffic needs to be treated differently from the eMBB traffic, otherwise, the reliability of URLLC traffic will be the same as the eMBB traffic. This affects all network layers, including the physical layer of the system.

The stringent requirements of URLLC on latency and reliability allow only for a very scarce utilization of available time and frequency resources. Once the UE has time critical URLLC data to send, it is crucial that the transmission can be scheduled and sent out as soon as possible. With non-deterministic and sporadic URLLC traffic an actual transmission does not happen frequently, but when it occurs it must be sent out quickly and reliably. This need for an immediate transmission opportunity restricts the number of active URLLC UEs that can be served at the same time. As a consequence, a big portion of the available time and frequency resources cannot be utilized for URLLC, since it always must be guaranteed that there are resources for Physical Downlink Control Channel (PDCCH) and Physical Downlink/Uplink Shared Channel (PDSCH/PUSCH) transmission. For a better resource utilization, 3GPP has therefore studied how NR can support services with different requirements to be multiplexed on shared resources. The idea is that the services with relaxed demands, such as eMBB, can be scheduled on the same resources as potential URLLC transmissions but would be de- prioritized when an URLLC transmission actually is going to be performed. In 3GPP Release 15 this issue has been addressed in downlink with the introduction of DL pre-emption. It is allowed that the gNB can pre-empt an ongoing DL transmission (e.g. of eMBB type) to send other data with higher priority (e.g. of URLLC type) to either the same or to a different UE. After the transmission of the higher priority data has been finished, the gNB can resume its earlier operation. When the eMBB transmission gets pre-empted, it is obvious that its decoding performance will be impacted. At least for the case of inter-UE multiplexing the eMBB UE does not even know that its transmission got pre-empted and that the gNB has replaced the data in some of its Physical Resource Blocks (PRBs) with data that is intended to another UE. In Release 15, downlink pre-emption indication (DL PI) has therefore been introduced. This DL PI is sent after the pre-emption and shall help the UE when decoding the corrupted eMBB transmission. How the DL PI is used to facilitate the decoding is up to UE implementation and not further defined in the specification.

Summary

An objective of embodiments of the invention is to provide a solution which mitigates or solves the drawbacks and problems of conventional solutions.

Another objective of embodiments of the invention is to provide improved uplink data transmission compared to conventional solutions.

The above and further objectives are solved by the subject matter of the independent claims. Further advantageous embodiments of the invention can be found in the dependent claims.

According to a first aspect of the invention, the above mentioned and other objectives are achieved with a client device for a wireless communication system, the client device being configured to

obtain first scheduling information for an uplink data transmission;

obtain second scheduling information for the uplink data transmission after having obtained the first scheduling information, wherein the second scheduling information indicates rescheduling information for the uplink data transmission; and

perform the uplink data transmission according to the first scheduling information and the second scheduling information.

To obtain first scheduling information and the second scheduling information can herein mean that the client device is configured to receive mentioned first and the second scheduling information, e.g. in signaling from a network access node. An advantage of the client device according to the first aspect is that the uplink data transmission can be rescheduled when uplink data packets need to be rescheduled in order to free radio resources for data packets associated with higher priority services. Thereby, improved radio spectrum utilization is achieved.

In an implementation form of a client device according to the first aspect, the first scheduling information is an uplink grant for the uplink data transmission.

An advantage with this implementation form is that the first scheduling information is sent using a well defined format and thereby spectrum efficient signalling over the radio interface is achieved.

In an implementation form of a client device according to the first aspect, the second scheduling information is associated with the uplink grant.

An advantage with this implementation form is that the client device will know which first scheduling information the second scheduling information is associated with and thereby also know how to reschedule the uplink data transmission. Thereby, spectral efficient rescheduling signalling is achieved.

In an implementation form of a client device according to the first aspect, the client device is further configured to

receive the first scheduling information in a radio resource control configuration message or a medium access control, MAC, control element.

An advantage with this implementation form is that the first scheduling information can be signaled according to semi persistent scheduling and thereby spectral efficient rescheduling of uplink data transmission is also achieved.

monitor for the second scheduling information upon reception of the first scheduling information.

An advantage with this implementation form is that the client device only needs to start monitoring for the second scheduling information when it has been allocated resources for the uplink data transmission. Hence, the monitoring will be much more power efficient (i.e. saving power in the client device) compared to e.g. the case when the client device continuously monitors for the second scheduling information.

In an implementation form of a client device according to the first aspect, the first scheduling information comprises a first set of information fields and the second scheduling information comprises a second set of information fields, and wherein the first set of information fields has more information fields than the second set of information fields.

An advantage with this implementation form is that only few information fields need to be signalled to the client device for rescheduling, hence giving room for more coding and thereby higher reliability of the second scheduling information.

In an implementation form of a client device according to the first aspect, the second set of information fields comprises a subset of the first set of information fields.

An advantage with this implementation form is that only few information fields need to be signalled to the client device for rescheduling, hence giving room for more coding and thereby higher reliability to the second scheduling information.

In an implementation form of a client device according to the first aspect, the second set of information fields comprises at least one additional information field not comprised in the first set of information fields.

An advantage with this implementation form is that the extra information field added in second scheduling information does not need to be sent in the first scheduling information (only related to the re-scheduling) and thereby the overall number of information fields bits sent for scheduling and rescheduling uplink data transmission is reduced. Thereby, lower payload and improved spectral efficiency is achieved.

In an implementation form of a client device according to the first aspect, the second set of information fields replaces the corresponding subset of the first set of information fields associated with the uplink data transmission.

An advantage with this implementation form is that only few information fields need to be signalled to the client device for rescheduling, hence giving room for more coding and thereby higher reliability of the second scheduling information. In an implementation form of a client device according to the first aspect, the second set of information fields indicates at least one of a time resource re-assignment and a frequency resource re-assignment for the uplink transmission.

An advantage with this implementation form is that by moving the uplink data transmission in time and/or frequency, e.g. for higher priority uplink data transmissions, improved spectrum utilization can be achieved in the wireless communication system. The higher priority uplink data transmissions can be generated by the client device itself or by other client devices in the wireless communication system.

In an implementation form of a client device according to the first aspect, at least one of the time resource re-assignment and the frequency resource re-assignment is indicated with a single bit.

An advantage with this implementation form is that signalling of the time resource re- assignment and the frequency resource re-assignment is compact and hence more coding can be applied to the second scheduling information thereby improving the reliability of the signalling.

In an implementation form of a client device according to the first aspect, the second set of information fields indicates at least one of a bandwidth part, a modulation and coding scheme, an identification of an uplink transmission to be rescheduled, and a part of an uplink transmission to be rescheduled.

An advantage with this implementation form is that in case the uplink data transmission is rescheduled, which enables possibilities to rearrange the rescheduled uplink data transmission. Thereby, optimized uplink data transmissions is achieved in the wireless communication system.

In an implementation form of a client device according to the first aspect, the uplink data transmission is associated with an enhanced mobile broadband service.

An advantage with this implementation form is that this gives possibilities to reschedule low priority traffic in case uplink traffic of higher priority needs to be transmitted over the air interface. Thereby, improved spectrum utilization is achieved in the wireless communication system. According to a second aspect of the invention, the above mentioned and other objectives are achieved with a network access node for a wireless communication system, the network access node being configured to

provide first scheduling information for an uplink data transmission to a client device; generate second scheduling information indicating rescheduling information for the uplink data transmission upon determine to reschedule the uplink data transmission;

provide the second scheduling information to the client device.

To provide the first scheduling information and the second scheduling information can herein mean that the network access node is configured to signal mentioned first and the second scheduling information to the client device.

An advantage of the network access node according to the second aspect is that the uplink data transmission can be rescheduled when uplink data packets need to be rescheduled in order to free radio resources for data packets associated with higher priority services. Thereby, improved radio spectrum utilization is achieved.

In an implementation form of a network access node according to the second aspect, the network access node is further configured to

obtain the uplink data transmission from the client device according to the first scheduling information and the second scheduling information.

To obtain the uplink data transmission from the client device can herein mean that the network access node is configured to receive uplink data transmission from the client device.

In an implementation form of a network access node according to the second aspect, determine to reschedule the uplink data transmission comprises

determine to reschedule the uplink data transmission based on a first service type associated with the uplink data transmission and a second service type associated with another uplink transmission served by the network access node.

An advantage with this implementation form is that the network access node can schedule uplink data traffic depending on the service type of the traffic. Thereby, improved use of radio resource in the wireless communication system is possible. In an implementation form of a network access node according to the second aspect, the first service type is enhanced mobile broadband and the second service type is ultra reliable and low latency communication.

In an implementation form of a network access node according to the second aspect, the second scheduling information is a group common rescheduling information for a plurality of client devices or a rescheduling information dedicated for a single client device.

An advantage with this implementation form is that the rescheduling can be applied not only to dedicated client devices, but also to a group of client devices, and hence spectrum efficient rescheduling signalling can be achieved also in case several client devices need to be rescheduled.

In an implementation form of a network access node according to the second aspect, the first scheduling information is an uplink grant for the uplink data transmission.

transmit the first scheduling information in a radio resource control configuration message or a medium access control, MAC, control element.

In an implementation form of a network access node according to the second aspect, the first scheduling information comprises a first set of information fields and the second scheduling information comprises a second set of information fields, and wherein the first set of information fields has more information fields than the second set of information fields.

An advantage with this implementation form is that only few information fields need to be signalled to the client device for rescheduling, hence giving room for more coding and thereby higher reliability of the second scheduling information. In an implementation form of a network access node according to the second aspect, the second set of information fields comprises a subset of the first set of information fields.

In an implementation form of a network access node according to the second aspect, the second set of information fields comprises at least one additional information field not comprised in the first set of information fields.

In an implementation form of a network access node according to the second aspect, the second set of information fields indicates at least one of a time resource re-assignment and a frequency resource re-assignment for the uplink transmission.

In an implementation form of a network access node according to the second aspect, at least one of the time resource re-assignment and the frequency resource re-assignment is indicated with a single bit.

An advantage with this implementation form is that signalling of the time resource re- assignment and the frequency resource re-assignment is compact and hence more coding can be applied to the second scheduling information thereby improving the reliability of the signalling. In an implementation form of a network access node according to the second aspect, the second set of information fields indicates at least one of a bandwidth part, a modulation and coding scheme, an identification of an uplink transmission to be rescheduled, and a part of an uplink transmission to be rescheduled.

According to a third aspect of the invention, the above mentioned and other objectives are achieved with a method for a client device, the method comprises

obtaining first scheduling information for an uplink data transmission;

obtaining second scheduling information for the uplink data transmission after having obtained the first scheduling information, wherein the second scheduling information indicates rescheduling information for the uplink data transmission; and

performing the uplink data transmission according to the first scheduling information and the second scheduling information.

The method according to the third aspect can be extended into implementation forms corresponding to the implementation forms of the client device according to the first aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the client device.

The advantages of the methods according to the third aspect are the same as those for the corresponding implementation forms of the client device according to the first aspect.

According to a fourth aspect of the invention, the above mentioned and other objectives are achieved with a method for a network access node, the method comprises

providing first scheduling information for an uplink data transmission to a client device; generating second scheduling information indicating rescheduling information for the uplink data transmission upon determine to reschedule the uplink data transmission;

providing the second scheduling information to the client device.

The method according to the fourth aspect can be extended into implementation forms corresponding to the implementation forms of the network access node according to the second aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the network access node.

The advantages of the methods according to the fourth aspect are the same as those for the corresponding implementation forms of the network access node according to the second aspect.

The invention also relates to a computer program, characterized in program code, which when run by at least one processor causes said at least one processor to execute any method according to embodiments of the invention. Further, the invention also relates to a computer program product comprising a computer readable medium and said mentioned computer program, wherein said computer program is included in the computer readable medium, and comprises of one or more from the group: ROM (Read-Only Memory), PROM (Programmable ROM), EPROM (Erasable PROM), Flash memory, EEPROM (Electrically EPROM) and hard disk drive.

Further applications and advantages of the embodiments of the invention will be apparent from the following detailed description.

Brief Description of the Drawings

The appended drawings are intended to clarify and explain different embodiments of the invention, in which:

- Fig. 1 shows a client device according to an embodiment of the invention;

- Fig. 2 shows a method for a client device according to an embodiment of the invention;

- Fig. 3 shows a network access node according to an embodiment of the invention;

- Fig. 4 shows a method for a network access node according to an embodiment of the invention;

- Fig. 5 shows a wireless communication system according to an embodiment of the invention;

- Fig. 6 shows a flow chart of a method for a client device according to an embodiment of the invention; and

- Fig. 7 shows a flow chart of a method for a network access node according to an embodiment of the invention.

Detailed Description

It has also been discussed to introduce a similar mechanism for UL pre-emption indication as for the DL pre-emption in Release 15. But 3GPP could not agree on the feasibility of such a mechanism for UL. For Release 16 it has been decided that the need and the feasibility for UL pre-emption will be studied. As opposed to the pre-emption indication in DL which is aimed to support the eMBB UE, the pre-emption indication in UL is intended to enable URLLC transmission in the first place. The inventors have realized that in the DL, it is easier since the gNB has full control and can stop transmitting to a first UE1 (eMBB) and decide to serve a second UE2 (URLLC) instead. The only performance hit is on the eMBB-UE, which is tolerable. The URLLC performance of the second UE2 is not impacted. In UL, it is much more complicated. There, the gNB must ensure that the URLLC transmission of the second UE2 can get scheduled quickly and also that its reception is not interfered by any other UE. Thus, in UL the UL PI must instruct the eMBB-UE to stop its transmission for some time so that the URLLC-UE2 transmission can be received safely. That also means that in contrary to the DL PI which can come after the URLLC data has been sent, in UL, the pre-emption indication has to come before the URLLC data is going to be sent. It has been noted that for the UL PI approach, one need first to cancel an already scheduled eMBB transmission and then to re- schedule the cancelled transmission. The load on the PDCCH would then be quite large, i.e. one PDCCH for cancelling and another PDCCH for re-scheduling. Therefore, there is a need for methods and devices solving the above mentioned drawbacks and shortcomings of conventional approaches.

Fig. 1 shows a client device 100 according to an embodiment of the invention. In the embodiment shown in Fig. 1 , the client device 100 comprises a processor 102, a transceiver 104 and a memory 106. The processor 102 is coupled to the transceiver 104 and the memory 106 by communication means 108 known in the art. The client device 100 further comprises an antenna or antenna array 1 10 coupled to the transceiver 104, which means that the client device 100 is configured for wireless communications in a wireless communication system. That the client device 100 is configured to perform certain actions or functions can in this disclosure be understood to mean that the client device 100 comprises suitable means, such as e.g. the processor 102 and the transceiver 104, configured to perform said actions or functions.

According to embodiments of the invention, the client device 100 is configured to obtain first scheduling information 502 for an uplink data transmission 510. The client device 100 is further configured to obtain second scheduling information 504 for the uplink data transmission 510 after having obtained the first scheduling information 502. The second scheduling information 504 indicates rescheduling information for the uplink data transmission 510. Furthermore, the client device 100 is configured to perform the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504. Fig. 2 shows a flow chart of a corresponding method 200 which may be executed in a client device 100, such as the one shown in Fig. 1 . The method 200 comprises obtaining 202 first scheduling information 502 for an uplink data transmission 510. The method 200 further comprises obtaining 204 second scheduling information 504 for the uplink data transmission 510 after having obtained the first scheduling information 502. The second scheduling information 504 indicates rescheduling information for the uplink data transmission 510. Furthermore, the method 200 comprises performing 206 the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504.

Fig. 3 shows a network access node 300 according to an embodiment of the invention. In the embodiment shown in Fig. 3, the network access node 300 comprises a processor 302, a transceiver 304 and a memory 306. The processor 302 is coupled to the transceiver 304 and the memory 306 by communication means 308 known in the art. The network access node 300 may be configured for both wireless and wired communications in wireless and wired communication systems, respectively. The wireless communication capability is provided with an antenna or antenna array 310 coupled to the transceiver 304, while the wired communication capability is provided with a wired communication interface 312 coupled to the transceiver 304. That the network access node 300 is configured to perform certain actions can in this disclosure be understood to mean that the network access node 300 comprises suitable means, such as e.g. the processor 302 and the transceiver 304, configured to perform said actions.

According to embodiments of the invention, the network access node 300 is configured to provide first scheduling information 502 for an uplink data transmission 510 to a client device 100. The network access node 300 is further configured to generate second scheduling information 504 indicating rescheduling information for the uplink data transmission 510 upon determine to reschedule the uplink data transmission 510. Furthermore, the network access node 300 is configured to provide the second scheduling information 504 to the client device 100.

Fig. 4 shows a flow chart of a corresponding method 400 which may be executed in a network access node 300, such as the one shown in Fig. 3. The method 400 comprises providing 402 first scheduling information 502 for an uplink data transmission 510 to a client device 100. The method 400 further comprises generating 404 second scheduling information 504 indicating rescheduling information for the uplink data transmission 510 upon determine to reschedule the uplink data transmission 510. Furthermore, the method 400 comprises providing 406 the second scheduling information 504 to the client device 100.

Fig. 5 shows a wireless communication system 500 according to an implementation. The wireless communication system 500 comprises a client device 100 and a network access node 300 configured to operate in the wireless communication system 500. For simplicity, the wireless communication system 500 shown in Fig. 5 only comprises one client device 100 and one network access node 300. However, the wireless communication system 500 may comprise any number of client devices 100 and any number of network access nodes 300 without deviating from the scope of the invention.

In the wireless communication system 500, the network access node 300 is connected to the client device 100. The client device 100 may e.g. be configured for an eMBB service. The network access node 300 provides/transmits first scheduling information 502 for an uplink data transmission 510 associated with the eMBB service to the client device 100, as shown in Fig. 5. If the network access node 300 determines that the uplink data transmission 510 should be rescheduled, e.g. based on another uplink data transmission with higher priority, the network access node 300 provides a second scheduling information 504 indicating rescheduling information for the uplink data transmission 510 to the client device 100, as shown in Fig. 5. The other uplink data transmission may e.g. be associated with a service having more stringent latency requirements, such as URLLC service. Based on the obtained/received second scheduling information 504, the client device 100 performs the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504 according to embodiments of the invention.

Fig. 6 shows a flow chart of a method 600 according to an embodiment of the invention which is executed in a client device 100, when the client device 100 is connected to the network access node 300.

In step 602, the client device 100 obtains first scheduling information 502 for an uplink data transmission 510. The uplink data transmission 510 may in embodiments be associated with an eMBB service as previously mentioned. The client device 100 may obtain the first scheduling information 502 from the network access node 300, i.e. receive the first scheduling information 502 in a transmission from the network access node 300. In this case, the client device 100 may receive the first scheduling information 502 in a radio resource control (RRC) configuration message or a medium access control (MAC) control element (CE) which implies semipersistent scheduling of uplink resources. However, the client device 100 may in embodiments instead obtain the first scheduling message by the use of other suitable signaling.

According to embodiments of the invention, the first scheduling information 502 is an uplink grant for the uplink data transmission 510. The uplink grant may indicate how the uplink data transmission 510 should be coded and transmitted. For example, the uplink grant may comprise information about time, frequency, modulation and coding scheme etc. for the uplink data transmission 510 according to the information fields in downlink control information (DCI) that may be of the DCI format 0_1 , but other DCI formats can also be applicable such as DCI format 0_0 for instance. The uplink grant can be obtained in response to a scheduling request transmitted by the client device 100 to the network access node 300.

Upon obtaining the first scheduling information 502 in step 602, the client device 100 starts to monitor in step 604 for second scheduling information 504 indicating rescheduling information for the uplink data transmission 510. When the first scheduling information 502 is an uplink grant for the uplink data transmission 510, the second scheduling information 504 is associated with the uplink grant. Monitoring can herein mean that the client device 100 monitors a configured Control Resource Set (CORSET) for a DCI corresponding to the second scheduling information.

In step 606, the client device determines if second scheduling information 504 has been obtained or not. If the outcome of the determination in step 606 is“NO”, i.e. the client device 100 has not obtained any second scheduling information 504, then the client device 100 continues to monitor for second scheduling information 504 in step 604 and further performs the uplink data transmission 510 according to the first scheduling information 502. The client device 100 may continue to monitor for second scheduling information 504 until the uplink data transmission 510 is completed/finalised.

On the other hand, if the outcome of the determination in step 606 is“YES”, i.e. the client device 100 has obtained second scheduling information 504, then the client device 100 moves to step 608. In step 608 the client device 100 re-schedules the uplink data transmission 510 based on the second scheduling information 504 and performs the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504. The client device 100 may e.g. fully cancel/discard the current uplink data transmission 510 according to the first scheduling information 502 and instead transmit the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504. In embodiments of the invention, only a subset of the uplink data transmission 510, e.g. one or more code block groups, transport blocks, resource blocks, OFDM symbols, or slots/subframes, is cancelled and rescheduled, while the rest of the uplink data transmission 510 remains unchanged.

According to embodiments of the invention, the first scheduling information 502 may comprise a first set of information fields and the second scheduling information 504 may comprise a second set of information fields. The first set of information fields can have more information fields than the second set of information fields. The second scheduling information 504 is used to reschedule the uplink data transmission 510, e.g. re-schedule the uplink data transmission 510 a short time instance later. Since it is the same data that should be transmitted but at a different time instance some of the information/parameters from the first scheduling information 502 can be re-used by the client device 100, e.g. transmission related information/parameters such as e.g. redundancy version, HARQ process number, etc. Hence, this information does not need to be comprised in the second scheduling information 504 and the second set of information fields may therefore have fewer information fields than the first set of information fields. Fewer information bits are therefore required in the second scheduling information 504, allowing the second scheduling information 504 to be transmitted with higher reliability as more coding can be applied and/or with lower payload.

Therefore, in embodiments of the invention, the second set of information fields comprises a subset of the first set of information fields. The second set of information fields may e.g. indicate at least one of a time resource re-assignment, a frequency resource re-assignment for the uplink transmission 510, a bandwidth part, and a modulation and coding scheme (MCS). When the second set of information fields indicates at least one of the time resource re- assignment and the frequency resource re-assignment, at least one of the time resource re- assignment and the frequency resource re-assignment may be indicated with a single bit. Re- assignment of time resources and/or frequency resource can herein mean that resources for uplink data transmissions are moved in time and/or frequency. Such move can be predefined and/or signaled. For example, a single bit could indicate a move of 4 slots and/or 12 subcarriers. Signaling with more bits can indicate more options. In another example the exact move in time and/frequency can be signaled, e.g. using Radio Resource Control (RRC) or MAC CE signaling. In this respect a parameter T can indicate the move in time (e.g. in number of slots or subframes) and a parameter F can indicate the move in frequency (e.g. in number of subcarriers).

When second set of information fields comprises a subset of the first set of information fields, the second set of information fields may replace the corresponding subset of the first set of information fields associated with the uplink data transmission 510. In other words, when the client device 100 obtains the second scheduling information 504 where the second set of information fields comprising a subset of the first set of information fields, the client device 100 may reschedule the uplink transmission 510 by replacing the corresponding subset of the first set of information fields received in the first scheduling information 502 with the second set of information fields received in the second scheduling information 504. For example, replacing the time resource re-assignment and/or the frequency resource re-assignment for the uplink transmission 510 from the first scheduling information 502 with the time resource re- assignment and/or the frequency resource re-assignment for the uplink transmission 510 from the second scheduling information 504.

Furthermore, the second set of information fields may comprise at least one additional information field not comprised in the first set of information fields. The additional information field in the second set of information fields may e.g. indicate at least one of an identification of an uplink data transmission to be rescheduled and a part of an uplink data transmission to be rescheduled. The identification of the uplink transmission to be rescheduled may be used to indicate which uplink data transmission the client device 100 should reschedule. For example, the client device 100 may have been given more than one uplink grant and hence have to identify which uplink data transmission to reschedule according to the second scheduling information 504. The part of the uplink transmission to be rescheduled may be used to indicate that the client device 100 should only reschedule a part of the uplink data transmission 510. For example, when the uplink data transmission 510 comprises a set of slots and only one slot in the set of slots is to be rescheduled to another later slot.

In embodiments of the invention, the second set of information fields may hence comprise a subset of the first set of information fields plus one or more additional information fields not comprised in the first set of information fields. Although one or more additional information fields are comprised in the second set of information fields, the second set of information fields comprises fewer information fields than the first set of information fields. Hence, the number of information fields from the first set of information fields not comprised in the second set of information fields is larger than the number of additional information fields comprised in the second set of information fields.

In embodiments of the invention, the second scheduling information 504 is associated with a further uplink transmission on PUSCH. According to this embodiment, the client device upon receiving second scheduling information comprising a pointer to a future coming uplink data transmission and said pointer together with information fields including time and/or frequency resources on where to re-schedule the future uplink data transmission, the coming uplink data transmission is rescheduled accordingly.

Fig. 7 shows a flow chart of a method 700 according to an embodiment of the invention which is executed in a network access node 300. The network access node 300 is connected to the client device 100 and act as a serving network access node.

In step 702, the network access node 300 provides first scheduling information 502 for an uplink data transmission 510 to the client device 100. The network access node 300 can provide the first scheduling information 502 by transmitting the first scheduling information 502 to the client device 100 in a RRC configuration message 506, a MAC CE 508, or any other suitable signaling format.

As described above with reference to method 600, the first scheduling information 502 may be an uplink grant for the uplink data transmission 510, where the uplink grant may indicate how the uplink data transmission 510 should be coded and transmitted by the client device 100. The uplink grant may e.g. comprise information about time, frequency, modulation and coding scheme etc. for the uplink data transmission 510 according to information fields in DCI format 0_1 or DCI format 0_0.

In step 704, the network access node 300 determines to reschedule the uplink data transmission 510. The network access node 300 may determine to reschedule the uplink data transmission 510 based on a first service type associated with the uplink data transmission 510 and a second service type associated with another uplink data transmission served by the network access node 300. The other uplink transmission served by the network access node 300 may be associated with the client device 100 or another client device. In embodiments, the first service type may have a lower priority than the second service type. The first service type is in an example eMBB and the second service type is URLLC. When the first service type has a lower priority than the second service type, the network access node 300 may hence determine to reschedule the uplink data transmission 510 based on that the other uplink transmission is associated with a higher priority service than the uplink data transmission 510. For example, the network access node 100 may determine that uplink resource allocated to the uplink data transmission 510 are needed for the other uplink data transmission associated with the higher priority service. Upon determining that the uplink resources are needed for the other uplink data transmission, the network access node 300 may determine to reschedule the uplink data transmission 510 such that the uplink resource can be freed up and used for the other uplink data transmission. Therefore, according to embodiments of the invention, the second service type has higher priority than the first service type.

Upon determining to reschedule the uplink data transmission 510 in step 704, the network access node 300 generates second scheduling information 504 indicating rescheduling information for the uplink data transmission 510 in step 706. The second scheduling information 504 may comprise a second set of information fields comprising a subset of the first set of information fields, as well as addition information fields, as previously described with respect to the Fig. 6.

Furthermore, the second scheduling information 504 may be a group common rescheduling information for a plurality of client devices or a rescheduling information dedicated for a single client device. In the first case, the plurality of client devices may have received their own respective uplink grant and the second scheduling information 504 may e.g. comprise a time resources assignment where all current uplink grants are cancelled and moved a certain time interval forward in time. All other information associated with the respective uplink grants may remain the same. In the latter case, the second scheduling information 504 may e.g. be dedicated for the client device 100 which performs rescheduling based on the received the second scheduling information 504, as described with reference to step 608 in Fig. 6.

In step 708, the network access node 300 provides/transmits the second scheduling information 504 indicating rescheduling information for the uplink data transmission 510 to the client device 100. The client device 100 hence obtains/receives the second scheduling information 504 and performs the uplink data transmission 510 according to the first scheduling information 502 and the second scheduling information 504, as previously described with reference to method 600. Hence, in response to the providing of the second scheduling information 504 to the client device 100, the network access node 300 obtains the uplink data transmission 510 from the client device 100 according to the first scheduling information 502 and the second scheduling information 504.

The client device 100 herein, may be denoted as a user device, a User Equipment (UE), a mobile station, an internet of things (loT) device, a sensor device, a wireless terminal and/or a mobile terminal, is enabled to communicate wirelessly in a wireless communication system, sometimes also referred to as a cellular radio system. The UEs may further be referred to as mobile telephones, cellular telephones, computer tablets or laptops with wireless capability. The UEs in this context may be, for example, portable, pocket-storable, hand-held, computer- comprised, or vehicle-mounted mobile devices, enabled to communicate voice and/or data, via the radio access network, with another entity, such as another receiver or a server. The UE can be a Station (STA), which is any device that contains an IEEE 802.1 1 -conformant Media Access Control (MAC) and Physical Layer (PHY) interface to the Wireless Medium (WM). The UE may also be configured for communication in 3GPP related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth generation wireless technologies, such as New Radio.

The network access node 300 herein may also be denoted as a radio network access node, an access network access node, an access point, or a base station, e.g. a Radio Base Station (RBS), which in some networks may be referred to as transmitter,“gNB”,“gNodeB”,“eNB”, “eNodeB”,“NodeB” or“B node”, depending on the technology and terminology used. The radio network access nodes may be of different classes such as e.g. macro eNodeB, home eNodeB or pico base station, based on transmission power and thereby also cell size. The radio network access node can be a Station (STA), which is any device that contains an IEEE 802.1 1 -conformant Media Access Control (MAC) and Physical Layer (PHY) interface to the Wireless Medium (WM). The radio network access node may also be a base station corresponding to the fifth generation (5G) wireless systems.

Furthermore, any method according to embodiments of the invention may be implemented in a computer program, having code means, which when run by processing means causes the processing means to execute the steps of the method. The computer program is included in a computer readable medium of a computer program product. The computer readable medium may comprise essentially any memory, such as a ROM (Read-Only Memory), a PROM (Programmable Read-Only Memory), an EPROM (Erasable PROM), a Flash memory, an EEPROM (Electrically Erasable PROM), or a hard disk drive.

Moreover, it is realized by the skilled person that embodiments of the client device 100 and the network access node 300 comprises the necessary communication capabilities in the form of e.g., functions, means, units, elements, etc., for performing the solution. Examples of other such means, units, elements and functions are: processors, memory, buffers, control logic, encoders, decoders, rate matchers, de-rate matchers, mapping units, multipliers, decision units, selecting units, switches, interleavers, de-interleavers, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, MSDs, TCM encoder, TCM decoder, power supply units, power feeders, communication interfaces, communication protocols, etc. which are suitably arranged togetherfor performing the solution.

Especially, the processor(s) of the client device 100 and the network access node 300 may comprise, e.g., one or more instances of a Central Processing Unit (CPU), a processing unit, a processing circuit, a processor, an Application Specific Integrated Circuit (ASIC), a microprocessor, or other processing logic that may interpret and execute instructions. The expression“processor” may thus represent a processing circuitry comprising a plurality of processing circuits, such as, e.g., any, some or all of the ones mentioned above. The processing circuitry may further perform data processing functions for inputting, outputting, and processing of data comprising data buffering and device control functions, such as call processing control, user interface control, or the like.

Finally, it should be understood that the invention is not limited to the embodiments described above, but also relates to and incorporates all embodiments within the scope of the appended independent claims.

Claims

1 . A client device (100) for a wireless communication system (500), the client device (100) being configured to

obtain first scheduling information (502) for an uplink data transmission (510);

obtain second scheduling information (504) for the uplink data transmission (510) after having obtained the first scheduling information (502), wherein the second scheduling information (504) indicates rescheduling information for the uplink data transmission (510); and perform the uplink data transmission (510) according to the first scheduling information (502) and the second scheduling information (504).

2. The client device (100) according to claim 1 , wherein the first scheduling information (502) is an uplink grant for the uplink data transmission (510).

3. The client device (100) according to claim 2, wherein the second scheduling information (504) is associated with the uplink grant.

4. The client device (100) according to any of the preceding claims, configured to

receive the first scheduling information (502) in a radio resource control configuration message or a medium access control, MAC, control element.

5. The client device (100) according to any of the preceding claims, configured to

monitorfor the second scheduling information (504) upon reception of the first scheduling information (502).

6. The client device (100) according to any of the preceding claims, wherein the first scheduling information (502) comprises a first set of information fields and the second scheduling information (504) comprises a second set of information fields, and wherein the first set of information fields has more information fields than the second set of information fields.

7. The client device (100) according to claim 6, wherein the second set of information fields comprises a subset of the first set of information fields.

8. The client device (100) according to claim 7, wherein the second set of information fields comprises at least one additional information field not comprised in the first set of information fields.

9. The client device (100) according to claim 7 or 8, wherein the second set of information fields replaces the corresponding subset of the first set of information fields associated with the uplink data transmission (510).

10. The client device (100) according to any of claims 6 to 9, wherein the second set of information fields indicates at least one of a time resource re-assignment and a frequency resource re-assignment for the uplink transmission (510).

1 1 . The client device (100) according to claim 10, wherein at least one of the time resource re- assignment and the frequency resource re-assignment is indicated with a single bit.

12. The client device (100) according to any of claims 6 to 1 1 , wherein the second set of information fields indicates at least one of a bandwidth part, a modulation and coding scheme, an identification of an uplink transmission to be rescheduled, and a part of an uplink transmission to be rescheduled.

13. The client device (100) according to any of the preceding claims, wherein the uplink data transmission (510) is associated with an enhanced mobile broadband service.

14. A network access node (300) for a wireless communication system (500), the network access node (300) being configured to

provide first scheduling information (502) for an uplink data transmission (510) to a client device (100);

generate second scheduling information (504) indicating rescheduling information for the uplink data transmission (510) upon determine to reschedule the uplink data transmission (510);

provide the second scheduling information (504) to the client device (100).

15. The network access node (300) according to claim 14, configured to

obtain the uplink data transmission (510) from the client device (100) according to the first scheduling information (502) and the second scheduling information (504).

16. The network access node (300) according to claim 14 or 15, wherein determine to reschedule the uplink data transmission (510) comprises

determine to reschedule the uplink data transmission (510) based on a first service type associated with the uplink data transmission (510) and a second service type associated with another uplink transmission served by the network access node (300).

17. The network access node (300) according to any of claims 14 to 16, wherein the second scheduling information (504) is a group common rescheduling information for a plurality of client devices or a rescheduling information dedicated for a single client device.

18. The network access node (300) according to any of claims 14 to 16, wherein the first scheduling information (502) is an uplink grant for the uplink data transmission (510).

19. The network access node (300) according to any of claims 14 to 18, configured to

transmit the first scheduling information (502) in a radio resource control configuration message or a medium access control, MAC, control element.

20. The network access node (300) according to any of claims 14 to 19, wherein the first scheduling information (502) comprises a first set of information fields and the second scheduling information (504) comprises a second set of information fields, and wherein the first set of information fields has more information fields than the second set of information fields.

21. The network access node (300) according to claim 20, wherein the second set of information fields comprises a subset of the first set of information fields.

22. The network access node (300) according to claim 21 , wherein the second set of information fields comprises at least one additional information field not comprised in the first set of information fields.

23. The network access node (300) according to any of claims 14 to 22, wherein the second set of information fields indicates at least one of a time resource re-assignment and a frequency resource re-assignment for the uplink transmission (510).

24. The network access node (300) according to claim 23, wherein at least one of the time resource re-assignment and the frequency resource re-assignment is indicated with a single bit.

25. The network access node (300) according to any of claims 20 to 24, wherein the second set of information fields indicates at least one of a bandwidth part, a modulation and coding scheme, an identification of an uplink transmission to be rescheduled, and a part of an uplink transmission to be rescheduled.

26. A method (200) for a client device (100), the method (200) comprising

obtaining (202) first scheduling information (502) for an uplink data transmission (510); obtaining (204) second scheduling information (504) for the uplink data transmission (510) after having obtained the first scheduling information (502), wherein the second scheduling information (504) indicates rescheduling information for the uplink data transmission (510); and

performing (206) the uplink data transmission (510) according to the first scheduling information (502) and the second scheduling information (504).

27. A method (400) for a network access node (300), the method (400) comprising

providing (402) first scheduling information (502) for an uplink data transmission (510) to a client device (100);

generating (404) second scheduling information (504) indicating rescheduling information for the uplink data transmission (510) upon determine to reschedule the uplink data transmission (510);

providing (406) the second scheduling information (504) to the client device (100).

28. A computer program with a program code for performing a method according to claim 26 or 27 when the computer program runs on a computer.