Method for uplink transmission cancellation

Abstract

The subject of the present invention is "Method for uplink transmission cancellation". A method, system and device for uplink transmission cancellation are disclosed. According to one aspect, the method includes receiving a cancellation indication of an uplink resource to be cancelled, determining a protected uplink resource to be protected from cancellation, and canceling transmissions on the uplink resources indicated to be cancelled other than the uplink resources determined to be protected from cancellation.

Description

[0001] This application is a divisional application of a patent application filed on October 7, 2020, with application number 202080084656.X and invention name “Method for canceling uplink transmission”. Technical Field

[0002] The present disclosure relates to wireless communications and, in particular, to uplink transmission cancellation. Background Art

[0003] Ultra-reliable and low-latency communication (URLLC) is one of the main use cases of the fifth generation (5G) new radio (NR) under development by the 3rd Generation Partnership Project (3GPP). URLLC has strict requirements on transmission reliability and latency, i.e., 99.9999% reliability within 1ms one-way latency. In NR Release 15 (Rel-15), several new features and enhancements were introduced to support these requirements. In 3GPP Rel-16, standardization work focuses on further enhancing URLLC system performance and ensuring reliable and efficient coexistence of URLLC and other NR use cases. An example scenario is when enhanced mobile broadband (eMBB) and URLLC radio devices (WDs) coexist in the same wireless communication cell. Here, two methods have been identified to support multiplexing and prioritization.

[0004] The first approach is based on power control to increase the power of the URLLC to make it more resilient to interference from (one or more) eMBB users. 3GPP power control for 3GPP Rel-15 WDs is specified in Section 7.1.1 of 3GPP Technical Standard (TS) 38.213. The advantage of this option is that it does not require any changes in the behavior of the eMBB WD. Therefore, this approach works on 3GPP Rel-15 WDs. One disadvantage is that in order to guarantee the performance of the URLLC WD while being interfered with by eMBB services, the transmit power spectral density (PSD) of the WD may have to be significantly increased. However, for example, a WD that is not near a base station may not have implemented this increased power budget and will therefore experience a much lower signal-to-interference-plus-noise ratio (SINR) than required.

[0005] The second method for supporting multiplexing and prioritization is based on a preemption indicator being transmitted from a network node such as a base station to an interfering eMBB WD. When a URLLC WD is scheduled on a time and / or frequency resource that has been scheduled based on a lower priority eMBB WD, the network node can transmit a preemption indicator to the eMBB WD. When this indicator is received, the eMBB WD will avoid transmitting on a set of preconfigured resources. The details of the preemption indicator and WD behavior when this signal is received are currently being considered by 3GPP. This indicator can point to one or more orthogonal frequency division multiplexing (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.

[0006] Note that the term “preempt” (preempt-occupy) can be used as an alternative to the term “interrupt” or “cancel.” All of these terms can be used interchangeably in the present disclosure.

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

[0008] One aspect of cancellation is the use of indicators to cancel what signal. Uplink cancellation can be used by the WD to cancel one or more of the uplink (UL) channels, namely the physical uplink shared channel (PUSCH), the sounding reference signal (SRS), the physical uplink control channel (PUCCH) and / or the physical random access channel (PRACH).

[0009] Several different versions of which resources to avoid transmitting on have been discussed by 3GPP. It may be difficult for a WD to change its transmission bandwidth during transmission. Therefore, in some versions of the cancellation indication, if the cancelable signal overlaps the signaled resources to be canceled in time and frequency resources, the WD cancels transmission on all OFDM symbols pointed to. Stopping transmission and resuming transmission may result in a phase discontinuity in the signal. Therefore, in some versions, the WD will not resume transmission even if the canceled signal occupies any resource elements in OFDM symbols later than the set of signaled resources. See Figure 1 , Figure 1 Examples of these two cancellation conditions are shown ( Figure 1 (A) and (B)).

[0010] Hereinafter, existing related concepts of downlink reserved resources and downlink control information (DCI) format 2_1 for downlink (DL) preemption indication are discussed.

[0011] Downlink reserved resources

[0012] In NR 3GPP Rel-15, some resources in the downlink (DL) may be defined as reserved resources, where the physical downlink shared channel (PDSCH) scheduled to overlap with the reserved resources will be rate matched. The reserved resources may be configured in many different ways. One of the most common ways is to semi-statically configure a set of resources, some of which may be further configured as reserved resources or may be dynamically indicated to be used as reserved resources.

[0013] In NR 3GPP Rel-15, a set of bitmaps is used to configure resource sets.

[0014] • Bitmap-1 (described by the Radio Resource Control (RRC) parameter resourceBlocks) indicates the set of resource blocks (RBs). The size of bitmap-1 corresponds to the size of the bandwidth part (BWP).

[0015] • Bitmap-2 (described by the RRC parameter symbolsInResourceBlock) indicates the set of OFDM symbols within a slot or a pair of slots. The size of bitmap-2 is either 14 or 28.

[0016] • Bitmap-3 indicates the time domain repetition pattern that repeats in the number of time slots in the pattern defined by Bitmap-1 and Bitmap-2. The size of Bitmap-3 can be up to 40 bits.

[0017] A resource set is defined as all resource blocks (RBs) with a value of '1' in bitmap-1 and all OFDM symbols with a value of '1' in bitmap-2 in all slots indicated by a value of '1' in bitmap-3.

[0018] Up to 8 different resource sets can be configured.In addition, resource sets can be semi-statically configured to be used as reserved resources or dynamically indicated by some of the sets as being used as reserved resources.

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

[0020] Complete details of the downlink reserved resources are given, for example, in section 5.1.4 of TS 38.214 version V15.6.0 and in PDSCH-Config and RateMatchPattern, RateMatchPatternId, RateMatchPatternLTE-CRS information elements (IEs) in TS 38.331, V15.6.0.

[0021] Downlink preemption indication

[0022] In NR 3GPP Rel-15, Downlink Control Information (DCI) format 2_1 is used to signal physical resource blocks (PRBs) and OFDM symbol(s) where a WD may assume that no transmission is intended for the WD.

[0023] The following information is transmitted using DCI format 2_1, using a cyclic redundancy check (CRC) scrambled by INT - Radio Network Temporary Identifier (RNTI):

[0024] • Preemption indication 1, preemption indication 2, …, preemption indication n.

[0025] According to 3GPP TS 38.213, subclause 11.2 of V.15.6.0, the size of DCI format 2_1 is configurable by higher layers up to 126 bits. Each preemption indication is 14 bits.

[0026] In principle, the downlink (DL) preemption indication provides a length-14 bitmap to indicate in OFDM symbol level whether all or part of a symbol is preempted. If the time domain granularity is one OFDM symbol, the corresponding frequency domain granularity is the entire bandwidth part (BWP). If the time domain granularity is two consecutive OFDM symbols, the corresponding frequency domain granularity is equal to half the BWP size.

[0027] Upon receiving an uplink (UL) cancellation, the WD cancels some UL transmissions within the resources indicated by the cancellation indication. In addition, such an indication can be very coarse, such as all resource blocks in the frequency domain. The cancellation includes at least the physical uplink shared channel (PUSCH) and possible other channels of the WD. It may be desirable to protect some of the uplink transmissions from cancellation, such as uplink control, sounding reference signal (SRS), physical random access channel (PRACH), or data transmission from some WDs in the cell. However, current solutions do not protect some of the uplink transmissions from cancellation, such as uplink control, SRS, PRACH, or data transmission from some WDs in the cell. Summary of the invention

[0028] Some embodiments advantageously provide methods, network nodes, and wireless devices for uplink transmission cancellation. Some embodiments include methods for protecting wireless device (WD) signal transmission when the WD receives a cancellation indicator, allowing the WD to ignore the cancellation indicator in special circumstances. Moreover, several alternatives for indicating a cancellation indication without affecting certain uplink (UL) transmissions are described herein. Some methods help minimize the harmful effects of the coarse granularity of the cancellation indication. As a result, information can be transmitted while ignoring the cancellation indication, thereby improving spectrum efficiency and quality of service (QoS) implementation.

[0029] In some embodiments, some of the uplink transmissions are protected from cancellation. For example, uplink control channel transmissions, sounding reference signal (SRS) transmissions, physical random access channel (PRACH), or data transmissions from some WDs in a cell may be protected from cancellation. This is in contrast to current solutions, which do not protect some of the uplink transmissions from cancellation, such as uplink control, SRS, PRACH, or data transmissions from some WDs in a cell.

[0030] According to one aspect, the WD is configured to communicate with a network node, the WD comprising a processing circuit configured to receive a cancellation indication of an uplink resource to be cancelled, determine protected uplink resources to be protected from cancellation, and cancel transmission on the uplink resources indicated to be cancelled other than the uplink resources determined to be protected from cancellation.

[0031] According to this aspect, in some embodiments, the determined protected uplink resources are indicated by a 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.

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

[0033] According to this aspect, the determined protected uplink resources are indicated by a 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.

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

[0035] According to this aspect, in some embodiments, the processing circuit is further configured to specify the uplink resource to be cancelled and the radio interface is further configured to transmit a cancellation indication of the uplink resource to be cancelled to the WD. In some embodiments, the cancellation indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in a group common message to be received by the WDs in the group. In some embodiments, the protected resource indication indicates time domain resources rather than frequency domain resources.

[0036] 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 a protected resource indication indicating the protected resources to the WD.

[0037] According to this aspect, in some embodiments, the method further includes specifying the uplink resource to be cancelled, and the radio interface is further configured to transmit a cancellation indication of the uplink resource to be cancelled to the WD. In some embodiments, the cancellation indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in a group common message to be received by the WDs in the group. In some embodiments, the protected resource indication indicates time domain resources rather than frequency domain resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] When with Figure 1 A more complete understanding of the present embodiments and the attendant advantages and features thereof will be more readily appreciated by reference to the following detailed description, wherein:

[0039] Figure 1 Transmission timing is described;

[0040] Figure 2 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host via an intermediate network according to the principles of the present disclosure;

[0041] Figure 3 is a block diagram of a host communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0042] Figure 4 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host, a network node, and a wireless device according to some embodiments of the present disclosure;

[0043] Figure 5is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host, a network node, and a wireless device according to some embodiments of the present disclosure;

[0044] Figure 6 is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host, implemented in a communication system including a host, a network node, and a wireless device, according to some embodiments of the present disclosure;

[0045] Figure 7 is a flow chart illustrating an exemplary method for receiving user data at a host implemented in a communication system including a host, a network node, and a wireless device according to some embodiments of the present disclosure;

[0046] Figure 8 is a flow chart of an exemplary process for uplink transmission cancellation in a network node;

[0047] Fig. 9 is a flow chart of an exemplary process for uplink transmission cancellation in a wireless device; and

[0048] Fig.10 The cancellation timing is explained;

[0049] Fig.11 illustrates examples of protected resource configurations; and

[0050] Fig.12 Another example of a protected resource configuration is illustrated. DETAILED DESCRIPTION

[0051] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in combinations of processing steps and device components related to uplink transmission cancellation. Therefore, components have been represented where appropriate by conventional symbols in the figures, which show only those specific details relevant to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0052] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc., may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to be limitations of the concepts described herein. Unless the context clearly indicates otherwise, as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It will be further understood that when used herein, the terms "comprises", "comprising", "includes", and / or "including" specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0053] In the embodiments described herein, connection terms "in communication with" and the like may be used to indicate electrical or data communications that may be achieved through, for example, physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations are possible to achieve electrical and data communications.

[0054] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate connection (although not necessarily direct) and may include wired and / or wireless connections.

[0055] The term "network node" used herein may be any kind of network node included in a radio network, and the network node may further include any of the following: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNode B (gNB), an evolved Node B (eNB or eNodeB), a Node B, a multi-standard radio (MSR) radio node such as an MSR BS, a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU), a remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. The term "radio node" as used herein may also be used to refer to a wireless device (WD) or a radio network node such as a wireless device (WD).

[0056] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD herein may be any type of wireless device, such as a wireless device (WD), capable of communicating with a network node or another WD via a radio signal. The WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0057] Moreover, in some embodiments, the general term "radio network node" is used. It can be any kind of radio network node, which can include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH).

[0058] Note that while terminology from one particular wireless system such as, for example, 3GPP LTE and / or New Radio (NR) may be used in the present disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned systems. Other wireless systems including, but not limited to, Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM) may also benefit from utilizing the ideas included in the present disclosure.

[0059] It is further noted that the functions described herein as being performed by a wireless device or network node may be distributed to multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein will not be limited to the performance of a single physical device and may in fact be distributed to several physical devices.

[0060] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meanings in the context of this specification and in the relevant field, and unless explicitly defined as such herein, the terms used herein will not be interpreted in an idealized or overly formal sense.

[0061] Embodiments provide uplink transmission cancellation. According to one aspect, a method includes receiving an indication of an uplink resource to be configured by a WD as a protected resource, determining a set of uplink resources to be protected from cancellation, and canceling transmissions indicated to be transmitted on the protected resources other than the transmissions on the protected resources determined to be protected from cancellation.

[0062] Returning again to the drawings, wherein like elements are referenced by like reference numerals, Figure 2, a schematic diagram of a communication system 10 such as a 3GPP type cellular network that can support standards such as LTE and / or NR (5G) according to an embodiment is shown, the communication system 10 including an access network 12 such as a wireless access network and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16) such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to wirelessly connect to the corresponding network node 16a, or to be paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b is wirelessly connectable to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to situations where only a single WD is in the coverage area or where a single WD is connecting to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0063] Moreover, it is contemplated that the WD 22 may communicate with more than one network node 16 and more than one type of network node 16 simultaneously and / or be configured to communicate with more than one network node 16 and more than one type of network node 16, respectively. For example, the WD 22 may have dual connectivity with a network node 16 supporting LTE and with the same or different network node 16 supporting NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0064] The communication system 10 itself may be connected to a host 24, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or may be embodied as a processing resource in a server farm. The host 24 may be under the ownership or control of a service provider, or the host 24 may be operated by or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host 24 may extend directly from the core network 14 to the host 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or managed network or a combination of more than one of a public, private, or managed network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0065] Figure 2 The communication system as a whole enables connectivity between one of the connected WDs 22a, 22b and the host 24. Connectivity can be described as an over-the-top (OTT) connection. The host 24 and the connected WDs 22a, 22b are configured to use the access network 12, the core network 14, any intermediate networks 30, and possible additional infrastructure (not shown) as intermediaries to transfer data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes do not know the routing of uplink and downlink communications. For example, the network node 16 may not be informed or need not be informed of the past routing of incoming downlink communications, where data originating from the host 24 is to be forwarded (e.g., switched) to the connected WD 22a. Similarly, the network node 16 does not need to know the future routing of outgoing uplink communications originating from the WD 22a toward the host 24.

[0066] The network node 16 is configured to include a protected resource designation (PRD) unit 32 configured to designate uplink resources of the WD as protected resources. The wireless device 22 is configured to include a cancel protection (CP) unit 34 configured to cancel transmissions indicated to be transmitted on protected resources other than transmissions on protected resources determined to be protected from cancellation.

[0067] Now refer to Figure 31 to describe an example implementation according to an embodiment of the WD 22, network node 16, and host 24 discussed in the previous paragraphs. In the communication system 10, the host 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 10. The host 24 further includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or instead of a processor such as a central processing unit and a memory, the processing circuit 42 may also include, for example, one or more processors and / or processor cores suitable for executing instructions and / or an integrated circuit of an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) for processing and / or control. The processor 44 may be configured to access (e.g. write to and / or read from) a memory 46, which may include, for example, cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read Only Memory) of any kind of volatile and / or non-volatile memory.

[0068] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or configured to cause such methods and / or processes to be performed, for example, by host 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host 24 described herein. Host 24 includes memory 46 configured to store data, programmed software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host 24. The instructions may be software associated with host 24.

[0069] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to a remote user of a WD 22 such as connected via an OTT connection 52 terminated at the WD 22 and the host 24. When providing services to the remote user, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the described functionality. In one embodiment, the host 24 may be configured to provide control and functionality to a service provider, and the host 24 may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host 24 may enable the host 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and / or the wireless device 22.

[0070] The communication system 10 further includes a network node 16 disposed in the communication system 10 and including hardware 58 that enables the network node 16 to communicate with the host 24 and with the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to interfaces with different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host 24. The connection 66 may be direct, or it may be through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0071] In the illustrated embodiment, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, the processing circuit 68 may include, for example, one or more processors and / or processor cores adapted to execute instructions and / or an integrated circuit such as an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) for processing and / or control, in addition to or in place of a processor such as a central processing unit and a memory. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read only memory) and / or an optical memory and / or an EPROM (erasable programmable read only memory) of any kind of volatile and / or non-volatile memory.

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

[0073] The communication system 10 further includes the already mentioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0074] The hardware 80 of the WD 22 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor such as a central processing unit and a memory such as a central processing unit, the processing circuit 84 may also include, for example, one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions, for processing and / or control. The processor 86 may be configured to access (e.g., write to and / or read from) a memory 88, which may include, for example, cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory) of any kind of volatile and / or non-volatile memory.

[0075] Therefore, WD 22 may further include software 90, which is stored in, for example, a memory 88 at WD 22 or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. With the support of the host 24, the client application 92 may be operable to provide services to human or non-human users via WD 22. In the host 24, the executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminated at WD 22 and the host 24. When providing services to users, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0076] The processing circuit 84 may be configured to control any of the methods and / or processes described herein and / or configured to cause such methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a cancel protection unit (CP) 34 that is configured to cancel transmissions indicated to be transmitted on protected resources other than transmissions on protected resources that are determined to be protected from cancellation.

[0077] In some embodiments, the internal workings of network node 16, WD 22, and host 24 may be as follows: Figure 3 As shown in , and independently, the surrounding network topology can be Figure 2 The surrounding network topology.

[0078] exist Figure 3In FIG. 5 , the OTT connection 52 has been abstractly drawn to illustrate communication between the host 24 and the wireless device 22 via the network node 16, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the WD 22 or hidden from the service provider operating the host 24, or hidden from both. When the OTT connection 52 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0079] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments use the OTT connection 52 to improve the performance of the OTT service provided to the WD 22, where the wireless connection 64 can form the last segment. More precisely, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption, and thus provide benefits such as reduced user waiting time, loose restrictions on file size, better responsiveness, extended battery life, etc.

[0080] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors that are improved by one or more embodiments. In response to changes in the measurement results, there may be further optional network functionality for reconfiguring the OTT connection 52 between the host 24 and the WD 22. The measurement process and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 52 passes or may be associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities by which the software 48, 90 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing selections, etc.; the reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functionalities may be known and implemented in the art. In some embodiments, the measurements may involve proprietary WD signaling of the host 24 that facilitates measurement of throughput, propagation times, latency, etc. In some embodiments, the measurements may be achieved because the software 48, 90 uses the OTT connection 52 to cause messages to be transmitted, particularly empty or 'dummy' messages to be transmitted, while the software 48, 90 monitors propagation times, errors, etc.

[0081] Thus, in some embodiments, host 24 includes processing circuitry 42 configured to provide user data and communication interface 40 configured to forward the user data to a cellular network for transmission to WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, network node 16 is configured and / or processing circuitry 68 of network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to WD 22, and / or the functions and / or methods described herein for preparing / terminating / maintaining / supporting / ending reception of transmissions from WD 22.

[0082] In some embodiments, host 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from a transmission from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to network node 16, and / or the functions and / or methods described herein for preparing / terminating / maintaining / supporting / ending reception of a transmission from network node 16.

[0083] although Figure 1 and Figure 2 Various "units" such as protected resource designation unit (PRD) 32 and unprotection unit (CP) 34 are shown as being within respective processors, but 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 within the processing circuitry or in a combination of hardware and software.

[0084] Figure 4 is to illustrate according to one embodiment in a case such as Figure 2 and Figure 3 A flow chart of an exemplary method implemented in a communication system of a communication system of the present invention. The communication system may include a reference Figure 3The method includes a host 24, a network node 16, and a WD 22 as described above. In a first step of the method, the host 24 provides user data (block S100). In an optional sub-step of the first step, the host 24 provides the user data by executing a host application such as, for example, the host application 50 (block S102). In a second step, the host 24 initiates a transmission to the WD 22 carrying the user data (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 transmits the user data carried in the transmission initiated by the host 24 to the WD 22 (block S106). In an optional fourth step, the WD 22 executes a client application such as, for example, the client application 92 associated with the host application 50 executed by the host 24 (block S108).

[0085] Figure 5 is to illustrate according to one embodiment in a case such as Figure 2 A flow chart of an exemplary method implemented in a communication system of a communication system of the present invention. The communication system may include a reference Figure 2 and Figure 3 The method includes a host 24, a network node 16, and a WD 22 as described above. In a first step of the method, the host 24 provides user data (block S110). In an optional sub-step (not shown), the host 24 provides the user data by executing a host application such as, for example, the host application 50. In a second step, the host 24 initiates a transmission to the WD 22 carrying the user data (block S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can be passed via the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0086] Figure 6 is to illustrate according to one embodiment in a case such as Figure 2 A flow chart of an exemplary method implemented in a communication system of a communication system of the present invention. The communication system may include a reference Figure 2 and Figure 3The host 24, network node 16 and WD 22 described above are described above. In an optional first step of the method, WD 22 receives input data provided by the host 24 (box S116). In an optional sub-step of the first step, WD 22 executes the client application 92, which provides user data as a reaction to the received input data provided by the host 24 (box S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (box S120). In an optional sub-step of the second step, WD provides user data by executing a client application such as, for example, the client application 92 (box S122). When providing user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, WD 22 may initiate the transmission of user data to the host 24 in an optional third sub-step (box S124). In a fourth step of the method, according to the teachings of the embodiments described throughout the present disclosure, the host 24 receives the user data transmitted from the WD 22 (box S126).

[0087] Figure 7 is to illustrate according to one embodiment in a case such as Figure 2 A flow chart of an exemplary method implemented in a communication system of a communication system of the present invention. The communication system may include a reference Figure 2 and Figure 3 The host 24, network node 16, and WD 22 described above are described above. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128) in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step, the network node 16 initiates a transmission of the received user data to the host 24 (block S130). In a third step, the host 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0088] Figure 8 is a flow chart of an exemplary process for uplink transmission cancellation in the network node 16. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuit 68 (including the PRD unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured, such as by means of the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60, to designate the uplink resources of the WD as protected resources (block S134). The process also includes transmitting a protected resource indication to the WD indicating the protected resources to the WD (block S136).

[0089] Fig. 9is a flow chart of an exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the CP unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to receive a cancellation indication of an uplink resource to be cancelled, such as by means of the processing circuit 84 and / or the processor 86 and / or the radio interface 82 (block S138). The process also includes determining a protected uplink resource to be protected from cancellation (block S140). The process further includes canceling transmissions on the uplink resources indicated to be cancelled, other than the uplink resources determined to be protected from cancellation (block S142).

[0090] Having described the general process flow of the disclosed arrangements and provided examples of hardware and software arrangements for implementing the disclosed processes and functions, the following section provides details and examples of arrangements for uplink transmission cancellation.

[0091] Use cases and general description

[0092] Typically, certain uplink time-frequency resources may be designated by the network node 16 as protected (or prioritized) uplink resources, where certain uplink transmissions of the target WD 22 are protected or prioritized. The target WD 22 is a WD 22 that has been provided with protected or prioritized resources. Throughout the following description, the terms "target WD 22" or "victim WD 22" may be used, in which case these terms refer to a WD 22 that receives an uplink (UL) cancellation indication and should cancel some of its UL transmissions. Moreover, the term "aggressor WD 22" refers to a WD 22 that needs to use resources for UL transmissions because another victim WD 22 may have to cancel their UL transmissions.

[0093] A certain uplink transmission may vary depending on the use case.

[0094] • In case of inter-WD uplink preemption based on cancellation indicator, the victim WD 22 may be provided with protected uplink resources so that the victim WD 22 may transmit certain UL channels or signals except PUSCH when the certain UL channels or signals reside within the protected uplink resources. The certain UL channels or signals may include: PUCCH carrying Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK), PUCCH carrying aperiodic channel state information (CSI), PRACH, etc.

[0095] • In case of inter-WD uplink preemption based on cancellation indicator, the aggressor WD 22 may have protected uplink resources, so that the aggressor WD 22 may transmit its PUSCH residing within the protected uplink resources, including dynamically scheduled PUSCH and / or UL configured grant-scheduled PUSCH. The aggressor WD 22 may need to know its protected uplink resources so that it knows that its PUSCH transmission can be performed, most likely preempting the victim WD's PUSCH transmission. This avoids confusion in identifying which WD 22 is allowed to be the aggressor WD 22 (it performs its PUSCH transmission) and which WD(s) 22 are the victim WD 22 (they are forced to cancel their PUSCH transmission).

[0096] • In case of power control based uplink preemption between WDs 22, the aggressor WD 22 may have protected uplink resources such that the aggressor WD 22 may transmit its PUSCH at an increased power level via the radio interface 82, where the PUSCH resides within the protected uplink resources. The PUSCH of the aggressor WD includes dynamically scheduled PUSCH and / or UL configured granted scheduled PUSCH. Similarly, this avoids confusion in identifying which WD 22 is allowed to be the aggressor WD 22 (which performs its PUSCH transmission at an increased power level) and which WD(s) are the victim WD (which performs its PUSCH transmission at a normal power level). Here, the increased power level may be compared with the normal power level, where the normal power level is used when uplink preemption between WDs 22 is not an issue.

[0097] • In the case of 3GPP Rel-16 enhanced PUSCH, the PUSCH transmission in the time domain is determined by means of the wireless device 22 using certain implicit rules. For example, when PUSCH is repeated and / or segmented in the time domain, the WD 22 can determine whether PUSCH transmission can be performed (or alternatively, should not be performed) in certain OFDM symbols. This is in contrast to 3GPP Rel-15 PUSCH scheduling, where the WD 22 is explicitly provided with the start and end symbols of the PUSCH transmission in the time slot. For 3GPP Rel-16 enhanced PUSCH, the WD 22 can be provided with protected uplink resources so that the WD 22 knows that it can use resources within the protected uplink resources, i.e., there is no need to skip PUSCH transmissions in the protected time-frequency resources. In addition to PUSCH, the WD 22 can also transmit other uplink channels / signals in the protected time-frequency resources, such as PUCCH, SRS, PRACH.

[0098] • In the case of 3GPP Rel-16 UL intra-WD preemption, where WD 22 is scheduled and configured with overlapping resources for two UL transmissions (PUSCH, PUCCH containing SR, Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK), Channel State Information (CSI), etc.), an indication of protected resources may be provided to WD 22 by network node 16. In such a case, WD 22 cancels the UL transmission whose resources are not part of the protected resources. Resources that are considered not to be part of the protected resources may include, for example:

[0099] o 1) Resources that do not intersect with protected resources in the time or frequency domain, and / or

[0100] o 2) Resources that are not a subset of the protected resources in the time domain or frequency domain.

[0101] That is, protected resources may be provided to WD 22 to prioritize certain UL transmissions.

[0102] Protected (or prioritized) resources may be provided to WD 22 in at least the following example ways:

[0103] o The protected (or prioritized) resources may be signaled in a WD 22 specific message. The message may be a Radio Resource Control (RRC) signaling, a Medium Access Control (MAC) Control Element (CE), or a DCI.

[0104] o Protected (or prioritized) resources may be signaled in a group common message, where the group common message is to be received by multiple WDs. The group common message may be a broadcast RRC message, a medium access control element (MAC CE), or a group common DCI.

[0105] Protected (or prioritized) resources may include:

[0106] o Alternative 1: All frequency resources within certain time domain resources may be used by WD 22. In this case, the indication of protected resources only requires an indication of the relevant time domain resources, but no indication of the frequency domain resources.

[0107] a) All frequency resources that the WD 22 can use may be all PRBs in a bandwidth part (BWP) or all PRBs in a component carrier.

[0108] o Alternative 2: Certain frequency resources within certain time domain resources. In this case, the indication of the protected resources needs to include an indication of the relevant time domain resources and an indication of the relevant frequency domain resources.

[0109] More details are provided below.

[0110] Protected uplink resources

[0111] General Description

[0112] exist Fig.10 The general idea of ​​the method according to some embodiments is described in . In some embodiments, this method includes introducing reserved UL resources, for example, by semi-static configuration. When WD 22 receives a cancellation indication indicating a region in the UL time-frequency resources, if a part of the indicated cancellation resources belongs to the reserved region, the reserved region is not included in the cancellation, that is, any signal being sent in the reserved region will not be cancelled.

[0113] Fig.10 This is an illustration of signal cancellation in the case of no protected resources (A) and in the case of using protected resources (B), taking a PUCCH signal as an example. In case (A), WD 22 is scheduled to transmit PUCCH, and upon detecting control information (CI), PUCCH is cancelled because PUCCH resources overlap with resources to be cancelled as indicated in CI. In case (B), PUCCH resources are included in protected resources and are excluded from being cancelled, even though CI indicates that the resource region to be cancelled overlaps with PUCCH resources.

[0114] Alternatively, protection may be applied to selected types of data / control / signals, i.e., some specific control / data / signals may be cancelled if they are in the reserved (protected) area, whereas other types of data / control / signals may not be cancelled if they are present in the reserved (protected) area.

[0115] As an example, the rule may be such that if there is a PUCCH in the reserved (protected) region, upon receiving the UL cancellation indication, the WD 22 does not cancel the transmission of the PUCCH in the protected region. On the other hand, if there is an SRS transmission in the protected region, upon receiving the UL cancellation indication, the WD 22 cancels the SRS transmission, regardless of the fact that the SRS may be completely or partially in the reserved (protected) region.

[0116] Configuration of protected resources

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

[0118] 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.

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

[0120] Fig.11 An example of a protected resource set consisting of time domain resources and frequency domain resources in the highlighted area is illustrated. For example, portions at the edge of a bandwidth portion (one or two PRBs at both ends) are configured as protected resources.

[0121] Fig.12 In one example, a protected resource collection (e.g. Fig.11 One or more of the protected resource sets (as shown in ) may be further configured to belong to a protected resource group, for example, protected resource set 1 belongs to protected resource group 1, while protected resource sets 2, 3, and 4 belong to protected resource group 2.

[0122] Semi-static activation of protected resources

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

[0124] Dynamic indication of protected resources

[0125] In a 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 4 protected resource sets are configured, 2 bits may be used to indicate one protected resource set. Alternatively, a bitmap of length 4 may be used to indicate which protected resource sets are considered part of the protected resources.

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

[0127] Which UL transmissions / signals should be protected

[0128] Semi-static indication of protected UL transmissions

[0129] In one non-limiting embodiment, certain UL transmissions are semi-statically configured to be protected from cancellation. Upon receiving the UL cancellation indication, if WD 22 has another UL transmission that belongs to the configured protected UL transmission set, WD 22 transmits that UL transmission even if the UL cancellation indication indicates cancellation resources that overlap with that UL transmission.

[0130] Examples of UL transmissions configured for protected transmission include PUCCH, PRACH, SRS, etc. In some versions of this embodiment, only a certain UL transmission is considered, such as PUCCH carrying HARQ-ACK.

[0131] Dynamic indication of protected UL transmissions

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

[0133] In some versions of the above embodiments, the field points to one or more of the configured UL transmissions to be considered protected. For example, if there is a PUCCH carrying HARQ-ACK and PRACH is configured, a one-bit or two-bit field may be used to indicate that one or both of the UL transmissions are considered protected.

[0134] Upon receiving the UL cancellation indication, if WD 22 has another UL transmission that belongs to the configured protected UL transmission set, WD 22 transmits that UL transmission even if the UL cancellation indication indicates cancellation resources that overlap with that UL transmission.

[0135] UL cancellation indication based on a set of configured cancellation resources

[0136] Another way to indicate transmission protection may be a more precise signaling of a cancellation indication based on a set of configured cancellation resources.

[0137] Resources described by consecutive RBs and OFDM symbols

[0138] In one non-limiting embodiment, the UL cancellation indication contains a field that indexes one or more sets of semi-statically configured resources (sets of consecutive RBs and OFDM symbols). The union of the indicated sets is considered the overall cancellation resources for WD 22.

[0139] In a non-limiting embodiment, different semi-statically configured resource sets may overlap in time or frequency. In a non-limiting embodiment, upon receiving the UL cancellation indication, WD 22 cancels all UL transmissions whose resources partially overlap with the resources indicated by the UL cancellation indication.

[0140] Resources described by a single resource element

[0141] In one non-limiting embodiment, the set of different resource elements in the BWP is semi-statically configured. In one non-limiting embodiment, the UL cancellation indication contains a field pointing to one or more semi-statically configured resource elements (REs). In one non-limiting embodiment, WD 22, upon receiving the UL cancellation indication, cancels all UL transmissions whose resources contain the REs indicated by the UL cancellation indication.

[0142] Implicit indication of reserved resources

[0143] In a non-limiting embodiment, the set of resources that can be indicated as being canceled in the cancellation indication is configurable to enable protection of some signals. In a non-limiting embodiment, the set of resources that can be indicated as being canceled in the cancellation indication does not include PRBs at the edge of the BWP or carrier. This allows the network node 16 to schedule, for example, PUCCH in these PRBs without canceling it. In a non-limiting embodiment, the cancellation indication set of resources is similar to the set of resources signaled by the preemption indicator, and the set of resources signaled by the preemption indicator covers one OFDM symbol and full bandwidth, or two OFDM symbols and half bandwidth. The difference is that the cancellation indicator excludes the set of PRBs at one or two edges of the BWP or carrier, and the number of PRBs can be configured.

[0144] According to one aspect, the WD 22 is configured to communicate with the network node 16, and the WD 22 includes a processing circuit 84, which is configured to receive a cancellation indication of an uplink resource to be cancelled, determine protected uplink resources to be protected from cancellation, and cancel transmissions on the uplink resources indicated to be cancelled other than the uplink resources determined to be protected from cancellation.

[0145] According to this aspect, in some embodiments, the determined protected uplink resources are indicated by canceling the 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.

[0146] According to another aspect, there is provided a method in a wireless device WD 22 configured to communicate with a network node 16. The method comprises 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 the uplink resources determined to be protected from cancellation.

[0147] According to this aspect, the determined protected uplink resources are indicated by canceling the 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.

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

[0149] According to this aspect, in some embodiments, the processing circuit 68 is further configured to specify the uplink resources to be cancelled, and the radio interface is further configured to transmit a cancellation indication of the uplink resources to be cancelled to the WD 22. In some embodiments, the cancellation indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in the downlink control information DCI. In some embodiments, the protected resource indication is transmitted in a group common message to be received by the WD 22 in the group. In some embodiments, the protected resource indication indicates time domain resources instead of frequency domain resources.

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

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

[0152] In one non-limiting embodiment, the sets of resources that may be indicated in the cancellation indication as being to be cancelled overlap in time and frequency. This may allow the network node 16 to select more than one set to signal to cancel a transmission and to protect other signals by selecting a set that does not overlap with the protected signal. In one non-limiting embodiment, the implicit indication of the reserved resources described above is used with a cancel all cancellation mechanism.

[0153] According to one aspect, the network node 16 is configured to communicate with a wireless device (WD 22), the network node 16 includes a radio interface 62 and / or a processing circuit 68 configured to designate uplink resources of the WD 22 as protected resources and transmit an indication of the protected resources to the WD 22.

[0154] According to this aspect, in some embodiments, a set of bitmaps are used to indicate protected resources.In some embodiments, designating uplink resources comprises determining, by means of processing circuitry 68, a set of uplink resources to be protected from cancellation.

[0155] According to another aspect, a method implemented in the network node 16 includes designating uplink resources of the WD 22 as protected resources and transmitting an indication of the protected resources to the WD 22 , for example by means of the processing circuit 68 .

[0156] According to this aspect, in some embodiments, a set of bitmaps are used to indicate protected resources.In some embodiments, designating uplink resources comprises determining, by means of processing circuitry 68, a set of uplink resources to be protected from cancellation.

[0157] According to yet another aspect, a wireless device (WD 22) configured to communicate with the network node 16 includes a radio interface 82 and / or processing circuitry 84 configured to receive an indication of uplink resources to be configured by the WD 22 as protected resources, determine a set of uplink resources to be protected from cancellation, and cancel transmissions indicated to be transmitted on the protected resources other than transmissions on the protected resources determined to be protected from cancellation.

[0158] According to this aspect, in some embodiments, protected resources determined to be protected from cancellation by means of, for example, processing circuitry 84 are indicated by indication. In some embodiments, protected resources determined to be protected from cancellation are semi-statically configured.

[0159] According to another aspect, a method implemented in a wireless device (WD 22) includes receiving, via a radio interface 82, an indication of uplink resources to be configured by the WD 22 as protected resources, determining a set of uplink resources to be protected from cancellation, and canceling transmissions indicated to be transmitted on the protected resources other than transmissions on the protected resources determined to be protected from cancellation.

[0160] According to this aspect, in some embodiments, protected resources determined to be protected from cancellation by means of processing circuitry 84 are indicated by indication. In some embodiments, protected resources determined to be protected from cancellation are semi-statically configured.

[0161] Some embodiments include the following:

[0162] Embodiment A1: A network node configured to communicate with a wireless device (WD), the network node being configured to and / or comprising a radio interface and / or comprising a processing circuit configured to:

[0163] designating uplink resources of the WD as protected resources; and

[0164] An indication of the protected resource is communicated to the WD.

[0165] Embodiment A2: The network node of Embodiment A1, wherein a set of bitmaps is used to indicate the protected resources.

[0166] Embodiment A3: The network node of Embodiment A1, wherein specifying uplink resources comprises determining a set of uplink resources to be protected from cancellation.

[0167] Embodiment B1: A method implemented in a network node, the method comprising:

[0168] designating uplink resources of the WD as protected resources; and

[0169] An indication of the protected resource is communicated to the WD.

[0170] Embodiment B2: The method of Embodiment B1, wherein a set of bitmaps is used to indicate the protected resources.

[0171] Embodiment B3: The method of Embodiment B1, wherein specifying uplink resources comprises determining a set of uplink resources to be protected from cancellation.

[0172] Embodiment C1: A wireless device (WD) configured to communicate with a network node, the WD configured to and / or comprising a radio interface and / or a processing circuit configured to:

[0173] receiving an indication of uplink resources to be configured by the WD as protected resources;

[0174] determining a set of uplink resources to be protected from cancellation; and

[0175] Transmissions indicated to be transmitted on the protected resources other than transmissions on the protected resources determined to be protected from cancellation are cancelled.

[0176] Embodiment C2: The WD of Embodiment C1, wherein the protected resource determined to be protected from cancellation is indicated by the indication.

[0177] Embodiment C3: The WD of Embodiment C1, wherein the protected resources determined to be protected from cancellation are semi-statically configured.

[0178] Embodiment D1: A method implemented in a wireless device (WD), the method comprising:

[0179] receiving an indication of uplink resources to be configured by the WD as protected resources;

[0180] determining a set of uplink resources to be protected from cancellation; and

[0181] Transmissions indicated to be transmitted on the protected resources other than transmissions on the protected resources determined to be protected from cancellation are cancelled.

[0182] Embodiment D2: A method as described in Embodiment D1, wherein the indication indicates the protected resource determined to be protected from cancellation.

[0183] Embodiment D3: A method as described in Embodiment D1, wherein the protected resources determined to be protected from cancellation are semi-statically configured.

[0184] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or a combination of all software and hardware embodiments generally referred to herein as "circuits" or "modules." Any process, step, action, and / or functionality described herein may be performed by a corresponding module and / or any process, step, action, and / or functionality described herein may be associated to a corresponding module, which may be implemented with software and / or firmware and / or hardware. In addition, the disclosure may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code included in the medium that can be executed by a computer. Any suitable tangible computer-readable medium including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device may be utilized.

[0185] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be appreciated that each block of the flowchart illustration and / or block diagram and the combination of blocks in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or a processor of other programmable data processing equipment to produce a machine, so that instructions executed by a processor of a computer or other programmable data processing equipment create components for implementing the functions / actions specified in a flowchart and / or block diagram block or multiple flowcharts and / or block diagram blocks.

[0186] These computer program instructions that can direct a computer or other programmable data processing device to operate in a specific manner may also be stored in a computer-readable memory or storage medium, so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction components that implement the functions / actions specified in a flowchart and / or block diagram or multiple flowcharts and / or block diagrams.

[0187] Computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions executed on the computer or other programmable device provide steps for implementing the functions / actions specified in a flowchart and / or block diagram block or multiple flowcharts and / or block diagram blocks.

[0188] It is to be understood that the functions / actions annotated in the blocks may not occur in the order annotated in the operating instructions. For example, depending on the functionality / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. Although some of the figures in the figures include arrows on the communication paths to illustrate the primary direction of communication, it is to be understood that communication may occur in the direction opposite to the arrows depicted.

[0189] The computer program code for the operation of the concept described herein can be written with an object-oriented programming language such as Java® or C++. However, the computer program code for the operation disclosed can also be written with a conventional process programming language such as "C" programming language. The program code can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or executed completely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or (for example, using an Internet service provider through the Internet) can be made to be connected to an external computer.

[0190] Many different embodiments have been disclosed herein in conjunction with the above description and figures. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be overly repetitive and obscure. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the figures should be interpreted as constituting a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and this specification including the figures should support claims to any such combination or subcombination.

[0191] Abbreviations that may be used in the preceding description include:

[0192] Abbreviations explain

[0193] CSI Channel State Information

[0194] HARQ-ACK Hybrid Automatic Repeat Request Acknowledgement

[0195] PUCCH Physical Uplink Control Channel

[0196] PUSCH Physical Uplink Shared Channel

[0197] SR Scheduling Request

[0198] UCI Uplink Control Information

[0199] Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been particularly shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. Various modifications and variations are possible according to the above teachings without departing from the scope of the following claims.

Claims

1. A wireless device WD (22) configured to communicate with a network node (16), the WD (22) comprising a processing circuit (84), the processing circuit (84) being configured to: receiving a cancellation indication of uplink resources to be cancelled; determining protected uplink resources to be protected from cancellation, wherein the determined protected uplink resources include uplink resources used 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 used for uplink control channel transmission are excluded from cancellation even if the cancellation indication indicates that the resources to be cancelled are overlapping with the uplink resources used for uplink control channel transmission.

2. The WD (22) according to claim 1, wherein: The determined protected uplink resources are indicated by the cancellation indication.

3. The WD (22) according to claim 1, wherein: The determined protected uplink resources are semi-statically configured.

4. The WD (22) according to any one of claims 1 to 3, wherein: The determined protected uplink resources include uplink resources for transmissions determined to be high priority transmissions.

5. The WD (22) according to any one of claims 1 to 3, wherein: The determined protected uplink resources include uplink resources used for random access channel transmission.

6. The WD (22) according to any one of claims 1 to 3, wherein: The determined protected uplink resources do not include uplink resources used for uplink shared channel transmission.

7. The WD (22) according to any one of claims 1 to 3, wherein: The determined protected uplink resources do not include uplink resources used for sounding reference signal transmission.

8. A method in a wireless device WD (22) configured to communicate with a network node (16), the method comprising: receiving (S138) a cancellation indication of the uplink resource to be cancelled; determining (S140) protected uplink resources to be protected from cancellation, wherein the determined protected uplink resources include uplink resources used for uplink control channel transmission; and Cancel (S142) transmission on uplink resources indicated to be canceled, except for uplink resources determined to be protected from cancellation, wherein even if the cancellation indication indicates that the resources to be canceled are overlapping with the uplink resources used for uplink control channel transmission, the uplink resources used for uplink control channel transmission are excluded from cancellation.

9. The method of claim 8, further comprising any features or steps as claimed in any one of claims 2 to 7.

10. A network node (16) configured to communicate with a wireless device WD (22), the network node (16) comprising: a processing circuit (68) configured to designate uplink resources of the WD (22) as protected uplink resources to be protected from cancellation, wherein the protected uplink resources include uplink resources used for uplink control channel transmission; and A radio interface (62) configured to transmit a protected resource indication indicating the protected uplink resources to the WD (22), wherein the uplink resources used for uplink control channel transmission are excluded from being cancelled even if a cancellation indication indicates that the resources to be cancelled are overlapping with the uplink resources used for uplink control channel transmission.

11. The network node (16) of claim 10, wherein: The processing circuit is further configured to specify uplink resources to be cancelled, and the radio interface is further configured to transmit the cancellation indication of the uplink resources to be cancelled to the WD (22).

12. The network node (16) of claim 11, wherein: The cancellation indication is transmitted in downlink control information DCI.

13. The network node (16) according to any one of claims 10 to 12, wherein: The protected resource indication is transmitted in downlink control information DCI.

14. The network node (16) according to any one of claims 10 to 12, wherein: The protected resource indication is transmitted in a group common message to be received by the WDs 22 in the group.

15. The network node (16) according to any one of claims 10 to 12, wherein: The protected resource indication indicates time domain resources instead of frequency domain resources.

16. A method in a network node (16) configured to communicate with a wireless device (WD) (22), the method comprising: designating uplink resources of the WD (22) as protected uplink resources to be protected from cancellation, wherein the protected uplink resources include uplink resources used for uplink control channel transmission; and A protected resource indication indicating the protected uplink resources is transmitted to the WD (22), wherein the uplink resources used for uplink control channel transmission are excluded from being cancelled even if a cancellation indication indicates that the resources to be cancelled are overlapping with the uplink resources used for uplink control channel transmission.

17. The method of claim 16, further comprising: Uplink resources to be cancelled are specified, and the radio interface is further configured to transmit the cancellation indication of the uplink resources to be cancelled to the WD (22).

18. The method of claim 17, further comprising any step or feature as claimed in any one of claims 12 to 15.

Images