Patent Description:
Next-generation wireless communication systems (e.g., 5GS) may include a <NUM> core network and a <NUM> radio access network (RAN), such as a New Radio (NR)-RAN. The NR-RAN supports communication via one or more cells. For example, a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and/or access a second cell of a second BS.

A BS may schedule access to a cell to support access by multiple UEs. For example, a BS may allocate different resources (e.g., time domain and frequency domain resources) for different UEs operating within a cell of the BS.

As the demand for mobile broadband access continues to increase, research and development continue to advance communication technologies, including technologies for enhancing communication within a wireless network in particular, not only to meet the growing demand for mobile broadband access, but to advance and enhance the user experience with mobile communications.

<CIT> discloses a radio terminal comprising a controller configured to transmit a physical uplink shared channel to a base station by an interlace mapping using a plurality of resource blocks distributed on a frequency axis while overlapping on a time axis. The controller receives, from the base station, control channel information on a time-frequency resource used for transmitting the physical uplink control channel. The controller stops transmission in a specific resource block corresponding to the time-frequency resource from among the plurality of resource blocks, based on the control channel information.

<CIT> discloses systems, apparatuses, methods, and computer-readable media for causing a user equipment (UE) device to receive a configuration signaling to monitor for uplink (UL) cancellation indications; monitor a search space for an UL cancellation indication; detect an UL cancellation indication in the search space; and in response, cancel at least a portion of a scheduled UL transmission.

The following presents a summary of one or more aspects of the present disclosure, in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form as a prelude to the more detailed description that is presented later.

Various aspects of the disclosure relate to canceling an uplink transmission. In some examples, after scheduling a first UE for an uplink transmission on a particular resource, a BS may elect to schedule a second UE with higher priority traffic on at least a portion of that same resource. In this case, the BS may send an uplink cancelation indication (UL CI) to instruct the first UE to cancel its transmission. For some transmissions on an unlicensed band (e.g., for New Radio - Unlicensed (NR-U) operation), an interlace structure and resource block (RB) sets are used for frequency-domain resource allocation. The disclosure relates in some aspects to an UL CI that can indicate interlace and/or RB set parameters for the frequency domain.

These and other aspects of the disclosure will become more fully understood upon a review of the detailed description, which follows. Other aspects, features, and embodiments of the present disclosure will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, example embodiments of the present disclosure in conjunction with the accompanying figures. While features of the present disclosure may be discussed relative to certain embodiments and figures below, all embodiments of the present disclosure can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments of the disclosure discussed herein. In similar fashion, while example embodiments may be discussed below as device, system, or method embodiments it should be understood that such example embodiments can be implemented in various devices, systems, and methods.

While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.

By virtue of the wireless communication system <NUM>, the UE <NUM> may be enabled to carry out data communication with an external data network <NUM>, such as (but not limited to) the Internet or an Ethernet network.

The radio access network <NUM> is further illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be an apparatus that provides a user with access to network services.

Within the present document, a "mobile" apparatus need not necessarily have a capability to move, and may be stationary. The term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies. UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of a mobile apparatus include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC), a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA), and a broad array of embedded systems, e.g., corresponding to an "Internet of Things" (IoT). A mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. A mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc. A mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid), lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc. Still further, a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.

In addition, the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols. As used herein, a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier. A slot may carry <NUM> or <NUM> OFDM symbols. A subframe may refer to a duration of <NUM>. Multiple subframes or slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration.

Referring now to <FIG>, by way of example and without limitation, a schematic illustration of a RAN <NUM> is provided. In some examples, the RAN <NUM> may be the same as the RAN <NUM> described above and illustrated in <FIG>. The geographic area covered by the RAN <NUM> may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station. <FIG> illustrates macrocells <NUM>, <NUM>, and <NUM>, and a small cell <NUM>, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.

Various base station arrangements can be utilized. For example, in <FIG>, two base stations <NUM> and <NUM> are shown in cells <NUM> and <NUM>; and a third base station <NUM> is shown controlling a remote radio head (RRH) <NUM> in cell <NUM>.

Within the RAN <NUM>, the cells may include UEs that may be in communication with one or more sectors of each cell. Further, each base station <NUM>, <NUM>, <NUM>, and <NUM> may be configured to provide an access point to a core network (e.g., as illustrated in <FIG>) for all the UEs in the respective cells. For example, UEs <NUM> and <NUM> may be in communication with base station <NUM>; UEs <NUM> and <NUM> may be in communication with base station <NUM>; UEs <NUM> and <NUM> may be in communication with base station <NUM> by way of RRH <NUM>; and UE <NUM> may be in communication with base station <NUM>. In some examples, the UEs <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> may be the same as the UE/scheduled entity <NUM> described above and illustrated in <FIG>.

In some examples, an unmanned aerial vehicle (UAV) <NUM>, which may be a drone or quadcopter, can be a mobile network node and may be configured to function as a UE. For example, the UAV <NUM> may operate within cell <NUM> by communicating with base station <NUM>.

In a further aspect of the RAN <NUM>, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs <NUM> and <NUM>) may communicate with each other using peer to peer (P2P) or sidelink signals <NUM> without relaying that communication through a base station (e.g., base station <NUM>). In a further example, UE <NUM> is illustrated communicating with UEs <NUM> and <NUM>. Here, the UE <NUM> may function as a scheduling entity or a primary sidelink device, and UEs <NUM> and <NUM> may function as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In still another example, a UE may function as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and/or in a mesh network. In a mesh network example, UEs <NUM> and <NUM> may optionally communicate directly with one another in addition to communicating with the scheduling entity <NUM>. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources. In some examples, the sidelink signals <NUM> include sidelink traffic (e.g., a physical sidelink shared channel) and sidelink control (e.g., a physical sidelink control channel).

In the radio access network <NUM>, the ability for a UE to communicate while moving, independent of its location, is referred to as mobility. The various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an access and mobility management function (AMF). The AMF (not shown in <FIG>) may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.

A radio access network <NUM> may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if signal quality from a neighboring cell exceeds that from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell. For example, UE <NUM> (illustrated as a vehicle, although any suitable form of UE may be used) may move from the geographic area corresponding to its serving cell <NUM> to the geographic area corresponding to a neighbor cell <NUM>. When the signal strength or quality from the neighbor cell <NUM> exceeds that of its serving cell <NUM> for a given amount of time, the UE <NUM> may transmit a reporting message to its serving base station <NUM> indicating this condition. In response, the UE <NUM> may receive a handover command, and the UE may undergo a handover to the cell <NUM>.

In a network configured for UL-based mobility, UL reference signals from each UE may be utilized by the network to select a serving cell for each UE. In some examples, the base stations <NUM>, <NUM>, and <NUM>/<NUM> may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs), unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH)). The UEs <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal. The uplink pilot signal transmitted by a UE (e.g., UE <NUM>) may be concurrently received by two or more cells (e.g., base stations <NUM> and <NUM>/<NUM>) within the radio access network <NUM>. Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations <NUM> and <NUM>/<NUM> and/or a central node within the core network) may determine a serving cell for the UE <NUM>. As the UE <NUM> moves through the radio access network <NUM>, the network may continue to monitor the uplink pilot signal transmitted by the UE <NUM>. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds that of the signal strength or quality measured by the serving cell, the network <NUM> may handover the UE <NUM> from the serving cell to the neighboring cell, with or without informing the UE <NUM>.

In various implementations, the air interface in the radio access network <NUM> may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access. Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs. For example, the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.

The air interface in the radio access network <NUM> may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, <NUM> NR specifications provide multiple access for UL transmissions from UEs <NUM> and <NUM> to base station <NUM>, and for multiplexing for DL transmissions from base station <NUM> to one or more UEs <NUM> and <NUM>, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, <NUM> NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Further, multiplexing DL transmissions from the base station <NUM> to UEs <NUM> and <NUM> may be provided utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

The air interface in the radio access network <NUM> may further utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions. Full duplex means both endpoints can simultaneously communicate with one another. Half duplex means only one endpoint can send information to the other at a time. In a wireless link, a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancelation technologies. Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot.

Various aspects of the present disclosure will be described with reference to an OFDM waveform, an example of which is schematically illustrated in <FIG>. It should be understood by those of ordinary skill in the art that the various aspects of the present disclosure may be applied to an SC-FDMA waveform in substantially the same way as described herein below. That is, while some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles may be applied as well to SC-FDMA waveforms.

Referring now to <FIG>, an expanded view of an example DL subframe (SF) <NUM> is illustrated, showing an OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may vary from the example described here, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers.

The resource grid <NUM> may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids <NUM> may be available for communication. The resource grid <NUM> is divided into multiple resource elements (REs) <NUM>. An RE, which is <NUM> subcarrier × <NUM> symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) <NUM>, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include <NUM> subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB <NUM> entirely corresponds to a single direction of communication (either transmission or reception for a given device).

Scheduling of UEs (e.g., scheduled entities) for downlink or uplink transmissions typically involves scheduling one or more resource elements <NUM> within one or more bandwidth parts (BWPs), where each BWP includes two or more contiguous or consecutive RBs. Thus, a UE generally utilizes only a subset of the resource grid <NUM>. In some examples, an RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE.

Each <NUM> subframe <NUM> may consist of one or multiple adjacent slots. In the example shown in <FIG>, one subframe <NUM> includes four slots <NUM>, as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include <NUM> or <NUM> OFDM symbols with a nominal CP. Additional examples may include mini-slots having a shorter duration (e.g., one or two OFDM symbols). These mini-slots may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.

An expanded view of one of the slots <NUM> illustrates the slot <NUM> including a control region <NUM> and a data region <NUM>. In general, the control region <NUM> may carry control channels (e.g., PDCCH), and the data region <NUM> may carry data channels (e.g., PDSCH or PUSCH). Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. The simple structure illustrated in <FIG> is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region(s) and data region(s).

Although not illustrated in <FIG>, the various REs <NUM> within a RB <NUM> may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs <NUM> within the RB <NUM> may also carry pilots or reference signals, including but not limited to a demodulation reference signal (DMRS) or a sounding reference signal (SRS). These pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB <NUM>.

In a DL transmission, the transmitting device (e.g., the scheduling entity) may allocate one or more REs <NUM> (e.g., within a control region <NUM>) to carry DL control information including one or more DL control channels, such as a PBCH; a physical control format indicator channel (PCFICH); a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH); and/or a physical downlink control channel (PDCCH), etc., to one or more scheduled entities. The transmitting device may further allocate one or more REs <NUM> to carry other DL signals, such as a DMRS; a phase-tracking reference signal (PT-RS); a channel state information - reference signal (CSI-RS); a primary synchronization signal (PSS); and a secondary synchronization signal (SSS).

The synchronization signals PSS and SSS, and in some examples, the PBCH and a PBCH DMRS, may be transmitted in a synchronization signal block (SSB) that includes <NUM> consecutive OFDM symbols, numbered via a time index in increasing order from <NUM> to <NUM>. In the frequency domain, the SSB may extend over <NUM> contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from <NUM> to <NUM>. Of course, the present disclosure is not limited to this specific SSB configuration. Other nonlimiting examples may utilize greater or fewer than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit a PBCH; and/or may utilize a different number of symbols and/or nonconsecutive symbols for an SSB, within the scope of the present disclosure.

The PCFICH provides information to assist a receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI) including but not limited to power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions. The PHICH carries HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc..

In an UL transmission, the transmitting device (e.g., the scheduled entity) may utilize one or more REs <NUM> to carry UL control information including one or more UL control channels, such as a physical uplink control channel (PUCCH), to the scheduling entity. UL control information may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. For example, the UL control information may include a DMRS or SRS. In some examples, the control information may include a scheduling request (SR), i.e., request for the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel, the scheduling entity may transmit downlink control information that may schedule resources for uplink packet transmissions. UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.

In addition to control information, one or more REs <NUM> (e.g., within the data region <NUM>) may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for a DL transmission, a PDSCH; or for an UL transmission, a physical uplink shared channel (PUSCH). In some examples, one or more REs <NUM> within the data region <NUM> may be configured to carry SIBs (e.g., SIB1), carrying system information that may enable access to a given cell.

The channels or carriers described above with reference to <FIG> are not necessarily all of the channels or carriers that may be utilized between a scheduling entity and scheduled entities, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

As discussed above, a BS may schedule uplink transmissions for UEs, specifying which time-domain and frequency-domain resources each UE is to use for its respective uplink transmission. In some scenarios, the uplink transmissions by different UEs may carry different types of traffic (e.g., with different requirements). For example, a transmission by a first UE may be a regular traffic transmission, while a transmission by a second UE may be for traffic having stricter latency requirements and/or reliability requirements. For example, the transmission by the second UE may be for enhanced ultra-reliable low latency communication (eURLLC). These different types of traffic may be associated with different priorities. For example, eURLLC traffic may have a higher priority than regular traffic.

In some cases, after scheduling a first uplink transmission for a first UE, a BS may determine that a second, higher priority, uplink transmission for a second UE needs to be scheduled. However, there might not be sufficient resources available for the second transmission. For example, the second transmission may have very strict latency requirement such that the second transmission cannot be delayed. In this case, the BS may elect to cancel the first transmission so that the BS can schedule for the second transmission one or more of the resources originally allocated for the first transmission.

A BS may use an uplink cancelation indication (UL CI) to instruct a UE to cancel a previously scheduled transmission. In some examples, the UL CI (hereafter referred to simply as CI for convenience) may take the form of downlink control information (DCI) format 2_4 signaling. That is, a BS may send a DCI format 2_4 to a UE to signal the UE to cancel a previously scheduled uplink transmission such as a PUSCH transmission or an SRS transmission.

A UE that detects a DCI format 2_4 from a serving cell may determine, for a scheduled PUSCH transmission (or a repetition of a PUSCH transmission if the PUSCH transmission is with repetitions), whether the DCI format 2_4 identifies a resource of the PUSCH transmission (or the repetition of the PUSCH transmission). For example, the UE may determine whether a group of symbols, from a set of symbols (e.g., designated TCI symbols) in the DCI format 2_4, has a corresponding bit value of '<NUM>' and whether that group of symbols includes a symbol of the PUSCH transmission (or the repetition of the PUSCH transmission). In addition, the UE may determine whether a group of PRBs, from a set of PRBs (e.g., designated BCI PRBs) in the DCI format 2_4, has a corresponding bit value of '<NUM>' and includes a PRB of the PUSCH transmission (or the repetition of the PUSCH transmission).

If these two conditions are met, the UE may cancel the scheduled PUSCH transmission (or the repetition of the PUSCH transmission). In some examples,, the cancelation of a PUSCH transmission (or the repetition of the PUSCH transmission) may include all symbols from the earliest symbol of the PUSCH transmission (or the repetition of the PUSCH transmission) that are in one or more groups of symbols having corresponding bit values of '<NUM>' in the DCI format 2_4.

Similarly, a UE that detects a DCI format 2_4 from a serving cell may determine, for a scheduled SRS transmission, whether the DCI format 2_4 identifies a resource of the SRS transmission. For example, the UE may determine whether a group of symbols, from a set of symbols (e.g., designated TCI symbols) in the DCI format 2_4, has a corresponding bit value of '<NUM>' and whether that group of symbols includes a symbol of the SRS transmission. In addition, the UE may determine whether a group of PRBs, from a set of PRBs (e.g., designated BCI PRBs) in the DCI format 2_4, has a corresponding bit value of '<NUM>' and includes a PRB of the SRS transmission.

If these two conditions are met, the UE may cancel the scheduled SRS transmission. In some examples, the cancelation of an SRS transmission may include symbols that are in one or more groups of symbols having corresponding bit values of '<NUM>' in the DCI format 2_4.

In some examples, the parameters for a CI such as DCI format 2_4 may include a payload size of the CI, a time duration for the CI, a time granularity for the CI, and a frequency region for the CI. A BS may configure a UE with these parameters using a radio resource control (RRC) message or some other suitable type of signaling.

In some examples, the payload size of the CI may be the number of bits for the cancelation indicator for the cell. In some examples, the CI payload size may be an RRC parameter CI-PayloadSize, designated, NCI. The length of the DCI may controlled by a separate RRC parameter dci-PayloadSize-forCI.

In some examples, the time duration for the CI may start a defined period of time (e.g., a defined number of symbols) after the PDCCH including the CI is received (e.g., the time duration starts from N2 after PDCCH). In some examples, the CI payload size may be an RRC parameter timedurationforCI, designated, TCI.

In some examples, the time granularity for the CI may indicate the number of partitions within the time duration for the CI. In some examples, the time granularity for the CI may be any of the values {<NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM>}. Other values may be used in other examples. In some examples, the time granularity for the CI may be an RRC parameter timeGranularityforCI, designated, GCI.

In some examples, the frequency region for the CI may be resource indication value (RIV) indication configured by an RRC message. In some example, the frequency region for the CI may be a value within a value range of <NUM>. Other values may be used in other examples. In some examples, the frequency region for the CI may be configured in a similar manner as an information element (IE) "locationAndBandwidth" that is used for configuring a BWP. The configuration of the frequency region for the CI may be per-serving cell specific. A reference point for the frequency region may be derived based on the RRC parameter offsetToCarrier (e.g., derived in a similar manner as the BWP configuration). In some examples, the frequency region for the CI may be an RRC parameter frequencyRegionforCI.

In some examples, a <NUM>-D bitmap is used to indicate the resources being canceled by a CI. <FIG> illustrates an example of a <NUM>-D bitmap <NUM> that may be used to indicate the resources for CI. Here, a BS sends DL information <NUM> including a CI <NUM> to a UE. The CI identifies time-domain resources (x-axis) and frequency domain resources (y-axis) subject to cancelation. Specifically, seven bits <NUM> of the CI indicate whether corresponding time resources are subject to cancelation, while four bits <NUM> of the CI indicate whether corresponding frequency resources are subject to cancelation. The resources subject to cancelation are indicated by the cross-hatched blocks (e.g., block <NUM>) in the bitmap <NUM>.

In the example of <FIG>, the <NUM>-D bitmap <NUM> includes M x N blocks (e.g., CI-PayloadSize = M x N). Here, M = GCI, where the applicable symbols within TCI are grouped into GCI groups with approximately equal size per group. Thus, N = CI-PayloadSize / M. The parameter NCI may be used to refer to the set of symbols within timedurationforCI excluding synchronization signal block (SSB) symbols and semi-static downlink (DL) symbols. In the bitmap <NUM>, CI-PayloadSize = <NUM>, timedurationforCI = timeGranularityforCI x <NUM> = <NUM> OFDM symbols, timeGranularityforCI = <NUM> groups, and frequencyRegionforCI = <NUM> sub-bands (sub-bands = frequencyRegionforCI / <NUM>). Other bitmap parameters may be used in other examples.

As discussed above, a network may use unlicensed radio frequency (RF) spectrum in some scenarios. For example, a network operator may deploy cells that are configured to communicate on an unlicensed RF spectrum (e.g., in addition to cells operating on a licensed RF spectrum) to extend the coverage of the network or to provide additional services (e.g., higher throughput) to UEs operating under the network. NR operation in unlicensed RF spectrum may be referred to as NR-U.

For UL transmissions on unlicensed RF spectrum, interlaced-based scheduling may be used in the frequency domain. For example, in NR-U, a PRB interlaced waveform may be used in the UL to satisfy occupied channel bandwidth (OCB) goals and/or to boost UL transmit power for a given power spectral density (PSD) limitation.

<FIG> illustrates an example of UL interlaces <NUM> (e.g., for NR-U). In this example, a <NUM> bandwidth <NUM> (e.g., for a <NUM> sub-carrier spacing (SCS)) is divided into nine clusters (e.g., including cluster <NUM><NUM>). A given interlace is repeated in each cluster. For example, interlace <NUM> is repeated in cluster <NUM>, cluster <NUM>,. , cluster <NUM>, while interlace <NUM> is repeated in cluster <NUM>, cluster <NUM>,. , cluster <NUM>, and so on.

A BS may schedule a UE to transmit according to one of more of the interlaces. For example, a BS may schedule a first UE to transmit on interlace <NUM> and schedule a second UE to transmit on interlace <NUM>. As another example, a BS may schedule a first UE to transmit on interlace <NUM> and interlace <NUM>. Other examples are possible.

A given interlace may correspond to a set of resources. For example, as indicated by the arrow <NUM>, interlace <NUM> may correspond to a resource block <NUM> and a slot or mini-slot <NUM>.

In some examples, for a given SCS, the PRB-based interlace design that follows may be supported for PUSCH and PUCCH. The same spacing (M) may be used between consecutive PRBs in an interlace for all interlaces regardless of carrier bandwidth (e.g., the number of PRBs per interlace may be dependent on the carrier bandwidth). Point A (e.g., a common reference point for RB grids) may be the reference for the interlace definition. For all bandwidths, the parameter M may correspond to <NUM> interlaces (M = <NUM>) for <NUM> SCS, while the parameter M may correspond to <NUM> interlaces (M = <NUM>) for <NUM> SCS.

In some examples, for interlace transmission of at least PUSCH and PUCCH, the PRB-based interlace design that follows may be supported for <NUM> carrier bandwidth and <NUM> SCS. The parameter M may correspond to <NUM> interlaces (M = <NUM>). The parameter N may correspond to <NUM> or <NUM> PRBs per interlace (N = <NUM> or <NUM> PRBs / interlace). In addition, <NUM> bits may be used for to provide <NUM> combinations of continuous interlaces, along with <NUM> combinations of discontinuous interlaces.

In some examples, for interlace transmission of at least PUSCH and PUCCH, the PRB-based interlace design that follows may be supported for <NUM> carrier bandwidth and <NUM> SCS. The parameter M may correspond to <NUM> interlaces (M = <NUM>). The parameter N may correspond to <NUM> or <NUM> PRBs per interlace (N = <NUM> or <NUM> PRBs / interlace). In addition, <NUM> bits may be used for <NUM> interlaces with a bitmap.

Comparing <FIG> and <FIG>, the contiguous resource bitmap defined by the CI of <FIG> may be inconsistent with the interlaced-based (e.g., noncontiguous) resource allocation of <FIG>. Thus, in some aspects, the CI scheme of <FIG> might not work well for UL transmissions in unlicensed RF spectrum (e.g., NR-U UL). While the CI parameters for the time domain may be directly applicable to UL transmissions in unlicensed RF spectrum, given that an interlace and RB set structure may be used for UL resource allocation in unlicensed RF spectrum, the CI frequency domain parameters might not directly apply to UL transmissions in unlicensed RF spectrum.

The disclosure relates in some aspects to a CI that specifies parameters in the frequency domain for an UL transmission in unlicensed RF spectrum that uses an interlace and RB set structure. As discussed above, the allocated resources in this case may be indicated by a combination of interlace and RB sets.

<FIG> illustrates an example of such a resource allocation <NUM>. <FIG> illustrates a set of common resource blocks (CRBs) (which may also be referred to as carrier resource blocks) and a set of physical resource blocks (PRBs) referenced to a Point A <NUM>. In the CRBs, five interlaces are applied across the whole band for <NUM> SCS. For example, two instance of interlace <NUM>604A and 604B are shown for sub-bands <NUM> and <NUM>, respectively.

In the PRBs (e.g., for a particular cell), an RB set <NUM>606A and an RB set <NUM>606B are allocated in this example. In addition, interlace <NUM> is allocated within the RB set <NUM>606A and the RB set <NUM>606B. For example, three instance of interlace <NUM>608A, 608B, and 608C are shown for the RB set <NUM>606A. In addition, three instance of interlace <NUM>610A, 610B, and 610C are shown for the RB set <NUM>606B.

In some examples, when a PRB interlaced waveform is used for an UL transmission, the bits of a CI (e.g., the frequency domain bits in the <NUM>-D bitmap of CI) may be defined to indicate the RB set and interlace based definition for the transmission. For example, given a total of F bits for the frequency domain bitmap, and a quantity R for the number of RB sets (R RB sets) in a cell with X interlaces, the F bits may be used to indicate the interlace(s) and/or RB set(s) to be canceled.

In some examples, a mapping between the F bits and the R RB sets and X interlaces may be determined by a bit mapping operation that uses a formula, a table, or in some other mapping technique. For example, a table may map a given bit of the F bits to a particular RB set or a group of RB sets. Alternatively or in addition, the table may map a given bit of the F bits to particular interlace or a set of interlaces. <FIG> illustrates several example bit mapping scenarios.

A mapping 700A of <FIG> illustrates an example where the number of F bits <NUM> is equal to the number of RB sets <NUM>. In a scenario where the identification of the canceled RB sets takes priority over the identification of the canceled interlaces, all of the F bits <NUM> may be used to indicate the RB sets <NUM> as shown.

A mapping 700B of <FIG> illustrates an example where the number of F bits <NUM> is less than the number of RB sets <NUM>. In a scenario whether the identification of the canceled RB sets takes priority over the identification of the canceled interlaces, all of the F bits <NUM> may be used to indicate the RB sets <NUM> as shown. In this case, since the number of F bits <NUM> is less than the number of RB sets <NUM>, at least one of the F bits 706A is used to indicate a group of RB sets 708A. Other mappings between the F bits <NUM> and the RBs sets <NUM> may be used in other examples.

A mapping 700C of <FIG> illustrates an example where the number of F bits <NUM> is greater that the number of RB sets <NUM>. In a scenario whether the identification of the canceled RB sets takes priority over the identification of the canceled interlaces, a first set of the F bits 710A may be used to indicate the RB sets <NUM>. In addition, a second set of the F bits 710B may be used to indicate the interlaces <NUM>. If the number of F bits 710B in the second set is less than the number of interlaces <NUM>, at least one of the F bits 710C of the second set may be used to indicate a group of interlaces 714A. Other mappings between the F bits <NUM> and the interlaces <NUM> may be used in other examples.

Mappings similar to the mappings 700A, 700B, and 700C could be applied for a scenario where the identification of the canceled interlaces takes priority over the identification of the canceled RB sets. In a first example (e.g., corresponding to the mapping 700A), all of the F bits may be used to indicate the interlaces in the case where the number of F bits is equal to the number of interlaces. In a second example (e.g., corresponding to the mapping 700B), all of the F bits may be used to indicate the interlaces in the case where the number of F bits is less to the number of interlaces. In this case, since the number of F bits is less than the number of interlaces, at least one of the F bits may be used to indicate a group of interlaces. In a third example (e.g., corresponding to the mapping 700C) where the number of F bits is greater than the number of interlaces, a first set of the F bits may be used to indicate the interlaces, while a second set of the F bits may be used to indicate the RB sets. In this case, if the number of F bits of the second set is less than the number of RB sets, at least one of the F bits of the second set may be used to indicate a group of RB sets.

A mapping 700D of <FIG> illustrates an example where the F bits <NUM> are split between the RB sets <NUM> and the interlaces <NUM>. For example, a first set of the F bits 716A may be used to indicate the RB sets <NUM>. In addition, a second set of the F bits 716B may be used to indicate the interlaces <NUM>. If the number of F bits 716A in the first set is less than the number of RB sets <NUM>, at least one of the F bits 716C of the first set may be used to indicate a group of RB sets 718A. If the number of F bits 716B in the second set is less than the number of interlaces <NUM>, at least one of the F bits 716D of the second set may be used to indicate a group of interlaces 720A. Other mappings between the F bits <NUM> and the RB sets <NUM> and/or the interlaces <NUM> may be used in other examples.

As mentioned above, bit mapping operations may be performed using a formula. Three example formula options that may be used to group RB sets and interlaces to be represented by the F bits follow. Other formulas may be used in other examples.

In a first option, the formula set forth in Equations <NUM> and <NUM> prioritizes RB sets (e.g., if a limited number of bits is available, the bits are first used to indicate the RB sets). For example, the formula first allocates bits to RB sets, and if there are remaining bits, the formula allocates bits to interlaces. <MAT> <MAT>.

Two examples of Equation <NUM> follow. In the first example, F = <NUM> and R = <NUM>. In the second example, F = <NUM> and R = <NUM>.

In the first example, for the first step, <MAT> groups including <MAT> RB sets corresponds to <MAT> groups including <MAT> RB sets. This equates to <NUM> - <NUM> + <NUM>*<NUM> groups including <NUM> RB sets. Thus, there are three groups of RB sets, where each group includes two RB sets. Accordingly, the three F bits identify the six RB sets. Thus, there is no need to perform the second step of Equation <NUM> in this example.

In the second example, for the first step, <MAT> groups including <MAT> RB sets corresponds to <MAT> groups including <MAT> RB sets. This equates to <NUM> - <NUM> + <NUM>*<NUM> groups including <NUM> RB sets. Thus, there is one group that includes one RB set. The second step of Equation <NUM> is then performed, <MAT> groups including <MAT> RB sets corresponds to <MAT> groups including <MAT> RB sets. This equates to <NUM> - <NUM>*<NUM> groups including <NUM> RB sets. Thus, there are two groups that include two RB sets. Accordingly, the three F bits identify the five RB sets.

In a second option, the formula the formula set forth in Equations <NUM> and <NUM> prioritizes interlaces (e.g., if a limited number of bits is available, the bits are used to indicate the interlace). For example, the formula first allocates bits to interlaces, and if there are remaining bits, the formula allocates bit to RB sets. <MAT> <MAT>.

In a third option, the formula the formula set forth in Equations <NUM> and <NUM> defines a joint RB sets and interlaces bitmap as a function of the number of bits available. For example, F is split between interlaces and RB sets (e.g., F = Fx + Fr, where Fx bits are for the interlaces and Fr bits are for the RB sets). <MAT><MAT>.

<FIG> illustrates an example of signaling in a communication system <NUM> according to the first example implementation. In this example, the system <NUM> includes a first UE <NUM>, a BS <NUM> that operates in the unlicensed band, and a second UE <NUM>. It should be appreciated that the system <NUM> would typically include other devices as well. In some implementations, the UE <NUM> and/or the UE <NUM> may correspond to the scheduled entity <NUM> of <FIG>. In some implementations, the BS <NUM> may correspond to the scheduling entity <NUM> (e.g., a gNB, a transmit receive point, etc.) of <FIG>.

At <NUM>, the BS <NUM> schedules a resource (resource <NUM>) for an NR-U transmission by the first UE <NUM>.

At <NUM>, the BS <NUM> sends an uplink grant to the first UE <NUM> that indicates the scheduled resource <NUM>.

At <NUM>, the BS determines that the second UE <NUM> has a higher priority transmission and therefore schedules a resource 1a for an NR-U transmission by the second UE <NUM>. Here, resource 1a overlaps resource <NUM> at least in part. In some examples, resource 1a is a subset of resource <NUM>. In some examples, a portion of resource 1a overlaps a portion of resource <NUM>. In some examples, resource 1a could entirely overlap resource <NUM>.

At <NUM>, the BS <NUM> sends an uplink grant to the second UE <NUM> that indicates the scheduled resource 1a.

Accordingly, at <NUM>, the BS <NUM> generates a CI to be sent to the first UE <NUM> to cancel the scheduled uplink transmission by the first UE <NUM> on resource <NUM>. In some examples, the BS <NUM> may use a bit mapping operation as described herein (e.g., a table any of the formulas of Equation <NUM> - <NUM>) to identify the interlace(s) and/or RB set(s) to be canceled.

At <NUM>, the BS <NUM> sends the CI for resource <NUM> to the first UE <NUM>.

At <NUM>, the first UE <NUM> identifies the interlace(s) and/or RB set(s) to be canceled due to the CI. In some examples, the first UE <NUM> may use a bit mapping operation as described herein (e.g., a table any of the formulas of Equation <NUM> - <NUM>) to identify the interlace(s) and/or RB set(s) to be canceled.

At <NUM>, the first UE cancels its scheduled transmission on resource <NUM>.

At <NUM>, the second UE <NUM> conducts the uplink transmission on resource 1a.

<FIG> is a diagram illustrating an example of a hardware implementation for a wireless communication device <NUM> employing a processing system <NUM>. For example, the wireless communication device <NUM> may be a user equipment (UE) or other device configured to wirelessly communicate with a base station, as illustrated in any one or more of <FIG>. In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system <NUM> that includes one or more processors <NUM>. In some implementations, the wireless communication device <NUM> may correspond to the scheduled entity <NUM> of <FIG>.

The wireless communication device <NUM> may be implemented with a processing system <NUM> that includes one or more processors <NUM>. Examples of processors <NUM> include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. In various examples, the wireless communication device <NUM> may be configured to perform any one or more of the functions described herein. That is, the processor <NUM>, as utilized in a wireless communication device <NUM>, may be used to implement any one or more of the processes and procedures described below.

In this example, the processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> communicatively couples together various circuits including one or more processors (represented generally by the processor <NUM>), a memory <NUM>, and computer-readable media (represented generally by the computer-readable medium <NUM>). The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface <NUM> provides an interface between the bus <NUM> and a transceiver <NUM> and between the bus <NUM> and an interface <NUM>. The transceiver <NUM> provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers <NUM>, each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). The interface <NUM> provides a communication interface or means of communicating with various other apparatus and devices (e.g., other devices housed within the same apparatus as the wireless communication device or other external apparatus) over an internal bus or external transmission medium, such as an Ethernet cable. Depending upon the nature of the apparatus, a user interface <NUM> (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface <NUM> is optional, and may be omitted in some examples, such as an IoT device.

One or more processors <NUM> in the processing system may execute software. The software may reside on a computer-readable medium <NUM>.

The computer-readable medium <NUM> may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The computer-readable medium <NUM> may reside in the processing system <NUM>, external to the processing system <NUM>, or distributed across multiple entities including the processing system <NUM>. The computer-readable medium <NUM> may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

In some aspects of the disclosure, the processor <NUM> may include circuitry configured for various functions. For example, the processor <NUM> may include communication and processing circuitry <NUM>. The communication and processing circuitry <NUM> may include one or more hardware components that provide the physical structure that performs various processes related to wireless communication (e.g., signal reception and/or signal transmission) as described herein. The communication and processing circuitry <NUM> may further include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and/or processing a signal for transmission) as described herein. In some examples, the communication and processing circuitry <NUM> may include two or more transmit/receive chains, each configured to process signals in a different RAT (or RAN) type. The communication and processing circuitry <NUM> may further be configured to execute communication and processing software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

In some implementations where the communication involves receiving information, the communication and processing circuitry <NUM> may obtain information from a component of the wireless communication device <NUM> (e.g., from the transceiver <NUM> that receives the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry <NUM> may output the information to another component of the processor <NUM>, to the memory <NUM>, or to the bus interface <NUM>. In some examples, the communication and processing circuitry <NUM> may receive one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry <NUM> may receive information via one or more channels. In some examples, the communication and processing circuitry <NUM> may include functionality for a means for receiving.

In some implementations where the communication involves sending (e.g., transmitting) information, the communication and processing circuitry <NUM> may obtain information (e.g., from another component of the processor <NUM>, the memory <NUM>, or the bus interface <NUM>), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry <NUM> may output the information to the transceiver <NUM> (e.g., that transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry <NUM> may send one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry <NUM> may send information via one or more channels. In some examples, the communication and processing circuitry <NUM> may include functionality for a means for sending (e.g., means for transmitting).

The processor <NUM> may include resource reservation circuitry <NUM> configured to perform resource reservation-related operations as discussed herein. The resource reservation circuitry <NUM> may further be configured to execute resource reservation software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

The processor <NUM> may include reservation cancelation circuitry <NUM> configured to perform reservation cancelation-related operations as discussed herein. The resource reservation circuitry <NUM> may include functionality for a means for receiving a cancelation indication. The reservation cancelation circuitry <NUM> may further be configured to execute reservation cancelation software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

<FIG> is a flow chart illustrating an example process <NUM> for a wireless communication system in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process <NUM> may be carried out by the wireless communication device <NUM> illustrated in <FIG>. In some aspects, the wireless communication device may be a user equipment. In some examples, the process <NUM> may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At block <NUM>, a wireless communication device may receive, from a base station, a first indication of a scheduled uplink transmission for the wireless communication device on an unlicensed radio frequency spectrum, wherein the first indication specifies at least one scheduled interlace of a plurality of interlaces and at least one set of scheduled resource blocks of a plurality of sets of resource blocks. For example, the communication and processing circuitry <NUM> and transceiver <NUM>, shown and described above in connection with <FIG>, may receive the first indication.

At block <NUM>, the wireless communication device may receive a cancelation indication from the base station, wherein the cancelation indication identifies the at least one scheduled interlace, the at least one set of scheduled resource blocks, or the at least one scheduled interlace and the at least one set of scheduled resource blocks. In some aspects, the cancelation indication may include a plurality of bits. In some aspects, the cancelation indication may include downlink control information (DCI) format 2_4. For example, the communication and processing circuitry <NUM> and transceiver <NUM>, shown and described above in connection with <FIG>, may receive the cancelation indication.

At block <NUM>, the wireless communication device may cancel the scheduled uplink transmission upon receiving the cancelation indication. For example, the reservation cancelation circuitry <NUM>, shown and described above in connection with <FIG>, may cancel the transmission.

In some aspects, the process may further include: performing a bit mapping operation to identify, from the cancelation indication, at least one of: a canceled interlace, a canceled set of resource blocks, or any combination thereof. In some aspects, the bit mapping operation may use a formula that prioritizes the plurality of sets of resource blocks over the plurality of interlaces. In some aspects, the bit mapping operation may use a formula that prioritizes the plurality of interlaces over the plurality of sets of resource blocks. In some aspects, the bit mapping operation may use a formula that identifies at least one canceled set of resource blocks and at least one canceled interlace.

In some aspects, the process may further include: identifying at least one canceled resource block based on one or more of the plurality of bits; and determining whether one or more of the at least one canceled resource block corresponds to the at least one set of scheduled resource blocks.

In some aspects, the process may further include: determining that the plurality of bits is greater in number than the plurality of sets of resource blocks; identifying at least one canceled resource block based on a first set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of sets of resource blocks; determining whether one or more of the at least one canceled resource block corresponds to the at least one set of scheduled resource blocks; identifying at least one canceled interlace based on a second set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of sets of resource blocks; and determining whether one or more of the at least one canceled interlace corresponds to the at least one scheduled interlace.

In some aspects, the process may further include: determining that the second set of the plurality of bits is fewer in number than the plurality of interlaces; identifying at least two canceled interlaces based on one bit of the second set of the plurality of bits after determining that the second set of the plurality of bits is fewer in number than the plurality of interlaces; and determining whether one or more of the at least two canceled interlaces corresponds to the at least one scheduled interlace.

In some aspects, the process may further include: identifying at least one canceled interlace based on one or more of the plurality of bits; and determining whether one or more of the at least one canceled interlace corresponds to the at least one scheduled interlace.

In some aspects, the process may further include: determining that the plurality of bits is fewer in number than the plurality of interlaces; identifying at least two canceled interlaces based on one bit of the plurality of bits after determining that the plurality of bits is fewer in number than the plurality of interlaces; and determining whether one or more of the at least two canceled interlaces corresponds to the at least one scheduled interlace.

In some aspects, the process may further include: determining that the plurality of bits is greater in number than the plurality of interlaces; identifying at least one canceled interlace based on a first set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of interlaces; determining whether one or more of the at least one canceled interlace corresponds to the at least one scheduled interlace; identifying at least one canceled resource block based on a second set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of interlaces; and determining whether one or more of the at least one canceled resource block corresponds to the at least one set of scheduled resource blocks.

In some aspects, the process may further include: determining that the second set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; identifying at least two canceled resource blocks based on one bit of the second set of the plurality of bits after determining that the second set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; and determining whether one or more of the at least two canceled resource blocks corresponds to the at least one set of scheduled resource blocks.

In some aspects, the process may further include: identifying at least one canceled resource block based on a first set of the plurality of bits; determining whether one or more of the at least one canceled resource block corresponds to the at least one set of scheduled resource blocks; identifying at least one canceled interlace based on a second set of the plurality of bits; and determining whether one or more of the at least one canceled interlace corresponds to the at least one scheduled interlace.

In some aspects, the process may further include: determining that the first set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; identifying at least two canceled resource blocks based on one bit of the first set of the plurality of bits after determining that the first set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; and determining whether one or more of the at least two canceled resource blocks corresponds to the at least one set of scheduled resource blocks.

<FIG> is a conceptual diagram illustrating an example of a hardware implementation for base station (BS) <NUM> employing a processing system <NUM>. In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system <NUM> that includes one or more processors <NUM>. In some implementations, the BS <NUM> may correspond to the scheduling entity <NUM> (e.g., a gNB, a transmit receive point, etc.) of <FIG>.

The processing system <NUM> may be substantially the same as the processing system <NUM> illustrated in <FIG>, including a bus interface <NUM>, a bus <NUM>, memory <NUM>, a processor <NUM>, and a computer-readable medium <NUM>. Furthermore, the core BS <NUM> may include an interface <NUM> (e.g., a network interface) that provides a means for communicating with various other apparatus within the core network and with one or more radio access network. The processor <NUM>, as utilized in BS <NUM>, may be used to implement any one or more of the processes described below. The wireless communication device <NUM> may be configured to perform any one or more of the operations described below in conjunction with <FIG>.

In some aspects of the disclosure, the processor <NUM> may include communication and processing circuitry <NUM>. The communication and processing circuitry <NUM> may include one or more hardware components that provide the physical structure that performs various processes related to communication (e.g., signal reception and/or signal transmission) as described herein. The communication and processing circuitry <NUM> may further include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and/or processing a signal for transmission) as described herein. The communication and processing circuitry <NUM> may further be configured to execute communication and processing software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

The processor <NUM> may include resource reservation circuitry <NUM> configured to perform resource reservation-related operations as discussed herein. The resource reservation circuitry <NUM> may include functionality for a means for determining that a second scheduled uplink transmission on the unlicensed radio frequency band is associated with a second priority. The resource reservation circuitry <NUM> may further be configured to execute resource reservation software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

The processor <NUM> may include reservation cancelation circuitry <NUM> configured to perform reservation cancelation-related operations as discussed herein. The reservation cancelation circuitry <NUM> may include functionality for a means for generating a cancelation indication. The reservation cancelation circuitry <NUM> may further be configured to execute reservation cancelation software <NUM> included on the computer-readable medium <NUM> to implement one or more functions described herein.

<FIG> is a flow chart illustrating another example process <NUM> for a wireless communication system in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process <NUM> may be carried out by the BS <NUM> illustrated in <FIG>. In some examples, the process <NUM> may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.

At block <NUM>, a BS may transmit a first indication of a first scheduled uplink transmission on an unlicensed radio frequency spectrum to a first wireless communication device, wherein the first indication specifies at least one interlace of a plurality of interlaces and at least one set of resource blocks of a plurality of sets of resource blocks, and wherein the first scheduled uplink transmission is associated with a first priority. For example, the communication and processing circuitry <NUM> and transceiver <NUM>, shown and described above in connection with <FIG>, may transmit the indication.

At block <NUM>, the BS may determine that a second scheduled uplink transmission on the unlicensed radio frequency spectrum is associated with a second priority. For example, the resource reservation circuitry <NUM>, shown and described above in connection with <FIG>, may determine the priority of a scheduled transmission.

At block <NUM>, the BS may generate a cancelation indication when the second priority is higher than the first priority, wherein the cancelation indication identifies the at least one interlace, the at least one set of resource blocks, or the at least one interlace and the at least one set of resource blocks. In some aspects, the cancelation indication may include a plurality of bits. In some aspects, the cancelation indication may include downlink control information (DCI) format 2_4. For example, the reservation cancelation circuitry <NUM>, shown and described above in connection with <FIG>, may generate the cancelation indication.

In some aspects, generating the cancelation indication may include: determining that the plurality of bits is fewer in number than the plurality of sets of resource blocks; and designating at least two sets of resource blocks of the plurality of sets of resource blocks by one bit of the plurality of bits after determining that the plurality of bits is fewer in number than the plurality of sets of resource blocks.

In some aspects, generating the cancelation indication may include: determining that the plurality of bits is greater in number than the plurality of sets of resource blocks; designating the plurality of sets of resource blocks by a first set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of sets of resource blocks; and designating the plurality of interlaces by a second set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of sets of resource blocks.

In some aspects, generating the cancelation indication may include: determining that the second set of the plurality of bits is fewer in number than the plurality of interlaces; and designating at least two interlaces of the plurality of interlaces by one bit of the second set of the plurality of bits after determining that the second set of the plurality of bits is fewer in number than the plurality of interlaces.

In some aspects, generating the cancelation indication may include: determining that the plurality of bits is fewer in number than the plurality of interlaces; and designating at least two interlaces of the plurality of interlaces by one bit of the plurality of bits after determining that the plurality of bits is fewer in number than the plurality of interlaces.

In some aspects, generating the cancelation indication may include: determining that the plurality of bits is greater in number than the plurality of interlaces; designating the plurality of interlaces by a first set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of interlaces; and designating the plurality of sets of resource blocks by a second set of the plurality of bits after determining that the plurality of bits is greater in number than the plurality of interlaces.

In some aspects, generating the cancelation indication may include: determining that the second set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; and designating at least two sets of resource blocks of the plurality of sets of resource blocks by one bit of the second set of the plurality of bits after determining that the second set of the plurality of bits is fewer in number than the plurality of sets of resource blocks.

In some aspects, generating the cancelation indication may include: designating the plurality of sets of resource blocks by a first set of the plurality of bits; and designating the plurality of interlaces by a second set of the plurality of bits.

In some aspects, generating the cancelation indication may include: determining that the first set of the plurality of bits is fewer in number than the plurality of sets of resource blocks; and designating at least two sets of resource blocks of the plurality of sets of resource blocks by one bit of the first set of the plurality of bits after determining that the first set of the plurality of bits is fewer in number than the plurality of sets of resource blocks.

At block <NUM>, the BS may transmit the cancelation indication to the first wireless communication device. For example, the communication and processing circuitry <NUM> and transceiver <NUM>, shown and described above in connection with <FIG>, may transmit the indication.

In some aspects, the process may further include: performing a bit mapping operation to designate, in the cancelation indication, at least one of: a canceled interlace, a canceled set of resource blocks, or any combination thereof. In some aspects, the bit mapping operation may use a formula that prioritizes the plurality of sets of resource blocks over the plurality of interlaces. In some aspects, the bit mapping operation may use a formula that prioritizes the plurality of interlaces over the plurality of sets of resource blocks. In some aspects, the bit mapping operation may use a formula that designates, in the cancelation indication, at least one canceled set of resource blocks and at least one canceled interlace.

Several aspects of a wireless communication network have been presented with reference to an example implementation.

The apparatus, devices, and/or components illustrated in <FIG> may be configured to perform one or more of the methods, features, or steps escribed herein.

Claim 1:
A method (<NUM>) of communication performed by a wireless communication device, the method comprising:
receiving (<NUM>), from a base station, a first indication of a scheduled uplink transmission for the wireless communication device on an unlicensed radio frequency spectrum, wherein the first indication specifies at least one scheduled interlace of a plurality of interlaces and at least one set of scheduled resource blocks of a plurality of sets of resource blocks;
receiving (<NUM>) a cancelation indication comprising a plurality of bits from the base station, wherein the cancelation indication identifies the at least one scheduled interlace, the at least one set of scheduled resource blocks, or the at least one scheduled interlace and the at least one set of scheduled resource blocks; and
canceling (<NUM>) the scheduled uplink transmission upon receiving the cancelation indication; characterized in that the method further comprises:
performing a bit mapping operation to identify, from the cancelation indication, at least one of: a canceled interlace, a canceled set of resource blocks, or any combination thereof, wherein the bit mapping operation uses a formula that prioritizes the plurality of sets of resource blocks over the plurality of interlaces by first allocating bits of the plurality of bits to the resource blocks and if there are remaining bits of the plurality of bits by allocating bits to interlaces.