GB2562120A

GB2562120A - Preemption indication details for eMBB-URLLC multiplexing in wireless communication systems

Info

Publication number: GB2562120A
Application number: GB1707268.7A
Authority: GB
Inventors: Jechoux Bruno; Wagner Sebastian; Salim Umer; Katranaras Efstathios
Original assignee: TCL Communication Ltd
Current assignee: TCL Communication Ltd
Priority date: 2017-05-05
Filing date: 2017-05-05
Publication date: 2018-11-07
Also published as: GB201707268D0

Abstract

A method for enabling sharing of downlink resources between Ultra Reliable and Low Latency Communications (uRLLC) and Enhanced Mobile Broadband (eMBB) transmissions in a wireless communication system. The method comprises transmitting data comprised in a first slot 302a of an eMBB transmission for reception by one or more eMBB users, enabling puncturing of the eMBB transmission to allow transmission of uRLLC data in a pre-emption region 308 of the first slot and transmitting data in a second slot 302b which contains control information 314 indicating whether any eMBB data in the first slot has been pre-empted by uRLLC data. The uRLLC data transmitted in the pre-emption region of the first slot comprises decodable uRLLC resource information. The control information in the second slot may comprise a single flag bit regarding the occurrence of the pre-emption. The invention seeks to improve downlink resource sharing in New Radio (NR).

Description

(71) Applicant(s):

TCL COMMUNICATION LIMITED

1910-12A Tower 3, 33 Canton Road, Tsim Sha Tsui,

Kowloon, Hong Kong (72) Inventor(s):

Bruno Jechoux Sebastian Wagner Umer Salim Efstathios Katranaras (74) Agent and/or Address for Service:

Simmons & Simmons LLP

CityPoint, One Ropemaker Street, London, EC2Y 9SS, United Kingdom (51) INT CL:

H04W 72/04 (2009.01) H04W 72/12 (2009.01) (56) Documents Cited:

R1-1704632; 3GPP TSG RAN WG1 meeting #88bis; Spokane, Washington, USA, 3rd-7th April 2017; On multiplexing eMBB and URLLC in DL'; Guangdong ΟΡΡΟ Mobile Telecom.

R1-1705407; 3GPP TSG RAN WG1 Meeting #88bis; Spokane, USA, 3rd-7th April 2017; 'Multiplexing of eMBB and URLLC in Downlink'; Samsung.

R1-1708266; 3GPP TSG RAN WG1 Meeting #89; Hangzhou, China, 15th-19th May 2017; 'Preemption Indication Details for eMBB URLLC Multiplexing';

TCL.

R1-1701920; 3GPP TSG-RAN WG1 Meeting #88; Athens, Greece, 13th-17th February 2017; 'Discussion on Preemption indicator for Multiplexing eMBB and URLLC in Downlink'; Fujitsu.

R1-1611700; 3GPP TSG RAN WG1 Meeting #87; Reno, USA, 14th-18th November 2016; 'eMBB data transmission to support dynamic resource sharing between eMBB and URLLC'; Guangdong ΟΡΡΟ Mobile Telecom.

R1-1700264; 3GPP TSG RAN WG1 AH_NR Meeting; Spokane, USA, 16th-20th January 2017; 'About URLLC and eMBB multiplexing in downlink'; ZTE Microelectronics.

(58) Field of Search:

INT CL H04W

Other: WPI, EPODOC, Patent Fulltext, XPI3E,

XP3GPP, INSPEC, Internet (54) Title of the Invention: Preemption indication details for eMBB-URLLC multiplexing in wireless communication systems

Abstract Title: Enabling sharing of downlink resources between Ultra Reliable and Low Latency Communications (uRRLC) and Enhanced Mobile Broadband (eMBB) transmissions (57) A method for enabling sharing of downlink resources between Ultra Reliable and Low Latency Communications (uRLLC) and Enhanced Mobile Broadband (eMBB) transmissions in a wireless communication system. The method comprises transmitting data comprised in a first slot 302a of an eMBB transmission for reception by one or more eMBB users, enabling puncturing of the eMBB transmission to allow transmission of uRLLC data in a pre-emption region 308 of the first slot and transmitting data in a second slot 302b which contains control information 314 indicating whether any eMBB data in the first slot has been pre-empted by uRLLC data. The uRLLC data transmitted in the pre-emption region of the first slot comprises decodable uRLLC resource information. The control information in the second slot may comprise a single flag bit regarding the occurrence of the pre-emption. The invention seeks to improve downlink resource sharing in New Radio (NR).

At least one drawing originally filed was informal and the print reproduced here is taken from a later filed formal copy.

1/7

03 18 $<·\

Figure 1

2/7

200

204

Figure 2

3/7

03 18

Figure 3

4/7

03 18

Frequency

406b

406c

406d

Mini slot <-> 408

-eMBB slot402a

-eMBB slot402b

414

Figure 4

5/7

03 18

Frequency

Figure 5

6/7

03 18

502a 502b

Figure 6

7/7

03 18

Figure 7

Preemption indication details for eMBB-URLLC multiplexing in Wireless Communication Systems

T echnical field

E mbodi ments of the present i nventi on general ly rel ate to wi rel ess communi cati on systems and i n particular to systems where URL LC (Ultra Reliable and Low Latency Communications) transmissions are multiplexed with eMBB (enhanced Mobile Broadband) transmissions ona downlink, and has particular application to the so- called NR, New Radio, (or5G) 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 3rd 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 U niversal 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 cel I is supported by a base station known as a gN B.

In the downlink of New Radio (NR), it has been considered that it will be possible to schedule higher priority URL LC (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 shari ng the resources, whether by puncturi ng or any other mechanism. Furthermore, the URLLC transmission affects (for example, corrupts) the eM BB transmission and so the problem of recovering affected eMBB data also needs to be addressed.

It has been proposed thatthe DCI (Downlink Control Information) of the URLLC puncturing resources is group common and hence decodable by URLLS and eMBB users. However, this proposal woul d requi re eM B B users to I i sten always at al I possi bl e I ocati ons of the puncturi ng URLLC transmission which would put a large burden on the computational complexity put to eMBB users additional to normal processing.

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 dai med subject matter, nor is it i ntended to be used as an aid in determining the scope of the claimed subject matter.

The invention is disclosed in the appended claims.

B ri ef descri pti on of the drawi ngs

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 i n the respective drawi ngs to ease understand! ng.

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 schematic showing a puncturing/preemption of eMBB data with URLLC data, according to an example.

Figure 3 is a schemati c showi ng an i ndication design for i ndi cati ng pre-emption of eM B B data transmitted to a wi rel ess communicati on devi ce, accordi ng to an embodi ment of the invention.

F igure 4 i s a schemati c showi ng an i ndi cati on design for i ndi cati ng pre-empti on of eM B B data transmitted to multiple wireless communication devices, according to an embodi ment of the i nventi on.

F igure 5 i s a schemati c showi ng an i ndi cati on design for i ndi cati ng pre-empti on of eM B B data i n multi pi e I ocati ons, accordi ng to an embodi ment of the i nventi on.

F igure 6 i s a schemati c showi ng an i ndi cati on design for i ndi cati ng pre-empti on of eM B B data i n a shared zone only, accordi ng to an embodi ment of the i nventi on.

Figure 7 is a flowchart indicating a pre-emption discovery procedure at a wireless communi cati on devi ce, accordi ng to an embodi ment of the i nventi on.

Detailed description

T hose ski 11 ed i n the art wi 11 recogni se and appreciate that the specifi cs of the exampl es descri bed are merely i 11 ustrati ve of some embodi ments and that the teachi ngs set forth herei n are appl i cabl e i n a variety of alternative setti ngs.

Figure 1 shows a wireless communication system 100 which is a 5G/NR system The system 100 i nd udes at I east one gN b 101 and other network entiti es (not shown). T he gN B 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. U E 102 can in reality be a device capable of using both services eMBB and URLLC but here its eMBB service capable features are active. UE 103isaURLLC UE; i.e. it receives URLLC transmissi ons on the downl i nk from the gNB 101 usi ng resources shared with the eM B B transmi ssi ons. T he U E s 102,103 may each be for exampl e, a cel I 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 gNB 101 is allowed to puncture the ongoing eMBB traffic to accommodate high priority URLLC traffic transmission on the resource initially allocated to eMBB traffic (i.e. URLLC transmissions are all owed 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 (HA RQ) process employing AC K/NACK (acknowledged or not acknowledged) responses.

In the system of 100 is assumed that transmissions have a frame structure which supports various TTIs (T ransmission 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, foraTDD (Time Division Duplex) scheme there are selfcontained subframes/slots where, e.g. in a so called downl ink-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 is a schematic showing a puncturing/preemption of eMBB data with URLLC data, accordi ng to an exampl e. D uri ng an eM B B transmi ssi on 200 to e.g. U E 102, U R L L C data 204 (e.g. intended for UE 103) is transmitted by puncturing eMBB data 202. If the UE 102 does not know where the punctured regi on i s, the dynami c U R L L C transmi ssi on corrupts the eMBB transmission 200 and degrades its performance.

Figure 3 is a schematic showing an indication design for indicating pre-emption of eMBB data transmitted to one or more wireless communication device (or UE), by a base station (or gNB), accordi ng to an embodiment of the invention. During an eMBB transmission 300, eMBB data is transmitted in slots 302a, 302b. The slots 302a, 302b comprise a Physical Downlink Control Channel (PDCCH) 304a, 304b respectively, and a Physical Downlink Shared Channel (PDSCH) 306a, 306b respectively. The PDCCHs 304a, 304b carry downlink control information (DCI) for the respective slots 302a, 302b. The DCI contained in each PDCCH 304a, 304b provides the control i nformati on to one or more UEs who have been schedul ed respectively i n the si ots 302a and 302b, and to be abl e to receive and decode the data that is contai ned i n the respective PDSC Hs 306a, 306b. T he data contai ned i n PDSC H 306a may be i ntended for one or more eMBB users, each of which would be allocated resources within the PDSCH 306a. Likewise for

PDSCH 306b, the data may be intended for one or more eMBB users, and these users may be different to the user(s) of PDSCH 306a. In the schematic of Figure 3, during the transmission of the slot 302a, the eMBB data is punctured (or pre-empted) by URLLC data. The URLLC data is transmi tied i n a mi ni -si ot 308. T he mi ni -si ot 308 has a si mi I ar structure to the si ots 302a, 302b, and comprises a PDCCH 310and corresponding PDSCH 312for the mini-slot The PDCCH 310 carries the DCI forthe URLLC data contained in the PDSCH 312, such that one or more URLLC UEs who have been scheduled in this mini-slot can receive and decode this data. There is no restriction if the U E(s) in the slots 302a and 302b are the same or different

As discussed with respect to Figure 2, such a puncturing event can degrade the performance of the eMBB data transmission if the eMBB UE does not know where the puncture region is (i.e. mini-slot 308). In the present embodiment the base station transmits a pre-emption indicator 314 inthe PDCCH 304b of following slot 302b. In the present embodiment the indicator 314 is a single bitflag that simply indicates the occurrence of pre-emption in the previous slot whilst in other embodi ments the i ndi cator 314 provi des more detai I ed i nformati on such as the I ocati on of the mi ni -si ot 308 i n frequency and/or ti me, or the number of mi ni -si ots if there are more than one. Asa result the eM B B U E can decode the DCI of PDCC H 304b, and discover that preemption occurred in the previous slot 302a.

In the embodi ments of the i nventi on, at I east the ti me-f requency resource i nformati on of the mini-slot 308 in the DCI carried by PDCCH 310 is decodable by both eMBB UEsand the desti ned URLLC UE. F urther, the base stati on transmi tti ng the data al igns the start ti me of the URLLC mini-slot 308 with a symbol start time of the slot 302a. The vertical lines 316 indicate the possible start times of the URLLC UE. Using this information, the eMBB UE isabletoscan all of the possible start points of the URLLC mini-slots, by trying to decode blindly the DCI of the mini-slot 308 at the possible start-points. After successful decoding of URLLC DCI, the eMBB U E knows the exact ti me/frequency resources that were pre-empted i n the si ot 302a and can decide to assist data decoding by nulling out or throwing the received signal on those resources. T he eMBB UEs and the base stati on can al so opt for the retransmi ssi on of the preempted data, dependent on the method of re-transmission decided (for example CBG based retransmission, PRB based retransmission or fractional retransmission).

In some embodi ments, the possi bi e start poi nt of the U R L L C data can al so be restri cted to one or multi pie frequency intervals in the frequency domain, indicated by the horizontal line 318. The same pri nci pi e appl i es, and the number of possi bi e start poi nts that the eM B B UEs scan depends on the specific arrangement of each embodimenL

Figure 4 is a schematic showing an indication design for indicating pre-emption of eMBB data transmitted to multiple wireless communication devices, according to an embodiment of the invention. Featuresin Figure 4 that have the same or similar function as those in Figure3 have been given similar reference numerals, with the prefix 4 instead of 3. For instance, the mi nisi otin Figure4 has been given the numeral 408, as opposed to 308 in Figure 3. The description of those features descri bed with reference to F igure 3 can be appl ied to the correspond! ng features i n Figure 4. Some features i n Figure 4 differ to those i n Figure 3 and are discussed i n more detail below.

In the schematic shown in Figure 4, the slot 4O2a contains data intended for several different eM B B U E s (a f i rst regi on of data 406a i s i ntended for a fi rst eM B B U E, a second regi on of data 406c i s i ntended for a second eM B B U E, and so on). T he P D C C H 404a carri es the D CI that indicates to the eMBB UEs the resources allocated to them. As shown in the schematic, the minisi ot 408 has pre-empted data i ntended for three eM B B U Es, but not one. In some embodi ments, the indicator 414 may be a single bitflag (as described with reference to Figure 3), and each eMBB U E i s abl e to scan al I of the possi bl e start poi nts of the U R L L C data wi thi n thei rail ocated resources, by trying to decode blindly the DCI of the mini-slot 408 at the possible start-poi nts within thei rail ocated resources. In an alternative embodiment the indicator 414 contains i nformati on rel ati ng to the I ocati on of the mi ni -si ot 408 i n ti me and/or frequency. If the I ocati on of the mini-slot 408 i n the frequency domain is given, then the eMBB UEs can determine whether the data i ntended for them was affected or not (so, advantageously, the eM B B U E al I ocated resources 406a knows that thei r data transmi ssi on was unaffected and does not need to search for the mi ni-sl ot 408).

Figure 5 is a schematic showing an indication design for indicating pre-emption of eMBB data in multi pi e I ocati ons, accordi ng to an embodi ment of the i nventi on. F eatures i n F igure 5 that have the same or si mi lar functi on as those i n F igure 3 have been given si mi lar reference numerals, with the prefix 5 instead of 3. For instance, the mini-slot in Figure 5 has been given the numeral 508, as opposed to 308 in Figure 3. The description of those features described with reference to Figure 3 can be applied to the corresponding features in Figure 5. Some features in Figure 5 differ to those in Figure 3 and are discussed in more detai I below.

In the schematic shown in Figure 5, the data for URLLC services arrives at two different time positions during the transmi ssi on of the slot 502a to one or multiple eMBB users. The base station or gNB thus creates two mini-slots, 508a and 508b, to serve these URLLC services that happen to be of different lengths.

In some embodiments, the preemption indicator 514 can either have a single flag 'in the DCI of slot 502b (i.e. in PDCCH 504b), which would tell the eMBB users that slot 502a was preempted. As the mini-slot can have a finite number of starting positions in time, and in some embodiments, in frequency, eMBB users, who had resource assignments in the last slot 502a, can try blind decoding on the common DCI space of these start intervals. Finding and reading this common search space, they are able to find the resources which the base station or gN B preempted in this slot and would precisely know the impact on their relevant resources received.

In other embodi ments, the base stati on or gN B can hel p further eMBB U E s i n preempt! on detection by adding several bits in the adjacent DCI of slot 502b. As an example, i nstead of a single bitflag as in some previous embodiments, there is a field which gives the number of minislots which occurred in the last slot (in the present embodiment, the number of mini-slots is two). If thi s f i el d contai ns a zero val ue, al I rel evant eM B B UEs know that there was no preempt! on i n the last slot 502a. In case of preemption, this field would indicate the number of mini-slots (e.g. 508a, 508b) which gNB had to create to serve URLLC services. This helps eMBB UEsintheir bl i nd decodi ng. As soon as the eM B B UEs have decoded the number of mi ni -si ots i ndi cated by this field, it knows that there is no further puncturing of data in the last slob which saves on computational complexity.

As discussed previously, in yet further embodiments, gNB provides some indication on the locations of the mini-slot occurrence in the last slot 502a. As shown in Figure 5 by dash-dot I i nes, i n the present embodi ment there are a fi nite number of positi ons i n the ti me/frequency gri d where mini-slots 508a, 508b can take place. In some embodiments, the positions are only limited in time. The figure shows only two frequency positions (delimited by dash-dot line 518) as an exemplary embodiment; but all ideas stay relevant if there is only one or multi pie frequency i nterval sail owed for the start of the mi ni -si ot i n the system bandwi dth.

In some scenarios, there is a desire to allow flexibility to schedule URL LC services quickly and to minimize the impact of the preemption on eMBB services. Thus, in some embodiments gNB has the flexibility to make two zones (preferably in frequency), where one zone is dedicated for eM B B servi ces and the users al I ocated here are not preempted. F igure 6 i s a schemati c showi ng an indication design for indicating pre-emption of eMBB data in a shared zone 620b only, according to an embodiment of the invention. Features in Figure 6 that have the same or similar function as those in Figure 3 have been given similar reference numerals, with the prefix 6 instead of 3. For instance, the mini-slot in Figure 6 has been given the numeral 608, as opposed to 308 in Figure 3. The description of those features described with reference to Figure 3 can be applied to the corresponding features in Figure 6. Some features in Figure 6 differ to those in Figure 3 and are discussed in more detail below.

In the schematic shown in Figure 6, the slots 602a and 602b are divided in the frequency domain into a 'no pre-emption zone_ 620a and a 'shared zone_ 620b. In the no preemption zone 620b, the base stati on or gN B does not make any U R L L C data transmi si ons. T hus, the eM B B UEs usi ng resources i n the no pre-empti on zone 620b do not need to I isten to any preempt!on indicators etc. The other zone is the shared zone 620a. This is the zone which gNB uses to serve U R L L C traffi c that cannot be served by schedul i ng i n the normal D C I. A si mpl e exampl e i s some very latency critical data arriving in the middle of the normal slot In some embodiments, gNB would be able to seale up or down the two zones as a function of how many U RL LC users are present i n the coverage area and as a functi on of thei r traffi c requi rements etc. I n a yet further embodi ment; gNB I ets the eM B B users know about the zone they are bei ng schedul ed, e.g„ by some higher layer signal I i ng and then correspond! ngly the eM B B users know if they have to take care of preemption relevant aspects or not

For the networks or gNESs having these zones, the invention and the proposals discussed with reference to Figures 3-5 apply verbati m to the shared or co-existence zone 620b where U R L L C servi ces may preempt the ongoi ng eM B B traffic. In other words, eM B B users knowi ng that they are being scheduled in this zone start listening to the preemption indication.

Figure 7 is a flowchart 700 indicating a pre-emption discovery procedure at a wireless communication device (i.e. an eMESES user), according to an embodiment of the invention.

T he step by step procedure at the eM B B users is descri bed i n the fol Iowing steps, Fi rst, i n step 702, all eMBB users scheduled in the first slot 'N_ check the PDCCH of the next slot 'N+1_, in the common search space (i.e. the DCI). If there is no pre-emption indication or flag (step 704) then al I the data i s val i d and the data i s added to the soft buffer of the eMBB user, and the normal decoding and HARQ procedure isfollowed (step 706). If there is a pre-emption i ndi cati on or fl ag that i ndi cates there was preempt! on i n the I ast si ot, the eM B B user(s) need to find the preempted PRBs (Physcial Resource Blocks). Upon preemption indication, the eMBB UE blindly decodes all the possible URLLC DCI start positions (step 708), as the scheduling part in terms of 'REs_ assignments is decodable by all users in the cel I.

N ext, i n embodi ments where the i ndi cator i nforms the eM B B users where the U R L L C data i s I ocated, the eMBB user(s) deci de whether thei r al I ocated resources are affected (step 710). If they are not affected then the eMBB user(s) proceed to step 706 as above. If they are affected then the eMBB user(s) proceed to step 712. (It wi 11 be appreciated that step 710 is ski pped i n embodi ments where the I ocati on of the U R L L C data i s not i ndi cated, and the eMBB user(s) proceed to step 712).

A t step 712, the eM B B user(s) f i nds the P R B s used by the U R L L C mi ni -si ot i n the I ast si ot and sees which of these PRBs were part of its assignment in the last slot This way eMBB UE gets to know precisely which of its allocated time frequency resources were punctured in the last slot It nul Is out the L L Rs for these PR Bs (' R E s_) to avoi d pol I uti ng its soft buffer with wrong val ues (i.e. discards the URLLC data). In embodi ments where the mini-slot start positions in terms of ti me and frequency are restri cted, eMBB U E s only need to I ook at those al I owed positi ons for a possible preemption event.

Fol I owi ng step 712, the eMBB user(s) try decodi ng the code bi ocks and fol I ow the standard compliant handling for pre-emption ack/nak and retransmission, which is predetermined in any given embodiment

Certain variants to the described invention will be apparent to the ski I led person. For example, the slot containing the pre-emption indicator/flag may be in the immediately following transmitted slot or in other embodiments the indicator/flag may be transmitted in latertransmitted slots. (If the URLLC data arrives very late in the slot say last symbol or in the mid of the last symbol and gNB punctures this last symbol or a fraction for mini-slot, there could be some reservations that if gNB will be able to prepared the DCI of the next slot with preemption indication flag. Normally if gNB is capable enough that it is able to puncture the I ast symbol of the slot, it may prepare the DCI as well with preemption indication. But if it s too complicated for gNB to put this indication in the next adjacent slot, there may be some higher layer signal ling i ndi cati on that preempt! on i ndi cati on i s systemati cal ly done I ater, 2 si ots after the preempt! on slot for example).

It i s noted that both the eM B B U E (si ot data) and U R L L C U E (mi ni -si ot) coul d be operati ng on different numeral ogies. Preferably, eMBB UE would know the numerology of URLLC for correct detection of U RL LC common DCI. E ither the U R L LC used numerology (or the possible set in use) could be part of the system information, and it would reduce the eMBB UE blind decodi ng attempts f or the U R L L C D C 1.1 n case of no i nformati on at al I on U R L L C numeral ogy, eMBB U E can try the possi bi e numeral ogi es al I owed by standard.

eMBB UEs, being scheduled in the shared or co-existence zone, may need to wait the DCI of the next siot before starti ng to decode the code blocks from the previous siot T his adds a certai n delay to the U E processi ng. One way to ci rcumvent this coul d be that eM B B U E may start the decoding for the code blocks which it has received completely without waiting for preemption indication. It listens to preemption flag in the next DCI but if no preemption or already successful decoding of certain code blocks, it does not need to search for the detailed mini-slot locations by blind decoding.

It wi 11 be appreci ated that the teachi ngs of one embodi ment descri bed with reference to one Figure could be combined with the teachings of other embodiments.

T he signal processi ng functi onal ity of the embodi ments of the i nventi on especial ly the gN B and the U E s 102,103 may be achieved usi ng computi ng systems or architectures known to those who are ski 11 ed i n the rel evant art. C omputi ng systems such as, a desktop, I aptop 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 devi ce for stori ng stati c i nformati on and i nstructi ons for a processor.

T he computi ng system may al so i nd ude an i nformati on storage system whi ch may i nd ude, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removabl e 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 (DV D) 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,

C D or DV D, 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 therei n.

In alternative embodiments, an information storage system may include other similar components for al I owi ng computer programs or other i nstructi ons or data to be I oaded i nto 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 removabl e storage units and i nterfaces that al I ow 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 i nterface can be used to al I ow software and data to be transferred between a computi ng 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-readabl e medi um 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 i nstructi ons for use by the processor compri si ng 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 i nventi on. Note that the code may di rectly 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„ Ii braries for performing standard functions) to do so.

In an embodiment where the elements are implemented using software, the software may be stored i n a computer- readabl e medi um and I oaded i nto computi ng system usi ng, for exampl e, removable storage drive. A control module (in this example, software instructions or executable computer program code), when executed by the processor i n the computer system causes a processor to perform the functi ons of the i nventi on as descri bed herei n.

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 i ntegrated ci rcuit (ASIC) and/or any other sub-system element.

It will be appreciated that for clarity purposes, the above description has described embodiments of the i nventi on with reference to a si ngl e processi ng I ogi c. H owever, the i nventive 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 i ntended to be I i mi ted to the specific form set forth herei n. 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 descri bed embodi ments may be combi ned i n 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 i nd usi on i n different dai ms does not i mply that a combi nati on of features i s not feasi bl e 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 i mply that the steps must be performed i n 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, zsecond, etc. do not preclude a plurality.

Although the present invention has been described in connection with some embodiments, it is not i ntended to be I i mi ted to the specific form set forth herei n. 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 descri bed embodi ments may be combi ned i n accordance with the invention. In the claims, the term:comprising or 'including, does not exclude the presence of other elements.

Claims

1. A method for enabl i ng shari ng of downl i nk resources between URLLC (UI tra R el i abl e and Low Latency Communications) and eMBB (enhanced Mobile Broadband) transmissions in a wireless communication system, the method comprising the steps of, at a base station:

transmi tti ng data compri sed i n a fi rst si ot of an eM Β B data transmi ssi on for recepti on by one or more eM Β B users;

enabling puncturing of the eMBB data transmission of the first slot to allow transmission of URLLC data i n a pre-empti on regi on of the fi rst si ot; and transmitting data in a second slot the second slot containing control information indicating whether any eM Μ B data i n the fi rst si ot has been pre-empted by U R L L C data;

wherei n the U R L L C data transmi tied i n the pre-empti on regi on of f i rst si ot compri ses at I east the URLLC resource information which is decodable by both the destined URLLC users and the eMBB users schedul ed i n the f i rst si ot

2. The method according to claim 1, wherein the control information in the second slot comprises a single bitflag regarding the occurrence ofthe preemption.

3. T he method accordi ng to cl ai m 1 or 2, wherei n the U R L L C data puncturi ng the eMBB data i n the f i rst si ot i s compri sed of mi ni -si ots, and the control i nformati on i n the second si ot i ndi cates the number of mi ni -si ots i n the f i rst si ot

4. T he method accordi ng to any precedi ng cI ai m, wherei n the control i nformati on regardi ng pre-emption in the second slot is common information or group common information such that it i s at I east decodabl e by al I the eM Β B users schedul ed i n the fi rst si ot

5. T he method accordi ng to any precedi ng clai nq wherein the base station aligns the start time of the U R L L C data with a symbol start ti me of the fi rst si ot.

6. The method according to any preceding claim, wherein the base station aligns the start frequency of the U R L L C data with one of a set of predetermi ned frequency val ues.

7. The method according to any preceding claim, wherein a dedicated frequency or time interval of the slots transmitted by the base station is dedicated for eMMB services, such that eMBB data is only pre-empted by URLLC data outside the interval.

8. The method according to claim 7, wherein the dedicated frequency or time interval is adjustable by the base station responsive to the number of U RL LC users present in the coverage area of the base stati on.

9. The method according to claim 7 or 8, wherein the base station transmits the dedicated frequency or ti me i nterval i nformati on to the wi rel ess communicati on device.

10. The method according to any preceding dainq wherein the second slot is the next slot transmi tted fol I owi ng the fi rst si ot

11. T he method accordi ng to any of dai ms 1 to 9, wherei n at I east one si ot is transmitted after the fi rst si ot and before the second si ot i s transmitted.

12. The method according to any preceding dainq wherein preceding the step of transmitting eMBB data in a second slot, the base station transmits to the wireless communication device i nformati on regardi ng the numerol ogy of U R L L C.

13. A method of processing eMBB (enhanced Mobile Broadband) transmissions in a wireless communication system, wherein the downlink resources of the eMBB transmissions are shared with U R L L C (U Itra R el i abl e and L ow L atency Communi cati ons), the method compri si ng the steps of, at a wireless communication device:

receiving data comprised in a first slot of the eMBB transmission;

receiving control information data in a second slot of the eMBB transmission, the second slot containing control information indicating whether eMBB data has been pre-empted by URLLC data in the first slot;

processing the control information to determine whether eMBB data has been pre-empted by URLLC data in the first slot;

responsive to determining that eMBB data has been pre-empted, processing the data of the first si ot to I ocate the U R L L C data, wherei n the U R L L C data compri ses U R L L C resource i nformati on which is decodable by the wireless communication device; and discarding the part of their received (or processed) data from the first slot which was pre-empted by URLLC data.

14. A method of processing eM BB transmissions according to claim 13, wherein immediately following the step of receiving data comprised in a first si of the wireless communication device begi ns process! ng the data comprised i n the fi rst slot.

15. A method of processing eMBB transmissions according to claim 13 or 14, wherein immediately following the step of receiving data comprised in the firs slot, the wireless communication device begins processing the data comprised in the first slot and uses the preempt! on rel evant control i nformati on from the second si ot only if there are decodi ng errors on the data of the first slot

16. A base stati on arranged to perform any of the methods accordi ng to dai ms 1 to 12.

17. A wireless communication device arranged to perform any of the methods according to claim 13 to 15.

18. A non-transitory computer readable medi um havi ng computer readable i nstructi ons stored thereon for execution by a processor to perform the method according to any of claims 1 to 12 or of 13 to 15.

GB 1707268.7

1-18