Patent Description:
Ultra-reliable and low latency communication (URLLC) is one of the main use cases of Fifth Generation (<NUM>) New Radio (NR) under development by the Third Generation Partnership Project (3GPP). URLLC has strict requirements on transmission reliability and latency, i.e., <NUM>% reliability within <NUM> one-way latency. In NR Release <NUM> (Rel-<NUM>), several new features and enhancements were introduced to support these requirements. In 3GPP Rel-<NUM>, standardization work is focused on further enhancing URLLC system performance as well as ensuring reliable and efficient coexistent of URLLC and other NR use cases. One example scenario is when both enhanced mobile broadband (eMBB) and URLLC wireless devices (WDs) co-exist in the same wireless communication cell. Here, two approaches have been identified to support multiplexing and prioritization.

The first method is based on power control to increase the power of the URLLC to make it more resilient to interference from the eMBB user(s). 3GPP power control for 3GPP Rel-<NUM> WDs are specified in section <NUM>. <NUM> of 3GPP Technical Standard (TS) <NUM>. An advantage of this option is that it does not require any changes in the behavior of the eMBB WD. Hence, this approach works with 3GPP Rel-<NUM> WDs. One disadvantage is that to guarantee the performance of the URLLC WD while being interfered by eMBB traffic, the WD's transmit power spectral density (PSD) may have to be increased significantly. But, for example, WDs not in the close vicinity of the base station may not have the power budget to perform this increase and will therefore experience much lower signal to interference plus noise ratio (SINR) than required.

The second method for supporting multiplexing and prioritization is based on a preemption indicator being transmitted from the network node, e.g., base station, to the interfering eMBB WDs. When a URLLC WD is scheduled on time and/or frequency resources that are already scheduled based on a lower priority eMBB WD, the network node can transmit a preemption indicator to the eMBB WD. Upon reception of this indicator, the eMBB WD will avoid transmitting on a set of preconfigured resources. The details of the preemption indicator and the WD behavior upon reception of this signal is currently being considered by the 3GPP. This indicator can point to one or more orthogonal frequency division multiplexed (OFDM) symbols, or to a set of resource elements. In some versions, there are several possible sets of OFDM symbols or sets of resource elements, and the indicator points to one or more of these sets.

Note that the term "preemption" (pre-emption) can be used as an alternative to the term "interruption" or "cancelation". All these terms may be used interchangeably in this disclosure.

Document <CIT> relates to uplink and downlink pre-emption indications.

A typical use case for such preemption or cancellation is when eMBB traffic is scheduled in a whole slot and all physical resource blocks (PRBs) and time sensitive URLLC need to be transmitted. Here, time sensitive means that instant access to the channel is required, and waiting until the next slot before transmission will introduce too much delay. In NR URLLC, traffic maybe be scheduled on one or a few OFDM symbols and with a significantly shorter time from the uplink grant to when the uplink transmission takes place. This means that eMBB users may already have been scheduled on all available time/frequency resources. With the preemption indicator, the network node (e.g., base station such as a gNB) can choose to preempt the eMBB traffic and hence reduce the interference to the URLLC WD.

One aspect of cancellation is what signal is cancelled using the indicator. The uplink cancellation may be used by the WD to cancel one or multiple of uplink (UL) channels, i.e., physical uplink shared channel (PUSCH), sounding reference signal (SRS), physical uplink control channel (PUCCH), and/or physical random access channel (PRACH).

Some different versions of which resources to avoid transmitting on have been discussed by the 3GPP. It may be difficult for a WD to change its transmission bandwidth during a transmission. Therefore, in some versions of cancellation indication, if a signal that can be canceled overlaps in time and frequency resources with the signaled resources that are to be canceled, the WD cancels transmissions on all of the OFDM symbols that are pointed to. Stopping a transmission and resuming it can lead to phase discontinuity of the signal. Therefore, in some versions the WD does not resume transmission even if the canceled signal occupies any resource elements in later OFDM symbols than the signaled set of resources. See <FIG> which shows examples of these two cancellation conditions (<FIG>).

In the following, existing related concepts of downlink reserved resource and downlink control information (DCI) format 2_1 for downlink (DL) preemption indication are discussed.

In NR 3GPP Rel-<NUM>, some resources in the downlink (DL) can be defined as reserved resources where the physical downlink shared channel (PDSCH) scheduled to overlap with the reserved resources will be rate-matched. Reserved resources can be configured in many different ways. One of the most common way is to semi-statically configure resource sets, some of which can be further configured as reserved resources or can be dynamically indicated to be used as reserved resources.

In NR 3GPP Rel-<NUM>, a set of bitmaps is used to configure the resource set.

The resource set is defined as all resource blocks (RBs) with value '<NUM>' in Bitmap-<NUM> and all OFDM symbols with value ` <NUM>' in Bitmap-<NUM> in all slots indicated by value ` <NUM>' in Bitmap-<NUM>.

Up to <NUM> different resource sets can be configured. Further, the resource sets may be semi-statically configured to be used as reserved resources or be dynamically indicated by some of the sets to be used as reserved resources.

For the dynamic indication, up to two groups of resource sets (rateMatchPatternGroup1 and rateMatchPatternGroup2) can be configured, and a bitmap indicator (the rate matching indicator field with size up to two bits) in the scheduling assignment indicates one or both groups to be used as reserved resources.

Complete details for downlink reserve resources are given, for example, in TS <NUM>, version V15. <NUM>, Section <NUM>. <NUM> and PDSCH-Config and RateMatchPattern, RateMatchPattemId, RateMatchPatternLTE-CRS information elements (IEs) in TS <NUM>, V15.

In NR 3GPP Rel-<NUM>, downlink control information (DCI)) format 2_1 is used for notifying the physical resource blocks (PRB) and OFDM symbol(s) where the WD may assume no transmission is intended for the WD.

The following information is transmitted using the DCI format 2_1 with cyclic redundancy check (CRC) scrambled by INT-radio network temporary identifier (RNTI):.

The size of DCI format 2_1 is configurable by higher layers up to <NUM> bits, according to Subclause <NUM> of 3GPP TS <NUM>, V. Each pre-emption indication is <NUM> bits.

In principle, the downlink (DL) preemption indication provides a length-<NUM> bitmap to indicate in an OFDM symbol level whether the whole or part of the symbol is pre-empted. If the time-domain granularity is one OFDM symbol, the corresponding frequency domain granularity is the whole bandwidth part (BWP). If time domain granularity is two consecutive OFDM symbols, the corresponding frequency domain granularity is equal to half of the BWP size.

Upon receiving uplink (UL) cancellation, the WD cancels some UL transmissions within resources that are indicated by the cancellation indication. Moreover, such indication can be very coarse, e.g., all resource blocks in the frequency domain. The cancellation includes at least the physical uplink shared channel (PUSCH) and possibly other channels of the WD. It can be desirable to preserve some of the uplink transmissions from cancellation, e.g., uplink control, sounding reference signal (SRS), physical random access channel (PRACH) or data transmissions from some WDs in the cell. However, current solutions do not preserve some of the uplink transmissions from cancellation, e.g., uplink control, SRS, PRACH or data transmissions from some WDs in the cell.

Some embodiments advantageously provide methods, network nodes and wireless devices for uplink transmission cancellation. Some embodiments, include methods of protecting wireless device (WD) signal transmissions when the WD receives a cancelation indicator, letting the WD ignore the cancelation indicator in special cases. Also, several alternatives to indicate cancelation indication without impacting certain uplink (UL) transmissions are described herein. Some methods help to minimize harmful effects of coarse granularity of the cancellation indication. As a result, information may be transmitted ignoring the cancellation indication, thereby improving spectral efficiency and quality of service (QoS) fulfillment.

In some embodiments, some of the uplink transmissions are preserved from cancellation. For example, the uplink control channel transmissions, sounding reference signal (SRS) transmissions, physical random access channel (PRACH) or data transmissions from some WDs in the cell may be protected from cancellation. This is in contrast to current solutions that do not preserve some of the uplink transmissions from cancellation, e.g., uplink control, SRS, PRACH or data transmissions from some WDs in the cell.

According to one aspect, a WD is configured to communicate with a network node, the WD comprising processing circuitry configured to receive a cancellation indication of uplink resources to be cancelled, determine protected uplink resources to be protected from cancellation, and cancel transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation.

According to this aspect, in some embodiments, the determined protected uplink resources are indicated by the cancellation indication. In some embodiments, the determined protected uplink resources are semi-statically configured. In some embodiments, the determined protected uplink resources include uplink resources for transmissions determined to be high priority transmissions. In some embodiments, the determined protected uplink resources include uplink resources for uplink control channel transmissions. In some embodiments, the determined protected uplink resources include uplink resources for random access channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for uplink shared channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for sounding reference signal transmissions.

According to another aspect, a method in a wireless device, WD, configured to communicate with a network node is provided. The method includes receiving a cancellation indication of uplink resources to be cancelled, determining protected uplink resources to be protected from cancellation, and cancelling transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation.

According to this aspect, the determined protected uplink resources are indicated by the cancellation indication. In some embodiments, the determined protected uplink resources are semi-statically configured. In some embodiments, the determined protected uplink resources include uplink resources for transmissions determined to be high priority transmissions. In some embodiments, the determined protected uplink resources include uplink resources for uplink control channel transmissions. In some embodiments, the determined protected uplink resources include uplink resources for random access channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for uplink shared channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for sounding reference signal transmissions.

According to yet another aspect, a network node is configured to communicate with a wireless device (WD). The network node includes processing circuitry configured to designate uplink resources of the WD as protected resources, and a radio interface configured to transmit to the WD a protected resources indication indicating the protected resources.

According to this aspect, in some embodiments, the processing circuitry is further configured to designate uplink resources to be cancelled and the radio interface is further configured to transmit to the WD a cancellation indication of the uplink resources to be cancelled. In some embodiments, the cancellation indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in a group common message to be received by WDs in a group. In some embodiments, the protected resources indication indicates time domain resources, but not frequency domain resources.

According to another aspect, a method in a network node configured to communicate with a wireless device (WD) is provided. The method includes designating uplink resources of the WD as protected resources, and transmitting to the WD a protected resources indication indicating the protected resources.

According to this aspect, in some embodiments, the method further includes designating uplink resources to be cancelled and the radio interface is further configured to transmit to the WD a cancellation indication of the uplink resources to be cancelled. In some embodiments, the cancellation indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in a group common message to be received by WDs in a group. In some embodiments, the protected resources indication indicates time domain resources, but not frequency domain resources.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to uplink transmission cancellation. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc..

Embodiments provide uplink transmission cancellation. According to one aspect, a method includes receiving an indication of uplink resources that are to be configured by the WD to be protected resources, determining a set of uplink resources to be protected from cancellation, and cancelling transmissions indicated to be transmitted on the protected resources except for transmissions on protected resources determined to be protected from cancellation.

Returning again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

A network node <NUM> is configured to include a protected resource designation (PRD) unit <NUM> which is configured to designate uplink resources of the WD as protected resources. A wireless device <NUM> is configured to include a cancellation protection (CP) unit <NUM> which is configured to cancel transmissions indicated to be transmitted on the protected resources except for transmissions on protected resources determined to be protected from cancellation.

The host application <NUM> may be operable to provide a service to a remote user, such as a WD <NUM> connecting via an OTT connection <NUM> terminating at the WD <NUM> and the host computer <NUM>. The "user data" may be data and information described herein as implementing the described functionality. In one embodiment, the host computer <NUM> may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry <NUM> of the host computer <NUM> may enable the host computer <NUM> to observe, monitor, control, transmit to and/or receive from the network node <NUM> and or the wireless device <NUM>.

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include protected resource designation (PRD) unit <NUM> which is configured to designate uplink resources of the WD as protected resources.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include cancellation protection unit (CP) <NUM> which is configured to cancel transmissions indicated to be transmitted on the protected resources except for transmissions on protected resources determined to be protected from cancellation.

Although <FIG> and <FIG> show various "units" such as protected resource designation unit (PRD) <NUM>, and cancellation protection unit (CP) <NUM> as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG> and <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S <NUM>). In an optional substep of the first step, the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM> (Block S102). In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S104). In an optional third step, the network node <NUM> transmits to the WD <NUM> the user data which was carried in the transmission that the host computer <NUM> initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S <NUM>). In an optional fourth step, the WD <NUM> executes a client application, such as, for example, the client application <NUM>, associated with the host application <NUM> executed by the host computer <NUM> (Block S108).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S <NUM>). In an optional substep (not shown) the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM>. In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S112). In an optional third step, the WD <NUM> receives the user data carried in the transmission (Block S114).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, the WD <NUM> receives input data provided by the host computer <NUM> (Block S <NUM><NUM>). In an optional substep of the first step, the WD <NUM> executes the client application <NUM>, which provides the user data in reaction to the received input data provided by the host computer <NUM> (Block S118). Additionally or alternatively, in an optional second step, the WD <NUM> provides user data (Block S <NUM>). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application <NUM> (Block S122). In providing the user data, the executed client application <NUM> may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD <NUM> may initiate, in an optional third substep, transmission of the user data to the host computer <NUM> (Block S124). In a fourth step of the method, the host computer <NUM> receives the user data transmitted from the WD <NUM>, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node <NUM> receives user data from the WD <NUM> (Block S <NUM>). In an optional second step, the network node <NUM> initiates transmission of the received user data to the host computer <NUM> (Block S130). In a third step, the host computer <NUM> receives the user data carried in the transmission initiated by the network node <NUM> (Block S132).

<FIG> is a flowchart of an exemplary process in a network node <NUM> for uplink transmission cancellation. One or more blocks described herein may be performed by one or more elements of network node <NUM> such as by one or more of processing circuitry <NUM> (including the PRD unit <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Network node <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to designate uplink resources of the WD as protected resources (Block S <NUM>). The process also includes transmitting to the WD a protected resources indication indicating the protected resources to the WD (Block S136).

<FIG> is a flowchart of an exemplary process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device <NUM> such as by one or more of processing circuitry <NUM> (including the CP unit <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Wireless device <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> is configured to receive a cancellation indication of uplink resources to be cancelled (Block S138). The process also includes determining protected uplink resources to be protected from cancellation (Block S140). The process further includes cancelling transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation (Block S142).

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for uplink transmission cancellation.

In general, certain uplink time-frequency resources may be designated by the network node <NUM> as protected (or prioritized) uplink resources, where the certain uplink transmissions of the target WD <NUM> are protected or prioritized. The target WD <NUM> is the WD <NUM> that has been provided with the protected or prioritized resources. Throughout the following descriptions the terms "target WD <NUM>", or "victim WD <NUM>" may be used, in which case these terms refer to the WD <NUM> that receives an uplink (UL) cancellation indication and should cancel some of its UL transmission. Also, the term "aggressor WD <NUM>" refers to a WD <NUM> that needs to use the resources for UL transmission, because of which the other victim WD <NUM> may have to cancel their UL transmission.

The certain uplink transmission may vary depending on the use cases.

That is, the protected resource may be provided to the WD <NUM> to prioritize certain UL transmission.

The protected (or prioritized) resources can be provided to a WD <NUM> in at least following example ways:.

The protected (or prioritized) resources can include:.

A general idea of the method according to some embodiments is illustrated in <FIG>. This method in some embodiments includes introduction of reserved UL resources, e.g., by semi-static configuration. When the WD <NUM> receives a cancellation indication, indicating an area in the UL time-frequency resources, if part of the indicated cancellation resources belongs to the reserved area, the reserved area is not included in the cancellation, i.e., any signal that is being sent in the reserved area is not cancelled.

<FIG> is an illustration of signal cancellation without protected resources (A) and with usage of protected resources (B) with a PUCCH signal as an example. In case (A), the WD <NUM> is scheduled to transmit PUCCH, upon detecting the control information (CI), cancels PUCCH since the PUCCH resources overlap with the resource-to-cancel as indicated in the CI. In case (B), which is claimed, the PUCCH resource is contained in the protected resource and is excluded from being canceled even if the CI indicates the resource-to-cancel area overlapping with the PUCCH resources.

Alternatively, the protection can be applied to a selected type of data/control/signal, i.e., if some specific control/datalsignal are in the reserved (protected) area, then they can be cancelled while if there are other types of data/control/signal in the reserved (protected) area, they are not cancelled.

As one example, the rule can be such that if there is PUCCH in the reserved (protected) area, then upon receiving an UL cancellation indication, the WD <NUM> does not cancel the transmission of PUCCH in the protected area. On the other hand, if there is an SRS transmission in the protected area, then upon receiving a UL cancellation indication, the WD <NUM> cancels SRS transmission, disregarding the fact that SRS can be fully or partially in the reserved (protected) area.

In one non-limiting embodiment, one or more protected resource sets are semi-statically configured in higher layers (RRC).

In one non-limiting embodiment, one or more protected resource sets are configured to belong to a protected resource group. In other words, grouping of sets is applied.

In one non-limiting embodiment, a set of one or more bitmaps are used to indicate time and frequency domain resources of a protected resource set.

<FIG> illustrates an example of protected resource sets consisting of time- and frequency-domain resources in the highlighted areas. For example, parts of the bandwidth part edge (one or two PRBs at both ends) are configured as protected resources.

<FIG> illustrates that in one example, one or more of the protected resource sets (for example as shown in <FIG>) can be further configured to belong to a protected resource group, e.g., protected resource set <NUM> belongs to protected resource group <NUM>, while protected resource set <NUM>, <NUM> and <NUM> belong to protected resource group <NUM>.

In one non-limiting embodiment, one or more resource sets among the configured protected resource sets or protected resource groups are semi-statically activated as the protected resource.

In one non-limiting embodiment, one or more resource sets among the configured protected resource sets are indicated by a field in the ULcancelation indication DCI. For example, if there are <NUM> protected resource sets configured, <NUM> bits may be used to indicate one protected resource set. Alternatively, a bitmap of length of <NUM> may be used to indicate which protected resource sets are considered as part of the protected resources.

Similarly, one or more resource groups among the configured protected resource groups may be indicated by a field in the ULcancelation indication DCI.

In one non-limiting embodiment, certain UL transmissions are semi-statically configured to be protected from cancelation. Upon receiving an UL cancelation indication, if the WD <NUM> has another UL transmission belonging to the configured protected UL transmission set, the WD <NUM> transmits that UL transmission even if the UL cancelation indication indicates the cancelation resources which overlap with that UL transmission.

An example of UL transmissions to be configured for protected transmission include PUCCH, PRACH, SRS, etc. In some versions of this embodiment, only certain specific UL transmission is considered, e.g., PUCCH carrying HARQ-ACK.

In one non-limiting embodiment, a field indicating certain protected transmissions is included in the UL cancelation indication DCI.

In some version of the above embodiment, the field points to one or more of the configured UL transmissions to be considered protected. For example, if there are PUCCH carrying HARQ-ACK and PRACH are configured, a one or two-bit field can be used to indicate that one or both of the UL transmissions are considered protected.

Upon receiving an UL cancelation indication, if the WD <NUM> has another UL transmission belonging to the configured protected UL transmission set, the WD <NUM> transmits that UL transmission even if the UL cancelation indication indicates the cancelation resources which overlap with that UL transmission.

Another way of indicating transmission protections can be more precise signaling of cancelation indication based on a configured set of cancelation resources.

In one non-limiting embodiment, an UL cancelation indication contains a field pointing to indices of one or more sets of semi-statically configured resources (a set of consecutive RBs and OFDM symbols). The union of the indicated sets are considered to be the overall cancelation resource for the WD <NUM>.

In one non-limiting embodiment, different semi-statically configured resource sets can overlap in time or frequency. In one non-limiting embodiment, a WD <NUM>, upon receiving an UL cancelation indication, cancels all UL transmission whose resources partially overlap with the resource indicated by the UL cancelation indication.

In one non-limiting embodiment, a set of different resource elements in the BWP are semi-statically configured. In one non-limiting embodiment, an UL cancelation indication contains a field pointing to one or more semi-statically configured resource elements (REs). In one non-limiting embodiment, a WD <NUM>, upon receiving an UL cancelation indication, cancels all UL transmission whose resources contains the REs indicated by the UL cancelation indication.

In one non-limiting embodiment, the sets of resources that can be indicated in a cancellation indication to be cancelled is configurable so as to enable protection of some signals. In one non-limiting embodiment, the sets of resources that can be indicated in a cancellation indication to be canceled do not include the PRBs at the edge of the BWP or carrier. This allows the network node <NUM> to schedule e.g. PUCCH in these PRBs without canceling it. In one non-limiting embodiment the cancellation indication set of resources are similar to the sets of resources signaled by the preemption indicator, which cover one OFDM symbol and the full bandwidth, or two OFDM symbols and half the bandwidth. The difference is that the cancelation indicator excludes a set of PRBs at one or both edges of the BWP or carrier, and the number of PRBs can be configured.

According to one aspect, a WD <NUM> is configured to communicate with a network node <NUM>, the WD <NUM> comprising processing circuitry <NUM> configured to receive a cancellation indication of uplink resources to be cancelled, determine protected uplink resources to be protected from cancellation, and cancel transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation. The features of this paragraph are claimed.

According to this aspect, in some embodiments, the determined protected uplink resources are indicated by the cancellation indication. In some embodiments, the determined protected uplink resources are semi-statically configured. In some embodiments, the determined protected uplink resources include uplink resources for transmissions determined to be high priority transmissions. In some claimed embodiments, the determined protected uplink resources include uplink resources for uplink control channel transmissions. In some embodiments, the determined protected uplink resources include uplink resources for random access channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for uplink shared channel transmissions. In some embodiments, the determined protected uplink resources do not include uplink resources for sounding reference signal transmissions.

According to another aspect, a method in a wireless device, WD <NUM>, configured to communicate with a network node <NUM> is provided. The method includes receiving a cancellation indication of uplink resources to be cancelled, determining protected uplink resources to be protected from cancellation, and cancelling transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation.

According to yet another aspect, a network node <NUM> is configured to communicate with a wireless device (WD) <NUM>. The network node <NUM> includes processing circuitry <NUM> configured to designate uplink resources of the WD <NUM> as protected resources, and a radio interface <NUM> configured to transmit to the WD <NUM> a protected resources indication indicating the protected resources.

According to this aspect, in some embodiments, the processing circuitry <NUM> is further configured to designate uplink resources to be cancelled and the radio interface is further configured to transmit to the WD <NUM> a cancellation indication of the uplink resources to be cancelled. In some embodiments, the cancellation indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in a group common message to be received by WDs <NUM> in a group. In some embodiments, the protected resources indication indicates time domain resources, but not frequency domain resources.

According to another aspect, a method in a network node <NUM> configured to communicate with a wireless device (WD) <NUM> is provided. The method includes designating uplink resources of the WD <NUM> as protected resources, and transmitting to the WD <NUM> a protected resources indication indicating the protected resources.

According to this aspect, in some embodiments, the method further includes designating uplink resources to be cancelled and the radio interface is further configured to transmit to the WD <NUM> a cancellation indication of the uplink resources to be cancelled. In some embodiments, the cancellation indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in downlink control information, DCI. In some embodiments, the protected resources indication is transmitted in a group common message to be received by WDs <NUM> in a group. In some embodiments, the protected resources indication indicates time domain resources, but not frequency domain resources.

In one non-limiting embodiment, the sets of resources that can be indicated in a cancellation indication to be canceled overlap in time and frequency. This may allow the network node <NUM> the choice of more than one set to signal to cancel a transmission, and could protect other signals by choosing a set that does not overlap with the protected signal. In one nonlimiting embodiment, the implicit indication of reserved resources above are used together with a cancelation mechanism that cancels all.

According to one aspect, a network node <NUM> is configured to communicate with a wireless device (WD <NUM>), the network node <NUM> including a radio interface <NUM> and/or processing circuitry <NUM> configured to designate uplink resources of the WD <NUM> as protected resources, and transmit an indication of the protected resources to the WD <NUM>. The features of this paragraph are claimed.

According to this aspect, in some embodiments, a set of bitmaps is used to indicate the protected resources. In some embodiments, designating uplink resources includes determining, via the processing circuitry <NUM>, a set of uplink resources to be protected from cancellation.

According to another aspect, a method implemented in a network node <NUM> includes designating, for example via the processing circuitry <NUM>, uplink resources of the WD <NUM> as protected resources, and transmitting an indication of the protected resources to the WD <NUM>.

According to yet another aspect, a wireless device (WD <NUM>) configured to communicate with a network node <NUM> includes a radio interface <NUM> and/or processing circuitry <NUM> configured to receive an indication of uplink resources that are to be configured by the WD <NUM> to be protected resources, determine a set of uplink resources to be protected from cancellation; and cancel transmissions indicated to be transmitted on the protected resources except for transmissions on protected resources determined to be protected from cancellation.

According to this aspect, in some embodiments, the protected resources determined, via for example the processing circuitry <NUM>, to be protected from cancellation are indicated by the indication. In some embodiments, the protected resources determined to be protected from cancellation are semi-statically configured.

According to another aspect, a method implemented in a wireless device (WD <NUM>) includes receiving, via the radio interface <NUM>, an indication of uplink resources that are to be configured by the WD <NUM> to be protected resources, determining a set of uplink resources to be protected from cancellation, and cancelling transmissions indicated to be transmitted on the protected resources except for transmissions on protected resources determined to be protected from cancellation.

According to this aspect, in some embodiments, the protected resources determined, via the processing circuitry <NUM>, to be protected from cancellation are indicated by the indication. In some embodiments, the protected resources determined to be protected from cancellation are semi-statically configured.

Claim 1:
A wireless device, WD, (<NUM>), configured to communicate with a network node (<NUM>), the WD (<NUM>) comprising processing circuitry (<NUM>) configured to:
receive a cancellation indication of uplink resources to be cancelled;
determine protected uplink resources, the protected uplink resources being uplink resources designated by the network node (<NUM>) to be protected from cancellation, wherein the determined protected uplink resources include uplink resources for uplink control channel transmissions; and
cancel transmissions on uplink resources indicated to be cancelled other than uplink resources determined to be protected from cancellation, wherein the uplink resources for uplink control channel transmissions are excluded from being canceled even if the cancellation indication indicates that the resources to be cancelled are overlapping with the uplink resources for uplink control channel transmissions.