WO2018126934A1

WO2018126934A1 - METHODS AND DEVICES FOR DOWNLINK RESOURCE SHARING BETWEEN URLLC AND eMBB TRANSMISSIONS IN WIRELESS COMMUNICATION SYSTEMS

Info

Publication number: WO2018126934A1
Application number: PCT/CN2017/118428
Authority: WO
Inventors: Efstathios KATRANARAS; Guang Liu; Guillaume Vivier; Thomas WINNIECKI
Original assignee: Jrd Communication (Shenzhen) Ltd
Priority date: 2017-01-05
Filing date: 2017-12-26
Publication date: 2018-07-12
Also published as: CN110402591A; GB2558564A; CN110402591B; GB201700108D0; GB2558564B

Abstract

Sharing of downlink resources between URLLC (Ultra Reliable and Low Latency Communications) and eMBB (enhanced Mobile Broadband) transmissions is achieved by enabling puncturing of a scheduled eMBB data transmission to allow transmission of URLLC data in a pre-emption region (P1-P4) of the same resource. An allocated mini-slot (307) in a subframe within the resource is reserved for retransmission of eMBB data that has been affected by a URLLC transmission (304) is identified to a eMBB UE 102. Information concerning whether or not puncturing has occurred is also transmitted to the UE 101. The invention has particular application to New Radio (5G) mobile communication systems.

Description

Methods and devices for downlink resource sharing between URLLC and eMBB transmissions in Wireless Communication Systems

Technical Field

Embodiments of the present invention generally relate to wireless communication systems and in particular to systems where URLLC (Ultra Reliable and Low Latency Communications) transmissions are multiplexed with eMBB (enhanced Mobile Broadband) transmissions on a downlink and has particular application to the so-called NR, New Radio, (or 5G) mobile communication system.

Background

Wireless communication systems, such as the third-generation (3G) of mobile telephone standards and technology are well known. Such 3G standards and technology have been developed by the Third Generation Partnership Project (3GPP) . The 3 ^rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications. Communication systems and networks have developed towards a broadband and mobile system. The 3rd Generation Partnership Project has developed the so-called Long Term Evolution (LTE) system, namely, an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, (E-UTRAN) , for a mobile access network where a macrocell is supported by a base station known as an eNodeB or eNB (evolved NodeB) . More recently, LTE is evolving further towards the so-called 5G or NR (new radio) systems where a cell is supported by a base station known as a gNB.

In the downlink of New Radio (NR) , it has been considered that it will be possible to schedule higher priority URLLC (Ultra Reliable and Low Latency Communications) transmissions on resources used by ongoing eMBB (enhance Mobile Broadband) transmissions. For example, these two types of transmission can be multiplexed within a carrier. Further, a pre-emption mechanism (sometimes known as puncturing) has been considered whereby a certain number of symbols (say 2 out of 14) in an eMBB transmission are punctured by a URLLC transmission. It has yet to be decided on the most efficient way of sharing the resources, whether by puncturing or any other mechanism. Furthermore, the URLLC transmission affects (for example, corrupts) the eMBB transmission and so the problem of recovering affected eMBB data also needs to be addressed.

Summary

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

According to a first aspect of the present invention there is provided a method for enabling sharing of downlink resources between URLLC (Ultra Reliable and Low Latency Communications) and eMBB (enhanced Mobile Broadband) transmissions in a wireless communication system, the method comprising; at a base station, using a resource to transmit eMBB data for reception by a wireless communication device, enabling puncturing of a scheduled eMBB data transmission to allow transmission of URLLC data in a pre-emption region of the same resource, reserving an allocated region within the resource for transmission of eMBB data that has been affected by a URLLC transmission, identifying the configured allocated region to the wireless communication device, and, at the wireless communication device, receiving puncturing information.

The puncturing information may be (1) explicitly provided to the wireless communication device by the base station or (2) realised by the wireless communication device without any explicit indication from the base station or understood by the wireless communication device using a combination of (1) and (2) .

Advantageously, downlink signal requirements can be kept to a minimum. An allocated resource region may reside within an eMBB subframe (or time slot) so that if a URLLC transmission had been allowed to puncture (pre-empt) an ongoing eMBB transmission, the allocated region can be used for (re) transmission of the affected eMBB data from a previous subframe. If the wireless communication device is made aware that puncturing has occurred and knows the identity (for example, a certain number of symbols within a particular subframe) of the allocated region, then it can deduce if such allocated region will be used for (re) transmission of affected eMBB data or for transmission of new eMBB data instead. The wireless communication device may thus map URLLC transmission resource regions to eMBB (re) transmission resource regions.

The puncturing information may include at least one of the following: a puncturing indicator message which indicates whether or not puncturing has occurred; information identifying the pre-emption region (for example information, coarse or detailed, about a time-frequency resource where eMBB transmissions have been affected or indices of "URLLC allowed" regions) ; RS (Reference Signal) Information (for example, information for enabling a wireless communication device to distinguish received eMBB transmissions from URLLC transmissions) .

The puncturing information may be communicated from the base station to a wireless communication device at the end of a subframe of an eMBB transmission.

The puncturing information may be included in eMBB Downlink Control Information (DCI) transmitted from the base station to the wireless communication device. Alternatively, the wireless communication device may infer puncturing information that is useful to it by monitoring URLLC DCI. As a further alternative the wireless communication device may use received coarse information from the base station about the time-frequency resources where eMBB transmissions have been affected and identify the exact resources used by blind detection.

The method may also include, at the base station, sending to the wireless communication device an indication that a retransmission of affected eMBB data will be transmitted; and/or an indication that a retransmission of affected eMBB data will occur in a subframe (or timeslot) immediately following the pre-emption region; and/or an indicator to notify the wireless communication device of resources in a subframe (or timeslot) (for example in a current slot) which are to be used by the base station for retransmitting affected eMBB data. One or more of these additional indications may be included in the puncturing information.

In order to reduce the buffering requirements at the wireless communication device, retransmission of affected data by the base station is done as quickly as possible, preferably in a subframe (or timeslot) immediately following a subframe/timeslot containing the pre-emption region. In this embodiment, the base station sends a "skip" indicator at the beginning of the following subframe (or timeslot) for reception by a wireless communication device. Alternatively, the known RIV-type (Resource Indication Value) scheduling may be used in order to allow a higher granularity in the scheduling of one or more wireless communication devices capable of receiving eMBB transmissions.

In order to reduce scheduling complexity (for both the base station and a wireless communication device) , a slot comprising the allocated region may be pre-allocated to a multiplicity of wireless communication devices capable of receiving eMBB transmissions from the base station and which have been scheduled in the same frame. This pre-allocated slot may be used for re-transmission of eMBB data which has been affected by pre-emption of URLLC data transmissions. In such a case, a wireless communication device may be arranged to use the DCI associated with the pre-allocated slot to check for any retransmission of pre-empted data. This method also provides the possibility of tuning the density of such pre-allocated slots based on URLLC traffic density.

In some embodiments, the method may include, in the base station, making a decision as to whether or not to retransmit affected eMBB data and if so, which mini-slot (amini-slot comprising a number of symbols of a subframe for example) , mini-slot group, code block, code block-group or transport block, for example, to retransmit. The method may also include, in the base station, making a decision as to how to retransmit affected eMBB data; for example the transmission format (e.g. redundancy version) to use. In some embodiments, the method may also include "flushing out" the affected (e.g. corrupted) data at the wireless communication device. In other embodiments, the method may include, at the base station, rescheduling affected eMBB data in one or more upcoming subframes (or time slots) either on the assumption that the wireless communication device cannot recover the data without additional retransmission or has been informed as such by feedback from the wireless communication device itself.

Considering that it is possible for a current eMBB subframe/timeslot to include a guard period or uplink symbols following the last downlink symbol as well as for the following eMBB subframe/timeslot to include downlink control symbols at its start, it can be beneficial in terms of minimising and achieving latency constraints for URLLC transmissions, to specifically reserve resources for URLLC data at the end and/or start of a subrame/timeslot.

In one embodiment, the wireless communication system is a 5G/NR system, the base station is a gNB, and the wireless communication device is a User Equipment.

According to a second aspect of the invention there is provided a base station , arranged to use a resource of a wireless communication system to transmit eMBB data for reception by a wireless communication device, enable puncturing of a scheduled eMBB data transmission to allow transmission of URLLC data in a pre-emption region of the same resource, reserve an allocated region within the resource for transmission of eMBB data that has been affected by a URLLC transmission, identify the allocated region to the wireless communication device, and transmit puncturing information for reception by the wireless communication device.

According to a third aspect of the invention, there is provided a wireless communication device configured to receive eMBB data using a resource and arranged to receive from a base station, an identification of an allocated region in said resource and puncturing information relating to puncturing of the resource by a URLCC transmission wherein said allocated region is reserved for retransmission of eMBB data affected by the URLCC transmission.

According to a fourth aspect of the invention, there is provided a non-transitory computer readable medium having computer readable instructions stored thereon for execution by a processor to perform the method according to the first aspect.

The non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.

Brief description of the drawings

Further details, aspects and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. Like reference numerals have been included in the respective drawings to ease understanding.

Figure 1 is a simplified block diagram of a wireless communication system capable of operating in accordance with an example embodiment;

Figure 2 is a diagram illustrating an example of eMBB scheduling; and

Figure 3 is a diagram illustrating an example of a mapping of puncturing regions to re-transmission regions.

Detailed description of the preferred embodiments

Those skilled in the art will recognise and appreciate that the specifics of the examples described are merely illustrative of some embodiments and that the teachings set forth herein are applicable in a variety of alternative settings.

Figure 1 shows a wireless communication system 100 which is a 5G/NR system. The system 100 includes at least one gNb 101 and other network entities (not shown) . The gNB 101 communicates with User Equipments (UEs) 102, 103. The gNB 101 performs the function (amongst others) of that of a base station and in general, a gNB may support multiple cells. In this example UE 102 is an eMBB UE; i.e. it receives eMBB transmissions on a downlink from the gNB 101. UE 103 is a URLLC UE; i.e. it receives URLLC transmissions on the downlink from the gNB 101 using resources shared with the eMBB transmissions. The UEs 102, 103 may each be for example, a cell phone, smart phone, wireless modem, laptop computer or other wireless communication device.

In the system 100 of Figure 1, eMBB and URLLC traffic are multiplexed in the downlink onto NR carriers whereby URLLC transmissions are allowed to dynamically puncture ongoing eMBB transmissions via a conventional pre-emption mechanism. In this example, the gNB 101 and UEs 102, 103 all support a known Hybrid Automatic Repeat Request (HARQ) process employing ACK/NACK (acknowledged or not acknowledged) responses.

In the system of 100 is assumed that transmissions have a frame structure which supports various TTIs (Transmission Time Intervals) , e.g. subframe/slot of 14/7 symbols for example (mainly considered for eMBB traffic) and a mini-slot of 1-2 symbols for example (mainly considered for URLLC traffic) . Furthermore, for a TDD (Time Division Duplex) scheme there are self-contained subframes/slots where, e.g. in a so called downlink-loaded subframe/slot, two symbols towards the end of the subframe/slot are used for uplink control. As is conventional, guard periods (GP) are provided between downlink and uplink transmission in order to allow enough time for switching.

Figure 2 illustrates an example of possible eMBB scheduling in TDD. A succession of downlink subframes (or timeslots) 201 are followed by a guard period 202 then an uplink frame 203 and then a further guard period 204. A typical subframe 205 is illustrated comprising a plurality of symbols 206 and frequencies 207. Subframe 205 may be used for eMBB data transmissions. Pre-emption regions P1, P2, P3 and P4, each of which may be considered to be mini-slots and comprise one or more symbols 206, represent regions of the subframe 205 that may be punctured by URLLC traffic. In this example, normal Downlink Control Information for the eMBB transmissions is communicated to UE 102 at the start of the subframe 205 using resources 208. Puncturing related information is communicated at the end of the subframe 205 using resources 209. In this example, pre-emption regions P2 and P3 are used for transmitting URLLC traffic comprising URLLC control and payload information and regions P1 and P4 are unused. Puncturing related information can be conveyed to the UE 102 (from the gNB 101) in the form of pre-emption signalling which can include: a pre-empt bitmap to identify the regions P1-P4 and whether or not they have been punctured, and an indication as to whether a retransmission of affected eMBB data is following (in a subsequent subframe for example) or not.

In general, several regions within an eMBB subframe/slot 201 which have been scheduled to an eMBB UE (UE 102 of Figure 1 for example) can be punctured by URLLC traffic. These regions can be allocated to URLLC UEs (such as UE 103 of Figure 1 for example) , and become known to eMBB UEs either by dynamic signalling, e.g. using UE-specific DCI or common DCI, or at the time of pre-configuration, pre-configuring meaning where certain eMBB resources are preconfigured as “allowed” resources to be used by potential URLLC traffic.

It will be understood that puncturing information can only be provided after it is known by the gNB 101, which eMBB resources have been affected by URLLC transmissions. Thus a UE 102 can be informed that eMBB data has been corrupted either; at each puncture event (e.g. by monitoring the DCI of a URLLC UE) ; or at the end of the same scheduling interval, or at a next scheduling interval of the same eMBB UE (e.g. when (re) transmission happens) ; or at a next scheduling interval of another eMBB UE. It will also be understood that at DCI-based indication may either be UE-specific or common for multiple UEs.

In the case where the UE is informed at each puncture event, it is possible to increase granularity in time for the eMBB control channel (or for another separate physical layer channel specified for this purpose) and indicate (explicitly or implicitly) the puncturing information as soon as the gNB decides on the pre-emption, e.g. just prior to or during a URLLC puncturing transmission. In general, such an approach will be highly intensive in terms of control overhead and/or UE requirements for additional monitoring and processing complexity. However, the UE can be configured to detect the URLLC presence only in cases of failed decoding by re-processing its reception buffer.

In terms of when puncturing or relevant retransmission information is indicated to the eMBB UE, if any of such information is given at a next slot, this is executed promptly (i.e the corrupted data is buffered at the eMBB for a relatively short length of time) and preferably in a pre-configured way (in order to reduce the monitoring needs for the eMBB UE) . For example, the gNB 101 can pre-configure an eMBB UE 102 to search for such information at the DCI of a resource block (RB) residing on the very next slot and the same subband, regardless if this is an RB originally scheduled to another UE.

Methods for scheduling (re) transmissions of affected eMBB data will now be described. In general, when corrupted/punctured data needs to be retransmitted/transmitted for an eMBB UE on a next scheduling interval, the gNB will have to decide which resources to schedule and how to indicate this to the eMBB UE. It is preferable for such scheduling procedure to be kept as efficient as possible in terms of: overhead introduced, especially when the amount of such (re) transmissions is large. This can be the case, for example, for (re) transmissions without ACK/NACK feedback. It is also preferable to limit the complexity of the scheduling. For example, an eMBB UE should not be forced to buffer its corrupted data for a very long time period, that is to say, long with respect to the number of HARQ processes (or more generally, the buffering capabilities of the UE) . It will be understood by those skilled in the art that if all buffering space of a UE is being used, it will not be able to receive any more transmissions, thereby leading to delay and throughput loss.

A simple solution is for the gNB to introduce an additional downlink grant for the eMBB UE in question, providing information on the relevant HARQ process, the allocated resources, MCS (Modulation and Coding Scheme) , etc., for example as a separate DCI or as an additional field in a DCI format and (re) transmit along with new data for this eMBB UE, when these arrive. Keeping full flexibility on resource allocation of such (re) transmissions, however, may incur significant signalling overhead and complexity as mentioned above. In addition, including additional DL grants to support such retransmissions will increase the DL control channel decoding complexity at the eMBB UE.

A first method which does not significantly suffer from the above drawbacks involves a one-to-one mapping of a puncturing ULRRC transmission with an eMBB (re) transmission. For example, if an indexing is used to distinguish among URLLC puncturing regions P1-P4 within an eMBB subframe/timeslot 205 (see Figure 2) , the same indexing can be adopted for respective (re) transmission regions in a following subframe. This "following" subframe may be the very next subframe but does not have to be. However, the further in time the "following" subframe can be depends generally on latency constraints for eMBB data and the buffering capability of the UE. The (re) transmission regions at a next subframe can be allocated to eMBB UEs by pre-configuration (in a message from the gNB) and understood by an eMBB UE to be allowed or potential regions for (re) transmission of affected eMBB data. As the frequency/time resources size of punctured eMBB data retransmissions actually correspond to the regions allocated for URLLC transmissions, such retransmissions will be of small bandwidth (compared to the larger eMBB transmissions bandwidth) . For such retransmissions, occupying a small portion of the eMBB transmission bandwidth, no real benefit comes from fully dynamic resource allocation in terms of sub-band scheduling. So it is preferable to allocate pre-configured regions within eMBB subframes/timeslots 201 in order to potentially schedule (re) transmission of affected data from a previous subframe/timeslot. In this case, the eMBB UE 102 just needs to know if such a pre-configured region is actually being used for the retransmission of affected data (and therefore contains information from a previous transport block) or, is not required for such a retransmission and contains new data instead. In one example, the gNB 101 explicitly indicates to the eMBB UE 102 that an allocated region for retransmission is used by, for example, using an additional indicator on the DCI of a retransmission subframe.

In a variation on this first method, the gNB 101 implicitly indicates to the eMBB UE 102 that an allocated region is being used for retransmission by reusing the puncturing indicator message mentioned above and by the UE considering the one-to-one mapping of potential URLLC indices to retransmission regions indices. Figure 3 illustrates an example of this method which uses implicit indication and with HARQ feedback. URLLC pre-emption regions in eMBB subframes have been preconfigured by a gNB. Also, allocated regions in eMBB subframes for retransmissions are automatically preconfigured by the gNB and made known to an eMBB. A subframe 301 precedes a following subframe 302.

Resources

303 and 304 in

subframes

301 and 302 respectively are scheduled to the eMBB UE 102.

Resources

305 and 306 in

subframes

301 and 302 respectively are scheduled to other UEs.

Regions

307, 308, 309, 310 in subframe 301 are potential pre-emption regions. In this example, potential pre-emption region 307 in subframe 301 has been allocated to and used for URLLC traffic but allocated region 308 has not been used. The gNB configures

retransmission regions

311 and 312 in resource 304 of subframe 302 and these are made known to an eMBB UE. The gNB indicates to the eMBB UE at the start 313 of subframe 302 that puncturing has occurred in the preceding subframe 301 in region 307 but no puncturing has occurred in region 308. The eMBB UE will therefore know that resources within region 311 refer to the (re) transmission (ReTx) of data from region 307 in the preceding subframe 301. It will also know that region 312 contains new data because region 308 in preceding subframe 301 has not been used. It will be understood by those skilled in the art that in general, corresponding

regions

307 and 311 may have different sizes, e.g. in cases where eMBB and URLLC scheduling units within the gNB use different frequency/time numerology.

A second method for scheduling retransmissions of affected eMBB data is to (re) transmit as quickly as possible (e.g. at the very next subframe/timeslot) regardless of which eMBB UE the targeted RB (resource block) belongs to. In this second method, the gNB 101 dynamically indicates to a first eMBB UE 102, which or if a URLLC pre-emption region within its scheduled subframe/timeslot is used. Then, at a following subframe/time slot, scheduled to any eMBB UE, resources within the starting symbols are reserved/scheduled for (re) transmission of eMBB affected data. Such scheduling can be done in either of two ways. A first way involves using a skip indicator. This can be included in DCI of the next subframe/timeslot to indicate the number of front symbols needing to be skipped or by indicating a bitmap of skipped symbols for discontinuous and non-front symbols. When the scheduled UE is not the UE 102 which received the punctured eMBB transmission, such a skip indicator has a possible additional advantage of power consumption reduction since the scheduled UE may wake up after the symbol where (re) transmission occurs. A second way involves allowing additional granularity in scheduling by scheduling a next subframe/timeslot with a starting symbol and optionally, the number of symbols.

A third method for scheduling transmissions of affected eMBB data is to schedule all (re) transmissions to pre-allocated subframes/timeslots. Typically, neither the gNB 101 nor UE 102 know in advance if some resource will be pre-empted by a URLLC transmission or not. However, the gNB can be configured to predict the likelihood of the arrival of URLLC traffic within a given scheduling period on a statistical basis Indeed, the system 100 typically has the knowledge of the number of URLLC devices connected, and possibly about the profile (type of Quality of Service bearer) of these devices. Moreover, the gNB 101 can be configured to build historical knowledge of the traffic required by URLLC devices that helps it to predict future URLLC traffic demands. Based on such knowledge, the gNB 101 schedules one or multiple subframes/timeslots to be shared by all eMBB devices capable of communicating with the gNB 101 that could be used for retransmission purposes e.g. at the end of a scheduling period when pre-emption by URLCC traffic occurred within this scheduling period . In this method, every eMBB UE knows in advance that it has resource pre-allocated for retransmission purpose whenever some of its traffic is punctured, the reserved subframe/timeslot occurring at the end of the scheduling period. Advantageously, as the resource is pre-allocated in advance, the signalling can be comparatively simple. In addition, only eMBB UEs that had their eMBB transmissions punctured have to monitor the specific pre-allocated subframe (s) /timeslot (s) for retransmission. If no puncturing (pre-emption) occurs, the pre-allocated subframe (s) /timeslot (s) can be used for other purposes such as for example, to transmit regular HARQ data for any eMBB UE that was scheduled during the scheduling period. Consequently, the pre-allocated subframe/timeslot is not lost.

The signal processing functionality of the embodiments of the invention especially the gNB and the

UEs

102, 103 may be achieved using computing systems or architectures known to those who are skilled in the relevant art. Computing systems such as, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc. ) , mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment can be used. The computing system can include one or more processors which can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.

The computing system can also include a main memory, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by a processor. Such a main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor. The computing system may likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for a processor.

The computing system may also include an information storage system which may include, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW) , or other removable or fixed media drive. Storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive. The storage media may include a computer-readable storage medium having particular computer software or data stored therein.

In alternative embodiments, an information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. Such components may include, for example, a removable storage unit and an interface , such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to computing system.

The computing system can also include a communications interface. Such a communications interface can be used to allow software and data to be transferred between a computing system and external devices. Examples of communications interfaces can include a modem, a network interface (such as an Ethernet or other NIC card) , a communications port (such as for example, a universal serial bus (USB) port) , a PCMCIA slot and card, etc. Software and data transferred via a communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface medium.

In this document, the terms ‘computer program product’ , ‘computer-readable medium’ and the like may be used generally to refer to tangible media such as, for example, a memory, storage device, or storage unit. These and other forms of computer-readable media may store one or more instructions for use by the processor comprising the computer system to cause the processor to perform specified operations. Such instructions, generally referred to as ‘computer program code’ (which may be grouped in the form of computer programs or other groupings) , when executed, enable the computing system to perform functions of embodiments of the present invention. Note that the code may directly cause a processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system using, for example, removable storage drive. A control module (in this example, software instructions or executable computer program code) , when executed by the processor in the computer system, causes a processor to perform the functions of the invention as described herein.

Furthermore, the inventive concept can be applied to any circuit for performing signal processing functionality within a network element. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP) , or application-specific integrated circuit (ASIC) and/or any other sub-system element.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to a single processing logic. However, the inventive concept may equally be implemented by way of a plurality of different functional units and processors to provide the signal processing functionality. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organisation.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as FPGA devices. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to ‘a’ , ‘an’ , ‘first’ , ‘second’ , etc. do not preclude a plurality.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognise that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ or “including” does not exclude the presence of other elements.

Claims

A method for enabling sharing of downlink resources between URLLC (Ultra Reliable and Low Latency Communications) and eMBB (enhanced Mobile Broadband) transmissions in a wireless communication system, the method comprising; at a base station, using a resource to transmit eMBB data for reception by a wireless communication device, enabling puncturing of a scheduled eMBB data transmission to allow transmission of URLLC data in a pre-emption region of the same resource, reserving an allocated region within the resource for transmission of eMBB data that has been affected by a URLLC transmission, identifying the reserved allocated region to the wireless communication device, and, at the wireless communication device, receiving puncturing information.
The method of claim 1 wherein the puncturing information includes one of the following: a puncturing indicator message which indicates whether or not puncturing has occurred; information identifying the pre-emption region; information for enabling a wireless communication device to distinguish received eMBB transmissions from URLLC transmissions; an indication that a retransmission of affected eMBB data will be transmitted; an indication that a retransmission of affected eMBB data will occur in a subframe/timeslot immediately following the pre-emption region; an indicator to notify the wireless communication device of resources in a subframe (or timeslot) which are to be used by the base station for retransmitting affected eMBB data.
The method of claim 1 or 2 wherein the puncturing information is communicated from the base station to the wireless communication device at the end of a subframe/timeslot of an eMBB transmission.
The method of any preceding claim wherein the puncturing information is included in eMBB Downlink Control Information (DCI) transmitted from the base station to the wireless communication device.
The method of any preceding claim comprising: at the base station, retransmitting affected eMBB data in a subframe/timeslot immediately following a subframe containing the pre-emption region.
The method of claim 5 comprising: at the base station, transmitting a "skip"indicator at the beginning of the subframe/timeslot following the subframe containing the pre-emption region for reception by a wireless communication device.
The method of any of claims 1-4 comprising: configuring the base station to use RIV-type scheduling for scheduling a retransmission of affected eMBB data.
The method of any of claims 1-4 comprising: at the base station, retransmitting affected eMBB data based on feedback received from the wireless communication device.
The method of claim 8 wherein the feedback comprises a HARQ process.
The method of any preceding claim comprising: at the base station, configuring the pre-emption region at the start of a subframe/timeslot and/or at the end of a subframe/timeslot.
The method of any preceding claim comprising: at the base station, indicating to the wireless communication device that an allocated region is to be used either for retransmission of affected eMBB data or new data.
The method of claim 11 comprising: at the base station, indicating to the wireless communication device that an allocated region is to be used for retransmission of affected eMBB data using an additional indicator on Downlink Control Information of a retransmission.
A base station arranged to use a resource of a wireless communication system to transmit eMBB data for reception by a wireless communication device, enable puncturing of a scheduled eMBB data transmission to allow transmission of URLLC data in a pre-emption region of the same resource, reserve an allocated region within the resource for transmission of eMBB data that has been affected by a URLLC transmission, identify the reserved allocated region to the wireless communication device, and transmit puncturing information for reception by the wireless communication device.
The base station of claim 11 wherein the base station is configured to make a decision as to: whether or not to retransmit affected eMBB data and if so, which mini-slot, mini-slot group, code block, code block-group or transport block to retransmit; which transmission format to use.
A wireless communication device configured to receive eMBB data using a resource and arranged to receive from a base station, an identification of an allocated region in said resource and puncturing information relating to puncturing of the resource by a URLCC transmission wherein said allocated region is reserved for retransmission of eMBB data affected by the URLCC transmission.
The wireless communication device of claim 13 arranged to extract puncturing information from eMBB Downlink Control Information received from the base station.
The wireless communication device of claim 13 arranged to determine information relating to puncturing of the resource by monitoring URLLC Downlink Control Information.
A non-transitory computer readable medium having computer readable instructions stored thereon for execution by a processor to perform the method according to any of claims 1-10.
The non-transitory computer readable medium of claim 14 comprising at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.