Uplink transmission cancellation

Abstract

To provide improved methods, systems, devices and apparatuses for supporting uplink transmission cancellation.SOLUTION: In a method, a base station or other network entity allocates uplink resources to user equipment pieces (UEs), or groups of UEs, and the base station subsequently reallocates the uplink resources. For example, a base station determines a reallocation of the uplink resources, and issues a cancellation or preemption indication corresponding to at least a portion of the previously allocated resources (e.g., allocated to particular UEs).SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] Cross-reference

[0001] This patent application claims the priority of U.S. Patent Application No. 16 / 809,406, filed Mar. 4, 2020, by Fakorian et al. and titled "UPLINK TRANSMISSION CANCELLATION", which claims the benefit of U.S. Provisional Patent Application No. 62 / 843,198, filed Mar. 3, 2019, by Fakorian et al. and titled "UPLINK TRANSMISSION CANCELLATION", assigned to the assignee of this application.

[0002]

[0002] The following generally relates to wireless communication, and more particularly to uplink transmission cancellation.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE®) systems, LTE Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes called New Radio (NR) systems. These systems may utilize technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spreading orthogonal frequency division multiple access (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may sometimes be known as user equipment (UE).

[0004]

[0004] Some wireless communication systems, such as NR systems, may support heterogeneous conditions for one or more service deployments. For example, communication devices such as base stations or UEs may support flexibility in allocating multiple supported services or traffic types over channel resources. As part of channel resource allocation, base stations and UEs may support prioritizing some communications over others, which may include prioritizing traffic or services having different reliability thresholds, different latency thresholds, or both. In some cases, efficient system use may be based on how resources are shared or allocated between different traffic types or UEs configured according to different traffic types. [Overview of the project]

[0005]

[0005] The techniques described relate to improved methods, systems, devices, and apparatus for supporting uplink transmission cancellation. In some examples, a base station or other network entity may allocate uplink resources to a UE or group of UEs, and the resources are subsequently reallocated (for example, based on prioritizing communications). For example, a base station may determine the reallocation of uplink resources and issue cancellation indications that may correspond to at least a portion of previously allocated resources (for example, allocated to a particular UE). UEs may be configured to monitor cancellation indications, and based on the cancellation indications received, UEs may decide whether to proceed with an uplink transmission using the uplink resources previously allocated to them.

[0006]

[0006] In some examples, cancellation instructions are used to prevent the UE from using at least a portion of pre-allocated uplink resources for uplink transmissions, which can support the dynamic allocation of uplink resources from communications associated with one latency threshold to communications associated with another. For example, resources originally allocated for enhanced mobile broadband (eMBB) communications may be reallocated for ultra-reliable low-latency communications (URLLC) (e.g., reallocation to more performance-oriented communications). In one example, an eMBB UE decoding an uplink cancellation instruction message may cancel or otherwise preempt the uplink transmission (e.g., depending in part or all on whether the uplink cancellation applies to the allocated resources corresponding to the uplink transmission). In some cases, a particular UE may ignore a cancellation instruction when the instruction is intended to stop uplink transmissions from other UEs in order to reallocate the uplink resource to that particular UE or to the type of traffic that should be transmitted by that particular UE. Thus, according to these and other examples, various types of uplink resource allocations may be reallocated, pre-empted, or reallocated, thereby supporting dynamic redistribution of uplink resources in wireless communication systems, which more effectively balances communication execution and resource use according to different priorities.

[0007]

[0007] A method for wireless communication is described below. This method may include identifying an uplink resource allocation, receiving an uplink cancellation indication, determining whether the identified allocation of the uplink resource is to be canceled based on the uplink cancellation indication, and performing uplink communication based on the determination.

[0008]

[0008] The following describes a device for wireless communication. This device may include a processor, a memory coupled to the processor (for example, operationally, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by the processor to cause the device to identify an uplink resource allocation, receive an uplink cancellation instruction, determine whether the identified allocation of the uplink resource is to be cancelled based on the uplink cancellation instruction, and perform uplink communication based on the determination.

[0009]

[0009] Another device for wireless communication is described. This device may include means for identifying an uplink resource allocation, means for receiving an uplink cancellation instruction, means for determining whether an identified allocation of an uplink resource is to be cancelled based on the uplink cancellation instruction, and means for performing uplink communication based on the determination.

[0010]

[0010] A non-transitory computer-readable medium for storing code for wireless communication is described. The code may include processor-executable instructions for identifying an uplink resource allocation, receiving an uplink cancellation instruction, determining whether the identified allocation of the uplink resource is cancelled based on the uplink cancellation instruction, and performing uplink communication based on the determination.

[0011]

[0011] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the allocation of uplink resources may be associated with a first type of communications, and an uplink cancellation instruction may be associated with a second type of communications. In some examples, the first type of communications may have a first latency threshold, and the second type of communications may have a second latency threshold different from the first latency threshold. In some examples, the second type of communications may have a higher priority than the first type of communications. In some examples, performing an uplink communication may include performing either a first type of communications or a second type of communications uplink communication, based on a decision.

[0012]

[0012] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether an identified allocation of uplink resources is to be canceled may include operations, features, means, or instructions for determining whether at least a portion of the allocation of uplink resources corresponds to one or more of the subsets of communication resources to which the cancellation applies, where each bit of the bitmap corresponds to each subset of communication resources, and each bit indicates whether the cancellation applies to each subset of communication resources.

[0013]

[0013] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether an identified allocation of an uplink resource is to be revoked may include an operation, feature, means, or instruction for determining that the bitmap corresponds to an uplink bandwidth part configured for the UE.

[0014]

[0014] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for identifying a repetition indicator, repeating bits of a bitmap according to the repetition indicator, where each repeated bit of the bitmap corresponds to each subset of communication resources, and each repeated bit indicates whether cancellation applies to each subset of communication resources.

[0015]

[0015] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that each subset of communication resources corresponding to each bit of a bitmap corresponds to an uplink resource in the UE's uplink / downlink time division duplex (TDD) configuration.

[0016]

[0016] Some examples of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for receiving a cancellation configuration prior to receiving an uplink cancellation instruction associated with a pattern of communication resources in the time domain and frequency domain, wherein the uplink cancellation instruction specifies the time for applying the pattern of communication resources for cancellation.

[0017]

[0017] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the cancellation configuration includes a radio resource control (RRC) configuration.

[0018]

[0018] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining whether an identified allocation of an uplink resource is to be canceled may include an operation, feature, means, or instruction for determining the time to apply the cancellation based on the time the uplink cancellation instruction was received and a configured time offset for the cancellation.

[0019]

[0019] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the configured time offset for cancellation may be based on the capability of the UE.

[0020]

[0020] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining the time for applying cancellation may be based on the uplink / downlink time-division duplex (TDD) configuration of the UE.

[0021]

[0021] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for receiving an uplink grant after receiving an uplink revocation instruction, and for the uplink grant to ignore at least a portion of the uplink revocation instruction, based on the fact that an uplink grant has been received after receiving the uplink revocation instruction, including communication resources associated with the uplink revocation instruction.

[0022]

[0022] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, uplink permission may be received in a physical downlink control channel (PDCCH).

[0023]

[0023] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, ignoring at least a portion of an uplink cancellation instruction may be based on the fact that the uplink authorization is associated with a second type of communication.

[0024]

[0024] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, ignoring at least a portion of an uplink cancellation instruction may be based on the type of physical channel associated with the uplink authorization.

[0025]

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining whether an identified allocation of uplink resources is cancelled may be based on the type of physical channel associated with the uplink communication.

[0026]

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining whether an identified allocation of uplink resources is cancelled may be based on the type of physical channel associated with the uplink cancellation indication.

[0027]

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining whether an identified allocation of uplink resources is cancelled may be based on the allocation type associated with the identified allocation of the uplink resources.

[0028]

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining whether an identified allocation of uplink resources is cancelled may be based on a second type of communication.

[0029]

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining whether an identified allocation of uplink resources is cancelled may be based on a type of communications associated with the uplink communication.

[0030]

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink cancellation indication may be received in a group common physical downlink control channel (GC-PDCCH).

[0031]

[0031] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, performing uplink communication may include operations, features, means, or instructions for transmitting uplink transmissions on a subset of the allocation of uplink resources, based on the decisions made herein.

[0032]

[0032] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, performing uplink communication may include actions, features, means, or instructions to refrain from using at least a portion of the allocation of uplink resources based on the aforementioned determination.

[0033]

[0033] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the first type of communication includes extended mobile broadband (eMBB) communication, and the second type of communication includes ultra-high reliability low latency (URLLC) communication.

[0034]

[0034] A method for wireless communication is described. This method may include transmitting an uplink resource allocation, determining a reallocation of the uplink resource, and, based on the determination, transmitting an uplink cancellation instruction corresponding to the uplink resource.

[0035]

[0035] The following describes a device for wireless communication. This device may include a processor, a memory coupled to the processor (for example, operationally, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by the processor to cause the device to transmit an uplink resource allocation, to determine a reallocation of the uplink resource, and, based on the determination, to transmit an uplink cancellation instruction corresponding to the uplink resource.

[0036]

[0036] Another device for wireless communication is described. This device may include means for transmitting an uplink resource allocation, means for determining a reallocation of the uplink resource, and means for transmitting an uplink cancellation instruction corresponding to the uplink resource based on the determination.

[0037]

[0037] A non-temporary computer-readable medium for storing a code for wireless communication is described. The code may include processor-executable instructions for transmitting an uplink resource allocation, determining a reallocation of an uplink resource, and, based on the determination, transmitting an uplink cancellation instruction corresponding to the uplink resource.

[0038]

[0038] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the allocation of uplink resources may be associated with a first type of communication, and the determination of the reallocation of uplink resources may be based on a second type of communication. In some examples, the first type of communication may have a first delay threshold, and the second type of communication may have a second delay threshold different from the first delay threshold. In some examples, the second type of communication may have a higher priority than the first type of communication.

[0039]

[0039] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for generating a bitmap associated with a set of communication resources in the time domain and the frequency domain, where each bit of the bitmap corresponds to a respective subset of the communication resources, and each bit indicates whether a cancellation applies to a respective subset of the communication resources, and transmitting an uplink cancellation instruction may include transmitting a bitmap.

[0040]

[0040] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the bitmap corresponds to the configured uplink bandwidth portion.

[0041]

[0041] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting an uplink cancellation instruction may include an operation, feature, means, or instruction for transmitting a repeating indicator associated with a bitmap.

[0042]

[0042] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, each subset of communication resources corresponding to each bit of the bitmap corresponds to the uplink resource in an uplink / downlink TDD configuration.

[0043]

[0043] Some examples of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting a cancel configuration prior to transmitting an uplink cancel instruction associated with a pattern of communication resources in the time domain and the frequency domain, the uplink cancel instruction may indicate a time for applying the pattern of communication resources for canceling.

[0044]

[0044] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting a cancellation configuration may include an operation, feature, means, or instruction for transmitting an RRC configuration.

[0045]

[0045] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining the reallocation of resources may include an operation, feature, means, or instruction for determining the time to apply the cancellation, based on the time at which an uplink cancellation instruction is sent and a configured time offset for the cancellation.

[0046]

[0046] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the configured time offset for cancellation may be based on UE capability.

[0047]

[0047] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining the time for applying cancellation may be based on an uplink / downlink time-division duplex (TDD) configuration.

[0048]

[0048] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include actions, features, means, or instructions for transmitting an uplink authorization to a UE, which includes communication resources associated with an uplink cancellation instruction, the uplink authorization instructing the UE to ignore at least a portion of the uplink cancellation instruction.

[0049]

[0049] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, uplink permission may be transmitted in a physical downlink control channel (PDCCH).

[0050]

[0050] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, uplink authorization may be associated with a second type of communication, and instructions to the UE to ignore at least a portion of an uplink cancellation instruction may be based on the fact that uplink authorization is associated with a second type of communication.

[0051]

[0051] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, uplink permission may be associated with the type of physical channel, and instructions to the UE to ignore at least a portion of uplink cancellation instructions may be based on the type of physical channel.

[0052]

[0052] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, determining the reallocation of uplink resources may include operations, features, means, or instructions for determining the reallocation of uplink resources allocated to a physical random access channel (PRACH) based at least in part on trigger conditions for transmission associated with uplink resources allocated to a PRACH.

[0053]

[0053] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the uplink cancellation instruction may be specific to the type of uplink physical channel.

[0054]

[0054] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the uplink cancellation instruction may be specific to the type of uplink resource allocation.

[0055]

[0055] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting an uplink cancellation instruction may include an operation, feature, means, or instruction for transmitting a group common physical downlink control channel (GC-PDCCH).

[0056]

[0056] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for receiving communications from one or more user devices (UEs) and transmitting uplink cancellation instructions based on the reallocation of uplink resources.

[0057]

[0057] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the first type of communication includes extended mobile broadband (eMBB) communication, and the second type of communication includes ultra-high reliability low latency (URLLC) communication. [Brief explanation of the drawing]

[0058] [Figure 1]

[0058] A diagram illustrating an example of a system for wireless communications that supports uplink transmission cancellation according to an aspect of the present disclosure. [Figure 2]

[0059] A diagram illustrating an example of a system for wireless communications that supports uplink transmission cancellation according to the aspects of this disclosure. [Figure 3A]

[0060] A diagram illustrating an example of mapping the bitfield of an uplink cancellation instruction for uplink transmission cancellation to a communication resource, as disclosed herein. [Figure 3B] A diagram illustrating an example of mapping the bitfield of an uplink cancellation instruction for uplink transmission cancellation to a communication resource, as disclosed herein. [Figure 4A]

[0061] A diagram illustrating an example of a processing timeline supporting uplink transmission cancellation according to the aspects of this disclosure. [Figure 4B] A diagram illustrating an example of a processing timeline supporting uplink transmission cancellation according to the aspects of this disclosure. [Figure 5]

[0062] A diagram illustrating an example of a wireless communication system and corresponding operation that supports uplink transmission cancellation according to the aspects of this disclosure. [Figure 6]

[0063] A block diagram of a device supporting uplink transmission cancellation according to the manner of this disclosure. [Figure 7] A block diagram of a device supporting uplink transmission cancellation according to the manner of this disclosure. [Figure 8]

[0064] A block diagram of a communication manager supporting uplink transmission cancellation according to the manner of disclosure. [Figure 9]

[0065] A diagram of a system including a device that supports uplink transmission cancellation according to the aspect of this disclosure. [Figure 10]

[0066] A block diagram of a device supporting uplink transmission cancellation according to the manner of this disclosure. [Figure 11] A block diagram of a device supporting uplink transmission cancellation according to the manner of this disclosure. [Figure 12]

[0067] A block diagram of a communications manager supporting uplink transmission cancellation according to the manner of this disclosure. [Figure 13]

[0068] A diagram of a system including a device that supports uplink transmission cancellation according to the aspect of this disclosure. [Figure 14]

[0069] A flowchart illustrating a method for supporting uplink transmission cancellation in the manner of this disclosure. [Figure 15] A flowchart illustrating a method for supporting uplink transmission cancellation in the manner of this disclosure. [Figure 16] A flowchart illustrating a method for supporting uplink transmission cancellation in the manner of this disclosure. [Figure 17] A flowchart illustrating a method for supporting uplink transmission cancellation in the manner of this disclosure. [Modes for carrying out the invention]

[0059]

[0070] Some communication systems may support different traffic types (e.g., traffic categories), which may include or refer to communication traffic having different reliability thresholds, different latency thresholds, different services, or various combinations thereof. For example, a wireless communication system may support a first traffic type (e.g., communication type) associated with relatively high reliability targets or thresholds and relatively low latency targets or thresholds, such as the Ultra-High Reliability Low Latency (URLLC) traffic type. A wireless communication system may also support a second traffic type associated with relatively low reliability targets or thresholds and relatively long or relaxed latency thresholds, such as the Extended Mobile Broadband (eMBB) traffic type. In some cases, to support various system operations (e.g., efficient use of wireless communication resources, proper allocation or balancing of wireless communication resources, proper support of traffic with different prioritization or latency thresholds), a wireless communication system may support dynamic resource sharing between traffic types, such as dynamic allocation of resources between URLLC and eMBB communications, or other communications, based on different traffic types, categories, or other prioritizations.

[0060]

[0071] The techniques described include various examples of dynamic resource allocation by preemption of pre-allocated uplink resources by a base station or other network entity communicating with the base station, such as a controller or resource allocation agency. For example, a base station or other network entity may allocate uplink resources to a UE or group of UEs (e.g., initial uplink resource allocation), and the base station may then issue a preemption indication (e.g., an uplink allocation cancellation indication) that corresponds to at least a portion of the pre-allocated uplink resources (e.g., those allocated to a particular UE). The UE may then detect such a cancellation indication and decide whether to proceed with uplink transmission using the uplink resources pre-allocated to them.

[0061]

[0072] In some cases, cancellation instructions are used to prevent a UE from using at least a portion of a pre-allocated uplink resource for uplink transmission, which may support dynamic allocation of uplink resources from communications associated with one delay threshold to communications associated with another, or any other reallocation based on communication prioritization. For example, resources originally allocated to eMBB communications may be reallocated to URLLC communications (e.g., reallocation to more performance-oriented communications). In some cases, a particular UE may ignore a cancellation instruction when it is intended to stop uplink transmission from another UE in order to reallocate the uplink resource to that particular UE or to the type of traffic that should be transmitted by that particular UE. Thus, according to these and other examples, various types of uplink resource allocations may be cancelled, pre-empted, or reallocated, thereby supporting dynamic redistribution of uplink resources in wireless communication systems, which more effectively balances communication execution and resource use according to different priorities.

[0062]

[0073] The aspects of this disclosure will first be described in the context of wireless communication systems. These aspects will be further illustrated and described by examples of signaling, operation, and resource mapping that may support the described techniques for uplink transmission cancellation. These aspects will also be illustrated and described by apparatus diagrams, system diagrams, and flowcharts relating to uplink transmission cancellation.

[0063]

[0074] Figure 1 shows an example of a wireless communication system 100 supporting uplink transmission cancellation according to an aspect of the present disclosure. The wireless communication system 100 includes a base station 105, an UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long-Term Evolution (LTE) network, an LTE Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support extended broadband communication, ultra-high reliability (e.g., mission-critical) communication, low-latency communication, or communication using low-cost and low-complexity devices.

[0064]

[0075] Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. Base station 105 as described herein may include, or be referred to by, any other appropriate term, base transceiver station, radio base station, access point, radio transceiver, node B, enode B (eNB), next-generation node B or giganode B (both of which may be called gNB), home node B, home enode B, or any other appropriate term. Wireless communication system 100 may include different types of base station 105 (e.g., macro base station or small cell base station). UE 115 as described herein may be able to communicate with various types of base station 105 and network equipment, including macro eNB, small cell eNB, gNB, relay base station, etc.

[0065]

[0076] Each base station 105 may be associated with a specific geographical coverage area 110 that supports communication with various UEs 115. Each base station 105 can provide communication coverage to its respective geographical coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UEs 115 may use one or more carriers. The communication link 125 shown in the wireless communication system 100 may include uplink transmissions from the UEs 115 to the base station 105, or downlink transmissions from the base station 105 to the UEs 115. Downlink transmissions are sometimes called forward link transmissions, and uplink transmissions are sometimes called reverse link transmissions.

[0066]

[0077] A geographical coverage area 110 for a base station 105 may be divided into sectors that constitute a portion of the geographical coverage area 110, each sector may be associated with a cell. For example, each base station 105 may provide communication coverage to macrocells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, a base station 105 may be mobile and therefore provide communication coverage to a moving geographical coverage area 110. In some examples, different geographical coverage areas 110 related to different technologies may overlap, and overlapping geographical coverage areas 110 related to different technologies may be supported by the same base station 105 or by different base stations 105. The wireless communication system 100 may include, for example, heterogeneous LTE / LTE-A / LTE-A Pro or NR networks in which different types of base stations 105 provide coverage to various geographical coverage areas 110.

[0067]

[0078] The term “cell” refers to a logical communication entity used for communication with a base station 105 (for example, via a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) to distinguish neighboring cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and various cells may be configured according to various protocol types (e.g., machine-type communications (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), etc.) that can provide access to various types of devices. In some cases, the term “cell” may refer to a portion (e.g., a sector) of a geographical coverage area 110 on which the logical entity operates.

[0068]

[0079] The UE115 may be distributed throughout the wireless communication system 100, and each UE115 may be fixed or mobile. The UE115 may also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other preferred term, where “device” may also be referred to as a unit, station, terminal, or client. UE115 may be a cellular phone, smartphone, personal digital assistant (PDA), multimedia / entertainment device (e.g., radio, MP3 player, video device, etc.), camera, game console, navigation / positioning device (e.g., GNSS (Global Navigation Satellite System) devices based on GPS (Global Positioning System), Beidou, GLONASS, or Galileo, ground-based devices, etc.), tablet computer, laptop computer, netbook, smartbook, personal computer, smart device, wearable device (e.g., smartwatch, smart clothing, smart glasses, virtual reality goggles, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), drone, robot / robot device, vehicle, vehicle device, meter (e.g., parking meter, electric meter, gas meter, water meter), monitor, gas pump, household appliance (e.g., kitchen appliance, washing machine, dryer), location tag, medical / healthcare device, implant, sensor / actuator, display, or any other suitable device configured to communicate via wireless or wired media. In some examples, UE115 could also refer to wireless local loop (WLL) stations, Internet of Things (IoT) devices, Internet of Things (IoE) devices, or MTC devices, which can be implemented in a variety of items such as home appliances, drones, robots, vehicles, and meters.

[0069]

[0080] Some UE115s, such as MTC devices or IoT devices, may be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with base stations 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information, relay that information to a central server or application program where the information can be made available, or present the information to a human interacting with the program or application. Some UE115s may be designed to collect information or enable automated machine behavior. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security detection, physical access control, and transaction-based business billing. In some embodiments, the techniques disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC / Enhanced MTC (eMTC, also known as CAT-M or Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT may refer to future technologies that can evolve from or build upon these technologies. For example, eMTC may include FeMTC (Further eMTC), eFeMTC (Further Enhanced eMTC), mMTC (Mass MTC), etc., and NB-IoT may include eNB-IoT (Enhanced NB-IoT), FeNB-IoT (Further Enhanced NB-IoT), etc.

[0070]

[0081] Some UE115s may be configured to utilize power-saving operating modes, such as half-duplex communication (for example, a mode that supports one-way communication via transmit or receive rather than simultaneous transmit and receive). In some examples, half-duplex communication may be implemented at a reduced peak rate. Other power-saving techniques for the UE115 include entering a power-saving "deep sleep" mode when not engaged in active communication, or operating on a limited bandwidth (for example, according to narrowband communication). In some cases, the UE115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

[0071]

[0082] In some cases, a UE115 may also communicate directly with other UE115s (for example, using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more of the groups of UE115s using D2D communication may be within the geographical coverage area 110 of base station 105. Other UE115s in such a group may be outside the geographical coverage area 110 of base station 105, or otherwise unable to receive transmissions from base station 105. In some cases, a group of UE115s communicating via D2D communication may use a one-to-many (1:M) system where each UE115 transmits to any other UE115 in the group. In some cases, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is practiced between UE115s without the involvement of base station 105.

[0072]

[0083] The base stations 105 can communicate with the core network 130 and with each other. For example, a base station 105 may interface with the core network 130 through the backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other either directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) over the backhaul link 134 (e.g., via X2, Xn, or other interfaces).

[0073]

[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an advanced packet core (EPC) that includes at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access layer functions (e.g., control plane) such as mobility, authentication, and bearer management for UE 115 serviced by base station 105 associated with the EPC. User IP packets may be forwarded through an S-GW which may itself be connected to a P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to a network operator's IP services. The operator's IP services may include access to the Internet, intranet, IP multimedia subsystem (IMS), or packet-switched (PS) streaming services.

[0074]

[0085] At least some of the network devices, such as the base station 105, may include sub-components such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity can communicate with the UE 115 via several other access network transmitting entities, which may be called radio heads, smart radio heads, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or integrated into a single network device (e.g., base station 105).

[0075]

[0086] The wireless communication system 100 may typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, as the wavelengths range from approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by building and environmental features. However, the waves can penetrate structures well enough to serve the UE 115 where the macrocell is located indoors. Transmitting UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmitting using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0076]

[0087] The wireless communication system 100 may also operate in the centimeter wave (SHF: super high frequency) region, which uses a frequency band from 3 GHz to 30 GHz, also known as the centimeter band. The SHF region includes bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which may be opportunistically used by devices that may tolerate interference from other users.

[0077]

[0088] The wireless communication system 100 can also operate in the millimeter-wave (EHF: extremely high frequency) region of the spectrum (e.g., 30 GHz to 300 GHz), also known as the millimeter-band. In some examples, the wireless communication system 100 may support millimeter-wave (mmW) communication between a UE 115 and a base station 105, where the EHF antennas of each device may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions is subject to greater atmospheric attenuation than SHF or UHF transmissions, and the distances may be shorter. The techniques disclosed herein may be used across transmissions using one or more different frequency domains, and the specified use of bands across these frequency domains may vary by country or regulatory body.

[0078]

[0089] In some cases, the wireless communication system 100 may use both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may utilize licensed assisted access (LAA), LTE unlicensed (LTE U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz ISM band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as base stations 105 and UE 115 may utilize listen-before-talk (LBT) procedures to ensure that the frequency channel is clear before transmitting data. In some cases, operation in unlicensed bands may be based on a carrier aggregation configuration with component carriers operating in licensed bands (e.g., LAA). Operation in unlicensed spectrums may include downlink transmission, uplink transmission, peer-to-peer transmission, or a combination thereof. Duplexing in unlicensed spectrums may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.

[0079]

[0090] In some examples, a base station 105 or UE 115 may be equipped with multiple antennas, which may be used to utilize techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, a wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may utilize multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals through different spatial layers, which may be called spatial multiplexing. Multiple signals may be transmitted by the transmitting device through different antennas or different combinations of antennas. Similarly, multiple signals may be received by the receiving device through different antennas or different combinations of antennas. Each of the multiple signals may be called a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0080]

[0091] Beamforming, sometimes called spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting or receiving device (e.g., base station 105 or UE115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that signals propagating in a particular direction relative to the antenna array undergo constructive interference while other signals undergo destructive interference. Coordination of signals communicated through antenna elements may involve the transmitting or receiving device applying specific amplitude and phase offsets to the signals carried through each of the antenna elements associated with the device. Coordination associated with each antenna element may be defined by a beamforming weight set associated with a particular direction (e.g., relative to the antenna array of the transmitting or receiving device, or to some other direction).

[0081]

[0092] In one example, base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, several signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions, which may include the signals being transmitted according to different beamforming weight sets associated with different transmission directions. Transmissions in various beam directions may be used to identify the beam direction for subsequent transmission and / or reception by base station 105 (e.g., by base station 105 or a receiving device such as UE 115).

[0082]

[0093] Some signals, such as data signals associated with a specific receiving device, may be transmitted by the base station 105 in a single beam direction (e.g., the direction associated with a receiving device such as UE115). In some examples, the beam direction associated with a transmission along a single beam direction may be determined at least in part on signals transmitted in various beam directions. For example, UE115 may receive one or more signals transmitted by base station 105 in different directions, and UE115 may report to base station 105 an indication of the signal it received with the best signal quality, or otherwise an acceptable signal quality. While these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE115 may utilize similar techniques to transmit a signal multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE115) or to transmit a signal in a single direction (e.g., to transmit data to a receiving device).

[0083]

[0094] A receiving device (for example, UE115, which may be an example of a mmW receiving device) can attempt multiple receive beams when receiving various signals from base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may attempt multiple receive directions by receiving through various antenna subarrays, by processing the received signal according to various antenna subarrays, by receiving according to various sets of receive beamforming weights applied to the received signal at multiple antenna elements of an antenna array, or by processing the received signal according to various sets of receive beamforming weights applied to the received signal at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to various receive beams or receive directions. In some examples, a receiving device may use a single receive beam to receive along a single beam direction (for example, when receiving a data signal). A single receive beam may be matched in a beam direction determined at least partially based on listening according to different receive beam directions (for example, a beam direction determined to have the highest signal intensity, the highest signal-to-noise ratio, or otherwise acceptable signal quality, at least partially based on listening according to multiple beam directions).

[0084]

[0095] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays that can support MIMO operation or transmit beamforming or receive beamforming. For example, one or more base station antennas or antenna arrays may be colocate in an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be located in diverse geographical locations. Base station 105 may have an antenna array having several rows and columns of antenna ports that base station 105 can use to support beamforming of communications with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations.

[0085]

[0096] In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use Hybrid Automatic Retransmission Requests (HARQ) to perform retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may establish, configure, and maintain RRC connections between the UE 115 and the base station 105 or core network 130, supporting radio bearers for user plane data. In the physical layer, transport channels may be mapped to physical channels.

[0086]

[0097] In some cases, the UE 115 and base station 105 may support data retransmission to increase the likelihood of successful data reception. HARQ feedback is one technique that increases the likelihood of data being correctly received over the communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic retransmission request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise conditions). In some cases, wireless devices may support same-slot HARQ feedback, where the device implements HARQ feedback in a particular slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0087]

[0098] The time interval in LTE or NR is, for example, T s = can be expressed as a multiple of the basic time unit, which can refer to a sampling period of 1 / 30,720,000 seconds. The time interval of the communication resources may be organized according to radio frames, each having a duration of 10 milliseconds (ms), and the frame duration is T f =307,200T sThis can be expressed as follows: A wireless frame can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may contain 10 subframes numbered from 0 to 9, each subframe having a duration of 1 ms. A subframe may be further divided into two slots, each having a duration of 0.5 ms, and each slot may contain 6 or 7 modulated symbol periods (depending, for example, on the length of a cyclic prefix added to the beginning of each symbol period). Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the smallest scheduling unit of the wireless communication system 100 and may be called a transmit time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (for example, in a burst of shortened TTIs (sTTIs) or using sTTIs in selected component carriers).

[0088]

[0099] In some wireless communication systems, a slot may be further divided into multiple minislots, each containing one or more symbols. In some cases, the symbols or minislots within a minislot may be the smallest unit of scheduling. For example, each symbol may vary in duration depending on the subcarrier interval or operating frequency band. Furthermore, some wireless communication systems may implement slot aggregation, where multiple slots or minislots are aggregated together and used for communication between the UE115 and the base station 105.

[0089]

[0100] The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication over communication link 125. For example, the carrier of communication link 125 may include a portion of the radio frequency spectrum band operating according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. The carrier may be associated with a predefined frequency channel (e.g., an Advanced Universal Mobile Communications System Terrestrial Radio Access Network (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be arranged according to a channel raster for discovery by UE 115. The carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted over the carrier may consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM).

[0090]

[0101] The carrier organization structure can differ across different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR). For example, communications over a carrier may be organized according to TTI or slots, each of which may include user data as well as control information or signaling to support decoding the user data. A carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling to coordinate operations for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition or control signaling to coordinate operations for other carriers.

[0091]

[0102] Physical channels can be multiplexed on the carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on the downlink carrier using, for example, time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM techniques. In some examples, control information transmitted in the physical control channel can be distributed in a cascaded manner between different control domains (for example, between a common control domain or common search space and one or more UE-specific control domains or UE-specific search spaces).

[0092]

[0103] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths for the carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each serviced UE 115 may be configured to operate over a portion or all of the carrier bandwidth. In other examples, some UE 115 may be configured for operation using a narrowband protocol type associated with a predefined portion or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., an “in-band” deployment of a narrowband protocol type).

[0093]

[0104] In systems utilizing MCM techniques, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, with the symbol period and subcarrier interval being inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements the UE115 receives, and the higher the order of the modulation scheme, the higher the data rate of the UE115 can be. In MIMO systems, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate for communication with the UE115.

[0094]

[0105] Devices in the wireless communication system 100 (for example, base station 105 or UE 115) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include base station 105 and / or UE 115 that support simultaneous communication over carriers associated with two or more different carrier bandwidths.

[0095]

[0106] The wireless communication system 100 may support a feature sometimes called carrier aggregation or multi-carrier operation, which involves communication with the UE 115 over multiple cells or carriers. The UE 115 may consist of multiple downlink component carriers and one or more uplink component carriers according to the carrier aggregation configuration. Carrier aggregation may be used with both FDD component carriers and TDD component carriers.

[0096]

[0107] In some cases, the wireless communication system 100 may use an enhanced component carrier (eCC). An eCC may be characterized by one or more features, including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (for example, when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in an unlicensed or shared spectrum (for example, when two or more operators are permitted to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that can be used by a UE 115 that is configured to use a limited carrier bandwidth (for example, to conserve power) or where it is not possible to monitor the entire carrier bandwidth.

[0097]

[0108] In some cases, eCC may use different symbol durations than other component carriers, which may include the use of reduced symbol durations compared to those of other component carriers. Shorter symbol durations may be associated with increased spacing between adjacent subcarriers. Devices such as UE115 or base station 105 using eCC may transmit broadband signals (e.g., according to frequency channels or carrier bandwidths such as 20, 40, 60, 80 MHz) with shortened symbol durations (e.g., 16.67 microseconds). The TTI in eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) may be variable.

[0098]

[0109] The wireless communication system 100 may be an NR system capable of using any combination of licensed spectrum, shared spectrum, and unlicensed spectrum bands. Flexibility in eCC symbol duration and subcarrier spacing can enable the use of eCC across multiple spectrums. In some examples, NR shared spectrum can increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across frequency domains) and horizontal (e.g., across time domains) sharing of resources.

[0099]

[0110] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems may be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Wireless networks, such as Wi-Fi® (i.e., IEEE 802.11) networks, and wireless local area networks (WLANs) may include access points (APs) that can communicate with one or more wireless or mobile devices. APs may be coupled to a network, such as the Internet, and may enable mobile devices to communicate over the network (or with other devices coupled to the access point). Wireless devices may communicate bidirectionally with network devices. For example, in a WLAN, a device may communicate with an associated AP via downlink (e.g., a communication link from the AP to the device) and uplink (e.g., a communication link from the device to the AP). Wireless personal area networks (PANs), which may include Bluetooth® connectivity, may provide short-range wireless connectivity between two or more paired wireless devices. For example, wireless devices such as cellular phones may use wireless PAN communication to exchange information, such as audio signals, with wireless headsets. Components within a wireless communication system are coupled to one another (for example, operationally, communicatively, functionally, electronically, and / or electrically).

[0100]

[0111] The wireless communication system 100 may be configured to support different traffic types (e.g., traffic categories, traffic priorities, service priorities), which may include or refer to communication traffic having different reliability thresholds, different delay thresholds, different services, or various combinations thereof. For example, the wireless communication system 100 may support a first traffic type (e.g., communication type) associated with a relatively high reliability target or threshold and a relatively low delay target or threshold, such as an ultra-high reliability low-latency communication (URLLC) traffic type. The wireless communication system 100 may also support a second traffic type associated with a relatively low reliability target or threshold and a relatively long or relaxed delay threshold, such as an extended mobile broadband (eMBB) traffic type. In some cases, to support various system operations (e.g., efficient use of wireless communication resources, appropriate allocation or balancing of wireless communication resources, appropriate support of traffic with different priorities or delay thresholds), the wireless communication system 100 may support dynamic resource sharing between traffic types, such as dynamic allocation of resources between URLLC communication and eMBB communication or other communications, based on different traffic types, categories, or other priorities.

[0101]

[0112] To support various uplink resource allocation techniques, base station 105 or other network entities (e.g., entities in core network 130, entities in distributed base station 105) may allocate uplink resources (e.g., initial uplink resource allocation) to UE 115, or groups of UE 115, for uplink transmission. In some examples, base station 105 or other network entities may subsequently decide to reallocate pre-allocated uplink resources, which may be triggered by a decision or detected need, desire, or request, for example, to support higher-priority communications. Thus, base station 105 or other network entities may generate and transmit uplink cancellation indications (ULCIs) that correspond to at least a portion of the pre-allocated uplink resources (e.g., those allocated to a particular UE 115). UE 115 may be configured to monitor ULCIs and therefore, based at least in part on received, detected, or decoded ULCIs, may decide whether to proceed with uplink transmission using the pre-allocated uplink resources to them.

[0102]

[0113] In some examples, ULCI is used to prevent a UE115 from using at least a portion of pre-allocated uplink resources for uplink transmissions, which may support dynamic allocation of uplink resources from communications associated with one delay threshold to communications associated with another, or any other reallocation based on communication prioritization. For example, resources originally allocated to a UE115 for eMBB communications (e.g., allocated to an eMBB UE and allocated to a UE115 configured for eMBB communications) may be reallocated to the same UE115 or a different UE115 for URLLC communications (e.g., reallocated to more performance-oriented communications). In some examples, a particular UE115 may ignore ULCI when ULCI is intended to stop uplink transmissions from other UE115s in order to reallocate uplink resources to a specific UE115 or to the type of traffic that should be transmitted by that particular UE115. Therefore, according to these and other examples, various types of uplink resource allocations may be canceled, pre-empted, or reallocated, thereby enabling the wireless communication system 100 to support more dynamic redistribution of uplink resources based on different communication priorities.

[0103]

[0114] Figure 2 shows an example of a wireless communication system 200 supporting uplink transmission cancellation according to an aspect of the present disclosure. The wireless communication system 200 may include a base station 105-a that supports communication with multiple UEs (e.g., UE115-a and UE115-b) within a supported geographical coverage area 110-a. In some examples, the communication may support mission-critical applications, including stringent communication performance (e.g., reliability thresholds, delay thresholds), along with other types of communication. The wireless communication system 200 may implement aspects of the wireless communication system 100 described with reference to Figure 1.

[0104]

[0115] In the wireless communication system 200, UE115-a and UE115-b may support different service deployments, such as URLLC services and eMBB services. For example, UE115-a may support URLLC transmission to reduce end-to-end latency for data transmission and reception associated with base station 105-a. In some examples, UE115-a may support transmissions of relatively small data packets, such as periodic transmissions, or correspond to URLLC UEs otherwise configured for that purpose. For example, UE115-a may include URLLC UEs that support data communications with operations associated with factory automation (e.g., automated manufacturing, supply chain management), transportation (e.g., vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication), or power distribution within a supported area or region (e.g., power grids), among other possible implementations.

[0105]

[0116] As an addition or alternative, UE115-b may support eMBB transmissions associated with high data rates over a wide coverage area supported by base station 105-a (e.g., geographical coverage area 110-a). In some examples, eMBB communications may be associated with relatively relaxed (e.g., longer) latency targets or thresholds, lower reliability targets or thresholds, or both, compared to URLLC communications. Furthermore, one or more of UE115-a and UE115-b may support data communications associated with multiple service deployments (e.g., URLLC and eMBB) as part of intra-UE or inter-UE operations.

[0106]

[0117] To support conditions associated with URLLC and eMBB service deployment, or other types of resource allocation based on communication prioritization, base stations 105-a and UEs 115-a and 115-b may support various techniques for dynamic uplink resource allocation and uplink transmission cancellation or preemption. For example, base station 105-a may be configured to transmit a ULCI at least in part on having decided to reallocate an uplink resource (for example, associated with an uplink resource allocated to one or both of UEs 115-a or 115-b), and UEs 115-a and 115-b may monitor such ULCIs to determine how to proceed with uplink communication. In other words, UEs 115 may be notified about cancelled uplink resources in the time domain and frequency domain. In various examples, each of the UE115-a or UE115-b may make uplink communication decisions, such as deciding whether to perform or proceed with an uplink transmission using at least a portion of the uplink resources pre-allocated to them, deciding to refrain from using at least a portion of the uplink resources pre-allocated to them, deciding to wait for another allocation of uplink resources before initiating or resuming uplink communication, or other decisions.

[0107]

[0118] ULCI can be signaled by base station 105-a to UE 115 (e.g., one or both of UE 115-a or 115-b, a group of UEs) according to various techniques. For example, UE 115 may be configured to monitor ULCI via various signaling by base station 105-a, such as various types of downlink control signaling, physical channel signaling, cell-specific signaling, etc. In some examples, ULCI may be transmitted in downlink control information (DCI) via a physical downlink control channel (PDCCH), which may support UE-specific ULCI. In some examples, UE 115 may be configured (e.g., by base station 105-a) to have a radio network temporary identifier (RNTI) for monitoring the PDCCH which may be carrying ULCI. In various examples, UE115 may be configured to have a common RNTI between uplink and downlink cancellation or preemption instructions, or different RNTIs between uplink and downlink cancellation or preemption instructions.

[0108]

[0119] In some examples, ULCI may be configured or transmitted in a group-common physical downlink control channel (GC-PDCCH), or otherwise in a group-common DCI (GC-DCI), or DCI format 2_1, which can support signaling ULCI associated with one or more sets of UE115s and can reduce signaling overhead compared to ULCI transmitted in UE-specific signaling. In some examples, ULCI, or GC-PDCCH or GC-DCI instruction, may be configured for a UE115 configured for a specific communication, such as eMBB communication (e.g., configured for eMBB UEs).

[0109]

[0120] In some examples, uplink cancellation may include various configurations, such as an RRC configuration or other connection establishments between base station 105-a and UE 115. For example, such configurations may be signaled to UE 115 (for example, by base station 105-a) in an information element (IE) or other configuration for uplink cancellation (e.g., UplinkCancellation or UplinkPreemption IE, int-RNTI configuration).

[0110]

[0121] A ULCI may be configured to be associated with a specific bandwidth in the frequency domain (e.g., a frequency carrier, frequency channel, bandwidth portion, or a set of one or more physical resource blocks (PRBs) in the frequency domain). In one example, UE115 may be configured according to an uplink bandwidth portion, and the set of PRBs for the received ULCI may be equal to or otherwise correspond to the active uplink bandwidth portion configured for UE115. In such an example, the cancellation or take-back associated with the ULCI may correspond to the entire configured uplink bandwidth or uplink bandwidth portion (e.g., uplink take-back without frequency domain partitioning), or the cancellation or take-back associated with the ULCI may correspond to some portion of the resources in the configured uplink bandwidth or uplink bandwidth portion (e.g., uplink take-back with frequency domain partitioning). Such divisions or partitioning may be called the granularity of resources in the frequency domain for uplink cancellation.

[0111]

[0122] ULCI may be configured to be associated with specific communication resources in the time domain, which may be comprised of RRC configurations (e.g., by base station 105-a) or other configurations. For example, resources in the time domain to which cancellation applies (e.g., corresponding to ULCI) may be indicated in symbol level intervals (e.g., symbol duration, OFDM symbol duration), such as a set of seven symbol durations or a set of fourteen symbol durations, or in subslots, such as seven subslots, each having a length of two symbol durations or four symbol durations. Such division or segmentation may be referred to as the granularity of resources in the time domain for cancellation, and in some examples, such granularity of resources in the time domain may be common between uplink cancellation or preemption and downlink cancellation or preemption.

[0112]

[0123] In various examples, the granularity of time-domain resources for uplink cancellation may depend on the granularity of frequency-domain partitioning, or the granularity of resources in the time-domain and frequency-domain may otherwise be correlated. For example, if the granularity of frequency-domain partitioning is relatively fine for a given number of bits in the cancellation bitfield, the granularity of time-domain partitioning may be relatively coarse. In an example for one explanation, the first configuration may include time-domain partitioning at the symbol level without frequency-domain partitioning, and the second configuration may include time-domain partitioning at the subslot level with frequency-domain partitioning (e.g., by bipartite in the frequency domain). In various examples, cancellation may be directed to a subset of resources corresponding to a given ULCI by bits in a bitfield contained within the ULCI, which may be associated with more flexible uplink cancellation, such as a relatively large number of choices for resource puncturing patterns or a relatively flexible amount of symbols to be cancelled, compared to other techniques.

[0113]

[0124] In some examples, the wireless communication system 200 may support two or more patterns of resources in the ULCI, such as supporting ULCI with or without frequency domain segmentation. A base station 105-a or other network entity may determine one of the resource patterns for the ULCI and signal the configuration to the UE 115 (e.g., by downlink control signaling, by RRC configuration), thereby enabling the UE 115 to properly interpret the ULCI received from the base station 105-a (e.g., according to the determined pattern). In one example, the UE 115 may support interpreting the ULCI (e.g., the bit field of the ULCI) according to two patterns of communication resources, which may be configured (e.g., by the base station 105-a) for one of the two patterns based on the value of the bit field in the configuration register or the DCI (e.g., a variable or IE timeFrequencySet). In the example for illustrative purposes, when the bit field value is 0, ULCI may be configured or interpreted to be for time-domain segmentation at the symbol level and without frequency-domain segmentation, and when the bit field value is 1, ULCI may be configured or interpreted to be for time-domain segmentation at the sub-slot level and with frequency-domain segmentation (for example, dividing the active uplink bandwidth portion into two subbands for the purpose of uplink cancellation).

[0114]

[0125] In some examples, a ULCI may be configured for or contain instructions for various repetition techniques. For example, a DCI corresponding to a ULCI may contain several bits (e.g., 1 or 2 bits, i.e., the first 2 bits of the ULCI bit field) that indicate the number of repetitions corresponding to a particular ULCI (e.g., from the time the ULCI is decoded). In the example for illustration, for a 2-bit repetition instruction, a value of 00 can indicate 0 repetitions, a value of 01 can indicate 1 repetition, a value of 10 can indicate 2 repetitions, and a value of 11 can indicate 3 repetitions. In various examples, repetitions may be applied at the bit level or the string level. In other examples, the UE115 may be configured more generally to interpret or apply repetitions to the received ULCI, thereby reducing the signaling overhead associated with repetition instructions.

[0115]

[0126] In an example for illustrative purposes, UE115 may be configured to identify or map the ULCI bit field in the group common DCI (GC-DCI) as 100000111 and interpret the first two bits (e.g., 10) as a repetition instruction indicating two repetitions (for example, assume UE115 is configured to have a 7-bit ULCI at the symbol level). Thus, UE only needs to apply the cancel pattern indicated by the remaining bits (e.g., 0000111, i.e., a bit field with a length of 7 bits) three times. When UE is configured to apply bit-level repetitions, UE may interpret the pattern indicated by the ULCI bit field as |000|000|000|000|111|111|111|, where the vertical bar is added for clarity to indicate that each bit is repeated three times before moving to the next remaining bit in the bit field. When the UE is configured to apply string-level repetition, the UE may interpret the pattern indicated by the ULCI bit field as |0000111|0000111|0000111|, where the vertical bar is added for clarity to indicate that the entire string of remaining bits is interpreted before the string of remaining bits is repeated again (for example, according to the indicated two repetitions). Thus, in either case, the indicated repetitions may support the UE in identifying 21 resources of the ULCI that may or may not be subject to cancellation based on seven bits of the bit field. In various cases, the above scenario may or may not assume any frequency domain partitioning, or it may include frequency domain partitioning. These and other techniques for indicating uplink cancellation repetitions may be combined with configurations for granularity in the time domain and frequency domain (e.g., a specific set of resources corresponding to each bit in the bit string), and other aspects of the ULCI.

[0116]

[0127] In another example, the wireless communication system 200 may support configuration or preconfiguration (for example, in a UE 115 at a base station 105) having a set of patterns for cancellation, including static configuration, semi-static configuration, and configuration by network entities (for example, a core network 130). In such an example, base station 105-a may select one of the configured set of patterns and send an instruction to UE 115 identifying the selected pattern. UE 115 may receive the instruction and, accordingly, process the received ULCI according to the instructed pattern when interpreting the received ULCI (for example, to support determining whether the received ULCI applies to the allocation of uplink resources). In various examples, such configuration or preconfiguration may be specific to a particular UE 115, common to a set of UE 115 (for example, according to a UE configured for a certain type of communication, according to group common signaling), or common to all UE 115 served by a cell or base station 105.

[0117]

[0128] In some examples, a pattern may be defined according to a start and length indicator value (SLIV) or an SLIV table, which may refer to a start symbol or other time for uplink cancellation, and a length or duration for cancellation. In various examples, the number of rows in such a table may correspond to, or otherwise be associated with, the number of bits for signaling a particular row. For example, in the case of a 16-row SLIV table, SLIV instruction signaling may be associated with 4 bits. In various examples, the signaling of such cancellation resource patterns (e.g., rows in an SLIV table) may accompany or precede a ULCI, and the ULCI itself may signal (e.g., in a single bit or flag) when the indicated pattern should be considered or applied for cancellation. In an example for illustrative purposes, base station 105-a may configure an SLIV table defining a set of SLIV patterns for cancellation for one or more UEs 115 (e.g., eMBB UEs, UEs configured for eMBB communications), and the bit width of the ULCI may be determined based on this SLIV table. In some cases, signaling which of the pre-configured set of cancellation patterns should be applied in uplink cancellation may be associated with lower signaling overhead than other techniques, such as signaling the entire bit field for the cancellation pattern along with each ULCI.

[0118]

[0129] Figures 3A and 3B illustrate examples of mapping a bit field of ULCI to communication resources for uplink transmit cancellation as per the present disclosure. For example, mappings 300-a and 300-b each illustrate how a bit field with the value 00011111010000 (e.g., a bitmap with a length of 14 bits) may be mapped to resources in the time and frequency domains for uplink cancellation, where a value of "0" indicates that cancellation is neither applied nor enabled for the indicated resource (e.g., the frequency-time portion), and a value of "1" indicates that cancellation is applied or enabled for the indicated resource. In other words, mappings 300-a and 300-b each illustrate an example of dividing a time and frequency resource into 14 parts mapped with 14 bits for uplink cancellation instructions.

[0119]

[0130] Mapping 300-a illustrates an example in which frequency domain segmentation is not used or configured within the ULCI. For example, the bit field may correspond to a duration 310-a in the time domain and a bandwidth 315-a in the frequency domain, where the duration 310-a may be equal to the cancel instruction periodicity. In some examples, the bandwidth 315-a may correspond to a configured uplink bandwidth portion (e.g., for UE115, for a set of UE115). In the example for one explanation, the bandwidth 315-a may be 10 MHz, but the techniques described may be applied to other bandwidths 315-a. Mapping 300-a may be applied according to a start time 330-a, which in some examples may be measured or started based at least in part on the time at which a particular ULCI is received (e.g., ULCI symbol, ULCI symbol duration) and a configured time offset. The periodicity of the cancel instruction for mapping 300-a is 2 slots (e.g., 28 symbols), and each bit in the bit field may correspond to a duration 320-a in the time domain (e.g., two symbol durations) equal to two symbols. Thus, each bit may correspond to a subset of communication resources corresponding to mapping 300-a, where the subset refers to a single instance of a communication resource having a duration 320-a and a bandwidth 315-a in order in the time domain. When a bit in the bit field has a value of 1, the cancel may be applied to the entire bandwidth 315-a (e.g., the entire configured uplink bandwidth portion).

[0120]

[0131] Mapping 300-b illustrates an example where frequency domain segmentation is used and configured within a ULCI. For example, the bit field may correspond to a duration 310-b in the time domain and a bandwidth 315-b in the frequency domain, where the duration 310-b may be equal to the cancel instruction periodicity. In various examples, the duration 310-b and bandwidth 315-b of mapping 300-b may or may not be equal to the duration 310-a and bandwidth 315-a of mapping 300-a. For example, bandwidth 315-b may correspond to a configured uplink bandwidth portion (e.g., for UE115, for a set of UE115). In the example for one explanation, bandwidth 315-b may be 10 MHz, but the techniques described may be applied to other bandwidths 315-b. Mapping 300-b may be applied according to a start time 330-b, which may be measured or started based at least in part on the time when a particular ULCI is received and the configured time offset.

[0121]

[0132] The cancel instruction periodicity for mapping 300-b is 2 slots (e.g., 28 symbols), and each bit in the bit field may correspond to the duration 320-b in the time domain (e.g., 4 symbol durations) of 4 symbols. However, in the example of mapping 300-b, each bit in the bit field may correspond to a fragment with bandwidth 315-b equal to bandwidth 325-b. In other words, each bit may correspond to a subset of communication resources corresponding to mapping 300-b, where the subset refers to a single instance of a communication resource having duration 320-b and bandwidth 325-b in order in the sawtooth pattern as shown. In other words, the first bit in the bit pair for the symbol group may be applicable to a lower subset of bandwidth 315-b (e.g., a lower subset of the active uplink bandwidth portion), and the second bit in the bit pair for the symbol group may be applicable to a higher subset of bandwidth 315-b (e.g., the higher bandwidth 325-b, i.e., the higher subset of the active uplink bandwidth portion). However, other patterns may be used to interpret the bit field across mapping 300-b.

[0122]

[0133] In some examples, a wireless communication system can support uplink cancellation according to either mapping 300-a or mapping 300-b. Therefore, base station 105 can choose either mapping 300-a or mapping 300-b and generate the ULCI accordingly. For UE 115 to correctly interpret the ULCI (for example, so that UE 115 and base station 105 have the same understanding of the time and frequency uplink resources being cancelled), base station 105 can signal which of the two mappings was configured for the ULCI, which may refer to a granularity instruction about the time and frequency resources for uplink cancellation. In some examples, such an instruction may be configured during DCI according to the value of the variable timeFrequencySet associated with the uplink cancellation granularity. If base station 105 selected mapping 300-a, base station 105 may set the value of timeFrequencySet to 0, and if base station 105 selected mapping 300-b, base station 105 may set the value of timeFrequencySet to 1. In some examples, a wireless communication system may simultaneously support uplink cancellation by both mapping 300-a and mapping 300-b, signaling each subset of the ULCI (according to the configured bandwidth portion, for example, according to the monitored resource set) or a configuration for the UE115 configured to monitor each subset of the ULCI.

[0123]

[0134] Figures 4A and 4B show examples of processing timelines 400-a and 400-b supporting uplink transmission cancellation according to aspects of the present disclosure. Processing timelines 400-a and 400-b may represent a mode of communication performed by a wireless communication system 100 or 200 and may show an example of applying mapping 300-a, described with reference to Figure 3A, for uplink cancellation, where mapping 300-a is applied with symbol-level granularity in the time domain. Processing timelines 400-a and 400-b may represent a sequence of symbol durations 410, but the techniques described are applicable to other durations as well. Furthermore, although described in the context of mapping 300-a, the techniques described may also be applicable to other mappings, such as mapping 300-b, or other configured mappings such as SLIV.

[0124]

[0135] The processing timeline 400-a may begin with a ULCI symbol 420-a indicating the symbol or symbol duration at which the ULCI is received in UE115. In some examples, the ULCI symbol 420-a may be the final symbol of a CORESET configured for UE115 to monitor a PDCCH or GC-PDCCH for the ULCI. As shown in mapping 300-a with reference to Figure 3A, the ULCI associated with the ULCI symbol 420-a may include a bit field having the value 0001111101000, where a value of 0 indicates that no uplink cancellation is applied to the indicated resource, and a value of 1 indicates that an uplink cancellation is applied to the indicated resource.

[0125]

[0136] The specific resource to which an uplink cancellation is indicated by a bitfield may be based at least in part on the time the ULCI (e.g., ULCI symbol 420-a, uplink cancellation instruction) is received and the time required to process, respond to, or react to the received ULCI. In the example of processing timeline 400-a, the reference time 425-a may be time-aligned with the end of ULCI symbol 420-a. A time offset X may be applied to or added to the reference time 425-a to identify time 430-a, where the time offset X may be associated with action time, round-trip time (RTT), processing time, or other offset between the receipt of the ULCI and various processing operations. In some cases, the offset X may be UE-specific or based on UE capabilities. In some examples, the offset X may correspond to or be based on time N2, which may point to physical uplink shared channel (PUSCH) preparation time. For example, the UE processing time for ULCI may be equal to or less than time N2, or some other criterion, preparation, or processing time (e.g., PUSCH undo time). In the example of processing timeline 400-a, the time offset X may have a duration of 4.5 symbols. In other examples, the time offset X may have a duration of 5.5 symbols, or some other duration.

[0126]

[0137] The base station 105 or UE 115 can identify the resource for uplink cancellation based on time 430-a according to various techniques. In the example of processing timeline 400-a, the bit field may be mapped to the first symbol following time 430-a (e.g., a symbol that begins at time 440-a) and across a set of symbols 450-a. In other words, in the example of processing timeline 400-a, the start time 330-a of mapping 300-a may be aligned with time 440-a of processing timeline 400-a, and the duration 310-a of mapping 300-a may correspond to a set of symbols 450-a. Thus, in the example of processing timeline 400-a, there may be five symbol durations 410-a between the end of ULCI symbol 420-a and the start of the uplink cancellation corresponding to ULCI symbol 420-a (e.g., time 440-a). In some cases, UE115 may refrain from transmitting over an uplink resource (e.g., a symbol duration with a value of "1") that is instructed to be canceled or preempted by the processing timeline 400-a. In some cases, the cancellation decision by UE115 may be based on additional considerations, including those described with reference to the wireless communication system 500 described with reference to Figure 5.

[0127]

[0138] Processing timeline 400-b can illustrate another example for ULCI mapping instructions to communication resources, where the mapping is based on an uplink / downlink TDD configuration, which may refer to a semi-static configuration between base station 105 and UE 115 (e.g., indicated by the TDD-UL-DL-ConfigurationCommon setting). Some symbols in processing timeline 400-b are indicated according to an exemplary uplink / downlink TDD configuration, where "U" represents an uplink symbol, "D" represents a downlink symbol, and "X" represents a flexible symbol that can be dynamically configured as an uplink or downlink.

[0128]

[0139] Processing timeline 400-b may begin with a ULCI symbol 420-b indicating the symbol or symbol duration for which the ULCI is received at UE115, and this symbol may share the properties of ULCI symbol 420-a as described with reference to Figure 4A. In the example of processing timeline 400-b, the reference time 425-b may be time-aligned with the end of ULCI symbol 420-b. To identify time 430-b, a time offset X may be applied to or added to the reference time 425-b. In the example of processing timeline 400-b, the bit field may be mapped to a first symbol configured for the uplink (e.g., indicated by "U") following time 430-b (e.g., a symbol beginning at time 440-b), and may span the entire set of symbols 450-b. In other words, in the example of processing timeline 400-b, the start time 330-a of mapping 300-a may be aligned with time 440-b of processing timeline 400-b, and the duration 310-a of mapping 300-a may correspond to a set of symbols 450-b. Thus, in the example of processing timeline 400-b, there may be seven symbol durations 410-b between the end of ULCI symbol 420-b and the start of the uplink cancellation corresponding to ULCI symbol 420-b (e.g., time 440-b). However, such a set of durations may vary depending on the specific TDD configuration of base station 105 or UE 115. The bitfield mapping of processing timeline 400-b is described in the context of a first symbol configured for uplink following time 430-b, but in other examples, the bitfield may be mapped according to a first uplink or spatial symbol (e.g., whichever appears first) following time 430-b. In some cases, UE115 may refrain from transmitting over an uplink resource (e.g., a symbol duration with a value of "1") that is instructed to be canceled or preempted by processing timeline 400-b. In some cases, the cancellation decision by UE115 may be based on additional considerations, including those described with reference to the wireless communication system 500 described with reference to Figure 5.

[0129]

[0140] Processing timeline 400-b shows an example where, starting at time 440, the bit field is mapped to each of a set of consecutive symbol durations 410, although other examples of processing timeline 400 do not need to be mapped to consecutive symbol durations 410. In other words, the mapping of bit fields to other processing timelines 400 (not shown) may have gaps according to several techniques. For example, UE115 may not expect the ULCI bitmap to indicate uplink cancellation in a symbol configured for downlink communication (e.g., according to a semi-static configuration indicated by TDD-UL-DL-ConfigurationCommon), so UE115 may interpret the bit field of ULCI to instead map only to symbol durations configured as uplink symbol durations, or only to symbol durations configured as uplink or flexible symbol durations (e.g., skipping symbol durations configured as downlink symbol durations). Such techniques can reduce signaling overhead because the ULCI bits are not wasted on instructions about resources allocated to downlink transmissions.

[0130]

[0141] Figure 5 shows an example of a wireless communication system 500 and corresponding operation that supports uplink transmission cancellation according to an aspect of this disclosure. In some examples, the wireless communication system 500 can implement an aspect of the wireless communication system 100 or 200 described with reference to Figures 1 and 2. The wireless communication system 500 includes a base station 105-c and a UE 115-c, which may be an example of the base station 105 and UE 115 described herein.

[0131]

[0142] In 510, base station 105-c may signal the allocation of uplink resources, which can be received by UE115-c.

[0132]

[0143] In 520, base station 105-c may decide on resource reallocation. In some examples, reallocation in 520 may relate to supporting a particular type or category of communication, or supporting a particular UE115 configured for a particular type or category of communication (e.g., URLLC communication, URLLC UE). In some examples, the reallocation decision may be based at least in part on a configured time offset, such as a processing time offset, which may be based at least in part on the capabilities of UE115-c.

[0133]

[0144] In 530, base station 105-c may signal a ULCI, which may be received by UE115-c. In various examples, the ULCI may be UE-specific or common to one or more sets of UE115s. For example, the ULCI may be signaled using GC-PDCCH transmission or other DCI or GC-DCI.

[0134]

[0145] In 540, UE115-c may determine whether a resource allocation (e.g., signaled in 510) is to be revoked. For example, UE115-c may identify a bitmap of ULCIs associated with a set of communication resources in the time domain and frequency domain and determine whether at least a portion of the uplink resource allocation corresponds to one or more of a subset of communication resources to which the revocation applies. In various examples, determining whether an uplink resource allocation is to be revoked may be based at least in part on the type of physical channel associated with the uplink communication, the type of physical channel associated with the uplink revocation instruction, the allocation type associated with the identified uplink resource allocation, the type or priority of communication associated with the ULCI, or the type or priority of subsequent uplink communication.

[0135]

[0146] In some examples, ULCI may have various dependencies on or relationships to dynamic authorizations, such as uplink authorizations received via DCI, including the relationships and scenarios described herein. In other words, in some examples, the decision to revoke an uplink authorization in 540 may be based at least partially on various scenarios for dynamic authorizations (for example, at least partially on a dynamic or DCI allocation category or type).

[0136]

[0147] For example, DCI scheduling following an uplink transmission (e.g., for higher-priority communications, such as URLLC communications) may override a ULCI cancellation received at 530. In other words, UE115-c may receive a ULCI at 530, but may also receive a dynamic uplink authorization (e.g., for a resource corresponding to or otherwise indicated by the ULCI) that causes UE115-c to ignore the ULCI at 530. For example, when the ULCI at 530 indicates that symbols 10-13 in the slot are cancelled or pre-empted (e.g., for URLLC transmissions), UE115-c may receive a DCI scheduling for a URLLC PUSCH on symbols 12-13 and therefore transmit an uplink transmission (e.g., a PUSCH transmission) on symbols 12-13. Therefore, even though resources are instructed to be canceled or preempted by a ULCI received at 530, UE115-c may still transmit uplink transmissions on those resources, thereby effectively ignoring the ULCI at 530. In some examples, ULCI530 may be configured (e.g., by base station 105-c) to clear lower-priority transmissions in order to support URLLC PUSCH transmissions by UE115-c (e.g., on symbols 12-13).

[0137]

[0148] In another example, UE115-c might not expect to receive a DCI authorization to allocate resources for an uplink transmission for an eMBB within a symbol that is instructed to be revoked or pre-empted by the ULCI. Instead, UE115-c recognizes the ULCI of 530 as pre-empting eMBB communication (for example, based on the type of communication corresponding to the ULCI), and therefore UE115-c may ignore such a subsequent DCI authorization for eMBB communication (for example, as an error condition). In other words, when UE115-c decodes a ULCI corresponding to a particular type or priority of communication, UE115-c may ignore a subsequent uplink authorization associated with the same particular type or priority of communication that would conflict with resources that are revoked or pre-empted by the ULCI of 530.

[0138]

[0149] In another example, UE115-c might not expect to receive both an uplink permission for eMBB transmission and a ULCI that would puncture, or otherwise cancel or preempt, the eMBB transmission during the same monitoring opportunity. Instead, base station 105-c should not schedule UE115-c for communications that would need to be separately punctured or preempted by ULCI 530, so UE115-c may ignore such permission for eMBB transmission (for example, as an error condition). In other words, if UE115-c decodes a ULCI that would puncture the assigned communications (for example, of the same communication type or category) during the same monitoring opportunity, UE115-c may ignore the uplink permission that would be punctured by ULCI 530.

[0139]

[0150] In another example, UE115-c might receive an uplink authorization for URLLC transmission (e.g., DCI authorization) and an ULCI for eMBB revocation during the same monitoring opportunity. In this case, UE115-c would ignore the ULCI for the resource authorized by the URLLC DCI. In other words, more generally, if UE115-c decodes an ULCI of 530 associated with a lower-priority transmission than an uplink authorization or other allocation of uplink resources, UE115-c may ignore at least a portion of the ULCI of 530. In such an example, ULCI 530 may be configured (e.g., by base station 105-c) to clear lower-priority transmissions in order to support UE115-c's uplink authorization for URLLC transmission.

[0140]

[0151] In some cases, eMBB authorization may be permitted to override the ULCI of 530. For example, when UE115-c is configured to transmit a physical uplink control channel (PUCCH) carrying acknowledgment signaling (e.g., ACK / NACK for eMBB communication) or to transmit a PRACH triggered by a PDCCH (e.g., a PRACH transmission by a PDCCH instruction), UE115-c may be configured to ignore the ULCI of 530.

[0141]

[0152] In some cases, base station 105-c or UE115-c may interpret or evaluate uplink cancellation of a random access transmission (e.g., a PRACH transmission) according to various conditions related to random access signaling or requests, or conditions related to the connection with base station 105-c (e.g., based on the conditions under which a PRACH transmission is triggered). For example, various events can trigger a PRACH transmission by UE115-c, such as initial access following an idle state (e.g., via RRC_IDLE), connection re-establishment (e.g., via the RRC connection re-establishment procedure), data arrival in a connected state when UE115-c and base station 105-c are not synchronized (e.g., downlink or uplink data arrival in the RRC_CONNECTED state when the uplink synchronization status is "asynchronous"), data arrival in a connected state when resources for scheduling a request are unavailable (e.g., uplink data arrival in the RRC_CONNECTED state when there are no PUCCH resources available to schedule a request), scheduling of request failures, handover requests (e.g., requests by the radio resource controller during synchronous reconfiguration), transition from an inactive state to establish time alignment for adding a secondary cell (e.g., the RRC_INACTIVE state), beam failure recovery, requests for other system information, or various other conditions.

[0142]

[0153] Depending on how the random access transmission to UE115-c is triggered, UE115-c may or may not be able to apply the ULCI 530 cancellation or preemption instruction, or it may be expected to apply it. For example, during initial access (e.g., when establishing a connection from an idle state), the identity of UE115-c may not be known to base station 105-c, and therefore base station 105-c may not have enough information to preempt or cancel the PRACH transmission by UE115-c. In another example, the downlink connection from base station 105-c to UE115-c may be unreliable during the PRACH procedure, and therefore UE115-c may not be able to successfully receive or decode the ULCI 530. Therefore, base station 105-c may not be able to assume that the preemption or cancellation of UE115-c's PRACH transmission (e.g., by the ULCI 350) will be successful. In other examples, such as when a PRACH transmission is triggered by base station 105-c (for example, by a PRACH via a PDCCH instruction due to the uplink connection with UE115-c being out of sync while the downlink connection remains reliable), base station 105-c may assume that the preemption or cancellation of the PRACH transmission will be successful. Thus, in some situations, base station 105-a may proceed with the reallocation of uplink resources at 520 and the transmission of ULCI at 530 based on the trigger conditions associated with the random access transmission (e.g., the PRACH transmission).

[0143]

[0154] In another example related to random access transmit triggering, UE115-c may not expect to receive a signaling to trigger a random access transmit by UE115-c (e.g., PRACH with the PDCCH instruction) and a ULCI that would puncture, or otherwise cancel or preempt the random access transmit (e.g., during the same monitoring opportunity). Instead, base station 105-c should not schedule UE115-c for a random access transmit that would need to be separately punctured or canceled by ULCI 530, so UE115-c may ignore such a trigger for a random access transmit (e.g., as an error condition). In other words, UE115-c may ignore the trigger for a random access transmit when it decodes a ULCI that would cancel a triggered random access transmit (e.g., during the same monitoring opportunity).

[0144]

[0155] In some examples, the UE115-c may be configured to monitor ULCI after it has been scheduled for a dynamic eMBB PUSCH transmit or other transmits that may be preempted by ULCI (for example, at least in part on that basis). Additionally or alternatively, if the UE115-c is not scheduled for an eMBB transmit (e.g., eMBB PUSCH) or other transmits that may be preempted by ULCI, the UE115-c may not need to monitor cancellations and may therefore be configured to avoid or refrain from such monitoring, thereby reducing power consumption or processor usage in the UE115-c. In some examples, the UE115-c may be configured to monitor uplink cancellations of other transmits, for example, after being triggered for an asynchronous SRS (A-SRS).

[0145]

[0156] In some examples, ULCI may have various dependencies on or relationships with configured transmissions or configured permissions of higher layers, including the relationships and scenarios described herein. In other words, in some examples, the decision to cancel an uplink in 540 may be based at least in part on various scenarios for transmissions in the higher layer configuration (for example, at least in part on the allocation category or type of the higher layer).

[0146]

[0157] For example, if UE115-c is configured by an upper layer to send PUCCH, PUSCH, or PRACH in a set of symbols in a slot, and UE115-c receives a ULCI indicating that some of the resources in the set of symbols (e.g., for eMBB transmissions) are pre-empted, then UE115-c does not need to send the configured PUCCH, PUSCH, or PRACH in the slot. In other words, in contrast to dynamic authorizations received via DCI, in some examples, when a ULCI indicates the cancellation of uplink resources corresponding to transmissions or configured authorizations in an upper layer configuration (e.g., corresponding to PUCCH, PUSCH, or PRACH transmissions), UE115-c does not need to be configured to ignore the ULCI of 530.

[0147]

[0158] In another example, if the upper layer configures UE115-c to transmit a sounding reference signal (SRS) in the set of symbols for a slot, and UE115-c receives a ULCI of 530 indicating that at least some of the symbols in the set will be preempted, then UE115-c only needs to transmit the SRS in a subset of the symbols in the set of symbols for the slot that are not affected by the ULCI (e.g., symbols not instructed to be canceled). However, in such an example, such configuration may not imply that UE115-c, with its upper-layer configuration transmissions, is required to monitor the ULCI. For example, the ULCI may have been monitored and received after UE115-c was scheduled for dynamic PUSCH transmissions (e.g., according to the allocation of uplink resources in 510).

[0148]

[0159] In some cases, the UE115-c may be configured to either interrupt or not interrupt transmissions of higher-layer configurations, which may be a configuration specific to certain types of physical channels.

[0149]

[0160] As an addition or alternative, UE115-c may be configured to have multiple configurations for ULCIs targeting different channels (e.g., different physical channels). In other words, a ULCI like the one received in 530 may be configured differently for different channels. For example, UE115-c may be configured according to different monitoring periodics for higher-layer configurations compared to a ULCI that monitors dynamic uplink authorization (e.g., dynamic authorization for PUSCH). In one example, UE115-c may be configured for periodic SRS transmissions according to SRS periodicity, and UE115-c may be configured for cancellation monitoring according to a periodicity matching SRS periodicity. In other examples, ULCIs may have different monitoring periodicities or resource granularity depending on the channel type, or the type of communication, or other communication configurations of the characteristics. In another example, for the transmission of several higher-layer configurations (e.g., one or more of the PUCCH or PRACH transmissions), the UE115-c may be configured to ignore the ULCI and proceed with the transmission of the higher-layer configurations regardless of whether the ULCI was received at 530 or not.

[0150]

[0161] In some examples, at 550, UE115-c may perform uplink communication, including transmissions according to the scenarios described above, based at least partially on the output of 540. For example, UE115-c may perform uplink transmissions on a subset of the uplink resource allocation based on the output of 540, or UE115-c may refrain from using at least a portion of the uplink resource allocation based on the output of 540. In some examples, UE115-c may refrain from using the entire uplink resource allocation and instead wait for another allocation of resources before performing uplink communication.

[0151]

[0162] Figure 6 shows a block diagram 600 of a device 605 supporting uplink transmission cancellation according to an aspect of this disclosure. Device 605 may be an example of an aspect of UE 115 described herein. Device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. Device 605 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0152]

[0163] Receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., information related to control channels, data channels, and uplink transmission cancellation). The information may be passed to other components of device 605. Receiver 610 may be an example of an embodiment of transceiver 915 as described with reference to Figure 9. Receiver 610 may use a single antenna or a set of antennas.

[0153]

[0164] The communication manager 615 identifies an uplink resource allocation associated with a first type of communication having a first delay threshold, receives an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold, determines whether the identified allocation of the uplink resource is cancelled based on the uplink cancellation instruction, and may, based on the determination, perform either the first type of communication or the second type of communication uplink communication. The communication manager 615 may be an example of an embodiment of the communication manager 910 described herein.

[0154]

[0165] The communications manager 615 or its subordinate components may be implemented in hardware, software (for example, executed by a processor), or any combination thereof. When implemented in code executed by a processor, the functions of the communications manager 615 or its subordinate components may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

[0155]

[0166] The communications manager 615 or its subordinate components may be physically located in various locations, including the distribution of functional parts to be implemented in different physical locations by one or more physical components. In some examples, the communications manager 615 or its subordinate components may be separate and distinct components according to various aspects of this disclosure. In some examples, the communications manager 615 or its subordinate components may be combined with one or more other hardware components, including, but not limited to, input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof, according to various aspects of this disclosure.

[0156]

[0167] The transmitter 620 can transmit signals generated by other components of device 605. In some examples, the transmitter 620 may be coupled with the receiver 610 in the transceiver module. For example, the transmitter 620 may be an example of an embodiment of the transceiver 915 described with reference to Figure 9. The transmitter 620 may use a single antenna or a set of antennas.

[0157]

[0168] Figure 7 shows a block diagram 700 of a device 705 supporting uplink transmission cancellation according to an aspect of this disclosure. Device 705 may be an example of an aspect of device 605 or UE115 as described herein. Device 705 may include a receiver 710, a communications manager 715, and a transmitter 735. Device 705 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0158]

[0169] Receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., information related to control channels, data channels, and uplink transmission cancellation). The information may be passed to other components of device 705. Receiver 710 may be an example of an embodiment of transceiver 915 as described with reference to Figure 9. Receiver 710 may use a single antenna or a set of antennas.

[0159]

[0170] The communications manager 715 may be an example of an embodiment of the communications manager 615 described herein. The communications manager 715 may include an uplink allocation manager 720, an uplink cancellation manager 725, and an uplink communications manager 730. The communications manager 715 may be an example of an embodiment of the communications manager 910 described herein.

[0160]

[0171] The uplink allocation manager 720 can identify the allocation of uplink resources associated with a first type of communication having a first delay threshold.

[0161]

[0172] The uplink cancellation manager 725 receives an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold, and may determine, based on the uplink cancellation instruction, whether the identified allocation of the uplink resource is cancelled.

[0162]

[0173] Based on its decisions, the uplink communication manager 730 may perform uplink communication of either the first type of communication or the second type of communication.

[0163]

[0174] Transmitter 735 can transmit signals generated by other components of device 705. In some examples, transmitter 735 may be collated with receiver 710 in a transceiver module. For example, transmitter 735 may be an example of an embodiment of transceiver 915 described with reference to Figure 9. Transmitter 735 may use a single antenna or a set of antennas.

[0164]

[0175] Figure 8 shows a block diagram 800 of a communications manager 805 supporting uplink transmission cancellation according to an aspect of this disclosure. Communications manager 805 may be an example of an aspect of communications manager 615, communications manager 715, or communications manager 910 as described herein. Communications manager 805 may include an uplink allocation manager 810, an uplink cancellation manager 815, an uplink communications manager 820, a bitmap interpreter 825, and a cancellation timeline manager 830. Each of these modules may communicate with one another directly or indirectly (for example, via one or more buses).

[0165]

[0176] The uplink allocation manager 810 can identify the allocation of uplink resources associated with a first type of communication having a first delay threshold.

[0166]

[0177] In some examples, the uplink allocation manager 810 may receive an uplink authorization after receiving an uplink cancellation instruction, and the uplink authorization includes the communication resources associated with the uplink cancellation instruction.

[0167]

[0178] The uplink cancellation manager 815 may receive an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold.

[0168]

[0179] In some cases, the uplink cancellation manager 815 may determine, based on the uplink cancellation instruction, whether the identified allocation of the uplink resource is cancelled.

[0169]

[0180] In some cases, the uplink cancellation manager 815 may determine whether at least a portion of the uplink resource allocation corresponds to one or more of a subset of communication resources to which cancellation applies.

[0170]

[0181] In some examples, the uplink cancellation manager 815 may determine that each subset of communication resources corresponding to each bit of the bitmap corresponds to the uplink resources in the UE's uplink / downlink time-division duplex (TDD) configuration.

[0171]

[0182] In some examples, the uplink cancellation manager 815 may receive a cancellation configuration prior to receiving an uplink cancellation instruction associated with a pattern of communication resources in the time domain and frequency domain, where the uplink cancellation instruction specifies the time for applying the pattern of communication resources for cancellation.

[0172]

[0183] In some cases, the uplink cancellation manager 815 may ignore at least a portion of an uplink cancellation instruction based on having received an uplink permission instruction after receiving the uplink cancellation instruction.

[0173]

[0184] In some cases, the cancellation configuration includes the RRC configuration.

[0174]

[0185] Based on its decisions, the uplink communication manager 820 may perform uplink communication of either the first type of communication or the second type of communication.

[0175]

[0186] In some cases, the uplink communications manager 820 may, based on its decisions, send uplink transmissions on a subset of the uplink resource allocation.

[0176]

[0187] In some cases, the uplink communications manager 820 may, based on its decisions, refrain from using at least a portion of the allocated uplink resources.

[0177]

[0188] In some cases, the first type of communication includes enhanced mobile broadband (eMBB) communication, and the second type of communication includes ultra-high reliability low latency (URLLC) communication.

[0178]

[0189] The bitmap interpreter 825 can identify bitmaps of uplink cancellation instructions associated with a set of communication resources in the time domain and frequency domain, where each bit of the bitmap corresponds to a subset of the communication resources, and each bit indicates whether cancellation applies to a subset of the communication resources.

[0179]

[0190] In some cases, the bitmap interpreter 825 may determine that the bitmap corresponds to the uplink bandwidth portion configured for the UE.

[0180]

[0191] In some cases, the bitmap interpreter 825 can identify repeating indicators.

[0181]

[0192] In some examples, the bitmap interpreter 825 may repeat bits of the bitmap according to a repeat indicator, where each repeated bit of the bitmap corresponds to a subset of communication resources, and each repeated bit indicates whether a cancel is applied to each subset of communication resources.

[0182]

[0193] The cancellation timeline manager 830 may determine the time to apply the cancellation based on the time the uplink cancellation instruction was received and the configured time offset for the cancellation.

[0183]

[0194] Figure 9 shows a diagram of system 900 including a device 905 that supports uplink transmission cancellation according to an aspect of the present disclosure. Device 905 may be an example of, or may include, a component of, device 605, device 705, or UE115 as described herein. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communications manager 910, a transceiver 915, an antenna 920, a memory 925, and a processor 935. These components may communicate electronically via one or more buses (for example, bus 940).

[0184]

[0195] The communication manager 910 identifies the allocation of uplink resources associated with a first type of communication having a first delay threshold, receives an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold, determines whether the identified allocation of uplink resources is cancelled based on the uplink cancellation instruction, and may perform either the first type of communication or the second type of communication uplink communication based on the determination.

[0185]

[0196] The actions performed by the communications manager 910 as described herein may be implemented to achieve one or more potential benefits. One implementation may allow the UE 115 to allocate uplink resources more quickly for higher-priority communications, such as URLLC uplink transmissions, thereby reducing latency and providing improved quality and reliability of service in the UE 115.

[0186]

[0197] The transceiver 915 may communicate bidirectionally via one or more antennas, wired links, or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, feeding the modulated packets to an antenna for transmission, and demodulating packets received from the antenna.

[0187]

[0198] In some cases, a wireless device may include a single antenna 920. However, in some cases, the device may have two or more antennas 920 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0188]

[0199] Memory 925 may include random access memory (RAM) and read-only memory (ROM). Memory 925 may store computer-readable computer executable code 930, which, when executed, causes the processor to perform various functions described herein. In some cases, memory 925 may include a basic input / output system (BIOS) that can control basic hardware or software operations, in particular, interactions with peripheral components or devices.

[0189]

[0200] Code 930 may include instructions for implementing aspects of this disclosure, including instructions for supporting wireless communication. Code 930 may be stored in a non-temporary computer-readable medium such as system memory or other types of memory. In some cases, Code 930 may not be directly executable by processor 935, but (for example, after compilation, interpretation, conversion, and / or execution) may cause the computer to perform the functions described herein.

[0190]

[0201] The processor 935 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 935 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 935. The processor 935 may be configured to execute computer-readable instructions stored in memory (e.g., memory 925) to cause device 905 to perform various functions (e.g., functions or tasks that support uplink transmission cancellation).

[0191]

[0202] Figure 10 shows a block diagram 1000 of a device 1005 supporting uplink transmission cancellation according to an aspect of this disclosure. Device 1005 may be an example of an aspect of a base station 105 described herein. Device 1005 may include a receiver 1010, a communications manager 1015, and a transmitter 1020. Device 1005 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0192]

[0203] Receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., information related to control channels, data channels, and uplink transmission cancellation). The information may be passed to other components of device 1005. Receiver 1010 may be an example of an embodiment of transceiver 1320 as described with reference to Figure 13. Receiver 1010 may use a single antenna or a set of antennas.

[0193]

[0204] The communication manager 1015 may transmit an allocation of uplink resources associated with a first type of communication having a first delay threshold, determine a reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold, and, based on the determination, transmit an uplink cancellation instruction corresponding to the uplink resources. The communication manager 1015 may be an example of an embodiment of the communication manager 1310 described herein.

[0194]

[0205] The communication manager 1015 or its subordinate components may be implemented in hardware, software (for example, run by a processor), or any combination thereof. When implemented in software run by a processor, the functions of the communication manager 1015 or its subordinate components may be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

[0195]

[0206] The communication manager 1015 or its subordinate components may be physically located in various locations, including being distributed so that parts of its functionality are implemented in different physical locations by one or more physical components. In some examples, the communication manager 1015 or its subordinate components may be separate and distinct components according to various aspects of this disclosure. In some examples, the communication manager 1015 or its subordinate components may be combined with one or more other hardware components, including, but not limited to, input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof, according to various aspects of this disclosure.

[0196]

[0207] Transmitter 1020 can transmit signals generated by other components of device 1005. In some examples, transmitter 1020 may be collated with receiver 1010 in a transceiver module. For example, transmitter 1020 may be an example of an embodiment of transceiver 1320, as described with reference to Figure 13. Transmitter 1020 may use a single antenna or a set of antennas.

[0197]

[0208] Figure 11 shows a block diagram 1100 of a device 1105 supporting uplink transmission cancellation according to an aspect of this disclosure. Device 1105 may be an example of an aspect of device 1005 or base station 105 as described herein. Device 1105 may include a receiver 1110, a communications manager 1115, and a transmitter 1135. Device 1105 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0198]

[0209] Receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., information related to control channels, data channels, and uplink transmission cancellation). The information may be passed to other components of device 1105. Receiver 1110 may be an example of an embodiment of transceiver 1320 as described with reference to Figure 13. Receiver 1110 may use a single antenna or a set of antennas.

[0199]

[0210] Communication manager 1115 may be an example of an embodiment of communication manager 1015 as described herein. Communication manager 1115 may include an uplink allocation manager 1120, a reallocation manager 1125, and a cancellation indication manager 1130. Communication manager 1115 may be an example of an embodiment of communication manager 1310 as described herein.

[0200]

[0211] The uplink allocation manager 1120 may send an allocation of uplink resources associated with a first type of communication having a first delay threshold.

[0201]

[0212] The reallocation manager 1125 may determine the reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold.

[0202]

[0213] The cancellation instruction manager 1130 may, based on its decision, send an uplink cancellation instruction corresponding to the uplink resource.

[0203]

[0214] The transmitter 1135 can transmit signals generated by other components of device 1105. In some examples, the transmitter 1135 may be collated with the receiver 1110 in the transceiver module. For example, the transmitter 1135 may be an example of an embodiment of the transceiver 1320 described with reference to Figure 13. The transmitter 1135 may use a single antenna or a set of antennas.

[0204]

[0215] Figure 12 shows a block diagram 1200 of a communications manager 1205 supporting uplink transmission cancellation according to an aspect of this disclosure. Communications manager 1205 may be an example of an aspect of communications manager 1015, communications manager 1115, or communications manager 1310 as described herein. Communications manager 1205 may include an uplink allocation manager 1210, a reallocation manager 1215, a cancellation instruction manager 1220, a bitmap generator 1225, a cancellation configuration manager 1230, a cancellation timeline manager 1235, and an uplink communications manager 1240. Each of these modules may communicate with one another directly or indirectly (for example, via one or more buses).

[0205]

[0216] The uplink allocation manager 1210 may send an allocation of uplink resources associated with a first type of communication having a first delay threshold.

[0206]

[0217] In some cases, the uplink allocation manager 1210 may send an uplink authorization to the UE, which includes the communication resources associated with the uplink cancellation instruction, and the uplink authorization instructs the UE to ignore at least a portion of the uplink cancellation instruction.

[0207]

[0218] The reallocation manager 1215 may determine the reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold.

[0208]

[0219] In some examples, the reallocation manager 1215 determines the reallocation of uplink resources allocated to a physical random access channel (PRACH) based at least in part on the trigger conditions for transmission associated with the uplink resources allocated to the PRACH.

[0209]

[0220] The cancellation instruction manager 1220 may, based on its decision, send an uplink cancellation instruction corresponding to the uplink resource.

[0210]

[0221] In some examples, sending an uplink cancellation instruction involves sending a bitmap.

[0211]

[0222] In some cases, the cancel instruction manager 1220 may send a repetition indicator associated with the bitmap.

[0212]

[0223] In some cases, the cancellation instruction manager 1220 may transmit a group common physical downlink control channel (GC-PDCCH).

[0213]

[0224] The bitmap generator 1225 can generate bitmaps associated with sets of communication resources in the time domain and frequency domain, where each bit of the bitmap corresponds to a subset of the communication resources, and each bit indicates whether cancellation is applied to a subset of the communication resources.

[0214]

[0225] The cancellation configuration manager 1230 may send a cancellation configuration prior to sending an uplink cancellation instruction associated with a pattern of communication resources in the time domain and frequency domain, where the uplink cancellation instruction specifies the time for applying the pattern of communication resources for cancellation.

[0215]

[0226] In some cases, the Cancellation Configuration Manager 1230 may send an RRC configuration.

[0216]

[0227] The cancellation timeline manager 1235 may determine the time to apply the cancellation based on the time the uplink cancellation instruction is sent and the configured time offset for the cancellation.

[0217]

[0228] The uplink communication manager 1240 may receive communications from one or more user equipment (UEs) based on the transmission of uplink resource reallocation and uplink cancellation instructions.

[0218]

[0229] In some cases, the first type of communication includes enhanced mobile broadband (eMBB) communication, and the second type of communication includes ultra-high reliability low latency (URLLC) communication.

[0219]

[0230] Figure 13 shows a diagram of system 1300 including a device 1305 that supports uplink transmission cancellation, according to an aspect of the present disclosure. Device 1305 may be an example of, or may include, a component of, device 1005, device 1105, or base station 105 as described herein. Device 1305 may include components for bidirectional voice and data communications, including components for transmitting and receiving communications, including a communications manager 1310, a network communications manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-station communications manager 1345. These components may communicate electronically via one or more buses (e.g., bus 1350).

[0220]

[0231] The communication manager 1310 may transmit an allocation of uplink resources associated with a first type of communication having a first delay threshold, determine a reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold, and, based on the determination, transmit an uplink cancellation instruction corresponding to the uplink resource.

[0221]

[0232] The actions performed by the communications manager 1310 as described herein may be implemented to realize one or more potential benefits. In one implementation, base stations 105 or other network entities may be able to more quickly reallocate uplink resources to different types of communications, which may have different latency thresholds, reliability thresholds, or other priorities. In another implementation, latency may be reduced and reliability may be improved for higher-priority communications, thus providing improved quality and reliability of service for various UEs 115 of the wireless communications system.

[0222]

[0233] The network communication manager 1315 can manage communication with the core network (for example, via one or more wired backhaul links). For example, the network communication manager 1315 can manage the transfer of data communications for one or more client devices such as UE115.

[0223]

[0234] The transceiver 1320 may communicate bidirectionally via one or more antennas, wired links, or wireless links, as described herein. For example, the transceiver 1320 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. The transceiver 1320 may also include a modem for modulating packets, feeding the modulated packets to an antenna for transmission, and demodulating packets received from the antenna.

[0224]

[0235] In some cases, the wireless device may include a single antenna 1325. However, in some cases, the device may have two or more antennas 1325 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0225]

[0236] Memory 1330 may include RAM and ROM. Memory 1330 may store computer-readable computer executable code 1330, which, when executed, includes instructions that cause the processor to perform various functions described herein. In some cases, memory 1330 may include a BIOS that can control basic hardware or software operations, such as interaction with peripheral components or devices.

[0226]

[0237] Code 1335 may include instructions for implementing aspects of this disclosure, including instructions for supporting wireless communication. Code 1335 may be stored in a non-temporary computer-readable medium such as system memory or other types of memory. In some cases, Code 1335 may not be directly executable by the processor 1340, but (for example, after compilation, interpretation, conversion, and / or execution) may cause the computer to perform the functions described herein.

[0227]

[0238] The processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support uplink transmission cancellation).

[0228]

[0239] The inter-station communication manager 1345 can manage communication with other base stations 105 and may include a controller or scheduler to coordinate communication with the UE 115 in cooperation with other base stations 105. For example, the inter-station communication manager 1345 may coordinate scheduling for transmissions to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1345 may provide an X2 interface within LTE / LTE-A wireless communication network technology to enable communication between base stations 105.

[0229]

[0240] Figure 14 shows a flowchart illustrating method 1400 for supporting uplink transmission cancellation according to the embodiments of this disclosure. The operation of method 1400 may be implemented by a UE 115 or its components as described herein. For example, the operation of method 1400 may be implemented by a communications manager as described with reference to Figures 6 to 9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. In addition or alternatively, the UE may use dedicated hardware to perform embodiments of the described functions.

[0230]

[0241] In 1405, the UE may identify the allocation of uplink resources associated with a first type of communication having a first delay threshold. The operation of 1405 may be carried out according to the methods described herein. In some examples, the operation of 1405 may be carried out by an uplink allocation manager described with reference to Figures 6 to 9.

[0231]

[0242] In 1410, the UE may receive an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold. The operation of 1410 may be carried out according to the methods described herein. In some examples, the operation of 1410 may be carried out by an uplink cancellation manager described with reference to Figures 6 to 9.

[0232]

[0243] In 1415, the UE may determine, based on the uplink cancellation instruction, whether the identified allocation of the uplink resource is cancelled. The operation of 1415 may be carried out according to the methods described herein. In some examples, the operation of 1415 may be carried out by an uplink cancellation manager as described with reference to Figures 6 to 9.

[0233]

[0244] In 1420, the UE may perform uplink communication of either the first type of communication or the second type of communication, based on its determination. The operation of 1420 may be carried out in accordance with the methods described herein. In some examples, the operation of 1420 may be carried out by an uplink communication manager as described with reference to Figures 6 to 9.

[0234]

[0245] Figure 15 shows a flowchart illustrating method 1500 for supporting uplink transmission cancellation according to the embodiments of this disclosure. The operation of method 1500 may be implemented by a UE 115 or its components as described herein. For example, the operation of method 1500 may be implemented by a communications manager as described with reference to Figures 6 to 9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform embodiments of the described functions.

[0235]

[0246] In 1505, the UE may identify the allocation of uplink resources associated with a first type of communication having a first delay threshold. The operation of 1505 may be carried out according to the methods described herein. In some examples, the operation of 1505 may be carried out by an uplink allocation manager described with reference to Figures 6 to 9.

[0236]

[0247] In 1510, the UE may receive an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold. The operation of 1510 may be carried out according to the methods described herein. In some examples, the operation of 1510 may be carried out by an uplink cancellation manager described with reference to Figures 6 to 9.

[0237]

[0248] In 1515, the UE may determine, based on the uplink cancellation instruction, whether the identified allocation of the uplink resource is cancelled. The operation of 1515 may be carried out according to the methods described herein. In some examples, the operation of 1515 may be carried out by an uplink cancellation manager as described with reference to Figures 6 to 9.

[0238]

[0249] In 1520, the UE may receive an uplink authorization after receiving an uplink cancellation instruction, the uplink authorization including the communication resources associated with the uplink cancellation instruction. The operation of 1520 may be carried out according to the methods described herein. In some examples, the operation of 1520 may be carried out by an uplink allocation manager as described with reference to Figures 6 to 9.

[0239]

[0250] In 1525, the UE may disregard at least a portion of the uplink cancellation instruction if it has received an uplink permission after receiving the uplink cancellation instruction. The operation of 1525 may be carried out in accordance with the methods described herein. In some examples, the operation of 1525 may be carried out by an uplink cancellation manager as described with reference to Figures 6 to 9.

[0240]

[0251] In 1530, the UE may, based on its determination, perform uplink communication of either the first type of communication or the second type of communication. Operation of 1530 may be carried out in accordance with the methods described herein. In some examples, the modes of operation of 1530 may be carried out by an uplink communication manager as described with reference to Figures 6 to 9.

[0241]

[0252] Figure 16 shows a flowchart illustrating method 1600 for supporting uplink transmission cancellation according to the embodiments of this disclosure. The operation of method 1600 may be implemented by a base station 105 or its components as described herein. For example, the operation of method 1600 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the base station may execute a set of instructions for controlling the base station's functional elements to perform the functions described. In addition or alternatively, the base station may perform embodiments of the functions described using dedicated hardware.

[0242]

[0253] In 1605, the base station may transmit an uplink resource allocation associated with a first type of communication having a first delay threshold. The operation of 1605 may be carried out according to the methods described herein. In some examples, the operation of 1605 may be carried out by an uplink allocation manager described with reference to Figures 10 to 13.

[0243]

[0254] In 1610, the base station may determine the reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold. The operation of 1610 may be carried out according to the methods described herein. In some examples, the operation of 1610 may be carried out by a reallocation manager described with reference to Figures 10 to 13.

[0244]

[0255] In 1615, the base station may, based on its decision, transmit an uplink cancellation instruction corresponding to the uplink resource. The operation of 1615 may be carried out in accordance with the methods described herein. In some examples, the operation of 1615 may be carried out by a cancellation instruction manager described with reference to Figures 10 to 13.

[0245]

[0256] Figure 17 shows a flowchart illustrating method 1700 supporting uplink transmission cancellation according to an aspect of this disclosure. The operation of method 1700 may be implemented by a base station 105 or its components as described herein. For example, the operation of method 1700 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described. In addition or alternatively, the base station may perform aspects of the functions described using dedicated hardware.

[0246]

[0257] In 1705, the base station may transmit an uplink resource allocation associated with a first type of communication having a first delay threshold. The operation of 1705 may be carried out according to the methods described herein. In some examples, the operation of 1705 may be carried out by an uplink allocation manager described with reference to Figures 10 to 13.

[0247]

[0258] In 1710, the base station may determine the reallocation of uplink resources based on a second type of communication having a second delay threshold different from the first delay threshold. The operation of 1710 may be carried out according to the methods described herein. In some examples, the operation of 1710 may be carried out by a reallocation manager described with reference to Figures 10 to 13.

[0248]

[0259] In 1715, the base station may, based on its decision, transmit an uplink cancellation instruction corresponding to the uplink resource. The operation of 1715 may be carried out according to the methods described herein. In some examples, the operation of 1715 may be carried out by a cancellation instruction manager described with reference to Figures 10 to 13.

[0249]

[0260] In 1720, the base station may send an uplink authorization to the UE, which includes the communication resources associated with the uplink cancellation instruction, and the uplink authorization instructs the UE to ignore at least a portion of the uplink cancellation instruction. The operation of 1720 may be carried out in accordance with the methods described herein. In some examples, the operation of 1720 may be carried out by an uplink allocation manager as described with reference to Figures 10 to 13.

[0250]

[0261] It should be noted that the methods described herein represent possible implementations, that the operations and steps may be reconfigured or, in some cases, modified, and that other implementations are possible. Furthermore, two or more embodiments of the methods may be combined.

[0251]

[0262] The techniques described herein may be used in a variety of wireless communication systems, including Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems may implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. Releases of IS-2000 are often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High-Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA®) and other variations of CDMA. TDMA systems may implement radio technologies such as Global System for Mobile Communications (GSM®).

[0252]

[0263] OFDMA systems can implement wireless technologies such as Ultra Mobile Broadband (UMB), Advanced UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX®), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the "Third Generation Partnership Project" (3GPP®). CDMA2000 and UMB are described in documents from an organization called the "Third Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and wireless technologies described herein, as well as for other systems and wireless technologies. While examples may be given of LTE, LTE-A, LTE-A Pro, or NR systems, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the descriptions, the techniques described herein are not limited to LTE, LTE-A, or LTE-A. Applicable to applications other than Pro or NR.

[0253]

[0264] Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UEs (User Entities) subscribed to a network provider's service. Small cells, compared to macrocells, may be associated with low-power base stations and may operate within the same or different frequency bands (e.g., licensed, unlicensed, etc.) as macrocells. Small cells can include picocells, femtocells, and microcells, depending on the specific example. Picocells, for example, can cover small geographical areas and can enable unrestricted access by UEs subscribed to a network provider's service. Femtocells can also cover small geographical areas (e.g., a home) and can provide limited access by UEs associated with femtocells (e.g., UEs within a limited subscriber group (CSG), UEs for users in a home, etc.). eNBs for macrocells are sometimes called macro eNBs. eNBs for small cells are sometimes called small cell eNBs, pico eNBs, femto eNBs, or home eNBs. eNBs can support one or more cells (for example, two, three, or four) and can also support communication using one or more component carriers.

[0254]

[0265] The wireless communication systems described herein may support synchronous or asynchronous operation. In synchronous operation, base stations may have similar frame timings, and transmissions from different base stations may be approximately time-coordinated. In asynchronous operation, base stations may have different frame timings, and transmissions from different base stations may not be time-coordinated. The techniques described herein may be used for either synchronous or asynchronous operation.

[0255]

[0266] The information and signals described herein may be represented using any of the following different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0256]

[0267] The various exemplary blocks and modules described in relation to the disclosure herein may be implemented or carried out using general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be carried out as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors associated with a DSP core, or any other such configuration).

[0257]

[0268] The functions described herein may be implemented in hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. When implemented in software (for example, executed by a processor), the functions may be stored on or transmitted via computer-readable media as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the accompanying claims. For example, depending on the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including the distribution of parts of the function so that they are implemented in different physical locations.

[0258]

[0269] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose or dedicated computer. Examples, but not limited to, non-temporary computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM®), flash memory, compact disk (CD)-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and can be accessed by a general-purpose or dedicated computer or general-purpose or dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disk and disc include CD, LaserDisc®, OpticalDisc, Digital Multipurpose Disc (DVD), FloppyDisc®, and Blu-ray® Disc, where disk typically reproduces data magnetically and disc optically reproduces data by laser. The above combinations are also included in the scope of computer-readable media.

[0259]

[0270] As used herein, including in the claims, “or” in a list of items (for example, a list of items ending with a phrase such as “at least one of” or “one or more of”) means an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” shall be construed as “at least partially based on”. When used herein in an enumeration of two or more items, the term “and / or” means that any one of the enumerated items may be used alone, or any combination of two or more of the enumerated items may be used. For example, if a composition is described as containing components A, B, and / or C, that composition may contain only A, only B, only C, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B, and C.

[0260]

[0271] In the attached diagrams, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes them from similar components. Where only the first reference label is used herein, its description is applicable to any similar component having the same first reference label, regardless of the second reference label or any other subsequent reference labels.

[0261]

[0272] The descriptions provided herein with respect to the accompanying drawings describe exemplary configurations and do not necessarily represent all examples that may be implemented or that fall within the scope of the claims. The term “exemplary” as used herein means “acting as an example, case, or illustration,” and does not mean “preferred” or “advantageous over other examples.” Detailed descriptions include specific details to give an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0262]

[0273] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Accordingly, this disclosure should be given the broadest scope that is consistent with the principles and novel features disclosed herein, and is not limited to the examples and designs described herein. The invention described in the original claims of this application is listed below. [C1] A method for wireless communication in user equipment (UE), Identifying the allocation of uplink resources associated with a first type of communication having a first delay threshold, Receiving an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold, Based at least in part on the aforementioned uplink cancellation instruction, determine whether the identified allocation of the uplink resource is cancelled, Based at least in part on the above-mentioned decision, to implement uplink communication of either the first type of communication or the second type of communication. A method for providing this. [C2] Determining whether the identified allocation of the uplink resource is to be revoked is: Identifying a bitmap of uplink cancellation instructions associated with a set of communication resources in the time domain and frequency domain, where each bit of the bitmap corresponds to a subset of the communication resources, and each bit indicates whether cancellation applies to the respective subset of the communication resources. The method of C1, comprising determining whether at least a portion of the allocation of uplink resources corresponds to one or more of the subsets of the communication resources to which cancellation applies. [C3] Determining whether the identified allocation of the uplink resource is to be revoked is: The method of C2, comprising determining that the bitmap corresponds to the uplink bandwidth portion configured for the UE. [C4] Identifying recurring indicators, The method of C2, further comprising repeating the bits of the bitmap according to the repeat indicator, wherein each repeated bit of the bitmap corresponds to each subset of the communication resources, and each repeated bit indicates whether cancellation is applied to each subset of the communication resources. [C5] The method of C2, further comprising determining that each subset of the communication resources corresponding to each bit of the bitmap corresponds to an uplink resource in the uplink / downlink time-division duplex (TDD) configuration of the UE. [C6] Determining whether the identified allocation of the uplink resource is to be revoked is: The method of C1, comprising determining a time for applying the cancellation based at least in part on the time the uplink cancellation instruction was received and a configured time offset for the cancellation. [C7] The method according to C6, wherein the configured time offset for cancellation is at least in part based on the capability of the UE. [C8] Determining the time for applying the cancellation is the method of C6, which is at least in part based on the uplink / downlink time-division duplex (TDD) configuration of the UE. [C9] Receiving the uplink cancellation instruction and then receiving the uplink permission, and the uplink permission includes the communication resources associated with the uplink cancellation instruction. The method of C1, further comprising ignoring at least a portion of the uplink cancellation instruction based at least partially on having received the uplink permission after receiving the uplink cancellation instruction. [C10] The method of C9, wherein ignoring at least a portion of the uplink cancellation instruction is at least in part based on the fact that the uplink authorization is associated with the second type of communication. [C11] Ignoring at least a portion of the uplink cancellation instruction is the method of C9, which is at least partially based on the type of physical channel associated with the uplink authorization. [C12] The method according to C1, wherein determining whether the identified allocation of the uplink resource is to be revoked is at least partially based on the type of physical channel associated with the uplink communication. [C13] The method according to C1, wherein determining whether the identified allocation of the uplink resource is to be canceled is at least partially based on the type of physical channel associated with the uplink cancellation instruction. [C14] The method according to C1, wherein determining whether the identified allocation of the uplink resource is to be canceled is at least partially based on the allocation type associated with the identified allocation of the uplink resource. [C15] The method of C1, wherein determining whether the identified allocation of the uplink resource is to be revoked is at least in part based on the second type of communication. [C16] The method of C1, wherein determining whether the identified allocation of the uplink resource is to be revoked is at least partially based on the type of communication associated with the uplink communication. [C17] Performing the aforementioned uplink communication means The method of C1, comprising refraining from using at least a portion of the allocation of uplink resources based at least in part on the aforementioned determination. [C18] A method for wireless communication at a base station, Transmitting an allocation of uplink resources associated with a first type of communication having a first delay threshold, The reallocation of the uplink resources is determined at least in part on a second type of communication having a second delay threshold different from the first delay threshold, Based at least in part on the above decision, send an uplink cancellation instruction corresponding to the uplink resource. A method for providing this. [C19] The system further comprises generating a bitmap associated with a set of communication resources in the time domain and the frequency domain, wherein each bit of the bitmap corresponds to a subset of the communication resources, and each bit indicates whether a cancellation is applied to the respective subset of the communication resources. The method of C18, wherein transmitting the uplink cancellation instruction comprises transmitting the bitmap. [C20] The bitmap corresponds to the configured uplink bandwidth portion, as described in C19. [C21] Sending the aforementioned uplink cancellation instruction means The method of C19, comprising transmitting a repeating indicator associated with the bitmap. [C22] Each subset of the communication resource corresponding to each bit of the bitmap corresponds to the uplink resource in an uplink / downlink TDD configuration, as described in C19. [C23] Determining the reallocation of resources is The method of C18, comprising determining a time for applying the cancellation based at least in part on the time at which the uplink cancellation instruction is transmitted and a configured time offset for the cancellation. [C24] The method described in C23, wherein the configured time offset for cancellation is at least partially based on UE capability. [C25] Determining the time for applying the cancellation is the method described in C23, which is at least partially based on an uplink / downlink time-division duplex (TDD) configuration. [C26] The method of C18, further comprising transmitting an uplink authorization to the UE, which includes a communication resource associated with the uplink cancellation instruction, wherein the uplink authorization instructs the UE to ignore at least a portion of the uplink cancellation instruction. [C27] The method according to C26, wherein the uplink authorization is associated with the second type of communication, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is at least in part based on the fact that the uplink authorization is associated with the second type of communication. [C28] The method according to C26, wherein the uplink authorization is associated with the type of physical channel, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is at least partially based on the type of physical channel. [C29] Means for identifying the allocation of uplink resources associated with a first type of communication having a first delay threshold, Means for receiving an uplink cancellation instruction associated with a second type of communication having a second delay threshold different from the first delay threshold, Means for determining whether the identified allocation of the uplink resource is canceled based at least in part on the uplink cancellation instruction, Based at least in part on the above determination, means for performing uplink communication of either the first type of communication or the second type of communication A device equipped with the following features. [C30] A means for transmitting an allocation of uplink resources associated with a first type of communication having a first delay threshold, Means for determining the reallocation of the uplink resources, at least in part on a second type of communication having a second delay threshold different from the first delay threshold, Based at least in part on the above determination, means for transmitting an uplink cancellation instruction corresponding to the uplink resource and A device equipped with the following features.

Claims

1. A method for wireless communication in a network entity, Output instructions for the level of detail regarding uplink cancellation, Output the allocation of uplink resources, To determine the reallocation of the aforementioned uplink resources, Based on the above determination, an uplink cancellation instruction corresponding to the uplink resource is output, the uplink cancellation instruction comprises a bitmap associated with the uplink resource, where each bit of the bitmap corresponds to a subset of the uplink resource and indicates whether cancellation is applied to each subset of the uplink resource, where the amount of uplink resource in each subset of the uplink resource is based on the indicated granularity for uplink cancellation, and the uplink cancellation instruction indicates the time to apply uplink cancellation based on the time of receipt of the uplink cancellation instruction and the time offset for uplink cancellation. A method for providing this.

2. The method according to claim 1, wherein the bitmap corresponds to the configured uplink bandwidth portion.

3. The method according to claim 1, wherein outputting the uplink cancellation instruction comprises outputting a repeat indicator associated with the bitmap.

4. The method according to claim 1, wherein each subset of the uplink resource corresponding to each bit of the bitmap corresponds to an uplink resource in an uplink / downlink TDD configuration.

5. The method according to claim 1, wherein the time offset for uplink cancellation is based on user equipment (UE) capability.

6. The method according to claim 1, wherein determining the time for applying uplink cancellation is based on an uplink / downlink time-division duplex (TDD) configuration.

7. The method according to claim 1, further comprising outputting an uplink authorization which includes a communication resource associated with the uplink cancellation instruction, wherein the uplink authorization instructs a user device (UE) to ignore at least a portion of the uplink cancellation instruction.

8. The method according to claim 7, wherein the uplink authorization is associated with a type of communication, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is based on the fact that the uplink authorization is associated with a type of communication.

9. The method according to claim 7, wherein the uplink authorization is associated with the type of physical channel, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is based on the type of physical channel.

10. It is a device, One or more memory locations that store processor-executable code, The device comprises one or more processors coupled to one or more of the memory, and the one or more processors are connected to the device. Output instructions for the level of detail regarding uplink cancellation, Output the allocation of uplink resources, To determine the reallocation of the aforementioned uplink resources, Based on the above determination, an uplink cancellation instruction corresponding to the uplink resource is output, the uplink cancellation instruction comprises a bitmap associated with the uplink resource, where each bit of the bitmap corresponds to a subset of the uplink resource and indicates whether cancellation is applied to each subset of the uplink resource, where the amount of uplink resource in each subset of the uplink resource is based on the indicated granularity for uplink cancellation, and the uplink cancellation instruction indicates the time to apply uplink cancellation based on the time of receipt of the uplink cancellation instruction and the time offset for uplink cancellation. A device that is operable to execute the code for causing the following to happen.

11. The apparatus according to claim 10, wherein the bitmap corresponds to the configured uplink bandwidth portion.

12. In order to output the uplink cancellation instruction, one or more processors provide the device with: The apparatus according to claim 10, which is operable to execute the code for causing the bitmap to output a repeating indicator associated with the bitmap.

13. The apparatus according to claim 10, wherein each subset of the uplink resource corresponding to each bit of the bitmap corresponds to an uplink resource in an uplink / downlink TDD configuration.

14. The apparatus according to claim 10, wherein the time offset for uplink cancellation is based on user equipment (UE) capability.

15. The one or more processors in the device, The apparatus according to claim 10, which is operable to execute the code for determining the time for applying uplink cancellation based on an uplink / downlink time-division duplex (TDD) configuration.

16. The one or more processors in the device The apparatus according to claim 10, which is operable to execute the code for causing to output an uplink permit having a communication resource associated with the uplink cancellation instruction, wherein the uplink permit instructs the user equipment (UE) to ignore at least a portion of the uplink cancellation instruction.

17. The apparatus according to claim 16, wherein the uplink authorization is associated with a type of communication, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is based on the fact that the uplink authorization is associated with a type of communication.

18. The apparatus according to claim 16, wherein the uplink authorization is associated with the type of physical channel, and the instruction to the UE to ignore at least a portion of the uplink cancellation instruction is based on the type of physical channel.

19. Means for outputting a granularity instruction for uplink cancellation, A means for outputting the allocation of uplink resources, Means for determining the reallocation of the uplink resources, Based on the above determination, means for outputting an uplink cancellation instruction corresponding to the uplink resource, the uplink cancellation instruction comprising a bitmap associated with the uplink resource, where each bit of the bitmap corresponds to a subset of the uplink resource and indicates whether cancellation is applied to each subset of the uplink resource, wherein the amount of uplink resource in each subset of the uplink resource is based on the indicated granularity for uplink cancellation, and the uplink cancellation instruction indicates the time for applying uplink cancellation based on the time of receipt of the uplink cancellation instruction and the time offset for uplink cancellation. A device equipped with the following features.

20. A non-temporary computer-readable medium for storing code for wireless communication in a network entity, wherein the code is: Output instructions for the level of detail regarding uplink cancellation, Output the allocation of uplink resources, To determine the reallocation of the aforementioned uplink resources, Based on the above determination, an uplink cancellation instruction corresponding to the uplink resource is output, the uplink cancellation instruction comprises a bitmap associated with the uplink resource, where each bit of the bitmap corresponds to a subset of the uplink resource and indicates whether cancellation is applied to each subset of the uplink resource, where the amount of uplink resource in each subset of the uplink resource is based on the indicated granularity for uplink cancellation, and the uplink cancellation instruction indicates the time to apply uplink cancellation based on the time of receipt of the uplink cancellation instruction and the time offset for uplink cancellation. A non-temporary computer-readable medium comprising instructions that can be executed by at least one processor to perform the following actions.

21. The method according to claim 1, wherein the allocation of the uplink resource is associated with a first type of communication having a first delay threshold, and the reallocation of the uplink resource is based on a second type of communication having a second delay threshold different from the first delay threshold.

22. The apparatus according to claim 10, wherein the allocation of the uplink resource is associated with a first type of communication having a first delay threshold, and the reallocation of the uplink resource is determined based on a second type of communication having a second delay threshold different from the first delay threshold.

Images