Patent Description:
To accommodate for Internet of Things (IOT) traffic, various work items in the Third Generation Partnership Project (3GPP) have been defined. Examples include <NPL>; <NPL>; <NPL>; and <NPL>.

Such concepts for IOT traffic often rely on transmission on a subband (sometimes also referred to as narrowband) of a carrier for IOT-terminals (UEs). Non-IOT UEs transmit on the entire bandwidth of the non-IOT traffic. Hence, a plurality of resource blocks (often referred to as physical resource block, PRB) - each PRB including multiple time-frequency resource elements (often referred to as physical resource element, PRE) of a time-frequency resource grid - are associated with the subband and therefore allocated to the IOT traffic.

In order to reduce complexity of the radio frequency front and of an IOT UE, the bandwidth of the subband is reduced if compared to the overall bandwidth of the carrier. For example, typical bandwidths of the subband are in the range of <NUM> - <NUM>, while the bandwidth of the carriers in the range of <NUM> - <NUM>, or even larger.

Further, typically different scheduling strategies are employed for scheduling a first transmission of IOT traffic on the subband and for scheduling a second transmission of non-IOT traffic outside of the subband. For example, different formats of scheduling information can be used for scheduling the first transmission and for scheduling the second transmission. For example, for scheduling the transmission on the subband, a Downlink Control Information (DCI) format <NUM>-1B can be used according to <NPL>. Differently, for scheduling the transmission outside the subband, a DCI format <NUM> according to <NPL> can be used.

It has been observed that due to different formats of the scheduling information used for scheduling of the transmission on the subband and for scheduling of the transmission outside of the subband, ambiguities can result. This can degrade the system reliability and/or spectral efficiency.

Further, on a general level, it has been observed that due to different requirements of IOT traffic and non-IOT traffic - e.g., in terms of contiguous channel access, etc. - flexibility in scheduling can be limited. This can increase latency.

On an even more general level, it has been observed that coexistence of transmissions with different requirements - e.g., in terms of format of the scheduling information, duration, bandwidth, etc. - on a common carrier can complicate the scheduling of these transmissions.

3GPP R1-<NUM> discloses an uplink suspending indication that is transmitted by the gNB.

3GPP R1-<NUM> discloses a UE that drops/skips transmission in a resource allocation which partially or fully overlaps with downlink resources indicated by a dynamic SFI.

Therefore, a need exists for advanced techniques of scheduling. In particular, a need exists for advanced scheduling techniques which overcome or mitigate at least some of the above-identified restrictions and drawbacks.

This need is met by the features of the independent claims <NUM>, <NUM>, <NUM>, and <NUM>.

The method according to claim <NUM> includes, in particular, receiving scheduling information for a transmission on a plurality of resource blocks. The method also includes, based on control information on at least one forbidden resource block included in the plurality of resource blocks, blocking the transmission on the at least one forbidden resource block.

The method according to claim <NUM> includes, in particular, transmitting scheduling information for a transmission on a plurality of resource block. The transmission is blocked on at least one forbidden resource block included in the plurality of resource blocks.

A method that is not claimed, and thus not covered by the scope of the appended claims, includes scheduling a first transmission between an access node and a first terminal. The method further includes puncturing the first transmission on at least one forbidden resource block. The method further includes scheduling a second transmission between the access node and a second terminal on the at least one forbidden resource block.

For example, the first transmission may allocate a first bandwidth. The second transmission may allocate a second bandwidth. The second bandwidth may be larger than the first bandwidth, e.g., at least by a factor of <NUM> or at least by a factor of <NUM>.

For example, the first transmission may be for IOT traffic; and the second transmission may be for non-IOT traffic. For example, the first UE may be an IOT UE; and the second UE may be a non-IOT UE.

For example, the first transmission may have a first transmission duration. For example, the second transmission may have a second transmission duration. The first transmission duration may be larger than the second transmission duration, e.g., by at least a factor of <NUM> or at least by a factor of <NUM>.

For example, a format of scheduling information for said scheduling of the first transmission may be different from a format of scheduling information for said scheduling of the second transmission. For example, different groups of PRBs may be used for scheduling, which may not be aligned.

Puncturing can be in at least one of time domain and frequency domain. Hence, the first transmission may be interrupted in at least one of time domain and frequency domain.

It is to be understood that the features mentioned above and those yet to be explained below may be used not only in the respective combinations indicated, but also in other combinations or in isolation without departing from the scope of the invention, which is defined by the scope of the appended claims.

Same reference signs in the various drawings refer to similar or identical components, functions or actions. The scope of the present invention is determined by the scope of the appended claims.

Hereinafter, techniques of wireless communication are described. Transmission of data on a wireless link is possible. Transmission of data includes transmitting data and/or receiving data. For example, uplink (UL) data may be communicated from a UE to an access node such as a base station (BS). Alternatively or additionally, downlink (DL) data may be communicated from the access node, e.g., the BS, to the UE.

For example, application data may be communicated. Application data is often also referred to as payload data user data. Application data may be defined on Layer <NUM> of an Open Systems Interface (OSI) transmission protocol stack. It would also be possible to communicate higher-layer control data, e.g., Layer <NUM> or Layer <NUM> control data, e.g., Radio Resource Control (RRC) control data.

The wireless communication can be supported by a BS of a cellular network. Hereinafter, for sake of simplicity, reference is primarily made to cellular networks and BSs; however, similar techniques may be readily applied to other kinds and types of access nodes of other kinds and types of networks.

In the various examples described herein, IOT traffic and non-IOT traffic is described. IOT traffic is between a BS and an IOT UE. Non-IOT traffic is between a BS and a non-IOT UE. Typically, non-IOT traffic includes a transmission allocation PRBs that are spread across the entire bandwidth of a carrier. The carrier may include multiple subcarriers. Some of these subcarriers may be associated with a subband of the carrier. Transmissions of IOT traffic are typically allocated to a subband.

Often, the transmission of IOT traffic has a smaller bandwidth, but a larger transmission duration if compared to a transmission of non-IOT traffic.

Specifically for transmissions of IOT traffic, a set of features where a comparably large coverage is achieved is referred to as Coverage Enhancement (CE). CE is envisioned to be applied for MTC and NB-IOT. A key feature of the CE is to implement multiple transmission repetitions of signals; thereby multiple repetitions of encoded data are facilitated. This typically increases the transmission duration. Each repetition may include the same redundancy version of the data. The repetitions may be "blind", i.e., may not in response to a respective retransmission request that may be defined with respect to a Hybrid Acknowledgment Repeat Request protocol (HARQ protocol). Rather, repetitions according to CE may be preemptive. Examples are provided by the <NPL>. By employing an appropriate CE policy, a likelihood of successful transmission can be increased even in scenarios of poor conditions of communicating on a corresponding wireless link. Robustness against channel fading is increased. Thereby, the coverage of networks can be significantly enhanced - even for low transmission powers as envisioned for the IOT domain.

According to various examples, a CE policy is employed for transmission between the UE and the network. The CE policy may define a repetition level. Messages or signals including a given redundancy version of encoded data are repeatedly communicated according to the repetition level: According to examples, a message is redundantly communicated using a plurality of repetitions. The message may include data which is encoded according to one and the same redundancy version: Hence, the same encoded data may be redundantly communicated a number of times according to various examples. Typically, different redundancy versions correspond to checksums of different length. In other examples, it would also be possible that different redundancy version employ checksums of the same length, but encoded according to the different coding scheme. Alternatively or additionally, different redundancy versions may employ different interleaving schemes. Each repetition of the plurality of repetitions can include the data encoded according to the same redundancy version, e.g., redundancy version <NUM> or redundancy version <NUM>, etc. Then, it is possible to combine the plurality of repetitions of the encoded data at the receiver side. , multiple received instances of the message may be combined. Such combination may be implemented in analog or digital domain, e.g., in the baseband. The combination yields a combined signal. Then, the decoding of the encoded data can be based on the combined signal. Thus, by aggregating the received information across the multiple repetitions, the probability of successfully decoding of the encoded signal increases. This facilitates CE. The count of repetition is sometimes referred to as the repetition level or CE level. Such techniques of CE may find particular application in the framework of the loT technology, e.g., according to 3GPP MTC or NB-loT. Here, typically, the transmitting UE implements a comparably low transmit power. Due to the multiple repetitions of the message, nonetheless, a sufficiently high likelihood of successfully receiving the message is provided for. The repetitions of CE may employ a frequency hopping pattern. This facilitates diversity.

The techniques described herein generally relates to scheduling of the transmission. Scheduling of the transmission may be implemented by a scheduler; typically, the scheduler is a function implemented at the BS. Scheduling may include reserving one or more time-frequency resource elements for a given transmission such that collision with other transmissions is avoided. This corresponds to allocating the one or more PREs to a given UE.

Often, PREs are allocated in groups of PRBs. A group of PRBs is referred to as resource block group (RBG). Typically, a PRB includes a number of PREs. Each PRE may be defined by a subcarrier of a carrier, e.g., according to a Orthogonal Frequency Division Multiplex (OFDM) modulation scheme; and/or may be defined in terms of a symbol of a certain duration.

According to examples, as transmission associated with IOT traffic and non-IOT traffic is scheduled by the same BS. Typically, the demands in terms of latency, contiguous channel access, etc.. are different for the IOT traffic and the non-IOT traffic. Also, the format of scheduling information used for a transmission of IOT traffic and a transmission of non-IOT traffic can be different. Hereinafter, techniques are described which help to balance such different needs of transmissions associated with IOT traffic and non-IOT traffic.

According to various examples, scheduling information is communicated. The scheduling information is for a transmission on a plurality of PRBs. Then, the transmission is blocked on at least one forbidden PRB which is included in the plurality of PRBs. This is based on a respective control information. Specifically, the transmission may be blocked by a UE, e.g., an IOT UE.

The at least one forbidden PRB may be a subset of the plurality of PRBs. Hence, the transmission may be partly blocked. In some examples, it would even be possible that the transmission is fully blocked for a certain time duration if the forbidden PRBs extend across the entire bandwidth allocated to the transmission.

By blocking the transmission in the at least one forbidden PRB, ambiguities due to different formats of scheduling information can be resolved. Specifically, overlaps due to different granularity of the scheduling information used for transmission on a subband and outside of the subband can be resolved. This helps to avoid transmission errors. Furthermore, spectral usage can be increased, because headroom to accommodate for potential ambiguities may be minimized or completely avoided. Further, in an associated blocking time duration, the BS can schedule another transmission. This gives the BS flexibility in scheduling transmissions of, e.g., IOT traffic and non-IOT traffic.

In detail, blocking the transmission at the UE facilitates puncturing the transmission at the BS. In other words, where the UE blocks the transmission in one or more forbidden PRBs, this facilitates insertion of a further transmission by puncturing the transmission. For example, the puncturing may facilitate interleaving a first transmission of IOT traffic and a second transmission of non-IOT traffic. The second transmission may have a shorted transmission duration; and may therefore be inserted into the blocking time duration when puncturing.

According to examples, a first transmission is scheduled between a BS and a first UE. The first transmission is then punctured on the at least one forbidden PRB. A second transmission is scheduled between the BS and a second UE - that may be different from the first UE - on the at least one forbidden PRB.

<FIG> schematically illustrates a wireless communication network <NUM> that may benefit from the techniques disclosed herein. The network may be a 3GPP-standardized cellular network such as <NUM>, <NUM>-LTE, or upcoming <NUM>-NR. Other examples include point-to-point networks such as Institute of Electrical and Electronics Engineers (IEEE)-specified networks, e.g., the <NUM>. 11x Wi-Fi protocol or the Bluetooth protocol. The network <NUM> may provide for IOT functionality including 3GPP NB-IOT or eMT, feMTC, efeMTC, etc..

The network <NUM> includes a BS <NUM> and a UE <NUM>. A wireless link <NUM> is established between the BS <NUM> and the UE <NUM>. The wireless link <NUM> includes a DL link from the BS <NUM> to the UE <NUM>; and further includes an UL link from the UE <NUM> to the BS <NUM>. Time-division duplexing (TDD), frequency-division duplexing (FDD), space-division duplexing (SDD), and/or code-division duplexing (CDD) may be employed for mitigating interference between UL and DL. Likewise, TDD, FDD, SDD, and/or CDD may be employed for mitigating interference between multiple UEs communicating on the wireless link <NUM> (not shown in <FIG>). For this, the BS <NUM> implements scheduling functionality.

The UE <NUM> may be one of the following: a smartphone; a cellular phone; a table; a notebook; a computer; a smart TV; an MTC device; an eMTC device; an loT device; an NB-IoT device; a sensor; an actuator; a non-IOT UE; an IOT UE; etc..

<FIG> schematically illustrates aspects with respect to the wireless communication network <NUM>. Here, different types of UEs <NUM>-<NUM> are connected to the BS <NUM>. For example, non-IOT UEs <NUM>, <NUM> are connected to the BS <NUM>. Also, IOT UEs <NUM>, <NUM> are connected to the BS <NUM>.

Typically, the receiver bandwidth of the IOT <NUM>, <NUM> is smaller than the receiver bandwidth of the non-IOT UEs <NUM>, <NUM>. Therefore, the IOT UEs <NUM>, <NUM> communicate on a subband of the carrier supported by the BS <NUM>; while the non-IOT UEs <NUM>, <NUM> can communicate across the entire bandwidth of a carrier supported by the BS <NUM>.

Typically, IOT UEs <NUM>, <NUM> and non-IOT UEs <NUM>, <NUM> are scheduled using scheduling information of different format. For example, different groupings of PRBs into RBGs may be employed for the IOT UEs <NUM>, <NUM> and the non-IOT UEs <NUM>, <NUM>.

<FIG> schematically illustrates the BS <NUM> and the UE <NUM> in greater detail.

The BS <NUM> includes a processor (CPU) <NUM> and an interface (IF) <NUM>, sometimes also referred to as frontend. The IF <NUM> includes a receiver and a transmitter. The BS <NUM> further includes a memory (MEM) <NUM>, e.g., a non-volatile memory. The memory may store program code that can be executed by the processor <NUM>. Thus, the processor <NUM> and the memory <NUM> form a control circuitry. Executing the program code may cause the processor <NUM> to perform techniques with respect to: scheduling multiple UEs <NUM>-<NUM> on the wireless link <NUM>; implementing transmission on a subband of a carrier; implementing transmission on a carrier; puncturing a transmission; etc..

The UE <NUM> includes a CPU <NUM> and an IF <NUM>, sometimes also referred to as frontend. The IF <NUM> includes a receiver and a transmitter. The UE <NUM> further includes a MEM <NUM>, e.g., a non-volatile memory. The memory <NUM> may store program code that can be executed by the processor <NUM>. Thus, the processor <NUM> and the memory <NUM> form a control circuitry. Executing the program code may cause the processor <NUM> to perform techniques with respect to: receiving scheduling information for a transmission on the wireless link <NUM>; implementing the transmission on a subband of a carrier; implementing the transmission on the carrier; blocking a transmission; etc..

While in <FIG> the UE <NUM> is shown for illustrative purpose, a similar configuration may be provided for the UE <NUM>-<NUM>. For example, the capability of the interface <NUM> of the UEs <NUM>, <NUM> may be limited if compared to the capability of the interface <NUM> of the UEs <NUM>, <NUM>, e.g., in terms of transmission bandwidth, etc..

<FIG> schematically illustrates aspects with respect to communicating scheduling information <NUM>. The scheduling information <NUM> is transmitted, at <NUM>, by the BS <NUM> and received by the UE <NUM>. The scheduling information <NUM> is for a transmission <NUM> on a plurality of PRBs. As such, the scheduling information <NUM> can be according to a predefined format which maps one or more indicators included in the scheduling information <NUM> - e.g., a scheduling bitmap - with the plurality of PRBs. For example, a DCI can be used.

The scheduling information <NUM>, in the scenario of <FIG> is for a DL transmission <NUM> of data <NUM> at <NUM>, e.g., application data or higher-layer control data.

For example, the DL transmission <NUM> can be on a physical DL shared channel (PDSCH).

The DL transmission <NUM> can include multiple repetitions of data, i.e., according to a CE technique (not illustrated in <FIG>).

The scheduling information <NUM> could also be for UL transmission of data, cf.

<FIG> schematically illustrates aspects with respect to communicating scheduling information <NUM>. The scheduling information <NUM> is transmitted, at <NUM>, by the BS <NUM> and received by the UE <NUM>. The scheduling information <NUM> is for a transmission <NUM> on a plurality of PRBs. As such, the scheduling information <NUM> can be according to a predefined format which maps one or more indicators included in the scheduling information <NUM> - e.g., a scheduling bitmap - with the plurality of PRBs.

For example, the scheduling information <NUM> can be transmitted on a physical DL control channel (PDCCH).

The scheduling information <NUM>, in the scenario of <FIG> is for an UL transmission <NUM> of data <NUM> at <NUM>, e.g., of application data or higher-layer control data.

For example, the UL transmission <NUM> can be on a physical UL shared channel (PUSCH).

For example, the UL transmission <NUM> can include multiple repetitions of data, i.e., according to a CE technique (indicated by the multiple arrows in <FIG>). The count of repetitions can be determined based on a CE level. The CE level may define a baseline count. The CE level also correlates with a time duration <NUM> required to complete the UL transmission <NUM>.

As will be appreciated from the illustration of <FIG>, the transmission of IOT traffic relying on a large CE level can occupy the wireless link <NUM> for a significant transmission time duration <NUM>. This also applies to transmissions of other types of traffic, including, but not limited to: enhanced Mobile Broadband (eMBB) and Ultra Reliable Low Latency Communication (URLLC), see 3GPP Technical Report (TR) <NUM> ver. <NUM>, TR <NUM> ver. URLLC may also rely on multiple repetitions of signals to enhance coverage, similar to the CE technique.

Hereinafter, strategies are described which facilitate fair access to the wireless link <NUM> for, both, transmissions associated with IOT traffic - typically associated with a long channel occupancy associated with the transmission time duration <NUM> - and transmissions associated with non-IOT traffic.

<FIG> schematically illustrates aspects with respect to a time-frequency resource grid <NUM>. The time-frequency resource grid <NUM> is defined across the bandwidth of a carrier <NUM>. The carrier includes multiple subcarriers, e.g., according to OFDM modulation. Symbols are defined in time domain. The symbols and subcarriers define PREs <NUM>, as atomic units that can encode data.

Multiple PREs <NUM> are collected into PRBs <NUM>-<NUM>. Each PRB <NUM>-<NUM> hence includes multiple REs <NUM> (in the non-limiting example of <FIG> there are 2x6=<NUM> REs per PRB. For example, for 3GPP LTE, a PRB consists of <NUM> subcarriers in the frequency dimension and <NUM> OFDM symbols in the time dimension.

Typically, the time-frequency resource grid <NUM> is structured into transmission frames and subframes. Each subframe has a certain duration, e.g., <NUM>. Each subframe includes a certain count of PRBs <NUM>-<NUM> (in <FIG>, only a single instance of PRBs <NUM>-<NUM> is illustrated in time domain for sake of simplicity).

To facilitate low-overhead scheduling, depending on the format of the scheduling information <NUM>, multiple PRBs <NUM>-<NUM> are collected into a RBG. Then, the RBG is the atomic unit that can be individually scheduled.

According to examples, a plurality of PRBs are scheduled for a transmission <NUM>, <NUM>. Hence, scheduling information <NUM> for a transmission <NUM>, <NUM> on the plurality of PRBs is communicated. For example, the scheduling information <NUM> may be indicative of one or more RBGs.

For example, in the scenario of <FIG>, scheduling information for transmission on the PRBs <NUM>-<NUM> in a narrowband <NUM> for IOT UEs <NUM>, <NUM> may be communicated. For example, in MTC CE mode B, for the narrowband <NUM>, <NUM> PRBs or <NUM> PRBs may be scheduled collectively. Then, based on control information, even though the scheduling information covers the PRBs <NUM>-<NUM> of the narrowband <NUM>, the transmission may be blocked for one or more forbidden PRBs <NUM> (dashed line in <FIG>; in <FIG> the PRB <NUM> is a forbidden PRB <NUM>).

Relying on the forbidden PRBs <NUM> helps to provide for flexibility in (I) the format of the scheduling information - which may rely on clustering into RBGs of different granularity for IOT UEs <NUM>, <NUM> and non-IOT UEs <NUM>, <NUM> - and (II) resource-efficient coexistence of non-IOT UEs <NUM>, <NUM> and IOT UEs <NUM>, <NUM> on the carrier <NUM>.

Specifically, the one or more forbidden PRBs <NUM> may facilitate puncturing of the respective transmission <NUM>, <NUM> at the BS <NUM>. In detail, it would be possible that the transmission <NUM>, <NUM> scheduled for the IOT UE <NUM>, <NUM> is punctured at the forbidden PRB <NUM>; the forbidden PRB <NUM> can then be used for a further transmission <NUM>, <NUM> between the BS <NUM> and a further UE <NUM>, <NUM>.

These findings are explained in greater detail hereinafter with respect to some example implementations.

For example, eMTC - e.g., used for the IOT UEs <NUM>, <NUM> - operates in a small bandwidth of <NUM> PRBs (<NUM> × <NUM> subcarriers or <NUM>. Here, <NUM> x <NUM> = <NUM> and some extra bandwidth is required for filtering, signal roll-off etc., leading to an overall signal bandwidth of <NUM>. The <NUM> PRBs form a subband (also known as narrowband) for eMTC. For example, the subbands <NUM> and <NUM> are illustrated in <FIG>. The subbands <NUM>, <NUM> have a smaller bandwidth if compared to the <NUM> bandwidth of an LTE non-IOT carrier <NUM>. This smaller bandwidth reduces the complexity of the RF front end of the UE <NUM>, <NUM> and hence reduces its cost.

The LTE carrier <NUM> is therefore divided into multiple non-overlapping subbands <NUM>, <NUM> for eMTC operations. The LTE system bandwidths of the carrier <NUM> are <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> which contain <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> PRBs in the frequency domain respectively.

With the exception of <NUM>, the total number of PRBs in a system bandwidth often cannot be divided equally into subbands that consist of <NUM> PRBs. The remaining PRBs are distributed such that the top and bottom parts of the system bandwidth of the carrier <NUM> contain equal numbers of PRBs and if there is an odd number of remaining PRBs, one PRB is placed in the middle of the system bandwidth. For example, a <NUM> PRB system bandwidth (<NUM>) can fit two full subbands leaving <NUM> PRBs <NUM>, <NUM>, <NUM> unused as shown in <FIG>. For these remaining PRBs <NUM>, <NUM>, <NUM>, one unused PRB <NUM>, <NUM> is put in both ends of the system bandwidth and the remaining PRB <NUM> is inserted in the middle of the system bandwidth. The PRBs <NUM>-<NUM> are allocated to the subband <NUM>; and the PRBs <NUM>-<NUM> are allocated to the subband <NUM>.

In LTE, the scheduling information for a DL transmission often uses a resource allocation format <NUM>. Here, the system bandwidth of the carrier <NUM> is divided into RBGs, where each RBG consists of NRB PRBs. An RBG is the granularity of resource allocation for PDSCH/PUSCH, that is the DL/UL resources are allocated in number of RBGs for a UE. The value NRB is dependent upon the system bandwidth and is summarized in Table <NUM>.

An example is shown in <FIG> for a <NUM> carrier <NUM> including <NUM> PRBs <NUM>-<NUM>. Here the <NUM> PRBs <NUM>-<NUM> are divided into <NUM> RBGs <NUM>-<NUM>, where <NUM> of these RBGs <NUM>-<NUM> are <NUM> PRBs wide, for example RBG <NUM> consists of PRB <NUM>, <NUM>, <NUM>. The last RBG <NUM> is <NUM> PRBs wide, PRBs <NUM>, <NUM>.

In 3GPP R1-<NUM>, it is observed that the RBG in the LTE band defined across the carrier <NUM> and the subbands <NUM>-<NUM> of eMTC are not aligned. For example, in <FIG>, the subbands <NUM> - <NUM> are arranged in the bandwidth of the carrier <NUM> such that they are centered with the two unused PRBs <NUM>, <NUM> placed at both edges of the carrier <NUM>. It can be observed that the RBGs <NUM>-<NUM> and subbands <NUM>-<NUM> are not PRB aligned, i.e. they do not start from the same PRB <NUM>-<NUM>.

A consequence of this misalignment between RBG <NUM>-<NUM> and the subbands <NUM>-<NUM> is that in a system that supports both LTE and eMTC - or, generally, transmissions of IOT traffic and non-IOT traffic which is scheduled differently, e.g., using different formats of the scheduling information - RBGs <NUM>-<NUM> that overlap with a used subband <NUM> -<NUM> cannot be scheduled for the non-IOT UEs <NUM>, <NUM>.

This is illustrated in <FIG>. Here, subband <NUM> is scheduled and is allocated to PRBs <NUM>-<NUM>. As described previously, RBG is the smallest granularity for PDSCH scheduling of the non-IOT UEs <NUM>, <NUM> and it can be observed that since PRBs <NUM>, <NUM> are used for the subband <NUM> for scheduling IOT UEs <NUM>, <NUM>, RBG <NUM> - including these PRBs <NUM>, <NUM> - cannot be used for scheduling non-IOT UEs <NUM>, <NUM>; thus, PRB <NUM> cannot be used by non-IOT UEs <NUM>, <NUM>. Similarly, PRB <NUM> is occupied by the subband <NUM> which prevents the usage of RBG <NUM> - despite the majority of RBG <NUM> PRBs - PRBs <NUM>, <NUM> - being outside the subband <NUM>. This leads to degradation in the cell throughput/spectral efficiency for the LTE system.

3GPP LTE MTC rel. <NUM> scope has been updated to include the support for more flexible starting PRB for PDSCH/PUSCH resource allocation in connected mode at least for UE operating in CE mode A/B configured with <NUM> max MTC channel bandwidth. See 3GPP RP-<NUM>.

Hereinafter, techniques are described which facilitate reducing unused PRBs, specifically in the aforementioned configurations. Thus, spectral utilization can be high when employing the techniques described herein.

For illustrative purposes, it is assumed that the IOT UE <NUM> is allocated to use subband <NUM>. Due to the need of extended coverage operation, that IOT UE <NUM> has also been allocated to transmit with N-times repetitions, i.e., CE technique with a CE level of N. There are also other non-IOT UEs <NUM>, <NUM> in the cell scheduled by the same BS <NUM> that can use any PRBs <NUM>-<NUM>, provided those PRBs are allocated in units of RBG, including for example RBG <NUM>, <NUM>, <NUM>.

In conventional scenarios, the non-IOT UEs <NUM>, <NUM> would be prevented from using PRBs <NUM>, <NUM>, <NUM>, because they are part of a RBG <NUM>, <NUM> which have some overlap with the subband <NUM>. For example, the PRBs <NUM>, <NUM> cannot be individually addressed without the PRB <NUM>, because all PRBs <NUM>-<NUM> are part of the collective RBG <NUM>. Thus, any scheduling of a non-IOT UE <NUM>, <NUM> using scheduling information indicative of allocation of the RBG <NUM> would lead to potential collision with the IOT UE <NUM> on the PRB <NUM>.

To avoid this, control information on forbidden PRBs <NUM> is used. The IOT UE <NUM> scheduled on the subband <NUM> blocks transmission on the forbidden PRBs <NUM>. In the example of <FIG>, the forbidden PRBs <NUM> are the PRBs <NUM>, <NUM> and <NUM>.

Because the IOT UE <NUM> blocks the transmission on the forbidden PRBs <NUM>, the RBGs <NUM>, <NUM> can be safely used for scheduling any non-IOT UE <NUM>, <NUM>. Thus, the transmission between the BS <NUM> and the IOT UE <NUM> is punctured by means of the forbidden PRBs <NUM>; the forbidden PRBs <NUM> are used for scheduling a further transmission between the BS <NUM> and one or more non-IOT UEs <NUM>, <NUM>.

As a general rule, there are different options available for blocking the transmission on any forbidden PRBs <NUM>. In one example, the respective UE <NUM>-<NUM> may refrain from using such forbidden PRBs <NUM>, even though scheduling information was received schedules a plurality of PRBs - e.g., a RBG - including one or more forbidden PRBs <NUM>. For example, respective data - otherwise allocated to a forbidden PRB - may be redistributed to a non-forbidden PRB. This may include extending the transmission in time domain and/or frequency domain. In one example, blocking can include suspending the transmission in accordance with any forbidden PRBs <NUM>. When blocking, transmitting and/or receiving on any forbidden PRBs <NUM> may be paused. For example, a transmission buffer - e.g., an HARQ buffer - may be persevered and maintained, and may not be flushed. Then, the transmission can be resumed once blocking is deactivated. The scheduling information <NUM> is for a plurality of PRBs which include one or more forbidden PRBs. For example, the scheduling information <NUM> may collectively allocate the plurality of PRBs to the respective UE <NUM>-<NUM>. Then, by means of the control information the allocation on the one or more forbidden PRBs <NUM> may be overridden, as part of said blocking.

As a general rule, the control information may specify whether blocking is to be implemented by suspending and resuming the transmission, including maintaining the transmission buffer; or by re-starting the transmission. Re-starting the transmission may include terminating the transmission which may include flushing the transmission buffer, re-initializing counters and/or timers, e.g., of a HARQ protocol, etc.. For example, the selection between (I) suspending and resuming and (II) re-starting the transmission may be based on a latency of the associated traffic. There may be a tendency to select re-starting the transmission for low-latency traffic. For example, the network may provide DL control signaling to instruct the selection between (I) suspending and resuming; and (II) re-starting the transmission. In other scenarios, this selection may be taken by the UE. There may also be a negotiation of this selection between UE and network.

In some examples, one or more forbidden PRBs <NUM> may be fixedly configured at the respective UE <NUM>-<NUM>. In further examples, the BS indicates one or more forbidden PRBs <NUM> to the UE <NUM>-<NUM>. The respective UE <NUM>-<NUM> may receive a DL configuration control message indicative of the control information on the one or more forbidden PRBs <NUM>. The DL configuration control message may be transmitted by the respective BS <NUM> scheduling. The DL configuration control message can enable to the BS <NUM> to puncture the respective transmission, to thereby accommodate for a further transmission. Thus, the DL control information may be referred to as pre-emption indication. The DL configuration control message helps to align puncturing of the transmission at the BS.

For example, the DL configuration control message may be an RRC control message. The DL configuration control message may be communicated separately from the scheduling information. Such indication of the control information can be explicit or implicit. For example, the respective UE <NUM>-<NUM> can be informed that blocking functionality is to be applied and the UE <NUM>-<NUM> then understands that any PRBs <NUM>-<NUM> within a subband <NUM>-<NUM> that are part of an RBG <NUM>-<NUM> that partially overlaps the subband <NUM>-<NUM> are invalid. For example, if the IOT UE <NUM> is allocated on subband <NUM>, the UE <NUM> can determine that PRBs <NUM>, <NUM>, <NUM> are forbidden PRBs <NUM>.

Hence, where the transmission is on a subband <NUM>-<NUM> of the carrier <NUM>, the one or more forbidden PRBs <NUM> can be associated with a RBG <NUM>-<NUM> which has an overlap with a part of the carrier <NUM> that is outside the subband <NUM>-<NUM> (in <FIG>, the overlap <NUM> is illustrated for the RBGs <NUM>, <NUM> associated with the subband <NUM>). Thus, the overlap <NUM> affects a further transmission which is across the carrier <NUM>.

Here, it is not mandatory that scheduling information is used for scheduling on the subbands <NUM>-<NUM> which has a format that also relies on the same RBGs <NUM>-<NUM> that are used by the scheduling information used for scheduling on the carrier <NUM>.

As a general rule, different criteria can be applied to conclude from an overlap <NUM> on which PRB(s) are to be implemented as forbidden PRB(s) <NUM>. For example, if there is an overlap <NUM> for a RBG <NUM>-<NUM>, then any PRBs <NUM>-<NUM> of the respective RBG <NUM>-<NUM> may be blocked.

In some examples, the transmission may be blocked fully or partly if the overlap <NUM> is larger than a predefined threshold. For example, the threshold may be <NUM>%. In the example of <FIG>, the overlap <NUM> for the RBG <NUM> is <NUM>/<NUM>=<NUM>%; hence, below the threshold. Then, the PRBs <NUM>, <NUM> of the RBG <NUM> may not be blocked. Differently, the overlap <NUM> for the RBG <NUM> is <NUM>/<NUM>=<NUM>%; hence, above the threshold. Then, the PRB <NUM> of the RBG <NUM> may be blocked. By relying on the threshold comparison, a fair balance between transmissions of IOT traffic and non-IOT traffic can be achieved.

The threshold may be indicated in DL control signaling or may be fixedly set.

The BS <NUM> can also indicate additional resources to compensate for any forbidden PRB <NUM>. This is illustrated in <FIG>.

<FIG> schematically illustrates allocated resources as a function of time for a transmission <NUM>, <NUM>. In <FIG> it is illustrated that forbidden PRBs <NUM> are defined. Thus, to compensate for the resources lacking due to the forbidden PRBs <NUM>, the baseline time duration <NUM> for which resources are scheduled is extended by an extension time duration <NUM>. For example, the baseline time duration <NUM> can correspond to the transmission time duration <NUM> in a conventional scenario. The extension time duration <NUM> can be considered by the scheduler at the BS <NUM>. The extension time duration <NUM> extends the duration of the transmission <NUM>, <NUM>.

The extension time duration <NUM> may be explicitly or implicitly indicated in the scheduling information <NUM>; in some examples, it would also be possible that the extension time duration <NUM> is not indicated by the scheduling information <NUM>, but rather derived by the BS <NUM> and the scheduled UE <NUM>-<NUM> from the control information used for determining the one or more forbidden PRBs <NUM>. For example, the extension time duration <NUM> can be determined based on the count of forbidden PRBs <NUM>. Then, the extension time duration <NUM> can extend the baseline time duration <NUM> that is defined by the scheduling information <NUM>.

For example, in a CE framework, the extension time duration <NUM> can be used to accommodate for additional repetitions of the signal. The additional repetitions can compensate for the reduced bandwidth due to the forbidden PRB(s) <NUM>.

For example, where a CE technique is employed, the count of the multiple repetitions of the data can be determined depending on a count of the forbidden PRBs <NUM>. Based on the repetition rate of the multiple repetitions, it is then possible to conclude back on the extension time period <NUM>.

There may be a tendency that for a larger count of forbidden PRBs <NUM> the count of repetitions of the CE technique is increased. For example, a respective mapping may be indicated in a corresponding DL control signaling. The mapping may be between the count of the forbidden PRBs <NUM> and the count of the repetitions. The mapping can then be used to determine the count of repetitions.

In detail, a so-called "additional repetitions" factor can be defined. The additional repetitions factor may determine the extension count of repetitions - associated with the extension time duration <NUM> - which are defined beyond a baseline count of repetitions - associated with the baseline time duration <NUM>. Typically, the baseline count of repetitions is determined based on a signal quality of the transmission, e.g., a receive signal strength, a bit error rate, etc..

As a general rule, there are various approaches available as to how the IOT UE <NUM>, <NUM> can determine the additional repetitions factor:
In one example, the additional repetitions factor is predefined, e.g., hardcoded according to a ruleset. The IOT UE <NUM>, <NUM> may then determine which additional repetitions factor to apply based on either: (I) There is a mapping between the number of forbidden PRBs <NUM> and the additional repetition factor; and/or (II) the IOT UE <NUM>, <NUM> is signaled an index of the additional repetitions factor to apply, e.g., in the DCI that schedules the IOT UE <NUM>, <NUM> with the subband <NUM>-<NUM> that is afflicted with the forbidden PRBs <NUM>. The IOT UE <NUM>, <NUM> can determine these additional repetitions by taking into account the percentage of forbidden PRBs <NUM>. For example, an IOT UE <NUM>, <NUM> is allocated <NUM> PRBs and <NUM> repetitions (baseline count). The BS <NUM> signals that one PRB - out of the <NUM> PRBs - is a forbidden PRB <NUM>. e.g., from RRC DL control signaling or DCI. Then, the IOT UE <NUM>, <NUM> can determine the additional repetition factor as [<NUM>/<NUM>×<NUM>]=<NUM>. That is, the IOT UE <NUM>, <NUM> extends its repetition from <NUM> (baseline count) to <NUM> using an extended count of <NUM> to compensate for the resources that were lost due to the forbidden PRB <NUM>.

The above information can be signaled to the IOT UE <NUM>, <NUM> via DCI or high-layer control signaling, e.g., RRC.

In <FIG>, the additional resources in the extension time duration <NUM> are directly adjacent to the original resources. In <FIG>, there is a gap <NUM> between the baseline time duration <NUM> and the extension time duration <NUM>. For example, the legacy N repetitions of the data and the extension repetitions are separated by the gap <NUM>. In the various examples described herein, such a gap <NUM> may be employed or not employed.

In the examples of <FIG>, the blocking <NUM> is activated throughout the transmission <NUM>, <NUM>. As a general rule, the blocking can be statically activated; the blocking, alternatively, could be dynamically activated and deactivated.

In one example, at least one DL activation control message may be communicated, i.e., transmitted by the BS <NUM> and/or received by the respective UE <NUM>-<NUM>. Blocking may be activated and/or deactivated depending on the at least one DL activation control message.

In one example, the DL activation control message may be indicative of a time duration during which said blocking is activated and/or deactivated. Hence, the puncturing of the transmission <NUM>, <NUM> at the BS <NUM> can be in accordance with the DL activation control message.

The DL activation control message may be generally communicated prior or after commencing the transmission <NUM>, <NUM> to be partly blocked and punctured. For example, the transmission <NUM>, <NUM> may commence and then, after commencing, the DL activation control message can be communicated.

In one example, the BS <NUM> may indicate which portion of the CE repetitions is to be blocked - e.g., sequence numbers associated with the CE repetitions may be indicated during which the blocking is activated. For example, sequence numbers of subframes of a transmission protocol used on the wireless link <NUM> may be indicated. Then, all CE repetitions hosted by these subframes may be blocked.

For example in <FIG>, an IOT UE <NUM>, <NUM> is configured for N repetitions (CE level) of application data on the PUSCH. The DL activation control message <NUM> is indicative of M subframes associated with a blocking time duration <NUM> for which blocking is to be activated on the forbidden PRBs <NUM>; the blocking time duration <NUM> corresponds to a transmission gap. For example, each subframe of the respective transmission protocol may include one or more repetitions of the CE technique.

The IOT UE <NUM>, <NUM> pauses its PUSCH transmission during these M subframes during the blocking time duration <NUM>. The IOT UE <NUM>, <NUM> then extends its repetition for the extension time duration <NUM> to compensate for the interrupted repetitions. In <FIG>, the one or more forbidden PRBs <NUM> do not extend across the entire bandwidth allocate to the transmission <NUM>, <NUM>; e.g., the bandwidth allocated to the transmission <NUM>, <NUM> may be defined by a respective subband <NUM>-<NUM> in an IOT scenario. In <FIG>, hence, the transmission <NUM>, <NUM> is partly blocked by the respective UE.

In <FIG> a scenario is illustrated for a larger amount of forbidden PRBs <NUM> where the entire transmission is interrupted. Here, the forbidden PRBs <NUM> cover the entire bandwidth of the transmission <NUM>, <NUM>. In <FIG>, the transmission <NUM>, <NUM> is hence fully blocked. As a general rule, in the various examples described herein, the transmission <NUM>, <NUM> may be full or partly blocked.

In the example of <FIG>, two DL activation control messages <NUM>, <NUM> are communicated from the BS <NUM> to the IOT UE <NUM>, <NUM>. The initial DL activation control message <NUM> is indicative of activation of blocking. The subsequent DL activation control message <NUM> is indicative of deactivation of blocking. This DL activation control message <NUM> hence acts to resume the previous PUSCH transmission of the IOT UE <NUM>, <NUM>.

As a general rule, in the various examples described herein, it is not mandatory to resume the previous transmission. Rather, a selection between (I) resuming the transmission; and (II) re-starting the transmission may be made. This selection may be made by the UE and/or the network. For example, this selection may be instructed by the network; or may be negotiated between the UE and the network. In some examples, it would be possible that one or more DL activation control messages (e.g., in <FIG> the DL activation control message <NUM> and/or the DL activation control message <NUM>; or DL activation control message <NUM> in <FIG>, etc.. ) and / or one or more DL configuration control messages are used to indicate whether, after the blocking time duration <NUM>, the previous transmission is to be resumed; or whether, after the blocking time duration <NUM>, the previous transmission is not be resumed, but rather restarted. Such re-starting may include a termination of the transmission. The termination may include buffer flushing, re-initializing of a HARQ protocol be re-initializing one or more counters and/or timers, etc..

In the example of <FIG>, the DL activation control message <NUM> is indicative of a repetitive schedule of said activating and deactivating of said blocking. Hence, a discontinuous transmission (DTX) schedule can be implemented. By means of a single DL activation control message <NUM>, blocking can be activated and deactivated multiple times; thus, multiple blocking time durations <NUM> are defined. This gives the BS <NUM> flexibility to schedule data for non-IOT UEs <NUM>, <NUM>. Using the DTX schedule helps to puncture the transmission <NUM>, <NUM> multiple times at the BS <NUM>.

As a general rule, the DTX schedule may be periodic or non-periodic. The DTX schedule may include a repetition of ON durations and OFF durations. These repetitions may be arranged periodically or non-periodically, with variable periodicity, etc..

As used herein, the DTX schedule can be applied for puncturing an UL transmission and/or a DL transmission. The DTX schedule may affect receiving and/or transmitting. Sometimes, DTX in connection with receiving is referred to as discontinuous reception (DRX), which is a special form of DTX described herein.

In the examples of <FIG>, while activating said blocking during the blocking time durations <NUM>, the IOT UE <NUM>, <NUM> can terminate transmission - but may not flush its HARQ buffer. This enables the IOT UE <NUM>, <NUM> to resume transmission when deactivating said blocking, e.g., after lapse of a blocking time duration <NUM> and/or upon receiving the DL activation control message <NUM>. In general terms, the transmission can be started, e.g., with deactivated blocking. The, when activating said blocking, the transmission is suspended on any forbidden PRB <NUM>. Upon deactivating said blocking, the transmission on the forbidden PRB(s) <NUM> is resumed. The transmission buffer may be maintained between said suspending and said resuming. Data scheduled for transmission on any forbidden PRB <NUM> may thereby be kept in the transmission buffer. This facilitates low-latency transmission.

This is explained in connection with <FIG>. For example, the IOT UE <NUM> is given an UL grant to transmit a PUSCH with N repetitions - which corresponds to the baseline time duration <NUM>. During its transmission, the BS <NUM> indicates using the DL activation control message <NUM> - e.g., implemented using a DCI - that the IOT UE <NUM> should suspend the transmission, but not flush its HARQ buffer after K repetitions. The BS <NUM> may then schedules other non-IOT UEs <NUM>, <NUM> for M maximum transmissions duration time. After some time, the MTC UE receives DL activation control message <NUM> which tells the IOT UE <NUM> to resume its previous PUSCH transmission using L repetitions. The value L can be N-K, but this need not be the case since typically repetitions in CE are assigned in powers of twos {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc}. It should also be appreciated that the BS <NUM> can also send a DCI for a new PUSCH transmission instead of resuming the previous transmission, which also implicitly indicates to the UE to flush its pervious PUSCH HARQ buffer.

As will be appreciated from the example of <FIG>, generally, - where the transmission <NUM>, <NUM> includes multiple repetitions - the blocking using the one or more forbidden PRBs <NUM> may occur in-between the multiple repetitions.

<FIG> illustrate details of scheduling a first transmission <NUM>, <NUM> and scheduling a second transmission <NUM> (filled areas in <FIG>) in accordance with a DTX schedule. The first transmission is punctured by means of the DTX schedule defining the blocking time intervals <NUM>.

For example, the transmission <NUM>, <NUM> may be for N repetitions on PDSCH or PUSCH. Gaps of length Mk, for the k-th gap, are used for puncturing the PDSCH/PUSCH transmission <NUM>, <NUM>. Here, a targeted repetition of N is scheduled by using respective scheduling information transmitted to the UE <NUM>, <NUM>; by overriding the scheduling information in accordance with the control information indicated by the DL configuration control message <NUM>, the UE <NUM>, <NUM> uses the DTX schedule to repeatedly block the transmission <NUM>, <NUM>. This results in the extension duration <NUM>. The extension duration <NUM> can be larger than the sum of all blocking durations <NUM>.

This allows the BS <NUM> to puncture the transmission <NUM>, <NUM> by scheduling another transmission <NUM> within the blocking time durations <NUM>.

Such techniques are not restricted to a specific kind and type of transmission <NUM>, <NUM>, <NUM>. For example, eMTC using CE may be used for the transmission <NUM>, <NUM>, but generally various use cases are conceivable where two or more transmission <NUM>, <NUM> and <NUM> of different durations need to share partially or fully their resources. An example of such transmission can be found in NR where a long transmission such as eMBB is pre-empted by a shorter transmission such as URLLC where the transmission cannot tolerate any latency and needs to be very reliable. During the blocking time durations <NUM>, the BS <NUM> can schedule a legacy LTE RB or in the NR scenario, the gNB can schedule URLLC during the gaps in an eMBB transmission.

The DTX schedule can be RRC configured, using the DL configuration control message. Blocking, in accordance with the DTX schedule and at the respective UE <NUM>-<NUM>, can be activated and deactivated in accordance with the DL activation control message, e.g., implemented using DCI. Hence, the respective UE <NUM>-<NUM> can be firstly RRC configured with a DTX schedule, but the respective UE <NUM>-<NUM> will not use this DTX schedule for blocking transmission, unless indicated by the DL activation control message <NUM>. This DL activation control message <NUM> can occur prior to the transmission <NUM>, <NUM> as shown in <FIG>, e.g., in the form of an UL/DL grant. Alternatively, the DL activation control message can occur during the transmission <NUM>, <NUM> as shown in <FIG>, e.g., in the form of an pre-emption indicator.

The DTX schedule can be configured only for a subset of frequency and time resources, or generally PRBs. That is, the UE <NUM>, <NUM> will only activate blocking the transmission <NUM>, <NUM> in accordance with the DTX schedule for a certain time duration, until a temporal validity of the DTX expires. This is beneficial for example if a corresponding subset of resources within the temporal validity is used for UL grant-free transmission. For example, the transmission <NUM> can be UL grant-free transmission. In 3GPP NR, UL grant free transmission is typically used for URLLC; here, a UE <NUM>, <NUM> can transmit a URLLC whenever it arrives without request for UL resources from the BS <NUM>. Hence, if an eMBB transmission <NUM>, <NUM> of the IOT UE <NUM>, <NUM> overlaps these grant free resources either partially or fully, the IOT UE <NUM>, <NUM> can block transmission in a accordance with the DTX schedule to facilitate co-scheduling of the UL grant-free transmission <NUM>.

A plurality of DTX schedules can be configured using the DL configuration control message. The DL configuration control message can be indicative of control information on multiple candidate DTX schedules. Each candidate DTX schedule may define different forbidden PRBs <NUM>. Then, to activate a selected one of the plurality of candidate DTX schedules, the DL activation control message can be transmitted. The DL activation control message can be indicative of a selected one of the candidate DTX schedules and can activate blocking of the transmission on one or more forbidden PRBs <NUM> defined by the selected candidate DTX schedule. This activation can occur prior to or after commencing of the transmission.

As a general rule, the DTX schedule can be uniform, instead of the irregular pattern shown in <FIG>. The blocking durations <NUM> can be of equal lengths. A constant periodicity may be employed. An example is shown in <FIG>, where the blocking time durations <NUM> are all of the same size and a fixed periodicity is employed. A uniform DTX pattern can be beneficial for the scheduler in scheduling LTE RBs or URLLC within the gaps of an existing transmission.

The DTX schedule may define full or partial blocking. Thus, during the blocking time durations <NUM> not all PRBs of the transmission <NUM>, <NUM> may be blocked, as shown in an example in <FIG>. Here, the forbidden PRBs <NUM> may change from period to period of the DTX schedule. This is beneficial if the PDSCH/PUSCH transmission overlaps part of an LTE's RBG or in the eMBB case, it partially overlaps a grant free resource region.

<FIG> is a flowchart of a method according to various examples. For example, the method according to <FIG> may be executed by the control circuitry <NUM>, <NUM> of the BS <NUM>.

At block <NUM>, a first transmission is scheduled between the BS and a first UE. For example, the first transmission could be associated with IOT traffic. For example, the first transmission could be implemented according to the eMBB protocol, the URLLC protocol, and/or employ CE using multiple repetitions.

Scheduling the first transmission can include transmitting scheduling information for the first transmission. The scheduling information can be indicative of a plurality of PRBs allocated to the first transmission. Details of communicating scheduling information and allocation of PRBs, e.g., using a RBG, have been described in connection with <FIG>.

For example, the scheduling information may define a baseline time duration during which PRBs are allocated to the first transmission. The scheduling information may define a baseline count of repetitions for a transmission using CE.

Next, at block <NUM>, the first transmission is punctured. There are various options available for implementing said puncturing. In one example, the first transmission is punctured on at least one forbidden PRB. The at least one forbidden PRB is included in the plurality of PRBs allocated to the first transmission when scheduling the first transmission at block <NUM>. For example, the at least one PRB can be surrounded in time domain and/or frequency domain by non-forbidden PRBs allocated to the first transmission. The at least one PRB may define a blocking time duration during which the UE at least partly blocks the first transmission. Hence, the at least one forbidden PRB can be used otherwise. By relying of the at least one forbidden PRB, the scheduling information - which includes the forbidden PRB - can be overridden.

Specifically, at block <NUM>, a second transmission between the BS and a second terminal is scheduled on the at least one forbidden PRB. Thereby, the second transmission can be surrounded by the first transmission, in time domain and/or frequency domain. The first and second transmission can be arranged interleaved in time domain.

There are various options available to define the at least one forbidden PRB. For example, the puncturing could be in accordance with a DTX schedule which defines the at least one forbidden PRB. Such scenarios have been explained in connection with <FIG>, <FIG>, <FIG>. The at least one forbidden PRB could be set in accordance with control information. The control information may be determined based on an overlap of a PRB group with, both, a subband of a carrier and a part of the carrier which is outside of the subband. In such a scenario, there may be no need to explicitly signal a DL configuration control message which is indicative of the control information. In other scenarios, it would be possible to signal the DL configuration control message to synchronize the at least one forbidden PRB between the BS and the UE.

The puncturing may include activation of the blocking and deactivation of the blocking of the transmission on the at least one forbidden PRB. For this, a DL activation control message may be transmitted by the BS and may be received by the UE. Thereby, said puncturing may be time constrained. The DL activation control message can activate and deactivate the blocking of the transmission at the UE.

In some examples, the puncturing of the first transmission may be in response to detecting an overlap of the first transmission with the second transmission. The overlap may correspond to at least one PRB or PRE which is allocated to, both, the first transmission and the second transmission. This may be judged based on said scheduling of the first transmission and/or said scheduling of the second transmission.

<FIG> is a flowchart of a method according to various examples. For example, the method of <FIG> may be executed by the control circuitry <NUM>, <NUM> of the UE <NUM>-<NUM>.

At block <NUM>, scheduling information is received. As such, block <NUM> can be inter-related to block <NUM>.

The scheduling information can be for a transmission on a plurality of PRBs. For example, the scheduling information may be indicative of the plurality of PRBs by using one or more RBGs.

At block <NUM>, the transmission is blocked on at least one forbidden PRB which is included in the plurality of PRBs associated with the scheduling information. This is based on control information. As such, block <NUM> can be inter-related to block <NUM>.

In order to compensate for any blocked PRBs, the transmission may be extended beyond the plurality of PRBs for which the scheduling information is received at block <NUM>. Hence, beyond the baseline time duration, an extension time duration can be implemented. The extension time duration can be determined, e.g., based on the count of the at least one forbidden PRB.

<FIG> is a signaling diagram illustrating communication between the BS <NUM>, the IOT UE <NUM> and the non-IOT UE <NUM>.

At <NUM>, a DL configuration control message <NUM> is transmitted by the BS <NUM> and received by the UE <NUM>. The DL configuration control message <NUM> is indicative of control information on at least one forbidden PRB <NUM>. For example, the DL configuration control information could be indicative of one or more DTX schedules which define the at least one forbidden PRB. For example, the DL configuration control message <NUM> may be a Layer <NUM> RRC control message.

The DL configuration control message <NUM> is generally optional. IN other scenarios, the at least one forbidden PRB <NUM> may be derived autonomously by the IOT UE <NUM> and the BS <NUM> from a cell configuration, e.g., including subbands and RBGs for scheduling (cf.

Next, at block <NUM>, scheduling information <NUM> is communicated from the BS <NUM> to the UE <NUM>. The BS <NUM> transmits the scheduling information <NUM> at <NUM> and the UE <NUM> receives the scheduling information <NUM> at <NUM>. The scheduling information <NUM> is for an UL transmission <NUM> between the IOT UE <NUM> and the BS <NUM>. As such, the scheduling information <NUM> is indicative of a plurality of PRBs, e.g., by means of one or more PRB groups. The plurality of PRBs is allocated to the UL transmission <NUM>.

At <NUM>, a DL activation control message <NUM> is communicated from the BS <NUM> to the IOT UE <NUM>. The DL activation control message <NUM> activates blocking of the UL transmission <NUM> in the at least one forbidden PRB <NUM>. In some examples, where the DL configuration control message <NUM> is indicative of a plurality of candidate DTX schedules, it would be possible that the DL activation control message <NUM> is indicative of a selected one of the plurality of candidate DTX schedules.

In the scenario of <FIG>, the DL activation control message <NUM> is communicated at <NUM>, i.e., prior to commencing the UL transmission <NUM> at <NUM>. In other scenarios, it would also be possible that the DL activation control message <NUM> is communicated after commencing the UL transmission <NUM> at <NUM>.

Next, at <NUM>, scheduling information <NUM> is communicated from the BS <NUM> to the non-IOT UE <NUM>. The scheduling information <NUM> is for a transmission <NUM> from the BS <NUM> to the UE <NUM>.

The transmission <NUM> is punctured at the BS <NUM> during blocking time durations <NUM>. When puncturing the UL transmission <NUM>, the BS <NUM> can use the respective forbidden PRB <NUM> to implement the DL transmission <NUM> by transmitting data is <NUM> at <NUM> and <NUM>. As illustrated in <FIG>, thereby, the transmission <NUM> and the transmission <NUM> are interleaved in time domain.

Within the block in time duration <NUM>, the UE <NUM> blocks the UL transmission <NUM>, on the forbidden PRBs <NUM> (in the example of <FIG>, for sake of simplicity, a full blocking of the UL transmission <NUM> is illustrated; while, generally, a partial blocking of the UL transmission <NUM> would be possible, e.g., as illustrated in <FIG>).

As illustrated in <FIG>, the UL transmission <NUM> includes multiple repetitions of the data <NUM>. Multiple repetitions are respectively communicated at <NUM>, <NUM>, <NUM>, and <NUM>. For example, each repetition of the data <NUM> may correspond to encoded data according to the same redundancy version. Then, the BS <NUM> can combine each received repetitions on analogue domain in order to achieve CE. Thus, a receive buffer of the BS <NUM> is to be maintained until completion of the transmission <NUM>. As illustrated in <FIG>, some repetitions are arranged prior to the blocking time durations <NUM>, while other repetitions are arranged after the blocking time durations <NUM>.

As a general rule, it is not required in all scenarios that the punctured and blocked transmission includes multiple repetitions. Other long dated transmissions - such as eMBB or URLLC - may also benefit from such approaches.

At <NUM>, a further DL activation control message causing the activation of the blocking is communicated from the BS <NUM> to the IOT UE <NUM>. In response to receiving the DL activation control message <NUM> at <NUM>, the UE <NUM> stops blocking the UL transmission <NUM>.

In order to compensate for the blocking during the blocking time duration <NUM>, an extension count of repetitions of the UL transmission <NUM> is implemented during the extension time duration <NUM>. For example, beyond a baseline count of repetitions - e.g., defined by the CE level of the CE policy, typically under consideration of the signal quality of communicating between the IOT UE <NUM> and the BS <NUM> -, an extension count of repetitions can be determined based on the count of forbidden PRB <NUM> during the blocking time duration <NUM>.

<FIG> schematically illustration aspects with respect to puncturing a first transmission <NUM>, <NUM> on at least one forbidden resource block and scheduling a second transmission <NUM> in accordance with said puncturing. The transmission <NUM>, <NUM> may be an UL transmission or a DL transmission. The transmission <NUM> may be an UL or DL transmission; in the scenario of <FIG>, for sake of simplicity, it is assumed that the transmission <NUM> is an UL transmission.

<FIG> is an example implementation in which the transmission <NUM> includes URLLC which is transmitted using UL grant-free resources. For example, respective scheduling information <NUM> communicated from the BS <NUM> to one or more UEs <NUM>, <NUM>; the scheduling information <NUM> can be indicative of a block of known PREs that are allocated for the transmission <NUM>.

These PREs of the UL transmission <NUM> may not be allocated to only a single UE; i.e., these PREs may not be dedicated resources. Rather, multiple UEs may access the PREs, to increase spectrum utilization. There is no need to explicitly grant an individual UE. This allows the UE <NUM>, <NUM> to transmit UL data on the grant-free resources without a specific scheduling request; the latency is reduced.

The transmission <NUM>, <NUM> includes eMBB. Such transmission is typically grant-based, i.e., individually scheduled by the network.

If the transmission <NUM>, <NUM> overlaps some of the grant-free resources (cf. <FIG>) of the transmission <NUM>, then, if URLLC data is transmitted in the grant-free resources of the transmission <NUM>, it may be interfered by the eMBB data of the transmission <NUM>, <NUM> (the overlap <NUM> is illustrated using a dotted line in <FIG>).

The BS <NUM> may not have a-priori knowledge on when URLLC data will be transmitted in a grant-free PRE of the transmission <NUM>. Hence, by implementing the eMBB transmission <NUM>, <NUM> using a DTX schedule (cf. <FIG>), at least some of the URLLC data of the transmission <NUM> - which is typically repeated for reliability purpose - would not be interfered when it coincides with the DTX gap, i.e., the blocking time duration <NUM> and the one or more forbidden PRBs <NUM>. For URLLC data of the transmission <NUM> which coincides with an ON duration of the DTX schedule, collision with eMBB data of the transmission <NUM>, <NUM> is possible. On average, such puncturing of the transmission <NUM>, <NUM> reduces the interference of the URLLC data in the grant-free transmission <NUM>.

In <FIG>, the transmission <NUM>, <NUM> is scheduled using scheduling information at time t0. For example, the transmission <NUM>, <NUM> can be between UE <NUM> and BS <NUM>.

The transmission <NUM>, <NUM> partially overlaps a set of UL grant-free resources of the transmission <NUM> (the allocated resources are illustrated using the dashed line).

While the UL grant-free resources of the transmission <NUM> are allocated in the time interval t1 - t4, only at time t3, UE <NUM> decides to use these grant-free resource to transmit the URLLC data (full black area in <FIG>). Multiple repetitions of the URLLC data are implemented until time t5.

A DL activation control message <NUM> activates the DTX schedule for the transmission <NUM>, <NUM>, e.g., in DCI. The DL activation control message <NUM> is optional. Generally, the UE <NUM> could be statically configured with the DTX schedule.

In some examples, one or more respective forbidden PRBs may be fixedly configured at the UE <NUM> by provisioning respective control information.

Due to the DTX schedule, not all of the repetitions of the URLLC data are interfered by the transmission <NUM>, <NUM>. In some embodiment, the DTX schedule is only activated if the overlap <NUM> between the transmission <NUM> and the transmission <NUM>, <NUM> is detected.

Summarizing, techniques have been described which rely on control information - e.g., indicated using DL control signaling - which is indicative of one or more forbidden / invalid PRBs. For example, an MTC transmission may thereby be at least partly blocked in accordance with the one or more forbidden PRBs. Then, an LTE or, generally, non-IOT UE may be scheduled on the one or more forbidden PRBs. RBGs can be used to indicate the one or more forbidden PRBs.

According to some aspects, a compensation for the one or more forbidden PRBs can be achieved by defining additional repetitions of a CE technique for the MTC transmission. These additional repetitions may be in addition to a baseline repetition count. The extension count of such additional repetitions may be signaled to the UE using DL control signaling, e.g., using a DL configuration control message or a DL activation control message as explained in connection with the various scenarios herein.

According to some aspects, a terminate and resume indication for the transmission to be blocked is described. A transmission gap results and may be used for scheduling one or more further UEs.

Although the invention has been shown and described with respect to certain preferred embodiments, equivalents and modifications will occur to others skilled in the art upon the reading and understanding of the specification. The present invention includes all such equivalents and modifications and is limited only by the scope of the appended claims.

For illustration, while above various examples have been described with respect to multiple repetitions of data on PUSCH in eMTC using the CE technique, this is applicable to also PDSCH. Generally, various examples described for UL can be applied for DL, as well; and vice versa.

Also, such techniques are readily applicable in any other system where two or more transmission of different durations need to share partially or fully their resources. For example in NR, a long transmission such as enhanced Mobile Broadband (eMBB) with expected <NUM> Gbps throughput is pre-empted by a shorter transmission such as Ultra Reliable Low Latency Communication (URLLC), where the transmission cannot tolerate any latency and needs to be very reliable.

Claim 1:
A method performed by a terminal (<NUM>), comprising:
- receiving, from a base station (<NUM>), a downlink configuration control message (<NUM>) indicative of control information on at least one invalid time-frequency resource block included in a plurality of resource blocks,
- receiving, from the base station, scheduling information (<NUM>) for a transmission (<NUM>, <NUM>) on the plurality of resource blocks (<NUM>-<NUM>),
- receiving, from the base station, a downlink activation control message (<NUM>), and
- upon blocking being activated by the downlink activation control message:
blocking the transmission (<NUM>) on the at least one invalid resource block based on the control information.