Verification of control information for semi-persistent scheduling cancellation

Abstract

Control information such as downlink control information (DCI) can be used to indicate whether the DCI is for semi-persistent scheduling (SPS) cancellation. For example, a base station can transmit, to a user equipment (UE), a first DCI to trigger an SPS configuration of a plurality of SPS occasions. The base station can also determine to cancel one or more SPS occasions of the plurality of SPS occasions, and transmit a second DCI to trigger an SPS cancellation of the one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

Description

[0001] CLAIM OF PRIORITY

[0002] This application claims priority to and the benefit of U.S. Patent Application No. 17 / 507,630, filed October 21, 2021, and Provisional Patent Application No. 63 / 104,454, filed October 22, 2020, in the U.S. Patent and Trademark Office, the entire contents of which are incorporated herein by reference as if fully set forth below in their entirety and for all applicable purposes. TECHNICAL FIELD

[0003] The technology discussed below relates generally to wireless communication systems, and more particularly, to methods and apparatus for canceling one or more semi-persistent scheduling (SPS) occasions with control information in a wireless communication system. BACKGROUND

[0004] In a wireless communication system, a base station can schedule communication resources for a user equipment (UE) using dynamic scheduling or semi-persistent scheduling. Dynamic scheduling is a mechanism in which the base station schedules downlink (e.g., physical downlink shared channel (PDSCH)) or uplink (e.g., physical uplink shared channel (PUSCH)) data in each subframe, e.g., using downlink control information (DCI). Dynamic scheduling provides the network with flexibility to allocate communication resources to the UE at the cost of increased control signaling overhead to send scheduling information for each uplink or downlink transmission.

[0005] To reduce communication overhead, the base station can allocate communication resources on a semi-persistent basis. Semi-persistent scheduling (SPS) is a mechanism in which the base station schedules uplink / downlink transmissions using a semi-static control message (e.g., radio resource control (RRC) message). SPS can greatly reduce control signaling overhead because the base station does not need to send scheduling information (e.g., grant) for each uplink or downlink communication. In this disclosure, SPS and configured scheduling can be used interchangeably. SUMMARY

[0006] 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 present disclosure, and is intended neither to identify key or critical elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form that is brief, so as to provide a conceptual presentation of the same as a prelude to the more detailed description that is presented later.

[0007] Aspects of the disclosure provide methods, systems, devices, and apparatuses for indicating semi-persistent scheduling (SPS) cancellation of one or more SPS occasions with downlink control information (DCI). A base station can include a particular value of one or more of a redundancy version field, a modulation and coding scheme (MCS) field, and a frequency domain resource allocation (FDRA) field within a DCI to indicate SPS cancellation. A UE can receive the DCI and determine whether the DCI is for SPS cancellation based on the particular value in one or more of the redundancy version field, the MCS field, and the FDRA field to indicate SPS cancellation.

[0008] In one example, a method of wireless communication by a base station is disclosed. The method includes transmitting, to a user equipment (UE), a first DCI to trigger a SPS configuration of a plurality of SPS occasions; determining to cancel one or more SPS occasions of the plurality of SPS occasions; and transmitting a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

[0009] In another example, a base station for wireless communication is disclosed. The base station includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor can be configured to transmit, to a UE, a first DCI to trigger a SPS configuration of a plurality of SPS occasions; determine to cancel one or more SPS occasions of the plurality of SPS occasions; and transmit a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

[0010] In another example, a non-transitory processor-readable storage medium having instructions for a base station thereon can be disclosed. The instructions, when executed by processing circuitry, cause the processing circuitry to transmit, to a UE, a first DCI to trigger a SPS configuration of a plurality of SPS occasions; determine to cancel one or more SPS occasions of the plurality of SPS occasions; and transmit a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

[0011] In yet another example, a base station for wireless communication can be disclosed. The base station includes means for transmitting, to a UE, a first DCI to trigger a SPS configuration of a plurality of SPS occasions; means for determining to cancel one or more SPS occasions of the plurality of SPS occasions; and means for transmitting a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

[0012] In one example, a method of wireless communication by a user equipment (UE) can be disclosed. The method includes receiving a first DCI to trigger a SPS configuration of a plurality of SPS occasions; receiving a second DCI including at least a redundancy version field including one or more redundancy version values; determining whether the second DCI indicates a SPS cancellation of one or more SPS occasions of the plurality of SPS occasions based at least on the one or more redundancy version values; and refraining from monitoring the one or more SPS occasions based on determining that the second DCI indicates the SPS cancellation.

[0013] In another example, a UE for wireless communication can be disclosed. The UE includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor can be configured to receive a first DCI to trigger a SPS configuration of a plurality of SPS occasions; receive a second DCI including at least a redundancy version field including one or more redundancy version values; determine whether the second DCI indicates a SPS cancellation of one or more SPS occasions of the plurality of SPS occasions based at least on the one or more redundancy version values; and refrain from monitoring the one or more SPS occasions based on determining that the second DCI indicates the SPS cancellation.

[0014] In another example, a non-transitory processor-readable storage medium having instructions for a UE thereon can be disclosed. The instructions, when executed by processing circuitry, cause the processing circuitry to receive a first DCI to trigger a SPS configuration of a plurality of SPS occasions; receive a second DCI including at least a redundancy version field including one or more redundancy version values; determine whether the second DCI indicates a SPS cancellation of one or more SPS occasions of the plurality of SPS occasions based at least on the one or more redundancy version values; and refrain from monitoring the one or more SPS occasions based on determining that the second DCI indicates the SPS cancellation.

[0015] In yet another example, a UE for wireless communication can be disclosed. The base station includes means for receiving a first DCI triggering a SPS configuration for a plurality of SPS occasions; means for receiving a second DCI including at least a redundancy version field including one or more redundancy version values; means for determining, based at least on the one or more redundancy version values, whether the second DCI indicates a SPS cancellation for one or more SPS occasions of the plurality of SPS occasions; and means for refraining from monitoring the one or more SPS occasions based on the determination that the second DCI indicates the SPS cancellation.

[0016] These and other aspects will become more fully understood upon review of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numerals refer to like elements through the several figures. Other aspects, features, and embodiments will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary embodiments in conjunction with the accompanying figures. While features can be discussed relative to certain embodiments and figures below, all embodiments can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments can be discussed as having certain advantageous features, one or more of such features can also be used in accordance with the various embodiments discussed herein. In similar fashion, while exemplary embodiments can be discussed below as device, system or method embodiments, it should be understood that such exemplary embodiments can be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF DRAWINGS

[0017] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects.

[0018] Figure 2 is a diagram illustrating an example of a radio access network in accordance with some aspects.

[0019] Figure 3 is a block diagram illustrating a transmitting device and a receiving device that support multiple-input multiple-output (MIMO) communication in accordance with some aspects.

[0020] Figure 4 is a schematic illustration of the organization of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0021] Figure 5 is a diagram illustrating an example semi-persistent scheduling (SPS) configuration for wireless communication in accordance with some aspects.

[0022] Figure 6 is an example diagram illustrating an example SPS configuration for wireless communication utilizing SPS cancellation DCI in accordance with some aspects.

[0023] Figure 7is an example flow diagram illustrating determination of a type of DCI for SPS according to some aspects.

[0024] Figure 8 is an example flow diagram illustrating determination of a type of DCI for SPS according to some aspects.

[0025] Figure 9 is an example flow diagram illustrating determination of a type of DCI for SPS according to some aspects.

[0026] Figure 10 is an example diagram illustrating a bitmap for SPS cancellation in SPS cancellation DCI according to some aspects.

[0027] Figure 11 is a block diagram conceptually illustrating an example of a hardware implementation for a base station according to some aspects of the disclosure.

[0028] Figure 12 is a flow diagram illustrating an example process for wireless communication at a base station using SPS configuration according to some aspects.

[0029] Figure 13 is a block diagram conceptually illustrating an example of a hardware implementation for a user equipment according to some aspects of the disclosure.

[0030] Figure 14 is a flow diagram illustrating an example process for wireless communication at a user equipment using SPS configuration according to some aspects. DETAILED DESCRIPTION

[0031] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts being described.

[0032] 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 can come about in many different arrangements and scenarios. Innovations described herein can be implemented across many different types of platforms, devices, systems, form factors, and deployment scenarios. For example, embodiments and / or uses can come about in an integrated chip embodiment or other non-module-component based devices (e.g., an end-user device, a vehicle, a communication device, a computing device, industrial equipment, retail / purchasing equipment, medical equipment, AI-enabled devices, etc.). While some examples can or can not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations can come about. Implementations can range 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 physical settings, devices incorporating described aspects and features can also necessarily include additional components and features to realize and practice 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 antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc.). Innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying size, shape, and constitution.

[0033] A base station can transmit downlink control information (DCI) for SPS related tasks. For example, DCI for SPS activation can be used to activate monitoring of SPS occasions, DCI for SPS release can deactivate monitoring of SPS occasions, and DCI for SPS cancellation can cancel one or more SPS occasions. After verifying that DCI received at a user equipment (UE) is SPS DCI, the UE can also determine the type of SPS related DCI based on values in one or more fields provided in the DCI. According to some aspects of the disclosure, to indicate SPS cancellation, a base station can include a particular value of at least a redundancy version field to indicate SPS cancellation. For example, to indicate SPS cancellation, at least one of the values in the redundancy version field can be one. In some aspects, a base station can include a redundancy version field within DCI to indicate SPS cancellation and a particular value of a modulation and coding scheme (MCS) field. For example, to indicate SPS cancellation, at least one of the values in the redundancy version field can be one and at least one of the values in the MCS field can be zero. In some aspects, a base station can include a redundancy version field within DCI to indicate SPS cancellation, a MCS field, and a particular value of a frequency domain resource allocation (FDRA) field. For example, to indicate SPS cancellation, at least one of the values in the redundancy version field can be one, at least one of the values in the MCS field can be zero, and the values in the FDRA field can be set to invalid values. When a UE receives DCI, the UE can determine whether the DCI is for SPS cancellation based on the particular values in one or more of the redundancy version field, the MCS field, and the FDRA field to indicate SPS cancellation.

[0034] The various concepts presented throughout this disclosure can be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. Referring now to Figure 1 By way of illustrative example, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 can be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.

[0035] The RAN 104 can implement any suitable wireless communication technology or technologies to provide radio access for the UEs 106. As one example, the RAN 104 can operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) (often referred to as 5G). As another example, the RAN 104 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (often referred to as LTE). The 3GPP refers to this hybrid RAN as a Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of the present disclosure.

[0036] As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network that controls to and from UE wireless radio transmissions in one or more cells. Base stations can be variously known as base transceiver stations (BTS), radio base stations, radio transceivers, transceiver functions, basic service sets (BSS), extended service sets (ESS), access points (AP), Node Bs (NB), eNode Bs (eNB), gNode Bs (gNB), transmission and reception points (TRP), or some other suitable terminology. In some examples, base stations can include two or more TRPs, which can be co-located or non-co-located. Each TRP can communicate on the same or different carrier frequencies, within the same or different frequency bands, and / or at the same or different technologies.

[0037] A radio access network (RAN) 104 is also illustrated that enables wireless communication for multiple mobile apparatuses. A mobile apparatus can be referred to as user equipment (UE) in 3GPP standards, but can also be known by other names including mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communications device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable terminology. A UE can be an apparatus (e.g., mobile apparatus) that provides user access to network services.

[0038] Within the present document, a "mobile" device need not have a mobile capability, and can be static. The term mobile device or mobile equipment broadly refers to a large variety of devices and technologies. A UE can include several hardware structural components sized, shaped, and arranged to help with communication; such components can include an antenna, antenna array, RF chain, amplifier, one or more processors, etc. electrically coupled to one another. For example, some non-limiting examples of a mobile device include a mobile phone, a cellular phone, a smartphone, 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 large variety of embedded systems corresponding to the "Internet of Things" (IoT), among others. Also, a mobile device can be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, a

[0039] Wireless communication between a RAN 104 and a UE 106 can be described as utilizing an air interface. Transmissions by a base station, e.g., base station 108, to one or more UEs, e.g., UE 106, can be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108). Another way to describe this scenario is to use the

[0040] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all of the devices and equipment within its serving area or cell. In the present disclosure, a scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities as discussed infra. That is, for scheduled communication, a UE 106, which can be a scheduled entity, can utilize resources allocated by the scheduling entity 108.

[0041] The base station 108 is not the only entity that can function as a scheduling entity. That is, in some examples, a UE can function as a scheduling entity that schedules resources for one or more scheduled entities, e.g., one or more other UEs.

[0042] As Figure 1 illustrated, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly, the scheduling entity 108 is a node or device responsible for scheduling traffic, including the downlink traffic 112, in a wireless communication network and, in some examples, including uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114 including, but not limited to, scheduling information (e.g., a grant), synchronization or timing information, or other control information from another entity in the wireless communication network, such as the scheduling entity 108. The scheduled entity 106 can transmit uplink control information 118 to the network, e.g., the scheduling entity 108.

[0043] Generally, the base stations 108 can include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system. The backhaul 120 can provide a link between the base stations 108 and the core network 102. In addition, in some examples, the backhaul network can provide interconnection between respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

[0044] The core network 102 can be a part of the wireless communication system 100 and can be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 can be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 can be configured according to a 4G evolved packet core (EPC), or any other suitable standard or configuration.

[0045] Figure 2 is an illustration of a radio access network (RAN) 200 according to some aspects. In some examples, the RAN 200 can be implemented as a 5G NR network. In the illustrated example, the RAN 200 includes a plurality of network devices, such as a base station 104, which can be a gNB in some examples. The base station 104 can communicate with a plurality of UEs 106, such as the UEs 106 described above in connection with FIG. 1.Figure 1 The RAN 104 in FIG. 2 is similar to the RAN 104 in FIG. 1 and includes a number of base stations 210, 212, and 214 and a number of UEs 220, 222, and 228. A base station is an element of a RAN that Figure 2 The macro cells 202, 204, and 206 and the small cell 208 can include one or more sectors. A sector is a sub-area of a cell. All sectors within a cell are served by the same base station. The radio links within a sector can be identified by a single logical identification belonging to that sector. In a cell divided in sectors, multiple sectors within a cell can be formed by groups of antennas, each responsible for communication with UEs in a part of the cell.

[0046] In Figure 2 In the illustrated example, the cells 202, 204, and 126 can be referred to as macro cells because the base stations 210, 212, and 214 support cells with very large sizes. Further, a base station 218 in a small cell 208 (e.g., a macro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.) is shown that can overlap in coverage with one or more macro cells. In this example, the cell 208 can be referred to as a small cell because the base station 218 supports a cell with a relatively small size. The size of a cell can be designed according to the capacity and the coverage of the system and component constraints.

[0047] It will be appreciated that the radio access network 200 can include any number of wireless base stations and cells. Further, a relay node can be deployed to extend the size or coverage area of a given cell. The base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 210, 212, 214, and / or 218 can be the same as the base station / scheduling entity 108 described above and illustrated in FIG. 1, and the mobile apparatuses 220, 222, and 228 can be the same as the UE 104 described above and illustrated in FIG. 1. Figure 1

[0048] Figure 2 A mobile apparatus 220 is also included. The mobile apparatus 220 can be configured to function as a base station. That is, in some examples, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station such as the mobile apparatus 220.

[0049] ​Within the RAN 200, a cell can include UEs that can be in communication with one or more sectors of each cell. Moreover, each base station 210, 212, 214, 218, and 220 can be configured to provide an access point to a core network 102 (see Figure 1 ) for all the UEs in the respective cells. For example, UEs 222 and 224 can be in communication with base station 210; UEs 226 and 228 can be in communication with base station 212; UEs 230 and 232 can be in communication with base station 214 via RRHs 216; UE 234 can be in communication with base station 218; and UE 236 can be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can be the same as the UEs / scheduled entities 106 described above and illustrated in FIG. 1. Figure 1

[0050] In some examples, a mobile network node (e.g., mobile device 220) can be configured to operate as a UE. For example, mobile device 220 can operate within cell 202 by communicating with base station 210.

[0051] In another aspect of the RAN 200, sidelink signals can 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 226 and 228) can communicate with each other using peer to peer (P2P) or sidelink signals 227 without relaying that communication through a base station (e.g., base station 212). In another example, UE 238 is illustrated communicating with UEs 240 and 242. Here, the UE 238 can function as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can function as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In yet another example, a UE can 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 the mesh network example, UEs 240 and 242 can optionally communicate directly with one another in addition to communicating with the scheduling entity 238. 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 can communicate utilizing scheduled resources.

[0052] ​The air interface in the RAN 200 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another. 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. Half-duplex emulation is frequently implemented for wireless links through the use of time-division duplex (TDD). In TDD, transmissions in different directions are separated in time, e.g., one direction transmits in the uplink time slots and the other direction transmits in the downlink time slots. 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. The direction can change very rapidly, e.g., several times per slot. In a wireless link, a full-duplex channel generally relies on physical isolation of the transmitter and receiver, and suitable interference cancelation techniques. Full-duplex emulation is frequently implemented for wireless links through the use of frequency-division duplex (FDD) or space-division duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies, e.g., within paired spectrum. In SDD, transmissions in different directions are separated in time using space division multiplexing (SDM), e.g., within unpaired spectrum. In other examples, full-duplex communication can be implemented within unpaired spectrum, e.g., within a single carrier bandwidth, where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication can be referred to herein as sub-band full duplex (SBFD), also known as flexible duplex.

[0053] The air interface in the RAN 200 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another. 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. Half-duplex emulation is frequently implemented for wireless links through the use of time-division duplex (TDD). In TDD, transmissions in different directions are separated in time, e.g., one direction transmits in the uplink time slots and the other direction transmits in the downlink time slots. 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. The direction can change very rapidly, e.g., several times per slot. In a wireless link, a full-duplex channel generally relies on physical isolation of the transmitter and receiver, and suitable interference cancelation techniques. Full-duplex emulation is frequently implemented for wireless links through the use of frequency-division duplex (FDD) or space-division duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies, e.g., within paired spectrum. In SDD, transmissions in different directions are separated in time using space division multiplexing (SDM), e.g., within unpaired spectrum. In other examples, full-duplex communication can be implemented within unpaired spectrum, e.g., within a single carrier bandwidth, where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication can be referred to herein as sub-band full duplex (SBFD), also known as flexible duplex.

[0054] In the RAN 200, the ability for a UE to communicate while moving independently of its location is referred to as mobility. The various physical channels established for the UE to communicate with the radio access network are generally Figure 1

[0055] In various aspects of the disclosure, the RAN 200 can utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., 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 can monitor various parameters of signals from its serving and neighboring cells. Depending on the quality of these parameters, the UE can 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 of the serving cell by a given amount, the UE can initiate a handoff or handover from the serving cell to the neighboring (target) cell. For example, the UE 224, illustrated as a vehicle, although any suitable form of UE can be used, can move from the geographic area corresponding to its serving cell 202 to the geographic area corresponding to neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds that of its serving cell 202 by a given amount over a given amount of time, the UE 224 can send a reporting message to its serving base station 210 indicating this condition. In response, the UE 224 can receive a handover command, and the UE can undergo a handover to cell 206.

[0056] ​In networks configured for UL-based mobility, UL reference signals from each UE can be utilized by the network to select a serving cell for each UE. In some examples, the base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., unified Primary Synchronization Signal (PSS), unified Secondary Synchronization Signal (SSS), and unified Physical Broadcast Channel (PBCH)). The UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit uplink pilot or reference signals. The uplink pilot signals transmitted by a UE (e.g., UE 224) can be received by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200 concurrently. Each of the cells can measure a strength of the pilot signals, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) can determine a serving cell for the UE 224. As the UE 224 moves through the radio access network 200, the network can continue to monitor the uplink pilot signals transmitted by the UE 224. When the signal strength or quality of the pilot signals measured by a neighboring cell exceeds that of the signal strength or quality measured by the serving cell, the network 200 can handover the UE 224 from the serving cell to the neighboring cell, with or without informing the UE 224.

[0057] Although the synchronization signals transmitted by the base stations 210, 212, and 214 / 216 can be unified, the synchronization signals can not identify a particular cell, but rather can identify a zone of multiple cells operating on the same frequency and / or with the same timing. The use of zones in 5G networks or other new generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, as the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0058] In some aspects of the disclosure, a scheduling entity and / or a scheduled entity can be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 3 An example of a wireless communication system 300 that supports MIMO is illustrated. In a MIMO system, a transmitter 302 includes multiple transmit antennas 304 (e.g., N transmit antennas), and a receiver 306 includes multiple receive antennas 308 (e.g., M receive antennas). Thus, there are N x M signal paths 310 from the transmit antennas 304 to the receive antennas 308. Each of the transmitter 302 and the receiver 306 can be implemented within, for example, a scheduling entity 108, a scheduled entity 106, or any other suitable wireless communication device.

[0059] The use of such multiple antenna technology enables the wireless communication system to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to transmit different streams of data, also referred to as layers, from a single UE to the base station on the same time-frequency resource. The data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, which is referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by a weight and phase shifting it) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enables each of the UE(s) to recover the one or more data streams destined for that UE. On the uplink, each UE transmits a spatially precoded stream, which enables the base station to identify the source of each spatially precoded stream.

[0060] The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of the MIMO system 300 is limited by the number of transmit antennas 304 or receive antennas 308, whichever is smaller. In addition, channel conditions at the UE, as well as other considerations such as available resources at the base station, can also impact the transmission rank. For example, the rank (and thus, the number of data streams) assigned to a particular UE on the downlink can be determined based on a rank indicator (RI) transmitted from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) and the measured signal-to-interference-and-noise ratio (SINR) on each of the receive antennas. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI, along with resource information (e.g., available resources and the amount of data to be scheduled for the UE), to assign a transmission rank to the UE.

[0061] In a time division duplex (TDD) system, the UL and DL are reciprocal in that they each use different time slots of the same frequency bandwidth. Thus, in a TDD system, the base station can assign a rank for DL MIMO transmission based on UL SINR measurements (e.g., based on sounding reference signals (SRS) or other pilot signals transmitted from the UE). Based on the assigned rank, the base station can then transmit a demodulation reference signal (DMRS) and / or a channel state information reference signal (CSI-RS) with a separate C-RS sequence for each layer to provide multi-layer channel estimation. From the CSI-RS, the UE can measure the channel quality for each layer and resource block and feed back an RI and a channel quality indicator (CQI) that indicates a modulation and coding scheme (MCS) for transmission to the UE for updating the rank and allocating REs for future downlink transmissions.

[0062] In the simplest case, such as Figure 3 As shown, in a 2x2 MIMO antenna configuration, rank-2 spatial multiplexing transmission sends a data stream from each transmit antenna 304. Each data stream arrives at each receive antenna 308 along a different signal path 310. The receiver 306 can then reconstruct the data stream using the received signals from each receive antenna 308.

[0063] Reference Figure 4 The example figure 400 schematically illustrates OFDM waveforms to describe various aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to DFT-s-OFDMA waveforms in essentially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can be applied to DFT-s-OFDMA waveforms and other waveforms.

[0064] Within this disclosure, a frame refers to a 10ms duration used for wireless transmission, and each frame consists of 10 subframes, each 1ms in length. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Reference is now made to... Figure 4 The diagram illustrates an expanded view of an exemplary DL subframe 402, showing an OFDM resource grid 404. However, as those skilled in the art will readily understand, the PHY transport structure for any particular application can differ from the example described herein, depending on any number of factors. Here, the horizontal direction represents time in OFDM symbols; and the vertical direction represents frequency in subcarriers or tones.

[0065] Resource grid 404 can be used to schematically represent the time-frequency resources available for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding number of resource grids 404 may be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. An RE is 1 subcarrier × 1 symbol, which is the smallest discrete part in the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used 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 as a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, independent of the number of parameter sets used. In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 408) corresponds exactly to a single communication direction (either transmitting or receiving for a given device).

[0066] UEs typically utilize only a subset of resource grid 404. An RB can be the smallest unit of resource that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the more advanced the modulation scheme selected for the air interface, the higher the UE's data rate.

[0067] In this illustration, RB 408 is shown as occupying a bandwidth less than the entire bandwidth of subframe 402, with some subcarriers shown above and below RB 408. In a given implementation, subframe 402 can have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying a duration less than the entire duration of subframe 402, although this is merely one possible example.

[0068] Each subframe 402 (e.g., a 1ms subframe) can consist of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, time slots can be defined by a specified number of OFDM symbols having a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-time slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). These mini-time slots may be transmitted in some cases, consuming resources scheduled for ongoing time slot transmissions for the same or different UEs.

[0069] An expanded diagram of time slot 410 illustrates time slot 410 including control area 412 and data area 414. Generally, control area 412 may carry control channels (e.g., Physical Downlink Control Channel (PDCCH)), and data area 414 may carry data channels (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure shown in the diagram is merely exemplary, and different time slot structures can be utilized and may include one or more of each of the control area and the data area.

[0070] Despite Figure 4 While not illustrated, the various REs 406 within RB 408 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within RB 408 can also carry pilot or reference signals. These pilot or reference signals can provide information for the receiving equipment to perform channel estimation for the corresponding channel, which can enable coherent demodulation / detection of the control and / or data channels within RB 408.

[0071] In DL transmission, a transmitting device (e.g., scheduling entity 108) may allocate one or more REs 406 (e.g., within control area 412) to one or more scheduled entities 106 to carry DL control information 114. This DL control information 114 includes one or more DL control channels that typically carry information originating from higher layers, such as the Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), etc. Furthermore, DL REs may be allocated to carry DL physical signals that do not typically carry information originating from higher layers. These DL physical signals may include a Primary Synchronization Signal (PSS); a Secondary Synchronization Signal (SSS); a Demodulation Reference Signal (DMRS); a Phase Tracking Reference Signal (PT-RS); a Channel State Information Reference Signal (CSI-RS), etc.

[0072] The synchronization signals PSS and SSS (collectively referred to as SSs), and in some examples, the PBCH, can be transmitted in an SS block that includes 4 consecutive OFDM symbols numbered from 0 to 3 in increasing order via time index. In the frequency domain, an SS block can extend over 240 consecutive subcarriers, numbered from 0 to 239 in increasing order via frequency index. Of course, the present disclosure is not limited to this specific SS block configuration. Other non-limiting examples can utilize more or less than two synchronization signals; can include one or more supplemental channels in addition to the PBCH; can omit the PBCH; and / or can utilize non-consecutive symbols of an SS block, within the scope of the present disclosure. The PDCCH can carry downlink control information (DCI) intended for one or more UEs in the cell. This can include, but is not limited to, power control commands, scheduling information, grants and / or an allocation of REs for the transmission of DL and UL communications.

[0073] In UL transmissions, the transmitting device (e.g., scheduled entity 106) can utilize one or more REs 406 to carry UL control information (UCI) 118. UCI can originate from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc., to the scheduling entity 108. Moreover, UL REs can carry UL physical signals that generally do not carry information originating from higher layers, such as a demodulation reference signal (DMRS), a phase-tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 can include a scheduling request (SR), i.e., a request to the scheduling entity 108 to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel 118, the scheduling entity 108 can transmit downlink control information 114, which can schedule resources for uplink packet transmissions.

[0074] UL control information can also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgment (ACK) or negative acknowledgment (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technique well-known in the art, wherein the integrity of packet transmissions can be checked at the receiving side for accuracy, e.g., using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK can be transmitted, whereas if not, a NACK can be transmitted. In response to a NACK, the transmitting device can issue a HARQ retransmission, which can implement chase combining, incremental redundancy, etc.

[0075] In addition to control information, one or more REs 406 (e.g., within the data region 414) can be allocated for use by user data or traffic data. Such traffic can be carried in one or more traffic channels, such as, for DL transmissions, a physical downlink shared channel (PDSCH); or for UL transmissions, a physical uplink shared channel (PUSCH).

[0076] To enable initial access to a cell by a UE, a RAN can provide system information (SI) characterizing the cell. This system information can be provided with minimum system information (MSI) and other system information (OSI). The MSI can be periodically broadcast in a cell to provide the most basic information required for initial cell access, as well as for acquiring any OSI that can be periodically broadcast or issued on-demand. In some examples, the MSI can be provided over two different downlink channels. For example, a PBCH can carry a master information block (MIB), and a PDSCH can carry a system information block type 1 (SIB1). In the art, the SIB1 can be referred to as remaining minimum system information (RMSI).

[0077] The OSI can include any SI that is not broadcast in the MSI. In some examples, a PDSCH can carry multiple SIBs, not limited to the SIB1 discussed above. Here, the OSI can be provided in these SIBs, e.g., SIB2 and those above.

[0078] The channels or carriers described above and illustrated in FIGS. 1 through 7 do not necessarily all must be utilized in a telecommunications system, and other channels or carriers can also be utilized in addition to or in lieu of those illustrated, such as other traffic, control, and feedback channels. Figure 1 and Figure 4 The channels or carriers described above and illustrated in FIGS. 1 through 7 do not necessarily all must be utilized in a telecommunications system, and other channels or carriers can also be utilized in addition to or in lieu of those illustrated, such as other traffic, control, and feedback channels.

[0079] These physical channels described above are typically multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry information between the network entity and the scheduled entity in the form of transport blocks (TBs). Transport block sizes (TBSs), which can correspond to the number of bits of information, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0080] Scheduling is the process of allocating communication resources (e.g., time, frequency, and spatial resources) in a wireless communication system 100. A scheduling entity 108 (e.g., a base station, such as a gNB or eNB) can use a dynamic scheduling method or a semi-persistent scheduling (SPS) method to schedule communication resources. In dynamic scheduling, the scheduling entity can use DCI to schedule resources for each data communication (e.g., PDSCH / PUSCH, and PUCCH). To reduce communication overhead, the scheduling entity can use SPS to schedule resources in a semi-static or semi-persistent manner. For example, using SPS, the scheduling entity can use one or more radio resource control (RRC) messages (e.g., SPS-Config) to configure one or more SPS occasions. Each SPS occasion can include downlink (DL) resources and / or uplink (UL) resources. Using SPS, the scheduling entity transmits a single trigger signal (e.g., DCI) within one or more SPS occasions configured in the SPS configuration.

[0081] Figure 5 is an example diagram 500 illustrating example SPS configurations for wireless communication according to some aspects. A base station (e.g., scheduling entity 108) can use SPS signaling 502 to transmit one or more SPS configurations to a UE (e.g., UE 106). In one example, the SPS signaling 502 can be an RRC message configuring one or more SPS configurations. Each SPS configuration can be identifiable by a corresponding index value (e.g., index 0 for SPS configuration 0, index 1 for SPS configuration 1). In some aspects, the base station can use different indices for each SPS configuration.

[0082] In some aspects, the same index can be used for a data SPS configuration of downlink data and a measurement SPS configuration of channel / interference measurements. The base station can use RRC and / or MAC CE signaling to configure both types of SPS configurations. In addition to the SPS configuration index, the base station can include a field in the DCI to indicate whether the index signals a data SPS configuration or a measurement SPS configuration. Thus, the UE can determine whether a downlink data SPS configuration or a measurement SPS configuration is triggered by the index and use the corresponding periodicity and feedback timing.

[0083] In some aspects, the RRC message can include a different index to identify each configured SPS configuration. The SPS configuration can schedule and allocate communication resources (e.g., time, frequency, and spatial resources) to SPS occasions with a predetermined periodicity, P. The base station can configure multiple SPS configurations for downlink data and / or channel measurements. From the index, the UE can identify the triggered SPS configuration and use the corresponding periodicity and feedback timing. In some aspects, the SPS configuration can include both downlink data and channel measurement resources across different SPS occasions. In some aspects, the SPS configuration can also allocate communication resources for transmitting HARQ feedback, such as HARQ ACK or HARQ NACK.

[0084] After the SPS configuration(s) are configured, the base station can transmit an activation DCI 504 (e.g., in a PDCCH) to activate the configured SPS configuration(s) at the UE. Prior to receiving the activation DCI 504, the SPS occasions can not be monitored by the UE. The activation DCI 504 can activate at least one SPS configuration, for example, by indicating the index of the SPS configuration to be activated. In some examples, the activation DCI 504 can include one or more indices to trigger one or more corresponding SPS configurations. In some examples, the activation DCI 504 can also indicate the index of the SPS configuration to be deactivated or reactivated. In some aspects, the activation DCI 504 can also indicate transmission parameters, such as MCS, resource allocation, antenna ports for SPS transmission, DMRS configuration, beamforming, precoding, etc.

[0085] In some aspects, the base station can configure a set of bitmaps for triggering a combined SPS configuration and use the DCI to select one of the bitmaps to trigger the desired SPS occasion corresponding to the selected bitmap. The base station can use RRC or MAC CE to communicate the set of bitmaps to the UE to reduce the DCI payload. In some aspects, the bitmap can be part of the SPS configuration. In this case, the base station can use a bitmap index in the DCI to signal the selected bitmap.

[0086] The base station can use the activation DCI 504 to configure one or more transmission parameters, for example, MCS, resource allocation, antenna ports for SPS transmission, DMRS configuration, beamforming, precoding, etc. For each activated SPS configuration, the UE can use a PUCCH occasion for transmitting uplink control information (UCI), which can include HARQ feedback, scheduling request (SR), and channel report, which can include channel characteristic measurements and / or interference measurements.

[0087] The base station can use the above SPS configuration, etc. to efficiently schedule frequency or periodic channel and interference measurements with low signaling overhead. Thus, the base station can have more up-to-date information about channel characteristics from the UE’s perspective. UE measurements can help the base station in channel precoding, interference / noise / channel estimation and prediction, and MCS and transmission configuration selection. The UE can also benefit from having up-to-date information about channel characteristics, which can enhance noise / interference / channel estimation over time. Having up-to-date channel and interference information also enhances data decoding and can result in lower error rates and higher data rates.

[0088] In Figure 5 In the example of FIG. 5, the UE monitors SPS occasions, such as SPS occasions 506 and 508, after the activation DCI 504 activates the particular SPS configuration. The SPS occasions 506 and 508 have a periodicity P (e.g., based on the particular SPS configuration) between consecutive SPS occasions. After the SPS occasion 508, the base station transmits a reactivation DCI 510 to reactivate the configured SPS configuration(s) at the UE. In some examples, the reactivation DCI 510 can reactivate the configured SPS configuration by reconfiguring transmission parameters, such as MCS, resource allocation, antenna ports for SPS transmissions, DMRS configuration, beamforming, precoding, etc. After receiving the reactivation DCI 510, the UE can monitor subsequent SPS occasions, such as SPS occasions 512, 514, and 516, according to the parameters indicated in the reactivation DCI 510. For example, the SPS occasions 512, 514, and 516 can be monitored according to the reconfigured transmission parameters using the reactivation DCI 510.

[0089] When the UE receives the SPS release DCI 518, the UE deactivates the configured SPS configuration. For example, when the UE receives the SPS release DCI 518, the UE stops monitoring subsequent SPS occasions.

[0090] In some cases, after an SPS configuration is activated, the base station can transmit an SPS cancel DCI to cause the base station to cancel one or more subsequent SPS occasions. The SPS cancel DCI can indicate a number of SPS occasions to cancel. When the SPS cancel DCI is received, the UE can skip monitoring the SPS occasions canceled by the SPS cancel DCI. For example, if the SPS cancel DCI indicates that one SPS occasion is canceled, the UE can skip monitoring one subsequent SPS occasion canceled by the SPS cancel DCI. In some aspects, the base station can transmit the SPS cancel DCI to the UE when the base station does not have data to transmit to the UE. The SPS cancel DCI is different from the SPS release DCI in that the SPS cancel DCI indicates a defined number of SPS occasions to skip monitoring, while the SPS release DCI deactivates monitoring of any subsequent SPS occasions indefinitely until another activation DCI is received. For example, when the UE receives the SPS cancel DCI, the UE can skip monitoring one or more subsequent SPS occasions canceled by the SPS cancel DCI and then resume monitoring the SPS occasions.

[0091] Figure 6 is an example diagram 600 illustrating example SPS configurations for wireless communications with SPS cancel DCI, according to some aspects. A base station 108 (e.g., a scheduling entity 108) can transmit one or more SPS configurations to a UE (e.g., a UE 106) using SPS signaling 602. Details of the SPS configurations and various types of DCI, including activation DCI, reactivation DCI, and SPS release DCI, are omitted for brevity, as they have been discussed above with reference to FIGs. 1-5. Figure 5 After the SPS configuration(s) are configured, the base station can transmit an activation DCI 604 (e.g., in a PDCCH) to activate the configured SPS configuration(s) at the UE. Prior to receiving the activation DCI 604, the SPS occasions can not be monitored by the UE. The activation DCI 604 can activate at least one SPS configuration, e.g., by indicating an index of the SPS configuration that is activated.

[0092] In Figure 6In some aspects, after the activation DCI 604 activates a particular SPS configuration, the UE monitors for SPS occasions, such as SPS occasions 606 and 608, which have a periodicity P between consecutive SPS occasions. After SPS occasion 608, the base station transmits a reactivation DCI 610 to reactivate the configured SPS configuration(s) at the UE. In some examples, the reactivation DCI 610 can reactivate the configured SPS configuration by reconfiguring transmission parameters, such as MCS, resource allocation, antenna ports for SPS transmissions, DMRS configuration, beamforming, precoding, etc. After receiving the reactivation DCI 610, the UE can monitor for subsequent SPS occasions, such as SPS occasions 612 and 618, according to the parameters indicated in the reactivation DCI 610. For example, SPS occasions 612 and 618 can be monitored according to the reconfigured transmission parameters using the reactivation DCI 610.

[0093] In Figure 6 In some aspects, after SPS occasion 612, the base station transmits an SPS cancellation DCI 614 to cancel one or more SPS occasions that occur after the SPS cancellation DCI 614 is received by the UE. The SPS cancellation DCI can indicate a number of SPS occasions to cancel. In Figure 6 In the example shown, the SPS cancellation DCI 614 indicates to cancel one subsequent SPS occasion, and thus the UE does not monitor for the SPS occasion at allocation portion 616 (e.g., configured by the reactivation DCI 610). After skipping allocation portion 616 according to the SPS cancellation DCI 614, the UE can resume monitoring for subsequent SPS occasions, such as SPS occasion 618.

[0094] When the UE receives the SPS release DCI 620, the UE deactivates the configured SPS configuration. For example, when the UE receives the SPS release DCI 620, the UE stops monitoring for subsequent SPS occasions.

[0095] In some aspects, when the UE receives a DCI, the UE can determine whether the DCI is for SPS activation, SPS reactivation, or SPS release, or is another type of DCI for dynamically rescheduling a PDSCH transmission. A two-step procedure can be implemented for the UE to verify whether the DCI is for SPS, and then determine the type of DCI for SPS (e.g., by determining whether the DCI is for SPS activation, SPS reactivation, or SPS release).

[0096] As the first step of the two-step procedure, the UE can verify that the DCI is for SPS if the following four conditions are met, where the four conditions are: (1) the CRC for the corresponding DCI format is scrambled with the CS-RNTI provided by the cs-RNTI field, (2) the new data indicator field for the enabled transport block in the DCI format is set to 0, (3) the downlink feedback information (DFI) flag field (if present) in the DCI format is set to 0, and (4) if the verification is for scheduling activation, and if the PDSCH-to-HARQ feedback timing indicator field in the DCI format is present, the PDSCH-to-HARQ feedback timing indicator field does not provide an inapplicable value from the dl-DataToUL-ACK field, where the dl-DataToUL-ACK field can include a list of timings for a given PDSCH to DL ACK.

[0097] If the first step verifies that the DCI is for SPS, the UE can perform the second step of the two-step procedure to determine the type of DCI for SPS. In some aspects, if the UE detects all 0s in the redundancy version (RV) field within the DCI, the UE can determine that the DCI is for SPS activation or for SPS reactivation. Thus, to generate a SPS activation DCI or a SPS reactivation DCI, the base station can set the RV field of the DCI to include all 0s. For example, if the SPS configuration has not been activated, and the RV field of the DCI includes all 0s, the UE can determine that the DCI is for SPS activation. For example, if the SPS configuration has already been activated, and the RV field of the DCI includes all 0s, the UE can determine that the DCI is for SPS reactivation. Table 1 below illustrates the conditions for determining that the DCI is for SPS activation or for SPS reactivation.

[0098]

[0099] Table 1: Conditions for SPS Activation DCI or SPS Reactivation DCI

[0100] In some aspects, if the UE detects that the RV field includes all 0s, the MCS field includes all 1s, and an invalid frequency domain resource allocation (FDRA) value is used, the UE can determine that the DCI is for SPS release. In an aspect, the UE can determine that an invalid FDRA value is used if the FDRA value is set to all 0s for FDRA type 0 or for dynamic switching between FDRA type 0 and FDRA type 1, or if the FDRA value is set to all 1s for FDRA type 1. Otherwise, the UE can determine that the FDRA value is a valid value. Table 1 below illustrates the conditions for determining that the DCI is for SPS release.

[0101]

[0102] Table 2: Conditions for SPS release DCI

[0103] In the past, no procedure has been established to determine that a DCI for SPS is for SPS cancellation. Thus, according to some aspects of the present disclosure, a UE can determine whether a DCI is for SPS cancellation based at least on an RV field in the DCI. In an aspect, the UE can determine whether the DCI is for SPS cancellation as a second step of a two-step procedure after performing a first step of verifying that the DCI is for SPS. For example, the UE can determine that the DCI is for SPS cancellation based on a particular value of one or more of an RV field, an MCS field, and an FDRA field. Thus, for example, one or more of the RV field, the MCS field, and the FDRA field can be repurposed to indicate SPS cancellation of the DCI. The UE can be Figure 1 、 Figure 2 and / or Figure 3 the UE or scheduled entity illustrated in any one or more of

[0104] According to a first approach, a base station can set an RV field in a DCI to indicate SPS cancellation. The base station can be Figure 1 、 Figure 2 and / or Figure 3 the base station or scheduling entity illustrated in any one or more of In an aspect, to indicate SPS cancellation, the RV field can be set to a value other than all 0s. For example, to indicate SPS cancellation, the RV field can be set to include one or more 1s (e.g., all 1s). When a UE determines that a DCI is for SPS, and further determines that the RV field includes a value other than all 0s (e.g., all values are 1s), then the UE can determine that the DCI for SPS is an SPS cancellation DCI. Table 3.1 below illustrates conditions for example values of an RV field to indicate SPS cancellation according to the first approach.

[0105]

[0106] Table 3.1: Conditions for SPS cancellation DCI according to the first approach

[0107] Figure 7 is an example flow diagram 700 illustrating determination of a type of DCI for SPS according to some aspects. The features in flow diagram 700 can be performed as part of a second step of a two-step procedure to determine a type of DCI for SPS. Further, the features in flow diagram 700 can be based on the conditions provided in Table 3.1.

[0108] At 702, the UE can determine whether the RV field is set to all 0s. If the UE determines at 702 that the RV field is set to all 0s, the UE can determine at 704 whether the FDRA value is a valid value. For example, if the FDRA value is set to all 0s for FDRA Type 0 or for dynamic switching between FDRA Type 0 and FDRA Type 1, or if the FDRA value is set to all 1s for FDRA Type 1, the UE can determine that the FDRA value is invalid. Otherwise, the UE can determine that the FDRA value is a valid value. If the UE determines at 704 that the FDRA value is a valid value, the UE can determine that the DCI is for SPS activation or SPS reactivation. If the UE determines at 704 that the FDRA value is an invalid value, the UE can determine at 706 whether the MCS field is set to all 0s. If the UE determines at 706 that the MCS field is set to all 0s, the UE can determine that the DCI is for SPS release. If the UE determines at 706 that the MCS field is not set to all 0s, the UE can determine that an error has occurred with the invalid DCI detection result.

[0109] In Figure 7 , if the UE determines at 702 that the RV field is not set to all 0s, the UE can determine that the DCI is for SPS cancellation.

[0110] According to a second approach, the base station can set the RV field and the MCS field in the DCI to indicate SPS cancellation. In an aspect, to indicate SPS cancellation, the RV field can be set to a value other than all 0s, and the MCS setting can be set to a value other than all 1s. For example, to indicate SPS cancellation, the RV field can be set to all 1s, and the MCS setting can be set to all 0s. When the UE determines that the DCI is for SPS, and further determines that the RV field includes a value other than all 0s (e.g., all values are 1), and the MCS field includes a value other than all 1s (e.g., all values are 0), the UE can determine that the DCI for SPS is an SPS cancellation DCI. Table 3.2 below illustrates conditions for example values of the RV field and the MCS field to indicate SPS cancellation according to the second approach.

[0111]

[0112] Table 3.2: Conditions for SPS cancellation DCI according to the second approach

[0113] Figure 8 is an example flow chart 800 illustrating determination of the type of DCI for SPS according to some aspects. The features in the flow chart 800 can be performed as part of the second step of the two-step procedure for determining the type of DCI for SPS. Further, the features in the flow chart 800 can be based on the conditions provided in Table 3.2.

[0114] At 802, the UE can determine whether the RV field is set to all Os. If the UE determines at 802 that the RV field is set to all Os, the UE can determine at 804 whether the FDRA value is a valid value. For example, if the FDRA value is set to all Os for FDRA Type 0 or for dynamic switching between FDRA Type 0 and FDRA Type 1, or if the FDRA value is set to all Is for FDRA Type 1, the UE can determine that the FDRA value is invalid. Otherwise, the UE can determine that the FDRA value is a valid value. If the UE determines at 804 that the FDRA value is a valid value, the UE can determine that the DCI is for SPS activation or SPS reactivation. If the UE determines at 804 that the FDRA value is an invalid value, the UE can determine at 806 that the MCS field is set to all Os. If the UE determines at 806 that the MCS field is set to all Os, the UE can determine that the DCI is for SPS release. If the UE determines at 806 that the MCS field is not set to all Os, the UE can determine that an error with invalid DCI detection has occurred.

[0115] If the UE determines at 802 that the RV field is not set to all Os, the UE can determine at 808 whether the MCS field is set to all Os. If the UE determines at 808 that the MCS field is set to all Os, the UE can determine that the DCI is for SPS cancellation. If the UE determines at 808 that the MCS field is not set to all Os, the UE can determine that an error with invalid DCI detection has occurred.

[0116] According to a third approach, the base station can set the RV field, the MCS field, and the FDRS field in the DCI to indicate SPS cancellation. In an aspect, to indicate SPS cancellation, the RV field can be set to a value other than all Os, the MCS setting can be set to a value other than all Is, and the FDRS field can be set to an invalid value. For example, to indicate SPS cancellation, the RV field can be set to all Is, the MCS field can be set to all Os, and the FDRA field can be set to all Os for FDRA Type 0 or for dynamic switching between FDRA Type 0 and FDRA Type 1, or the FDRA value can be set to all Is for FDRA Type 1. When the UE determines that the DCI is for SPS, and further determines that the RV field includes a value other than all Os (e.g., all values are 1), the MCS field includes a value other than all Is (e.g., all values are 0), and the FDRS field is set to an invalid value, the UE can determine that the DCI for SPS is an SPS cancellation DCI. Table 3.3 below illustrates conditions for example values of the RV field and the MCS field to indicate SPS cancellation according to the third approach.

[0117]

[0118]

[0119] Table 3.3: Conditions for SPS cancellation DCI according to the third approach

[0120] Figure 9 is an example flowchart 900 illustrating determination of the type of DCI for SPS according to some aspects. The features in flowchart 900 can be performed as part of the second step of the two-step procedure for determining the type of DCI for SPS. Further, the features in flowchart 900 can be based on the conditions provided in Table 3.3.

[0121] At 902, the UE can determine whether the FDRA value is a valid value. For example, if the FDRA value is set to all 0s for FDRA type 0 or for dynamic switching between FDRA type 0 and FDRA type 1, or if the FDRA value is set to all 1s for FDRA type 1, the UE can determine that the FDRA value is invalid. Otherwise, the UE can determine that the FDRA value is a valid value. If the UE determines at 902 that the FDRA value is a valid value, the UE can determine at 904 whether the RV field is set to all 0s. If the RV field is set to all 0s, the UE can determine that the DCI is for SPS activation or for SPS reactivation. If the RV field is not set to all 0s, the UE can determine that an error with invalid DCI detection result has occurred.

[0122] If the UE determines at 902 that the FDRA value is invalid, the UE can determine at 906 whether the RV field is set to all 0s and the MCS is set to all 0s. If the RV field is set to all 0s and the MCS is set to all 0s, the UE can determine that the DCI is for SPS release.

[0123] If the RV field is not set to all 0s and / or the MCS field is not set to all 0s, the UE can determine at 908 whether the RV field is set to all 1s and the MCS field is set to all 0s. At 908, if the RV field is set to all 1s and the MCS field is set to all 0s, the UE can determine that the DCI is for SPS cancellation. At 908, if the RV field is not set to all 1s and / or the MCS field is not set to all 0s, the UE can determine that an error with invalid DCI detection result has occurred.

[0124] According to some aspects, for example, after verifying that the DCI is a valid SPS cancellation DCI, the UE can also check the bitmap to determine which SPS occasion is cancelled by the SPS cancellation DCI indication. In an aspect, the SPS cancellation DCI can include a bitmap having X number of bits, where X is an integer. The value of X can be configured via a RRC message. The value of the xth bit in the bitmap can indicate that the xth SPS occasion in the cancellation window is cancelled. A value of 1 for the xth bit can indicate that the xth SPS occasion in the cancellation window is cancelled, and a value of 0 for the xth bit can indicate that the xth SPS occasion in the cancellation window is not cancelled. In an aspect, the length of the cancellation window can be implicitly derived based on the number of bits in the bitmap in the SPS cancellation DCI. For example, if the bitmap has X bits, the UE can determine that the length of the cancellation window covers X SPS occasions.

[0125] Figure 10 is an example diagram 1000 illustrating a bitmap for SPS cancellation in an SPS cancellation DCI according to some aspects. Details of SPS configurations and various types of DCIs, including activation DCI, reactivation DCI, and SPS release DCI, are omitted for brevity as they have been discussed above with reference to Figure 5 After the SPS configuration(s) are configured, the base station can transmit an activation DCI 1002 (e.g., in a PDCCH) to activate the configured SPS configuration(s) at the UE. Prior to receiving the activation DCI 1002, the SPS occasions can not be monitored by the UE. The activation DCI 1002 can activate at least one SPS configuration, for example, by indicating the index of the SPS configuration to be activated.

[0126] In Figure 10 After the activation DCI 1002 activates a particular SPS configuration, the UE monitors SPS occasions, such as SPS occasions 1004, 1006, and 1010, which have a periodicity P (e.g., according to the particular SPS configuration). In Figure 10 After the SPS occasion 1006, the base station transmits an SPS cancellation DCI 1008 to cancel one or more SPS occasions after the SPS cancellation DCI 1008 is received by the UE. The SPS cancellation DCI can indicate the number of SPS occasions to be cancelled. In Figure 10In the example of FIG. 10, the SPS cancellation DCI 1008 includes a bitmap 1022 that indicates which SPS occasions are cancelled. In the example of FIG. 10, the bitmap 1022 includes four bits, which indicate four values including 1, 0, 0, and 1, respectively. The SPS cancellation DCI 1008 further includes a SPS cancellation window 1032, which indicates the four subsequent SPS occasions that are cancelled. In the example of FIG. 10, the SPS cancellation window 1032 starts at a delay 1042 after the SPS cancellation DCI 1008 is received. The delay 1042 can be configured by the network via RRC or can be indicated in the SPS cancellation DCI 1008. The length of the SPS cancellation window 1032 can be implicitly derived based on the number of bits in the bitmap 1022. For example, because the bitmap 1022 has four bits, the UE can determine that the length of the cancellation window is four SPS occasions.

[0127] In the example of FIG. 10, the SPS cancellation DCI 1008 includes a bitmap 1022 that indicates which SPS occasions are cancelled. In the example of FIG. 10, the bitmap 1022 includes four bits, which indicate four values including 1, 0, 0, and 1, respectively. The SPS cancellation DCI 1008 further includes a SPS cancellation window 1032, which indicates the four subsequent SPS occasions that are cancelled. In the example of FIG. 10, the SPS cancellation window 1032 starts at a delay 1042 after the SPS cancellation DCI 1008 is received. The delay 1042 can be configured by the network via RRC or can be indicated in the SPS cancellation DCI 1008. The length of the SPS cancellation window 1032 can be implicitly derived based on the number of bits in the bitmap 1022. For example, because the bitmap 1022 has four bits, the UE can determine that the length of the cancellation window is four SPS occasions. Figure 10 Figure 10 In the example of FIG. 10, the SPS cancellation DCI 1008 includes a bitmap 1022 that indicates which SPS occasions are cancelled. In the example of FIG. 10, the bitmap 1022 includes four bits, which indicate four values including 1, 0, 0, and 1, respectively. The SPS cancellation DCI 1008 further includes a SPS cancellation window 1032, which indicates the four subsequent SPS occasions that are cancelled. In the example of FIG. 10, the SPS cancellation window 1032 starts at a delay 1042 after the SPS cancellation DCI 1008 is received. The delay 1042 can be configured by the network via RRC or can be indicated in the SPS cancellation DCI 1008. The length of the SPS cancellation window 1032 can be implicitly derived based on the number of bits in the bitmap 1022. For example, because the bitmap 1022 has four bits, the UE can determine that the length of the cancellation window is four SPS occasions.

[0128] In some aspects, the base station can include the bitmap for SPS cancellation in a cancellation bitmap field defined in the SPS cancellation DCI. The cancellation bitmap field can be a newly added field in the SPS cancellation DCI. In an aspect, the SPS cancellation DCI with the cancellation bitmap field can be a DL DCI format 1 0, 1 1, or 1 2.

[0129] ​In some aspects, one or more existing fields in the DCI can be used to include a bitmap for SPS cancellation, rather than adding new fields. For example, because the SPS cancellation DCI may not carry DL data scheduling information, one or more fields in the SPS cancellation DCI may be unusable and therefore can instead be used to indicate a bitmap. In one aspect, the base station can indicate a bitmap in one or more fields in the SPS cancellation DCI that are associated with the antenna port, DMRS, initial seed, MCS, and FDRA, respectively. For example, in a first approach, one or more fields associated with the antenna port, DMRS, initial seed, MCS, and FDRA, respectively, can be used to indicate a bitmap, but the RV field cannot be used to indicate a bitmap because only the RV field is used to indicate SPS cancellation DCI. In another example, in a second approach, one or more fields associated with the antenna port, DMRS, initial seed, and FDRA, respectively, can be used to indicate a bitmap, but the RV field and the MCS field cannot be used to indicate a bitmap because the RV field and the MCS field are used to indicate SPS cancellation DCI. In another example, in the third approach, one or more fields associated with the antenna port, DMRS, and initial seed can be used to indicate the bitmap, but the RV field, MCS field, and FDRA field cannot be used to indicate the bitmap because the RV field, MCS field, and FDRA field are used to indicate that the SPS cancels DCI.

[0130] Figure 11 This is a block diagram illustrating an example of a hardware implementation of a base station 1100 employing a processing system 1114. For example, base station 1100 could be... Figure 1 , Figure 2 and / or Figure 3 Any one or more of the base stations or scheduling entities illustrated in the diagram.

[0131] Base station 1100 may be implemented using a processing system 1114 including one or more processors 1104. Examples of processors 1104 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, base station 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 utilized in base station 1100 may be used to implement the functions described below and Figure 5 to Figure 10 and Figure 12 Any one or more of the processes and procedures illustrated in the diagram.

[0132] In this example, the processing system 1114 can be implemented with a bus architecture, generally represented by the bus 1102. The bus 1102 can include any number of interconnecting buses and bridges depending on the specific application of the processing system 1114 and the overall design constraints. The bus 1102 communicatively couples various circuitry including one or more processors, generally represented by the processor 1104, memory 1105, and the processor-readable medium, generally represented by the processor-readable storage medium 1106. The bus 1102 can also link various other circuitry, such as a timing source, peripherals, voltage regulators, and power management circuitry, which are well known in the art, and therefore, will not be further described. The bus interface 1108 provides an interface between the bus 1102 and the transceiver 1110. The transceiver 1110 provides a communication interface or means for communicating with various other apparatuses over a transmission medium. Depending upon the nature of the apparatus, a user interface 1112 (e.g., keyboard, display, speaker, microphone, joystick) can also be provided. Of course, this user interface 1112 is optional and can be omitted in some examples, such as a base station.

[0133] In some aspects, the processor 1140 can include a communication management circuit 1140 that can be configured to perform various functions including, for example, transmitting, to a UE, a first DCI that triggers a SPS configuration of a plurality of SPS occasions. For example, the communication management circuit 1140 can be configured to implement one or more of the functions described below with regard to, for example, block 1202. Figure 12

[0134] In some aspects, the communication management circuit 1140 can be configured to perform various functions including, for example, transmitting, to a UE, a second DCI that triggers a SPS cancellation of one or more SPS occasions, the second DCI including at least a redundancy version field including one or more redundancy version values to indicate the SPS cancellation. For example, the communication management circuit 1140 can be configured to implement one or more of the functions described below with regard to, for example, block 1210. Figure 12

[0135] In some aspects, the communication management circuit 1140 can be configured to perform various functions including, for example, transmitting, to a UE, a SPS cancellation delay value to indicate a delay in cancelling one or more SPS occasions after the second DCI is received by the UE. For example, the communication management circuit 1140 can be configured to implement one or more of the functions described below with regard to, for example, block 1208. Figure 12

[0136] ​​​In some aspects, the processor 1104 can include an SPS management circuit 1142 that can be configured to perform various functions including, for example, determining to cancel one or more SPS occasions of a plurality of SPS occasions. For example, the SPS management circuit 1142 can be configured to implement one or more of the functions described below with regard to Figure 12 FIG. 12, including, for example, block 1206.

[0137] In some aspects, the SPS management circuit 1142 can be configured to perform various functions including, for example, determining that there is no downlink data to transmit to a UE. For example, the SPS management circuit 1142 can be configured to implement one or more of the functions described below with regard to Figure 12 FIG. 12, including, for example, block 1204.

[0138] The processor 1104 is also responsible for managing the bus 1102 and general processing, including the execution of software stored on the processor-readable storage medium 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described below for any particular apparatus. The processor- readable storage medium 1106 and the memory 1105 can also be used for storing data used by the processor 1104 when executing software.

[0139] One or more processors 1104 in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software may reside on processor-readable storage medium 1106. Processor-readable storage medium 1106 may be a non-transitory processor-readable storage medium. Non-transitory processor-readable storage media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical disks (e.g., compact discs (CDs) or digital multifunction discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable media for storing software and / or instructions that can be accessed and read by a computer. Processor-readable storage medium 1106 may reside in processing system 1114, be external to processing system 1114, or be distributed across multiple entities including processing system 1114. Processor-readable storage medium 1106 may be embodied in a computer program product. For example, a computer program product may include processor-readable storage medium within packaging material. Those skilled in the art will recognize that how best to implement the functionality described throughout this disclosure depends on the specific application and the overall design constraints imposed on the system.

[0140] In one or more examples, the processor-readable storage medium 1106 may include communication management software / instructions 1150, which may be configured to perform various functions, including, for example, sending a first DCI to the UE for triggering multiple SPS timings. For example, the communication management software / instructions 1150 may be configured to implement the following... Figure 12 One or more of the functions described, including, for example, box 1202.

[0141] In some aspects, the communication management software / instruction 1150 can be configured to perform various functions, including, for example, sending a second DCI for triggering the cancellation of one or more SPS timings, the second DCI including at least a redundant version field comprising one or more redundant version values ​​to indicate SPS cancellation. For example, the communication management software / instruction 1150 can be configured to implement the following regarding... Figure 12 One or more of the functions described, including, for example, box 1210.

[0142] In some aspects, the communication management software / instruction 1150 can be configured to perform various functions, including, for example, sending the UE an SPS cancellation delay value indicating a delay in canceling one or more SPS timings after the second DCI is received by the UE. For example, the communication management software / instruction 1150 can be configured to implement the following regarding Figure 12 One or more of the functions described, including, for example, box 1208.

[0143] In some aspects, the processor-readable storage medium 1106 may include SPS management software / instructions 1152, which may be configured to perform various functions, including, for example, determining to cancel one or more SPS timings among a plurality of SPS timings. For example, the SPS management software / instructions 1152 may be configured to implement the following description... Figure 12 One or more of the functions described, including, for example, box 1206.

[0144] In some respects, the SPS management software / instruction 1152 can be configured to perform various functions, including, for example, determining that no downlink data exists to be sent to the UE. For example, the SPS management software / instruction 1152 can be configured to implement the following regarding... Figure 12 One or more of the functions described, including, for example, box 1204.

[0145] Figure 12 This is a flowchart illustrating an exemplary process 1200 for wireless communication using an SPS configuration, according to some aspects. As described below, in certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may be claimed for use in all implementations of all embodiments. In some examples, process 1200 may be... Figure 12 The process is implemented by the base station 1100 shown in the diagram. In some examples, process 1200 can be implemented by any suitable means or component for implementing the functions or algorithms described below.

[0146] At block 1202, the base station may send a first DCI to the UE for triggering multiple SPS timings. In one aspect, communication management circuitry 1140 may provide components for sending the first DCI via transceiver 1110.

[0147] In one aspect, at block 1204, the base station can determine that there is no downlink data to be transmitted to the UE. In another aspect, SPS management circuitry 1142 can provide components for determining that there is no downlink data.

[0148] At block 1206, the base station can determine to cancel one or more SPS occasions of the plurality of SPS occasions. In an aspect, the SPS management circuitry 1142 can provide a means for determining to cancel the one or more SPS occasions.

[0149] In an aspect, at block 1208, the base station can transmit, to the UE, an SPS cancellation delay value to indicate a delay for cancelling the one or more SPS occasions after the second DCI is received by the UE. In an aspect, the communication management circuitry 1140 can provide a means for transmitting the SPS cancellation delay value.

[0150] At block 1210, the base station can transmit the second DCI to trigger the SPS cancellation of the one or more SPS occasions, the second DCI including at least: a redundancy version field including one or more redundancy version values to indicate the SPS cancellation. In an aspect, the communication management circuitry 1140 can provide a means for transmitting, via the transceiver 1110, the second DCI.

[0151] In an aspect, the SPS cancellation delay value is indicated via at least one of an RRC configuration or the second DCI.

[0152] In an aspect, at least one of the one or more redundancy version values is one.

[0153] In an aspect, the second DCI further includes: an SPS cancellation bitmap field including one or more bitmap values to indicate the one or more SPS occasions for the SPS cancellation. In an aspect, a number of the one or more bitmap values in the cancellation bitmap field is associated with an SPS cancellation window indicating a time window to cancel the one or more SPS occasions.

[0154] In an aspect, the second DCI further includes: an antenna port field, a DMRS field, an initial seed field, an MCS field, and an FDRA field, and at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, the FDRA field includes one or more bitmap values to indicate the one or more SPS occasions for the SPS cancellation.

[0155] In an aspect, the second DCI further includes: an MCS field including one or more MCS values, and the one or more redundancy version values and the one or more MCS values are included in the second DCI to indicate the SPS cancellation. In an aspect, at least one of the one or more redundancy version values is one, and at least one of the one or more MCS values is zero. In an aspect, the second DCI further includes: an antenna port field, a DMRS field, an initial seed field, and a FDRA field, and at least one of the antenna port field, the DMRS field, the initial seed field, the FDRA field includes one or more bitmap values indicating one or more SPS occasions for the SPS cancellation.

[0156] In an aspect, the second DCI further includes: an MCS field including one or more MCS values, and the one or more redundancy version values and the one or more MCS values are included in the second DCI to indicate the SPS cancellation. In an aspect, at least one of the one or more redundancy version values is one, and at least one of the one or more MCS values is zero. In an aspect, the second DCI further includes: an antenna port field, a DMRS field, an initial seed field, and a FDRA field, and at least one of the antenna port field, the DMRS field, the initial seed field, the FDRA field includes one or more bitmap values indicating one or more SPS occasions for the SPS cancellation.

[0157] In one configuration, the base station 1100 for wireless communication includes means for transmitting, to a UE, a first DCI to trigger a SPS configuration of a plurality of SPS occasions; means for determining to cancel one or more SPS occasions of the plurality of SPS occasions; and means for transmitting a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least: a redundancy version field including one or more redundancy version values to indicate the SPS cancellation. In an aspect, the base station 1100 can further include means for determining that there is no downlink data to transmit to the UE. In one aspect, the aforementioned means can be the processor(s) 1104 configured for Figure 11 In one configuration, the base station 1100 for wireless communication includes means for transmitting, to a UE, a first DCI to trigger a SPS configuration of a plurality of SPS occasions; means for determining to cancel one or more SPS occasions of the plurality of SPS occasions; and means for transmitting a second DCI to trigger a SPS cancellation of the one or more SPS occasions, the second DCI including at least: a redundancy version field including one or more redundancy version values to indicate the SPS cancellation. In an aspect, the base station 1100 can further include means for determining that there is no downlink data to transmit to the UE. In one aspect, the aforementioned means can be the processor(s) 1104 configured for

[0158] Of course, in the above examples, the circuitry included in the processor 1104 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the processor readable storage medium 1106, or one or more circuitries of the processor 1104 utilizing, for example, programmatic Figure 11 , Figure 1 and / or Figure 2 any other suitable means for carrying out the functions described herein. Figure 3

[0159] Figure 12 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary UE 1300 employing a processing system 1314. In accordance with various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements can be implemented with a processing system 1314 that includes one or more processors 1304. For example, UE 1300 can be a user equipment (UE) or scheduled entity illustrated in any one or more of Figure 13 , Figure 1 and / or Figure 2 .

[0160] The processing system 1314 can be substantially the same as the processing system 1114 illustrated in Figure 3 , including the bus interface 1308, bus 1302, memory 1305, processor 1304, and processor readable storage medium 1306. Further, the UE 1300 can include a user interface 1312 and transceiver 1310 substantially similar to that described above in Figure 11 . That is, the processor 1304 as utilized in a UE 1300 can be configured to implement any one or more of the processes described and illustrated with respect to Figure 11 and Figure 5 to Figure 10 .

[0161] In some aspects, the processor 1340 can include a communication management circuitry 1340 that can be configured to perform various functions, including, for example, receiving a first DCI that triggers a SPS configuration for a plurality of SPS occasions. For example, the communication management circuitry 1340 can be configured to implement one or more of the functions described below with respect to Figure 14 , including, for example, block 1402.

[0162] In some aspects, the communication management circuitry 1340 can be configured to perform various functions, including, for example, receiving a SPS cancellation delay value indicating a delay for cancelling one or more SPS occasions after a second DCI is received by the UE. For example, the communication management circuitry 1340 can be configured to implement one or more of the functions described below with respect to Figure 14 ​One or more of the described functions, including, e.g., block 1404.

[0163] In some aspects, the communication management circuitry 1340 can be configured to perform various functions including, e.g., receiving a second DCI including at least a redundancy version field including one or more redundancy version values. For example, the communication management circuitry 1340 can be configured to implement one or more of the described functions, including, e.g., block 1402. Figure 14 One or more of the described functions, including, e.g., block 1406.

[0164] In some aspects, the processor 1304 can include SPS management circuitry 1342 that can be configured to perform various functions including, e.g., determining, based at least on the one or more redundancy version values, whether the second DCI indicates a SPS cancellation of one or more SPS occasions of the plurality of SPS occasions. For example, the SPS management circuitry 1342 can be configured to implement one or more of the described functions, including, e.g., block 1408. Figure 14 One or more of the described functions, including, e.g., block 1406.

[0165] In some aspects, the SPS management circuitry 1342 can be configured to perform various functions including, e.g., determining, based on a number of the one or more bitmap values in the cancellation bitmap field, a SPS cancellation window indicating a window of time to cancel the one or more SPS occasions. For example, the SPS management circuitry 1342 can be configured to implement one or more of the described functions, including, e.g., block 1410. Figure 14 One or more of the described functions, including, e.g., block 1406.

[0166] In some aspects, the SPS management circuitry 1342 can be configured to perform various functions including, e.g., refraining from monitoring the one or more SPS occasions based on determining that the second DCI indicates the SPS cancellation. For example, the SPS management circuitry 1342 can be configured to implement one or more of the described functions, including, e.g., block 1412. Figure 14 One or more of the described functions, including, e.g., block 1406.

[0167] In one or more examples, the processor-readable storage medium 1306 can include communication management software / instructions 1350 that can be configured to perform various functions including, e.g., receiving a first DCI to trigger a SPS configuration of a plurality of SPS occasions. For example, the communication management software / instructions 1350 can be configured to implement one or more of the described functions, including, e.g., block 1402. Figure 14 One or more of the described functions, including, e.g., block 1406.

[0168] In some aspects, the communication management software / instruction 1350 can be configured to perform various functions, including, for example, receiving an SPS cancellation delay value indicating a delay in canceling one or more SPS timings after the second DCI is received by the UE. For example, the communication management software / instruction 1350 can be configured to implement the following regarding Figure 14 One or more of the functions described, including, for example, box 1404.

[0169] In one or more examples, the communication management software / instruction 1350 can be configured to perform various functions, including, for example, receiving a second DCI, which at least includes a redundant version field comprising one or more redundant version values. For example, the communication management software / instruction 1350 can be configured to implement the following regarding... Figure 14 One or more of the described functions include, for example, box 1406. In one or more examples, processor-readable storage medium 1306 may include SPS management software / instructions 1352, which may be configured to perform various functions, including, for example, determining whether a second DCI indicates the cancellation of one or more SPS timings among a plurality of SPS timings based at least on one or more redundancy version values. For example, SPS management software / instructions 1352 may be configured to implement the following regarding Figure 14 One or more of the functions described, including, for example, box 1408.

[0170] In some respects, the SPS management software / instruction 1352 can be configured to perform various functions, including, for example, determining an SPS cancellation window based on the number of one or more bitmap values ​​in a cancellation bitmap field, the SPS cancellation window indicating a time window for canceling one or more SPS events. For example, the SPS management software / instruction 1352 can be configured to implement the following regarding... Figure 14 One or more of the functions described, including, for example, box 1410.

[0171] In one or more examples, the SPS management software / instruction 1352 can be configured to perform various functions, including, for example, avoiding monitoring one or more SPS events based on determining a second DCI to instruct SPS cancellation. For example, the SPS management software / instruction 1352 can be configured to implement the following regarding... Figure 14 One or more of the functions described, including, for example, box 1412.

[0172] Figure 14is a flowchart illustrating an exemplary process 1400 for wireless communication using SPS, in accordance with some aspects. As described below, some or all of the features illustrated in the figure can be omitted in certain implementations, and some illustrated features can be required in all implementations. In some examples, process 1400 can be performed by UE 1300 illustrated in FIG. 13. In some examples, process 1400 can be performed by any suitable apparatus or means for performing the functions or algorithm described below. Figure 14 In some examples, process 1400 can be performed by any suitable apparatus or means for performing the functions or algorithm described below.

[0173] At block 1402, the UE can receive a first DCI triggering an SPS configuration of a plurality of SPS occasions. In one aspect, communication management circuitry 1140 can provide a means for receiving the first DCI via transceiver 1310.

[0174] In one aspect, at block 1404, the UE can receive an SPS cancellation delay value indicating a delay for cancelling one or more SPS occasions after the second DCI is received by the UE. In one aspect, the SPS cancellation delay value can be received via at least one of an RRC configuration or the second DCI. In one aspect, communication management circuitry 1140 can provide a means for receiving the SPS cancellation delay value.

[0175] At block 1406, the UE can receive a second DCI including at least a redundancy version field including one or more redundancy version values. In one aspect, communication management circuitry 1140 can provide a means for receiving the second DCI via transceiver 1310.

[0176] In one aspect, the second DCI further includes an SPS cancellation bitmap field including one or more bitmap values indicating one or more SPS occasions for SPS cancellation.

[0177] At block 1408, the UE can determine whether the second DCI indicates SPS cancellation of one or more SPS occasions of the plurality of SPS occasions based at least on the one or more redundancy version values. In one aspect, SPS management circuitry 1142 can provide a means for determining whether the second DCI indicates SPS cancellation.

[0178] In one aspect, at block 1410, the UE can determine an SPS cancellation window based on a number of the one or more bitmap values in the cancellation bitmap field, the SPS cancellation window indicating a time window to cancel the one or more SPS occasions. In one aspect, SPS management circuitry 1142 can provide a means for determining the SPS cancellation window.

[0179] At block 1412, the UE can refrain from monitoring one or more SPS occasions based on determining that the second DCI indicates SPS cancellation. In one aspect, the SPS management circuitry 1142 can provide a means for refraining from monitoring one or more SPS occasions.

[0180] In one aspect, refraining from monitoring one or more SPS occasions can be based on one or more bitmap values. In one aspect, refraining from monitoring one or more SPS occasions can be performed based on a SPS cancellation delay value after receiving the second DCI.

[0181] In one aspect, determining whether the second DCI indicates SPS cancellation can include determining that the second DCI indicates SPS cancellation when at least one of the one or more redundancy version values in the second DCI is one.

[0182] In one aspect, the second DCI further includes an antenna port field, a DMRS field, an initial seed field, an MCS field, and an FDRA field, and at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, the FDRA field includes one or more bitmap values indicating one or more SPS occasions for SPS cancellation. In this aspect, refraining from monitoring one or more SPS occasions is based on the one or more bitmap values.

[0183] In one aspect, the second DCI further includes an MCS field including one or more MCS values, and determining whether the second DCI indicates SPS cancellation is based at least on the one or more redundancy version values and the one or more MCS values. In one aspect, determining whether the second DCI indicates SPS cancellation can include determining that the second DCI indicates SPS cancellation when at least one of the one or more redundancy version values is one and where at least one of the one or more MCS values is zero.

[0184] In one aspect, the second DCI further includes an antenna port field, a DMRS field, an initial seed field, and an FDRA field, and at least one of the antenna port field, the DMRS field, the initial seed field, the FDRA field includes one or more bitmap values indicating one or more SPS occasions for SPS cancellation. In this aspect, refraining from monitoring one or more SPS occasions is based on the one or more bitmap values.

[0185] In an aspect, the second DCI further includes: an FDRA field including a plurality of FDRA values, and the determining whether the second DCI indicates the SPS cancellation is based on one or more redundancy version values, one or more MCS values, and the plurality of FDRA values indicating the SPS cancellation. In an aspect, the determining whether the second DCI indicates the SPS cancellation can include: determining that the second DCI indicates the SPS cancellation when at least one of the one or more redundancy version values is one, and at least one of the one or more MCS values is zero, and the plurality of FDRA values are zeros for a first FDRA type or a dynamic switching mode, or the plurality of FDRA values are ones for a second FDRA type. In an aspect, the second DCI further includes: an antenna port field, a DMRS field, and an initial seed field, and at least one of the antenna port field, the DMRS field, or the initial seed field includes one or more bitmap values indicating one or more SPS occasions for the SPS cancellation, wherein the refraining from monitoring the one or more SPS occasions is based on the one or more bitmap values.

[0186] In one configuration, the UE 1300 for wireless communication includes means for receiving a first DCI triggering a SPS configuration for a plurality of SPS occasions; means for receiving a second DCI including at least: a redundancy version field including one or more redundancy version values; means for determining, based at least on the one or more redundancy version values, whether the second DCI indicates a SPS cancellation for one or more SPS occasions of the plurality of SPS occasions; and means for refraining from monitoring the one or more SPS occasions based on the determining that the second DCI indicates the SPS cancellation. In one aspect, the aforementioned means can be the processor(s) 1304 configured as discussed supra for carrying out the functions recited by the aforementioned means. In another aspect, the aforementioned means can be a circuit or any apparatus configured to carry out the functions recited by the aforementioned means. Figure 13 In one configuration, the UE 1300 for wireless communication includes means for receiving a first DCI triggering a SPS configuration for a plurality of SPS occasions; means for receiving a second DCI including at least: a redundancy version field including one or more redundancy version values; means for determining, based at least on the one or more redundancy version values, whether the second DCI indicates a SPS cancellation for one or more SPS occasions of the plurality of SPS occasions; and means for refraining from monitoring the one or more SPS occasions based on the determining that the second DCI indicates the SPS cancellation. In one aspect, the aforementioned means can be the processor(s) 1304 configured as discussed supra for carrying out the functions recited by the aforementioned means. In another aspect, the aforementioned means can be a circuit or any apparatus configured to carry out the functions recited by the aforementioned means.

[0187] Of course, in the above examples, the circuitry included in the processor 1304 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the processor-readable storage medium 1306, or any other suitable apparatus or Figure 13 、 Figure 1 and / or Figure 2 any other suitable apparatus or means described in the detailed description section of the present document and / or throughout the present disclosure, and utilizing, for example, one or more of the processes and / or algorithms described with respect to the Figure 3 section of the present document.

[0188] The following provides an overview of several aspects of the present disclosure.

[0189] Aspect 1: A method of wireless communication by a base station, comprising: transmitting, to a user equipment (UE), a first downlink control information (DCI) to trigger a semi-persistent scheduling (SPS) configuration of a plurality of SPS occasions; determining to cancel one or more SPS occasions of the plurality of SPS occasions; and transmitting a second DCI to trigger an SPS cancellation of the one or more SPS occasions, the second DCI including at least: a redundancy version field including one or more redundancy version values to indicate the SPS cancellation.

[0190] Aspect 2: The method of aspect 1, further comprising: determining that there is no downlink data to transmit to the UE, wherein determining to cancel the one or more SPS occasions is based on determining that there is no downlink data.

[0191] Aspect 3: The method of aspect 1 or 2, further comprising: transmitting, to the UE, an SPS cancellation delay value to indicate a delay to cancel the one or more SPS occasions after the second DCI is received by the UE.

[0192] Aspect 4: The method of aspect 3, wherein the SPS cancellation delay value is indicated via at least one of a radio resource control (RRC) configuration or the second DCI.

[0193] Aspect 5: The method of any of aspects 1 through 4, wherein at least one of the one or more redundancy version values is one.

[0194] Aspect 6: The method of any of aspects 1 through 5, wherein the second DCI further includes: an SPS cancellation bitmap field including one or more bitmap values to indicate the one or more SPS occasions for the SPS cancellation.

[0195] Aspect 7: The method of aspect 6, wherein a number of the one or more bitmap values in the cancellation bitmap field is associated with an SPS cancellation window indicating a time window to cancel the one or more SPS occasions.

[0196] Aspect 8: The method of any of aspects 1 through 7, wherein the second DCI further includes: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, a modulation and coding scheme (MCS) field, and a frequency domain resource allocation (FDRA) field, and wherein at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, the FDRA field includes one or more bitmap values to indicate the one or more SPS occasions for the SPS cancellation.

[0197] Aspect 9: The method of any of aspects 1 through 8, wherein the second DCI further comprises: a modulation and coding scheme (MCS) field comprising one or more MCS values, and wherein the one or more redundancy version values and the one or more MCS values are included in the second DCI to indicate the SPS cancellation.

[0198] Aspect 10: The method of aspect 9, wherein at least one of the one or more redundancy version values is one, and wherein at least one of the one or more MCS values is zero.

[0199] Aspect 11: The method of aspect 9, wherein the second DCI further comprises: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, and a frequency domain resource allocation (FDRA) field, and wherein at least one of the antenna port field, the DMRS field, the initial seed field, the FDRA field comprises one or more bitmap values indicating one or more SPS occasions for the SPS cancellation.

[0200] Aspect 12: The method of any of aspects 1 through 11, wherein the second DCI further comprises: a modulation and coding scheme (MCS) field comprising one or more MCS values and a frequency domain resource allocation (FDRA) field comprising a plurality of FDRA values, and wherein the one or more redundancy version values, the one or more MCS values, and the plurality of FDRA values are included in the second DCI to indicate the SPS cancellation.

[0201] Aspect 13: The method of aspect 12, wherein at least one of the one or more redundancy version values is one, and at least one of the one or more MCS values is zero, and wherein the plurality of FDRA values are zeros for a first FDRA type or a dynamic switching mode, or the plurality of FDRA values are ones for a second FDRA type.

[0202] Aspect 14: The method of aspect 12, wherein the second DCI further comprises: an antenna port field, a demodulation reference signal (DMRS) field, and an initial seed field, and wherein at least one of the antenna port field, the DMRS field, or the initial seed field comprises one or more bitmap values indicating one or more SPS occasions for the SPS cancellation.

[0203] Aspect 15: A base station comprising: a transceiver configured to communicate with a radio access network, a memory, and at least one processor communicatively coupled to the transceiver and the memory, wherein the at least one processor and the memory are configured to perform any of aspects 1 through 14.

[0204] Aspect 16: A base station configured for wireless communication, comprising: at least one means for performing any of aspects 1 through 14.

[0205] Aspect 17: A non-transitory processor-readable storage medium having instructions for a base station embodied thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any of aspects 1 through 14.

[0206] Aspect 18: A method of wireless communication by a user equipment (UE), comprising: receiving a first downlink control information (DCI) triggering a semi-persistent scheduling (SPS) configuration of a plurality of SPS occasions; receiving a second DCI including at least: a redundancy version field including one or more redundancy version values; determining, based at least on the one or more redundancy version values, whether the second DCI indicates a SPS cancellation of one or more SPS occasions of the plurality of SPS occasions; and refraining from monitoring the one or more SPS occasions based on determining that the second DCI indicates the SPS cancellation.

[0207] Aspect 19: The method of aspect 18, wherein determining whether the second DCI indicates the SPS cancellation comprises: determining that the second DCI indicates the SPS cancellation when at least one of the one or more redundancy version values in the second DCI is one.

[0208] Aspect 20: The method of aspect 18 or 19, further comprising: receiving a SPS cancellation delay value indicating a delay to cancel one or more SPS occasions after the second DCI is received by the UE, wherein refraining from monitoring the one or more SPS occasions is performed based on the SPS cancellation delay value after receiving the second DCI.

[0209] Aspect 21: The method of aspect 20, wherein the SPS cancellation delay value is received via at least one of a radio resource control (RRC) configuration or the second DCI.

[0210] Aspect 22: The method of any of aspects 18 through 21, wherein the second DCI further includes: a SPS cancellation bitmap field including one or more bitmap values indicating one or more SPS occasions for the SPS cancellation, and wherein refraining from monitoring the one or more SPS occasions is based on the one or more bitmap values.

[0211] Aspect 23: The method of aspect 22, further comprising: determining, based on a number of the one or more bitmap values in the cancellation bitmap field, a SPS cancellation window indicating a time window to cancel the one or more SPS occasions, wherein refraining from monitoring the one or more SPS occasions is performed within the SPS cancellation window.

[0212] Aspect 24: The method of any of aspects 18 through 23, wherein the second DCI further comprises: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, a modulation and coding scheme (MCS) field, and a frequency domain resource allocation (FDRA) field, wherein at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, the FDRA field comprises one or more bitmap values indicating one or more SPS occasions for the SPS cancellation, and wherein refraining from monitoring the one or more SPS occasions is based on the one or more bitmap values.

[0213] Aspect 25: The method of any of aspects 18 through 24, wherein the second DCI further comprises: an MCS field comprising one or more modulation and coding scheme (MCS) values, and wherein determining whether the second DCI indicates the SPS cancellation is based at least on the one or more redundancy version values and the one or more MCS values.

[0214] Aspect 26: The method of aspect 25, wherein determining whether the second DCI indicates the SPS cancellation comprises: determining that the second DCI indicates the SPS cancellation when at least one of the one or more redundancy version values is one, and wherein at least one of the one or more MCS values is zero.

[0215] Aspect 27: The method of aspect 25, wherein the second DCI further comprises: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, and a frequency domain resource allocation (FDRA) field, wherein at least one of the antenna port field, the DMRS field, the initial seed field, the FDRA field comprises one or more bitmap values indicating one or more SPS occasions for the SPS cancellation, and wherein refraining from monitoring the one or more occasions is based on the one or more bitmap values.

[0216] Aspect 28: The method of aspect 25, wherein the second DCI further comprises: an FDRA field comprising a plurality of frequency domain resource allocation (FDRA) values, and wherein determining whether the second DCI indicates the SPS cancellation is based on the one or more redundancy version values, the one or more MCS values, and the plurality of FDRA values indicating the SPS cancellation.

[0217] Aspect 29: The method of aspect 28, wherein determining whether the second DCI indicates the SPS cancellation comprises: determining that the second DCI indicates the SPS cancellation when: at least one of the one or more redundancy version values is one, and at least one of the one or more MCS values is zero, and the plurality of FDRA values are zeros for a first FDRA type or a dynamic switching mode, or the plurality of FDRA values are ones for a second FDRA type.

[0218] Aspect 30: The method of Aspect 28, wherein the second DCI further comprises: an antenna port field, a demodulation reference signal (DMRS) field, and an initial seed field, and wherein at least one of the antenna port field, the DMRS field, or the initial seed field comprises one or more bitmap values indicating one or more SPS occasions for the SPS cancellation, and wherein refraining from monitoring the one or more SPS occasions is based on the one or more bitmap values.

[0219] Aspect 31 : A UE comprising: a transceiver configured to communicate with a radio access network, a memory, and at least one processor communicatively coupled to the transceiver and the memory, wherein the at least one processor and the memory are configured to perform any of aspects 18 through 30.

[0220] Aspect 32: A UE configured for wireless communication comprising: at least one means for performing any of aspects 18 through 30.

[0221] Aspect 33: A non-transitory processor-readable storage medium having instructions for a UE stored thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any of aspects 18 through 30.

[0222] Several aspects of a wireless communication network have been presented with reference to the example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure can be extended to other telecommunication systems, network architectures and communication standards.

[0223] By way of example, various aspects can be implemented within other systems defined by 3 GPP such as Long-Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunication System (UMTS), and / or Global System for Mobile (GSM). Various aspects can also be implemented within systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). For example, various aspects can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra- Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0224] Within the disclosure, the word“exemplary” is used to mean“serving as an example, instance, or illustration.” Any implementation or aspect described herein as“exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term“aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term“coupled” as used herein is intended to

[0225] Figure 14 One or more of the components, steps, features and / or functions illustrated in the Figures can be rearranged and / or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added or made optional without departing from the novel features described herein. Figure 1 to Figure 14 Figure 1 to Figure 14 The apparatus, devices, and / or components illustrated in the Figures can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0226] It will be understood that the particular order or hierarchy of steps in the methods disclosed is an example process. Based upon design preferences, it is understood that the particular order or hierarchy of steps in the methods can be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0227] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. Phrases such as "at least one of' or "one or more of' a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether these disclosure elements are explicitly recited in the claims. No claim element is to be construed as a means plus function unless the element is expressly recited using the phrase "means for."

Claims

1. A base station for wireless communication, comprising: At least one memory containing instructions; as well as At least one processor, the processor being configured to execute the instructions to cause the base station to: Send the first downlink control information (DCI) to the user equipment (UE) to trigger multiple semi-persistent scheduling (SPS) opportunities for SPS configuration; It was determined that there was no downlink data to be sent to the UE; Based on the determination that the downlink data does not exist, a limited number of SPS opportunities are to be cancelled from among the multiple SPS opportunities. as well as Send a second DCI for triggering the cancellation of the limited number of SPS events, the second DCI including at least: a redundant version field including one or more redundant version values ​​to indicate the SPS cancellation.

2. The base station according to claim 1, wherein, The at least one processor is further configured to execute the instructions to cause the UE to determine: Send the UE an SPS cancellation delay value to indicate a delay in the timing of canceling the predetermined number of SPS after the second DCI is received by the UE.

3. The base station according to claim 1, wherein, At least one of the one or more redundant version values ​​is one.

4. The base station according to claim 1, wherein, The second DCI further includes: an SPS cancellation bitmap field comprising one or more bitmap values ​​indicating the defined number of SPS timings for the SPS cancellation.

5. The base station according to claim 4, wherein, The number of one or more bitmap values ​​in the cancel bitmap field is associated with an SPS cancellation window, which indicates a time window for canceling the predetermined number of SPS events.

6. The base station according to claim 1, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, a modulation and coding scheme (MCS) field, and a frequency domain resource allocation (FDRA) field. Wherein, at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, and the FDRA field includes one or more bitmap values ​​indicating the predetermined number of SPS timings for SPS cancellation.

7. The base station according to claim 1, wherein, The second DCI also includes: an MCS field comprising one or more modulation and coding scheme MCS values, and The one or more redundant version values ​​and the one or more MCS values ​​are included in the second DCI to indicate the cancellation of the SPS.

8. The base station according to claim 7, wherein, At least one of the one or more redundant version values ​​is one, and at least one of the one or more MCS values ​​is zero.

9. The base station according to claim 7, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, and a frequency domain resource allocation (FDRA) field, and Wherein, at least one of the antenna port field, the DMRS field, the initial seed field, and the FDRA field includes one or more bitmap values ​​indicating the limited number of SPS timings for SPS cancellation.

10. The base station according to claim 1, wherein, The second DCI further includes: an MCS field comprising one or more modulation and coding scheme MCS values ​​and an FDRA field comprising multiple frequency domain resource allocation (FDRA) values, and The one or more redundant version values, the one or more MCS values, and the multiple FDRA values ​​are included in the second DCI to indicate the cancellation of the SPS.

11. The base station according to claim 10, wherein, At least one of the one or more redundant version values ​​is one, and at least one of the one or more MCS values ​​is zero. Wherein, the plurality of FDRA values ​​are zero for the first FDRA type or dynamic switching mode, or the plurality of FDRA values ​​are one for the second FDRA type.

12. The base station according to claim 10, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, and an initial seed field, and Wherein, at least one of the antenna port field, the DMRS field, or the initial seed field includes one or more bitmap values ​​indicating the predetermined number of SPS timings for SPS cancellation.

13. A method for wireless communication via a base station, comprising: Send the first downlink control information (DCI) to the user equipment (UE) to trigger multiple semi-persistent scheduling (SPS) opportunities for SPS configuration; It was determined that there was no downlink data to be sent to the UE; Based on the determination that the downlink data does not exist, a limited number of SPS opportunities are to be cancelled from among the multiple SPS opportunities. as well as Send a second DCI for triggering the cancellation of the limited number of SPS events, the second DCI including at least: a redundant version field including one or more redundant version values ​​to indicate the SPS cancellation.

14. The method of claim 13, further comprising: Send the UE an SPS cancellation delay value to indicate a delay in the timing of canceling the predetermined number of SPS after the second DCI is received by the UE.

15. A user equipment (UE) for wireless communication, comprising: At least one memory containing instructions; as well as At least one processor, the processor being configured to execute the instructions to cause the UE to: Receive the first downlink control information (DCI) for the SPS configuration used to trigger multiple semi-persistent SPS timings; Receive a second DCI, the second DCI including at least: a redundant version field including one or more redundant version values; At least based on the one or more redundant version values, determine whether the second DCI indicates the cancellation of a limited number of SPS times among the plurality of SPS times; and Based on determining that the second DCI indicates the cancellation of the SPS to avoid monitoring the limited number of SPS opportunities.

16. The UE according to claim 15, wherein, At least one processor configured to execute the instructions to cause the UE to determine whether the second DCI indicates the SPS cancellation is configured to: When at least one of the one or more redundant version values ​​in the second DCI is one, it is determined that the second DCI indicates that the SPS is cancelled.

17. The UE according to claim 15, wherein, The at least one processor is further configured to execute the instructions to cause the UE to: The receiving instruction specifies the SPS cancellation delay value for the delay in canceling the predetermined number of SPS timings after the second DCI is received by the UE. At least one processor configured to avoid monitoring the limited number of SPS opportunities is configured to avoid monitoring the limited number of SPS opportunities based on an SPS cancellation delay value after receiving the second DCI.

18. The UE according to claim 15, wherein, The second DCI further includes: an SPS cancellation bitmap field comprising one or more bitmap values ​​indicating the predetermined number of SPS timings for the SPS cancellation, and At least one processor configured to avoid monitoring the limited number of SPS opportunities is configured to avoid monitoring the limited number of SPS opportunities based on the one or more bitmap values.

19. The UE according to claim 18, wherein, The at least one processor is further configured to execute the instructions to cause the UE to: The SPS cancellation window is determined based on the number of one or more bitmap values ​​in the cancellation bitmap field, the SPS cancellation window indicating the time window for canceling the predetermined number of SPS events. At least one processor configured to avoid monitoring the limited number of SPS opportunities is configured to avoid monitoring the limited number of SPS opportunities within the SPS cancellation window.

20. The UE according to claim 15, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, a modulation and coding scheme (MCS) field, and a frequency domain resource allocation (FDRA) field. Wherein, at least one of the antenna port field, the DMRS field, the initial seed field, the MCS field, and the FDRA field includes one or more bitmap values ​​indicating the predetermined number of SPS timings for SPS cancellation, and At least one processor configured to avoid monitoring the limited number of SPS opportunities is configured to avoid monitoring the limited number of SPS opportunities based on the one or more bitmap values.

21. The UE according to claim 15, wherein, The second DCI also includes: an MCS field comprising one or more modulation and coding scheme MCS values, and Specifically, at least one processor configured to determine whether the second DCI indicates the SPS cancellation is configured to: determine whether the second DCI indicates the SPS cancellation based at least on the one or more redundancy version values ​​and the one or more MCS values.

22. The UE according to claim 21, wherein, At least one processor configured to execute the instructions to cause the UE to determine whether the second DCI indicates the SPS cancellation is configured to: When at least one of the one or more redundant version values ​​is one, and at least one of the one or more MCS values ​​is zero, it is determined that the second DCI indicates that the SPS is cancelled.

23. The UE according to claim 21, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, an initial seed field, and a frequency domain resource allocation (FDRA) field. Wherein, at least one of the antenna port field, the DMRS field, the initial seed field, and the FDRA field includes one or more bitmap values ​​indicating the predetermined number of SPS timings for SPS cancellation, and At least one processor configured to avoid monitoring the limited number of SPS opportunities is configured to avoid monitoring the limited number of SPS opportunities based on the one or more bitmap values.

24. The UE according to claim 21, wherein, The second DCI also includes: an FDRA field comprising multiple frequency domain resource allocation FDRA values, and Specifically, at least one processor configured to determine whether the second DCI indicates the cancellation of the SPS is configured to: determine whether the second DCI indicates the cancellation of the SPS based on the one or more redundant version values ​​indicating the cancellation of the SPS, the one or more MCS values, and the plurality of FDRA values.

25. The UE according to claim 24, wherein, At least one processor configured to execute the instructions to cause the UE to determine whether the second DCI indicates the SPS cancellation is configured to: The second DCI is determined to be canceled when the following conditions are met: At least one of the one or more redundant version values ​​is one, and at least one of the one or more MCS values ​​is zero. The plurality of FDRA values ​​are zero for the first FDRA type or dynamic switching mode, or the plurality of FDRA values ​​are one for the second FDRA type.

26. The UE according to claim 24, wherein, The second DCI also includes: an antenna port field, a demodulation reference signal (DMRS) field, and an initial seed field, and Wherein, at least one of the antenna port field, the DMRS field, or the initial seed field includes one or more bitmap values ​​indicating the predetermined number of SPS timings for SPS cancellation, and Specifically, the timing for avoiding monitoring the limited number of SPS is based on one or more bitmap values.

27. A method for wireless communication performed by a user equipment (UE), comprising: Receive the first downlink control information (DCI) for the SPS configuration used to trigger multiple semi-persistent SPS timings; Receive a second DCI, the second DCI including at least: a redundant version field including one or more redundant version values; At least based on the one or more redundant version values, determine whether the second DCI indicates the cancellation of a limited number of SPS times among the plurality of SPS times; and Based on determining that the second DCI indicates the cancellation of the SPS to avoid monitoring the limited number of SPS opportunities.

28. The method according to claim 27, wherein, Determining whether the second DCI instructs the SPS to be cancelled includes: When at least one of the one or more redundant version values ​​in the second DCI is one, it is determined that the second DCI indicates that the SPS is cancelled.

29. A computer-readable medium having program code recorded thereon, wherein, The program code may be executed by one or more processors of the user equipment (UE) to cause the processors to perform the method of any one of claims 27-28.

30. A computer-readable medium having program code recorded thereon, wherein, The program code may be executed by one or more processors of the base station UE to cause the processors to perform the method of any one of claims 13-14.

Images