Semi-persistent resource release timing signaling

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can perform communications between the UE and a base station based at least in part on a set of semi-persistent resource occasions. The UE can receive a downlink control information releasing the set of semi-persistent resource occasions. The UE can determine a release time for releasing the set of semi-persistent resource occasions, where the release time for releasing the set of semi-persistent resource occasions is related to a time of reception of the downlink control information. The UE can release the set of semi-persistent resource occasions at the release time based at least in part on the downlink control information.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 107,428, entitled “SEMI-PERSISTENT RESOURCE RELEASE TIMING SIGNALING,” filed October 29, 2020, by Elshafie et al., and U.S. Patent Application No. 17 / 508,330, entitled “SEMI-PERSISTENT RESOURCE RELEASE TIMING SIGNALING,” filed October 22, 2021, by Elshafie et al.; each of these U.S. Provisional Patent Applications and each of these U.S. Patent Applications is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communication, including semi-persistent resource release timing signaling. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), or LTE-A Pro systems) and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, also referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses supporting semi-persistent resource release timing signaling. Generally, the described techniques provide various mechanisms to provide indications of the release time of semi-persistent resource timings. For example, a base station can transmit an indication of the release timing for a user equipment (UE) to release a configured resource (e.g., a semi-persistent resource timing). This indication can be transmitted in a release downlink control information (DCI). The release DCI can indicate a Kc value associated with the release time (e.g., Kc can correspond to the release time and / or an offset value relative to the release DCI at the symbol, micro-slot, and / or slot level). Available Kc values ​​(e.g., one or more tables indicating available release times) can be configured for the UE via radio resource control (RRC) configuration signaling for configuring semi-persistent resources and / or using other RRC / media access control (MAC) control element (CE) signaling. The UE can receive an indication of the release time in the release DCI and determine the release time based on this indication and the timing of the release DCI (e.g., based on the last symbol of the release DCI). Accordingly, the UE can release the configured resources at the release time. Depending on which option is adopted, the UE may or may not monitor resource timing and / or provide feedback message signaling for resource timings that at least partially overlap with the release time.

[0006] A method for performing wireless communication at a UE is described. The method may include performing communication between the UE and a base station based on a set of semi-persistent resource opportunities, receiving a Distributed Content Query (DCI) for releasing the set of semi-persistent resource opportunities, determining a release time for releasing the set of semi-persistent resource opportunities, and releasing the set of semi-persistent resource opportunities at the release time based on the DCI, wherein the release time for releasing the set of semi-persistent resource opportunities is related to the reception time of the DCI.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions, executable by the processor, cause the apparatus to perform communication between the UE and a base station based on a set of semi-persistent resource opportunities, receive a Distributed Information Query (DCI) for releasing the set of semi-persistent resource opportunities, determine a release time for releasing the set of semi-persistent resource opportunities, and release the set of semi-persistent resource opportunities at the release time based on the DCI, wherein the release time for releasing the set of semi-persistent resource opportunities is related to the reception time of the DCI.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include components for performing communication between the UE and a base station based on a set of semi-persistent resource opportunities, components for receiving a Distributed Citation Index (DCI) for releasing the set of semi-persistent resource opportunities, components for determining a release time for releasing the set of semi-persistent resource opportunities, and components for releasing the set of semi-persistent resource opportunities at the release time based on a factual DCI, wherein the release time for releasing the set of semi-persistent resource opportunities is related to the reception time of the DCI.

[0009] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to perform communication between the UE and a base station based on a set of semi-persistent resource opportunities, receive a Distributed Information Query (DCI) for releasing the set of semi-persistent resource opportunities, determine a release time for releasing the set of semi-persistent resource opportunities, and release the set of semi-persistent resource opportunities at the release time based on the DCI, wherein the release time for releasing the set of semi-persistent resource opportunities is related to the reception time of the DCI.

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the release time may include operations, features, components, or instructions for receiving an indication of the release time in the DCI.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a configuration signal that includes an indication of one or more tables associated with an available release time, wherein determining the release time may be based on the configuration signal and the DCI.

[0012] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the configuration signal includes at least one of the following: a first RRC configuration signal for configuring the timing of semi-persistent resources, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities occurring between receiving the DCI and the release time based on the communication and the DCI, and for performing the communication between the UE and the base station during the one or more semi-persistent resource opportunities based on the identification.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the DCI, and for performing the communication between the UE and the base station based on the identification during the one or more semi-persistent resource opportunities.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing the communication may include operations, features, components, or instructions for sending a feedback message associated with the communication between the UE and the base station during and based on the release time of the one or more semi-persistent resource opportunities, the feedback message indicating confirmation information for the one or more semi-persistent resource opportunities.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the DCI, and for avoiding the execution of the communication between the UE and the base station during the one or more semi-persistent resource opportunities based on the identification.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, avoiding the execution of the communication may include operations, features, components, or instructions for discarding communication executed during the one or more semi-persistent resource opportunities and for avoiding sending feedback messages associated with the discarded communication between the UE and the base station during the one or more semi-persistent resource opportunities and based on the release time, the feedback messages indicating confirmation information for the one or more semi-persistent resource opportunities.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin at or after the release time based on the communication and the DCI, and for avoiding the execution of the communication between the UE and the base station during the one or more semi-persistent resource opportunities based on the identification.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a feedback message associated with the communication between the UE and the base station based on the release time, the feedback message indicating confirmation information for one or more semi-persistent resource opportunities in the set that can be selected based on the release time and the DCI.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the release time may include operations, features, components, or instructions for determining the last symbol associated with the DCI and for determining the release time based on the last symbol associated with the DCI and the DCI.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a UE capability message indicating a UE processing time associated with the UE processing the DCI, wherein the release time may be based on the UE processing time.

[0022] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the release time may be based on at least one of a symbol offset, a microslot offset, a slot offset or a combination thereof between the DCI and the release time.

[0023] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the set of semi-persistent resource opportunities includes downlink semi-persistent scheduling (SPS) resource opportunities, uplink configuration grant (CG) resource opportunities, or both.

[0024] A method for wireless communication at a base station is described. The method may include performing communication between the base station and a UE based on a set of semi-persistent resource timings, determining a release time for the set of semi-persistent resource timings for the UE to release, and transmitting a Distributed Information Confirmation (DCI) for releasing the set of semi-persistent resource timings, wherein the release time for the set of semi-persistent resource timings for the UE is related to the reception time of the DCI, and wherein the set of semi-persistent resource timings is released at the UE based on the release time of the DCI.

[0025] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions, executable by the processor, cause the apparatus to perform communication between the base station and a UE based on a set of semi-persistent resource opportunities, determine a release time for the set of semi-persistent resource opportunities for the UE to release, and transmit a Distributed Information Query (DCI) for releasing the set of semi-persistent resource opportunities, wherein the release time for the set of semi-persistent resource opportunities for the UE to release is related to the reception time of the DCI, and wherein the set of semi-persistent resource opportunities is released at the UE based on the release time of the DCI.

[0026] Another apparatus for wireless communication at a base station is described. The apparatus may include components for performing communication between the base station and a UE based on a set of semi-persistent resource timings, components for determining a release time for the set of semi-persistent resource timings for the UE to release, and components for transmitting a Distributed Integrated Circuit (DCI) for releasing the set of semi-persistent resource timings, wherein the release time of the set of semi-persistent resource timings for the UE is related to the reception time of the DCI, and wherein the set of semi-persistent resource timings is released at the UE based on the release time of the DCI.

[0027] A non-transitory computer-readable medium is described, storing code for wireless communication at a base station. The code may include instructions executable by a processor to perform communication between the base station and a UE based on a set of semi-persistent resource opportunities, determine a release time for the set of semi-persistent resource opportunities for the UE to release, and transmit a Distributed Information Confirmation (DCI) for releasing the set of semi-persistent resource opportunities, wherein the release time for the set of semi-persistent resource opportunities for the UE to release is related to the reception time of the DCI, and wherein the set of semi-persistent resource opportunities is released at the UE based on the release time of the DCI.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an indication of the release time in the DCI.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending configuration signals that include indications of one or more tables associated with an available release time, wherein the release time may be based on the configuration signals and the DCI.

[0030] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the configuration signal includes at least one of the following: a first RRC configuration signal for configuring the timing of semi-persistent resources, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities occurring between receiving the DCI and the release time based on the communication and the DCI, and for performing the communication between the base station and the UE based on the identification during the one or more semi-persistent resource opportunities.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the DCI, and for performing the communication between the base station and the UE based on the identification during the one or more semi-persistent resource opportunities.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing the communication may include operations, features, components, or instructions for receiving feedback messages associated with communication between the base station and the UE during the one or more semi-persistent resource timings and based on the release time, the feedback messages indicating confirmation information for the one or more semi-persistent resource timings.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the DCI, and for avoiding the execution of the communication between the base station and the UE during the one or more semi-persistent resource opportunities based on the identification.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, avoiding the execution of the communication may include operations, features, components, or instructions for avoiding receiving feedback messages associated with discarded communication between the UE and the base station during the one or more semi-persistent resource opportunities and based on the release time, the feedback messages indicating confirmation information for the one or more semi-persistent resource opportunities.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more semi-persistent resource opportunities that begin at or after the release time based on the communication and the DCI, and for avoiding the execution of the communication between the base station and the UE during the one or more semi-persistent resource opportunities based on the identification.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, based on the release time, a feedback message associated with the communication between the base station and the UE, the feedback message indicating confirmation information for one or more semi-persistent resource opportunities in the set that can be selected based on the release time and the DCI.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the release time may include operations, features, components, or instructions for determining the last symbol associated with the DCI and for determining the release time based on the last symbol associated with the DCI and the DCI.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a UE capability message indicating a UE processing time associated with the UE processing the DCI, wherein the release time may be based on the UE processing time.

[0040] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the release time may be based on at least one of a symbol offset, a microslot offset, a slot offset or a combination thereof between the DCI and the release time.

[0041] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the set of semi-persistent resource opportunities includes downlink SPS resource opportunities, uplink CG resource opportunities, or both. Attached Figure Description

[0042] Figure 1 Examples of wireless communication systems supporting semi-persistent resource release timing signaling according to aspects of this disclosure are illustrated.

[0043] Figure 2 Examples of wireless communication systems supporting semi-persistent resource release timing signaling according to aspects of this disclosure are illustrated.

[0044] Figure 3A and Figure 3BAn example of a release time configuration for semi-persistent resource release timing signaling, according to aspects of this disclosure, is illustrated.

[0045] Figure 4 An example is illustrated of a process supporting semi-persistent resource release timing signaling according to aspects of this disclosure.

[0046] Figure 5 and Figure 6 A block diagram of an apparatus supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown.

[0047] Figure 7 A block diagram of a communication manager supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown.

[0048] Figure 8 A schematic diagram of a system including a device supporting semi-persistent resource release timing signaling is shown according to aspects of this disclosure.

[0049] Figure 9 and Figure 10 A block diagram of an apparatus supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown.

[0050] Figure 11 A block diagram of a communication manager supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown.

[0051] Figure 12 A schematic diagram of a system including a device supporting semi-persistent resource release timing signaling is shown according to aspects of this disclosure.

[0052] Figures 13 to 17 A flowchart illustrating a method for supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Detailed Implementation

[0053] Some wireless communication systems may use semi-persistent resources (e.g., semi-persistent resource timing) for communication in the downlink (e.g., semi-persistent scheduling (SPS) resources) and / or uplink (e.g., configuration grant (CG) resources). Such resources are typically configured by the base station for Radio Resource Control (RRC) for the User Equipment (UE). The base station then sends an Activate Downlink Control Message (DCI) to activate the configured resource, optionally sends a Reactivate DCI to reconfigure the resource, and subsequently sends a Release DCI to release the configured semi-persistent resource. However, wireless communication does not define any aspect of the timing of the release of the configured semi-persistent resource after the UE receives the Release DCI.

[0054] The aspects of this disclosure are initially described in the context of wireless communication systems. Generally, the described techniques provide various mechanisms to provide indications of the release time of semi-persistent resource timings. For example, a base station may transmit an indication of the release timing for a UE to release configured resources (e.g., semi-persistent resource timings). This indication may be transmitted in a release DCI. The release DCI may indicate a Kc value associated with the release time (e.g., Kc may correspond to the release time and / or an offset value relative to the release DCI at the symbol, micro-slot, and / or slot level). Available Kc values ​​(e.g., one or more tables indicating available release times) may be configured for the UE via RRC configuration signaling for configuring semi-persistent resources and / or using other RRC / Media Access Control (MAC) control element (CE) signaling. The UE may receive an indication of the release time in the release DCI and determine the release time based on this indication and the timing of the release DCI (e.g., based on the last symbol of the release DCI). Accordingly, the UE may release the configured resources at the release time. Depending on which option is adopted, the UE may or may not monitor resource timing and / or provide feedback message signaling for resource timings that at least partially overlap with the release time.

[0055] This disclosure is further illustrated and described with reference to apparatus diagrams, system diagrams and flowcharts relating to semi-persistent resource release timing signaling.

[0056] Figure 1 An example of a wireless communication system 100 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0057] Base stations 105 can be distributed throughout a geographic area to form a wireless communication system 100, and can be different types of devices or devices with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. The coverage area 110 can be an example of a geographic area on which base station 105 and UE 115 can support signal communication according to one or more radio access technologies.

[0058] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be different types of devices or devices with different capabilities. Figure 1 Some example UE 115s are shown below. Figure 1 As shown, the UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices).

[0059] Base station 105 may communicate with core network 130, communicate with each other, or both. For example, base station 105 may interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 may communicate with each other directly (e.g., directly between base stations 105), indirectly (e.g., via core network 130), or both via backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, backhaul link 120 may be one or more radio links or include one or more radio links.

[0060] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or giga-NodeB (any of which may be referred to as gNB), home NodeB, home eNodeB or other suitable terms.

[0061] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., and UE 115 may be implemented in a variety of objects, such as home appliances or vehicles, meters, etc.

[0062] like Figure 1As shown, the UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s that can sometimes be used as relays, as well as base station 105 and network devices including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations.

[0063] UE 115 and base station 105 can wirelessly communicate with each other via one or more carriers through one or more communication links 125. The term "carrier" can refer to a set of radio spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion (e.g., a bandwidth portion (BWP)) of a radio spectrum band operating according to one or more physical layer channels of a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operations for the carrier, user data, or other signaling. Wireless communication system 100 can use carrier aggregation or multi-carrier operation to support communication with UE 115. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0064] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCH)) and can be located according to a channel grid for discovery by UE 115. The carrier may operate in standalone mode, in which initial acquisition and connection can be implemented by UE 115 via the carrier, or the carrier may operate in non-standalone mode, in which connection is anchored using different carriers (e.g., the same or different radio access technologies).

[0065] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0066] A carrier can be associated with a specific bandwidth of the radio spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth can be one of several defined bandwidths of a carrier used for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) can have a hardware configuration that supports communication over a specific carrier bandwidth, or can be configured to support communication over a single carrier bandwidth within a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0067] The signal waveform transmitted via a carrier can consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can consist of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely proportional. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both). Therefore, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate the UE 115 can potentially achieve. Wireless communication resources can refer to a combination of radio spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further improve the data rate or data integrity for communication with the UE 115.

[0068] One or more parameter sets (numerology) can be supported for a carrier, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of the UE 115 can be restricted to one or more active BWPs.

[0069] The time interval of base station 105 or UE 115 can be expressed as a multiple of a basic time unit, such as T. s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δfmax This can represent the maximum supported subcarrier spacing, and N f This can represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. In addition to the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or frequency band of the operation.

[0071] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0072] Physical channels can be multiplexed on a carrier using various techniques. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by multiple symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information in a control information format with a given payload size. The search space set can include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0073] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., via a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), etc.). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of base station 105), the range of such cells can range from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, external spaces between or overlapping geographic coverage areas 110, etc.

[0074] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a low-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0075] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access to different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0076] In some examples, base station 105 may be mobile, and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0077] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and in some examples, transmissions from different base stations 105 can be time-disaligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0078] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay that information to a central server or application, which utilizes or presents the information to a person interacting with the application. Some UE 115 devices can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0079] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside the carrier.

[0080] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communication and may be supported by one or more mission-critical services such as mission-critical key-touch (MCPTT), mission-critical video (MCViedo), or mission-critical data (MCData). Support for mission-critical functions may include service prioritization, and mission-critical services may be used for public safety or general business applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0081] In some examples, UE 115 can also communicate directly with other UE 115 via device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UE 115s using D2D communication can be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, the group of UE 115s communicating via D2D communication can utilize a one-to-many (1:M) system, in which each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE 115s without the involvement of base station 105.

[0082] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0083] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and can include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) routing packets to or interconnecting with external networks. The control plane entity can manage non-access stratum (NAS) functions of UE 115 served by base station 105 associated with core network 130, such as mobility, authentication, and bearer management. User IP packets can be passed through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to IP service 150 for one or more network operators. IP services 150 may include access to the Internet, (multiple) intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0084] Some network devices (such as base station 105) may include sub-components (such as access network entity 140), which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transmission entities 145, which may be referred to as a radio head, smart radio head, or transmit / receive point (TRP). Each access network transmission entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or combined into a single network device (e.g., base station 105).

[0085] Wireless communication system 100 can operate using one or more frequency bands typically in the range of 300 MHz to 300 GHz. The region from 300 MHz to 3 GHz is generally referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features, but these waves are sufficient to penetrate structures to enable macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0086] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) of the frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, this may be advantageous for the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater atmospheric attenuation and shorter distances. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary depending on the country or regulatory body.

[0087] Wireless communication system 100 can utilize both licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 can use Licensed Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio spectrum bands, devices such as base station 105 and UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed bands can be based on a combination of carrier aggregation configuration and component carriers operating in licensed bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmission, uplink transmission, P2P transmission, D2D transmission, etc.

[0088] Base station 105 or UE 115 may be equipped with multiple antennas, which may employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located in a single antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with multiple rows and columns of antenna ports, which base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio beamforming for signals transmitted via the antenna ports.

[0089] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique can be referred to as spatial multiplexing. Multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) in which multiple spatial layers are transmitted to the same receiving device and multi-user MIMO (MU-MIMO) in which multiple spatial layers are transmitted to multiple devices.

[0090] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique used at a transmitting or receiving device (e.g., base station 105, UE 115) to shape or manipulate an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating in a specific orientation relative to the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0091] Base station 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to implement beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions. For example, base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device such as base station 105 or by a receiving device such as UE 115) to identify the beam direction for subsequent transmission or reception by base station 105.

[0092] Base station 105 may transmit signals, such as data signals associated with a specific receiving device, in a single beam direction (e.g., the direction associated with a receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or otherwise acceptable signal quality.

[0093] In some examples, transmissions performed by devices (e.g., base station 105 or UE 115) may be performed using multiple beam directions, and the devices may use a combination of digital pre-decoding or radio beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to the number of beam configurations across the system bandwidth or one or more sub-bands. Base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may be pre-decoded or undecoded. UE 115 may provide feedback for beam selection, which may be a pre-decoded matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction subsequently transmitted or received by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0094] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, the receiving device (e.g., UE 115) can attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device can attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signals according to different antenna subarrays; receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights); or processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these methods can be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). The single receiving configuration can be aligned on a beam direction determined based on listening according to different receiving configuration directions (e.g., a beam direction determined based on listening according to multiple beam directions to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality).

[0095] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for communication on logical channels. The Media Access Control (MAC) layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between UE 115 and base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0096] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique to increase the likelihood of correct data reception over communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve the throughput of the MAC layer under adverse radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support simultaneous time-slot HARQ feedback, where the device can provide HARQ feedback in a specific time slot for data received in the preceding symbol of that time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0097] UE 115 can perform communication between UE 115 and base station 105 based at least in part on a set of semi-persistent resource opportunities. UE 115 can receive a DCI for releasing the set of semi-persistent resource opportunities. UE 115 can determine a release time for the set of semi-persistent resource opportunities, wherein the release time for releasing the set of semi-persistent resource opportunities is related to the reception time of the DCI. UE 115 can release the set of semi-persistent resource opportunities at the release time based at least in part on the DCI.

[0098] Base station 105 can perform communication between base station 105 and UE 115 based at least in part on a set of semi-persistent resource timings. Base station 105 can determine a release time for the set of semi-persistent resource timings for UE 115 to release, wherein the release time for the set of semi-persistent resource timings for UE 115 to release is related to the reception time of DCI. Base station 105 can transmit a DCI for releasing the set of semi-persistent resource timings, wherein the set of semi-persistent resource timings is based at least in part on the release time by UE 115 of the DCI.

[0099] Figure 2 An example of a wireless communication system 200 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is illustrated. The wireless communication system 200 may include a base station 205 and / or a UE 210, which may be examples of the corresponding devices described herein.

[0100] The wireless communication system 200 may use configured semi-persistent resources (e.g., semi-persistent resource timings) for communication in the downlink (e.g., SPS resources) and / or uplink (e.g., CG resources). These resources are typically configured by base station 205 for the RRC of UE 210. Base station 205 may subsequently send an activation DCI to activate the configured resources, optionally send a reactivation DCI to reconfigure the resources, and subsequently send a release DCI to release the configured semi-persistent resources.

[0101] In other words, base station 205 may send or otherwise provide (and UE 210 may receive or otherwise obtain) configuration signaling (e.g., RRC configuration signaling) for configuring semi-persistent resource timings (e.g., SPS and / or CG resource timings, which may also be referred to as SPS configuration and / or CG configuration). For example, the configuration signaling may configure frequency resources, spatial resources, decoding resources, resource-associated periods, and provide indications of HARQ-ACK feedback resources to be used for semi-persistent resource timings, etc.

[0102] Base station 205 may, for example, send a Semi-Persistent Resource Timing Activation DCI at time t0 to activate certain configured semi-persistent resource timings (e.g., at least some of the configured semi-persistent resource timings, which may also be referred to as active SPS timing 215 in the downlink example). The activation DCI may carry or otherwise transmit indications of various transmission parameters to be used for communication using the activated semi-persistent resource timing. For example, the activation DCI may carry or otherwise transmit indications of modulation and decoding schemes (MCS), resource block allocations, antenna ports (e.g., spatial information), etc., to be used for communication between base station 205 and UE 210 using the activated semi-persistent resource timing. Accordingly, base station 205 and UE 210 may perform communication at least in part based on some of the configured semi-persistent resource timings in response to the activation DCI (e.g., communication may be performed during active SPS timing 215).

[0103] If needed, base station 205 may send or otherwise provide (and UE 210 may receive or otherwise obtain) a reactivation DCI (e.g., also referred to as SPS reactivation DCI in the downlink example) to change one or more of the transmission parameters being used for communication during active SPS timing 215. For example, at time t1, base station 205 may send or otherwise provide (and UE 210 may receive or otherwise obtain) a reactivation DCI that changes MCS, resource block allocation, antenna port configuration, etc., for subsequent communication using active SPS timing 215.

[0104] Base station 205 may transmit or otherwise provide (and UE 210 may receive or otherwise obtain) a release DCI (e.g., also referred to as SPS release DCI in the downlink example) for a set of semi-persistent resource release opportunities (e.g., releasing at least some of the configured semi-persistent resource release opportunities). For example, at time t2, base station 205 may transmit or otherwise provide (and UE 210 may receive or otherwise obtain) a DCI for the set of semi-persistent resource release opportunities. Generally, UE 210 may release the set of semi-persistent resource release opportunities in response to the release DCI.

[0105] Some wireless communication systems can define a minimum time (Nc) for UE 210 to process SPS release of DCI. In some respects, Nc can have different values ​​depending on considerations such as UE capabilities of UE 210, the subcarrier spacing (SCS) of the component carriers used to release DCI, the SCS of the SPS physical downlink shared channel (PDSCH), and the SCS of the released SPS PDSCH (e.g., the timing of semi-persistent resource release via DCI release). In some respects, Nc can be defined based on the number of OFDM symbols starting with the last symbol of DCI release. However, the default Nc value is the default value for general network configuration and may or may not extend to semi-persistent resource timings overlapping with the release time.

[0106] Some wireless communication systems do not provide a mechanism for determining the release time of a semi-persistent resource allocation being released via a release DCI. That is, current wireless communication systems do not define a gap between the effective time of UE 210 receiving the release DCI and the release of the semi-persistent resource opportunity. This can lead to ambiguity between base station 205 and UE 210 regarding when the SPS resource is released (e.g., in the downlink example). For example, in some cases, UE 210 may release the SPS PDSCH (e.g., the semi-persistent resource opportunity) immediately after successfully receiving the decoded SPS release DCI. Because base station 205 may not fully understand UE 210's processing and response time, ambiguity may exist regarding when the semi-persistent resource opportunity is released. This could lead to a situation where UE 210 successfully receives and decodes the release DCI during a semi-persistent resource opportunity used for communication. Accordingly, the UE may release that semi-persistent resource opportunity. This could further lead to ambiguity and / or lost communication between base station 205 and UE 210 regarding HARQ-ACK feedback message signaling.

[0107] Accordingly, aspects of the described technology provide multiple mechanisms to support UE behavior before, during, or after Kc (e.g., at the symbol, micro-slot, and / or slot offset level) from the end of the SPS release of DCI / PDCCH (e.g., from the last symbol of the released DCI). For example, the described technology provides multiple mechanisms to define the time when the SPS release of DCI takes effect (e.g., release time). In some aspects, the described technology provides UE 210 with the option to stop or not stop monitoring SPSPDSCH timings (e.g., semi-persistent resource timings), and / or to report or not report HARQ-ACK feedback for those timings that overlap with the release time. Typically, Kc can correspond to the actual release time and / or information used to determine the release time (e.g., offset value in the time domain). Accordingly, references to release time and / or Kc can be used interchangeably.

[0108] For example, base station 205 and UE 210 may perform communication based on semi-persistent resource timings. This may include UE 210 not monitoring released SPS timings 220 (e.g., configured but not activated semi-persistent resource timings) because these resources are not activated. At time t0, base station 205 may send an activation DCI (e.g., creating an active SPS timing 215) to UE 210 to activate at least some of the configured semi-persistent resource timings. The activation DCI may use the activated semi-persistent resource timings (e.g., active SPS timing 215) to provide transmission parameters for communication (e.g., uplink and / or downlink communication) between base station 205 and UE 210. As discussed, base station 205 may send or otherwise provide (and UE 210 may receive or otherwise obtain) a reactivation DCI that reconfigures one or more transmission parameters for the configured semi-persistent resource timings at time t1. Base station 205 and UE 210 can continue communication using semi-persistent resource timings (e.g., active SPS timing 215) based on reconfigured transmission parameters.

[0109] Base station 205 may transmit or otherwise provide (and UE 210 may receive or otherwise obtain) a release DCI for a set of semi-persistent resource opportunities at time t2. For example, a release DCI may release one or more subsequent semi-persistent resource opportunities. In some aspects, the release DCI may carry or otherwise transmit an indication of the release time. Generally, the release time can be measured from the time of receiving the SPS release DCI (e.g., the last symbol of the DCI releasing the semi-persistent resource opportunity), which occurs at time t3 in the non-limiting example illustrated in wireless communication system 200. Typically, Kc may be at least equal to or greater than Nc and may correspond to the symbol offset, micro-slot offset, and / or slot offset between the last symbol of the release DCI and the effective time when the semi-persistent resource opportunity is released. In some aspects, Kc may be indicated (explicitly and / or implicitly) in the release DCI. For example, Kc may be indicated in the Time Domain Resource Allocation (TDRA) resource allocation field transmitted in the release DCI. In one example, a new TDRA table (e.g., a table with fewer rows than the one used for the PDSCH allocation list pdsch-AllocationList) can be defined for Kc. In another example, the release DCI can utilize the K0 value in the TDRA configuration table (e.g., pdsch-AllocationList and PDSCH-TimeDomainResourceAllocation). In this example, base station 205 can define a TDRA table for UE 210 and ensure that the selected TDRA row index indicated in the release DCI, K0 (which will correspond to Kc in the release DCI), is selected with a value greater than or equal to Nc. Accordingly, the release DCI can include a TDRA indication used by UE 210 as Kc, which can provide information for determining the release time.

[0110] In some respects, the value of Kc can be configured by base station 205 for UE 210. For example, base station 205 may send or otherwise provide (and UE 210 may receive or otherwise obtain) a configuration signal carrying or otherwise transmitting an indication of one or more tables (e.g., tables corresponding to Kc values) associated with an available release time (e.g., a newly defined Kc table). The configuration signal may include RRC signaling, such as RRC configuration signaling used to configure a set of semi-persistent resource opportunities. In this configuration example, each semi-persistent resource opportunity (e.g., SPS configuration) may have its own configured Kc table / value. In another example, different or other RRC and / or MAC CE configuration signaling may be used to configure UE 210 via (multiple) Kc tables. In this configuration example, some and / or all of the configured semi-persistent resource opportunities (e.g., a group or all of the SPS configuration) may be configured with the same Kc value / (multiple) tables. As discussed, Kc may be at least equal to or greater than Nc.

[0111] Accordingly, UE 210 can determine the release time of the set of opportunities to release semi-persistent resources based on the release DCI. For example, the release time of the set of opportunities to release semi-persistent resources can be related to the reception time of the release DCI and an indication of the release time transmitted in the release DCI (e.g., an indication of Kc). For example, UE 210 can identify the last symbol of the release DCI and determine the release time based on the Kc indication. Accordingly, UE 210 can release the set of opportunities to release semi-persistent resources at the release time (e.g., at time t3) based on the release DCI. That is, UE 210 and / or base station 205 can determine the release time based on the Kc indication transmitted in the release DCI, which identifies the offset between the last symbol of the release DCI and the release time.

[0112] As discussed above, the Kc indication carried or otherwise transmitted in the release DCI can be based on the capabilities of UE 210. Since Nc can be the default processing time configured by the network, in some respects, UE 210 can send or otherwise provide (and base station 205 can receive or otherwise obtain) a UE capability message indicating the processing time of UE 210. Typically, the processing time of UE 210 can correspond to the time UE 210 spends processing and responding to the release DCI. In this case, base station 205 can select or otherwise determine the value of Kc to be transmitted in the release DCI based on the capabilities of UE 210 (e.g., based on the UE processing time indicated in the capability message).

[0113] In some cases, release time can correspond to overlapping semi-persistent resource timings. For example... Figure 2As shown, the release time (e.g., time t3) occurs when UE 210 and base station 205 are communicating during a semi-persistent resource timing (e.g., the SPS PDSCH timing in the downlink example). In this case, several options are provided for UE 210 to use.

[0114] One option may include base station 205 and UE 210 continuing communication using one or more semi-persistent resource opportunities that occur in a manner overlapping with the release time. That is, a semi-persistent resource opportunity that begins before the release time and ends after the release time can be considered to overlap with the release time, such as... Figure 2 As shown. In cases where base station 205 and / or UE 210 identify one or more semi-persistent resource timings overlapping with release times, base station 205 and UE 210 can continue communication during the overlapping semi-persistent resource timings. That is, if a PDSCH timing (e.g., active SPS timing 215) begins before the release time but after receiving the release DCI, then UE 210 and / or base station 205 (e.g., depending on whether the communication is uplink or downlink) can continue monitoring / decoding the semi-persistent resource timing. UE 210 (or base station 205 in the uplink example) can send or otherwise provide HARQ-ACK feedback for the overlapping semi-persistent resource timings. Accordingly, UE 210 can send or otherwise provide (and base station 205 can receive or otherwise obtain) a feedback message associated with the communication occurring during the overlapping semi-persistent resource timings. The feedback message can carry or otherwise transmit acknowledgment information (e.g., HARQ-ACK feedback information) for the overlapping semi-persistent resource timings. Accordingly, the option may include an SPS timing from the end of the DCI OFDM symbol to the beginning of the PDSCH assignment of the SPS configuration after the Kc time offset from the release of the DCI.

[0115] In another option, this could include overlapping semi-persistent resource timings not used for communication between base station 205 and UE 210. Again, base station 205 and / or UE 210 may identify or otherwise determine that one or more of the semi-persistent resource timings begin before the release time and end after the release time (e.g., overlapping with the release time if the PDSCH is not fully received). In this option, base station 205 and / or UE 210 may avoid performing communication during one or more semi-persistent resource timings. That is, UE 210 may discard communication performed during one or more semi-persistent resource timings. UE 210 (or base station 205 in the uplink example) may avoid transmitting feedback information associated with the discarded communication. That is, this option could include SPS timings from the end of the DCI OFDM symbol to the end of the PDSCH allocation of the SPS configuration after a Kc time offset from the release of the DCI. Since base station 205 may not care whether UE 210 continues to monitor SPS PDSCH after it sends an SPS PDSCH release (e.g., release DCI), this option may be beneficial in terms of HARQ-ACK. Instead, base station 205 may only care about UE 210 that does not include HARQ-ACK feedback for SPS PDSCH in its HARQ-ACK codebook. Accordingly, this option could include allowing UE 210 to stop monitoring the PDSCH timing and not send its HARQ-ACK feedback for that PDSCH timing if it has not ended.

[0116] In some respects, semi-persistent resource opportunities (e.g., active SPS opportunity 215) occurring between the receive release DCI and the release time can continue to be used for communication between base station 205 and UE 210. For example, base station 205 and / or UE 210 can identify or otherwise determine that one or more of the semi-persistent resource opportunities occur (e.g., are completed) between the receive release DCI (e.g., the last symbol of the release DCI) and the release time (e.g., end before time t3). In this example, base station 205 and UE 210 can continue to use those one or more semi-persistent resource opportunities. Accordingly, if a PDSCH opportunity occurs before the release time but ends after the receive release DCI, then UE 210 can continue to monitor this PDSCH opportunity and send its HARQ-ACK feedback accordingly.

[0117] In some respects, semi-persistent resource opportunities that begin at or after the release time can be released or otherwise discarded. Accordingly, base station 205 and UE 210 can release semi-persistent resource opportunities and thus avoid performing communication on these semi-persistent resource opportunities. Accordingly, for any PDSCH opportunity that does not begin before the release time (e.g., the released SPS opportunity 220), UE 210 may not monitor / decode the PDSCH opportunity and may not send its HARQ-ACK feedback.

[0118] Accordingly and depending on the timing of the semi-persistent resource timing relative to the release time, UE 210 may send or otherwise provide (and base station 205 may receive or otherwise obtain) a feedback message (e.g., HARQ-ACK feedback) associated with the communication between base station 205 and UE 210. The feedback message may carry or otherwise transmit an indication of confirmation information (e.g., acknowledgment or negative acknowledgment) for one or more semi-persistent resource timings selected based on the release time and release DCI.

[0119] Figure 3A and Figure 3B An example of a release time configuration 300 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is illustrated. Aspects of the release time configuration 300 may be implemented by or at wireless communication systems 100 and / or 200. Aspects of the release time configuration 300 may be implemented by or at a base station and / or UE, the base station and / or UE being examples of the corresponding devices described herein. Generally, release time configuration 300-a may correspond to the option that a semi-persistent resource allocation overlapping with the release time is used to perform communication between the base station and the UE. Generally, release time configuration 300-b may correspond to the option that a semi-persistent resource allocation overlapping with the release time is not used (e.g., discarded or otherwise released) to perform communication between the base station and the UE.

[0120] As discussed above, the described aspects of the technology provide various mechanisms by which the base station can provide the UE with an indication of the release time (e.g., defining Kc, the offset between the last symbol of the release DCI and the actual release time) in a DCI that releases semi-persistent resource opportunities (e.g., SPS resource opportunities supporting SPS PDSCH communication and / or CG resource opportunities supporting CG PUSCH communication). For example, the UE and the base station can perform communication based on semi-persistent resource opportunities configured by the base station for the UE. For example, the base station can use RRC configuration signaling to configure various SPS and / or CG configurations for the UE. The base station can activate some of the semi-persistent resource opportunities used to perform communication between the base station and the UE (e.g., uplink and / or downlink communication). The base station can activate some of the semi-persistent resource opportunities by sending an activation DCI to the UE that provides various transmission parameters to be used for communication using semi-persistent resource opportunities. Accordingly, the UE and the base station can perform communication based on a set of semi-persistent resource opportunities (e.g., active semi-persistent resource opportunities). The base station may send or otherwise provide (and the UE may receive or otherwise obtain) a release DCI for the set of semi-persistent resource opportunities. The release DCI may carry or otherwise transmit an indication of the release time for the semi-persistent resource opportunities (e.g., a Kc value may be indicated in the TDRA field and / or Kc may be explicitly signaled in the release DCI using a new Kc field / bit). Accordingly, the UE may release the set of semi-persistent resource opportunities at the release time based on the release DCI. As discussed above, in some examples, this may result in one or more semi-persistent resource opportunities overlapping with the release time (e.g., one or more semi-persistent resource opportunities may begin before the release time and end after the release time). Figure 3A and Figure 3B Two unrestricted options are shown that can be used in this scenario.

[0121] First refer to Figure 3A In the release time configuration 300-a, the base station may send or otherwise provide (and the UE may receive or otherwise obtain) a release DCI carrying or otherwise transmitting an indication of the release time (e.g., the release DCI may include a TDRA field and / or a dedicated field indicating or otherwise corresponding to a Kc value, where the Kc value is selected to be at least equal to or greater than Nc). The UE may use the indication in the release DCI to identify or otherwise determine the release time of a set used for semi-persistent resource allocation.

[0122] In some cases, one or more (only one is shown as an example) semi-persistent resource timings can occur between the DCI reception time and the release time (e.g., between the last symbol of the released DCI and the release time). Figure 3AIn the non-limiting example shown, this could include a semi-persistent resource opportunity 305 occurring between the reception of the DCI release and the release time. In this case, the base station and the UE can continue communication during the semi-persistent resource opportunity 305. This could include the UE continuing to monitor / decode the semi-persistent resource opportunity 305 and providing HARQ-ACK feedback for the semi-persistent resource opportunity 305.

[0123] In some cases, the timing of one or more (only one is shown as an example) semi-persistent resources can overlap with their release time (e.g., it can start before the release time and end after the release time). Figure 3A In the non-limiting example shown, this could include a semi-persistent resource timing 310 that begins before the release time and ends after the release time. In this case, and according to one option, the base station and the UE can continue communication during the semi-persistent resource timing 310. This could include the UE continuing to monitor / decode the semi-persistent resource timing 310 and providing HARQ-ACK feedback for the semi-persistent resource timing 310.

[0124] In some cases, one or more (only one is shown as an example) semi-persistent resource timings can occur after the release time (e.g., they can begin at or after the release time). Figure 3A In the non-limiting example shown, this could include a semi-persistent resource opportunity 315 that begins at or after the release time. In this case, the base station and the UE may discard or otherwise release the semi-persistent resource opportunity 315. That is, the base station and / or the UE may avoid performing communication during the semi-persistent resource opportunity 315. This could include the UE discarding any monitored / decoded portions of the semi-persistent resource opportunity 315 and avoiding providing HARQ-ACK feedback for the semi-persistent resource opportunity 315.

[0125] Next reference Figure 3B In the release time configuration 300-b, the base station may send or otherwise provide (and the UE may receive or otherwise obtain) a release DCI carrying or otherwise transmitting an indication of the release time (e.g., the release DCI may include a TDRA field and / or a dedicated field indicating or otherwise corresponding to a Kc value, wherein the Kc value is selected to be at least equal to or greater than Nc). The UE may use the indication in the release DCI to identify or otherwise determine the release time for a set used for semi-persistent resource allocation.

[0126] In some cases, one or more (only one is shown as an example) semi-persistent resource timings can occur between the DCI reception time and the release time (e.g., between the last symbol of the released DCI and the release time). Figure 3BIn the non-limiting example shown, this could include a semi-persistent resource opportunity 320 occurring between the receipt of the DCI release and the end of the release time. In this case, the base station and the UE can continue communication during the semi-persistent resource opportunity 320. This could include the UE continuing to monitor / decode the semi-persistent resource opportunity 320 and providing HARQ-ACK feedback for the semi-persistent resource opportunity 320.

[0127] In some cases, the timing of one or more (only one is shown as an example) semi-persistent resources can overlap with their release time (e.g., it can start before the release time and end after the release time). Figure 3B In the non-limiting example shown, this could include a semi-persistent resource timing 325 that begins before the release time and ends after the release time. In this case, and according to another option, this could include the base station and / or the UE discarding or otherwise releasing the semi-persistent resource timing 325. That is, the base station and / or the UE could avoid performing communication during the semi-persistent resource timing 325. This could include the UE discarding any monitored / decoded portions of the semi-persistent resource timing 325 and avoiding providing HARQ-ACK feedback for the semi-persistent resource timing 325.

[0128] In some cases, one or more (only one is shown as an example) semi-persistent resource timings can occur after the release time (e.g., they can begin at or after the release time). Figure 3B In the non-limiting example shown, this could include a semi-persistent resource timing 330 that begins at or after the release time. In this case, the base station and the UE may discard or otherwise release the semi-persistent resource timing 330. That is, the base station and / or the UE may avoid performing communication during the semi-persistent resource timing 330. This could include the UE discarding any monitored / decoded portions of the semi-persistent resource timing 330 and avoiding providing HARQ-ACK feedback for the semi-persistent resource timing 330.

[0129] Accordingly, Release Time Configuration 300 illustrates two non-restrictive options that can be adopted by the UE and / or base station when one or more semi-persistent resource opportunities overlap with a release time determined based on Release DCI.

[0130] Figure 4 An example of a process 400 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is illustrated. Aspects of process 400 may be implemented by or at wireless communication systems 100 and / or 200, and / or release timing configuration 300. Aspects of process 400 may be implemented by UE 405 and / or base station 410, which may be examples of the corresponding devices described herein.

[0131] At 415, base station 410 may optionally transmit or otherwise provide (and UE 405 may optionally receive or otherwise obtain) configuration signals for configuring semi-persistent resource timing. Configuration signals may include RRC signaling configuring SPS and / or CG configurations for downlink and / or uplink communication between UE 405 and base station 410, respectively. In some aspects, configuration signals may carry or otherwise transmit information identifying one or more tables associated with available release times. For example, configuration signals may indicate or otherwise identify one or more Kc tables to be used for semi-persistent resource timing, wherein each row in the Kc table is associated with a specific release time (e.g., a Kc value). The Kc tables may correspond to newly defined Kc tables explicitly transmitted by signaling, wherein one or more rows correspond to different Kc values. In other aspects, different RRC configurations and / or MAC CE signaling may be used to configure UE 405 via Kc tables.

[0132] At 420, base station 410 may optionally transmit or otherwise provide (and UE 405 may optionally receive or otherwise obtain) an activation DCI for activating a semi-persistent resource timing. The activation DCI may carry or otherwise transmit information identifying various transmission parameters that will be used for communications performed using the activated semi-persistent resource timing.

[0133] Accordingly, at 425, UE 405 and base station 410 can perform communication based on semi-persistent resource timings. For example, communication may include uplink and / or downlink communication using one or more configured and active SPS timings and / or CG timings, respectively.

[0134] At 430, base station 410 may identify or otherwise determine a release time for the set of opportunities for UE 405 to release semi-persistent resources. The release time may be related to the reception time of the DCI for releasing the semi-persistent resources. For example, the release time may be an offset between the last symbol of the released DCI and the release time at the symbol level, micro-slot level, and / or slot level. In some aspects, the release time may be based on a network-configured Nc value; for example, base station 410 may ensure that the release time is at least equal to or greater than Nc. In some aspects, the release time may be based on the capabilities of UE 405. For example, UE 405 may send or otherwise provide a UE capability message to base station 410 indicating the processing time of UE 405. The processing time may correspond to the time spent by UE 405 to receive and decode the released DCI and to perform the release. Accordingly, in some examples, base station 410 may identify, determine, or otherwise select a release time for the semi-persistent resource opportunities based on UE capabilities.

[0135] At 435, base station 410 may transmit or otherwise provide (and UE 405 may receive or otherwise obtain) a DCI (e.g., a release DCI) for a set of release opportunities for semi-persistent resources. In some aspects, the release DCI may carry or otherwise transmit an indication of the release time. For example, the release DCI may include a TDRA value corresponding to a row in a TDRA table. The row in the TDRA table may correspond to a specific Kc value, which defines the offset between the last symbol of the release DCI and the release time. In another example, the release DCI may explicitly carry or otherwise transmit a Kc field indicating the Kc value, such as a K1 field similar to that carried in some DCIs.

[0136] Accordingly at 440, UE 405 may identify or otherwise determine the release time of the set of opportunities to release semi-persistent resources, wherein the release time is related to the reception time of the released DCI (e.g., the last symbol). For example, UE 405 may determine the last symbol associated with the release of the DCI and determine the release time based on the last symbol of the DCI within the DCI itself (e.g., the Kc value indicated in the DCI). In response at 445, UE 405 may release the set of opportunities to release semi-persistent resources according to the release time of the released DCI.

[0137] In some aspects, one or more of the semi-persistent resource opportunities may occur between the receipt of the DCI release and the release time. In this case, UE 405 and base station 410 may continue communication during the semi-persistent resource opportunity that occurs between the receipt of the DCI release and the release time.

[0138] In some aspects, one or more of the semi-persistent resource opportunities may begin at or after the release time. In this case, UE 405 and base station 410 may avoid performing communication during the semi-persistent resource opportunity that begins at or after the release time. For example, UE 405 and / or base station 410 may discard any portion of the monitored and / or decoded semi-persistent resource opportunity, and / or may not provide HARQ-ACK feedback reports for these semi-persistent resource opportunities that begin at or after the release time.

[0139] In some aspects, one or more of the semi-persistent resource timings may begin before the release time and end after the release time (e.g., they may overlap with the release time). In this case, different options can be used for overlapping semi-persistent resource timings. That is, different methods can be used when UE 405 and / or base station 410 identify or otherwise determine that one or more of the semi-persistent resource timings begin before the release time and end after the release time.

[0140] One option may include UE 405 and base station 410 continuing communication during one or more semi-persistent resource moments that overlap with the release time. For example, UE 405 (in the downlink example) and / or base station 410 (in the uplink example) may continue monitoring / decoding communication during the overlapping semi-persistent resource moments and provide HARQ-ACK feedback reports accordingly. For example, UE 405 (in the downlink example) may send or otherwise transmit a feedback message including acknowledgment information for the overlapping semi-persistent resource moments. In the uplink example, base station 410 may send or otherwise transmit a feedback message including acknowledgment information for the overlapping semi-persistent resource moments.

[0141] Another option may include UE 405 and base station 410 avoiding continued communication during one or more semi-persistent resource moments that overlap with the release time. For example, UE 405 (in the downlink example) and / or base station 410 (in the uplink example) may drop or release any monitored / decoded communication during the overlapping semi-persistent resource moments, and may also avoid providing HARQ-ACK feedback reports accordingly.

[0142] Figure 5 A block diagram 500 of a device 505 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Device 505 may be an example of an aspect of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0143] Receiver 510 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to semi-persistent resource release timing signaling). The information may be transmitted to other components of device 505. Receiver 510 may use a single antenna or a collection of antennas.

[0144] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to semi-persistent resource release timing signaling). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may use a single antenna or a collection of multiple antennas.

[0145] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components for performing aspects of semi-persistent resource release timing signaling as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0146] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., as communication management circuitry). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0147] Additionally or alternatively, in some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented as code executed by a processor (e.g., as communication management software or firmware). If implemented as processor-executed code, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0148] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 520 may receive information from the receiver 510, send information to the transmitter 515, or integrate with the receiver 510, transmitter 515, or both in combination to receive information, send information, or perform various other operations as described herein.

[0149] Communication manager 520 may support wireless communication at the UE according to examples disclosed herein. For example, communication manager 520 may be configured as or otherwise support a component for performing communication between the UE and the base station based on a set of semi-persistent resource opportunities. Communication manager 520 may be configured as or otherwise support a component for receiving a DCI for releasing a set of semi-persistent resource opportunities. Communication manager 520 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource opportunities, wherein the release time of the set of semi-persistent resource opportunities is related to the reception time of the DCI. Communication manager 520 may be configured as or otherwise support a component for releasing a set of semi-persistent resource opportunities based on a DCI at a release time.

[0150] According to the examples described herein, by including or configuring a communication manager 520, device 505 (e.g., a processor that controls or is otherwise coupled to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can support techniques for reducing ambiguity between the base station and the UE regarding the timing of the release of semi-persistent resources. This can improve communication between the UE and the base station and reduce system overhead, unnecessary retransmissions, etc.

[0151] Figure 6 A block diagram 600 of a device 605 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] Receiver 610 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels regarding semi-persistent resource release timing signaling). The information may be transmitted to other components of device 605. Receiver 610 may use a single antenna or a collection of antennas.

[0153] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels regarding semi-persistent resource release timing signaling), user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may use a single antenna or a collection of multiple antennas.

[0154] Device 605 or its various components may be examples of parts for performing aspects of semi-persistent resource release timing signaling as described herein. For example, communication manager 620 may include resource communication manager 625, release DCI manager 630, release timing manager 635, release manager 640, or any combination thereof. Communication manager 620 may be an example of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with receiver 610, transmitter 615, or both, to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or integrate with receiver 610, transmitter 615, or a combination thereof to receive information, transmit information, or perform various other operations as described herein.

[0155] Communication manager 620 may support wireless communication at the UE according to examples disclosed herein. Resource communication manager 625 may be configured as or otherwise support a component for performing communication between the UE and the base station based on a set of semi-persistent resource timings. Release DCI manager 630 may be configured as or otherwise support a component for receiving DCIs for the set of semi-persistent resource timings. Release timing manager 635 may be configured as or otherwise support a component for determining the release time for the set of semi-persistent resource timings, wherein the release time for the set of semi-persistent resource timings is related to the DCI reception time. Release manager 640 may be configured as or otherwise support a component for releasing the set of semi-persistent resource timings based on DCIs at release times.

[0156] Figure 7 A block diagram 700 of a communication manager 720 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both described herein. The communication manager 720 or its various components may be examples of parts for performing aspects of the semi-persistent resource release timing signaling as described herein. For example, the communication manager 720 may include a resource communication manager 725, a release DCI manager 730, a release timing manager 735, a release manager 740, a release timing indication manager 745, a resource timing usage manager 750, a release timing manager 755, a UE capability manager 760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0157] Communication manager 720 may support wireless communication at the UE according to examples disclosed herein. Resource communication manager 725 may be configured as or otherwise support a component for performing communication between the UE and the base station based on a set of semi-persistent resource timings. Release DCI manager 730 may be configured as or otherwise support a component for receiving DCIs for the set of semi-persistent resource timings. Release timing manager 735 may be configured as or otherwise support a component for determining the release time for the set of semi-persistent resource timings, wherein the release time for the set of semi-persistent resource timings is related to the DCI reception time. Release manager 740 may be configured as or otherwise support a component for releasing the set of semi-persistent resource timings based on DCIs at release times.

[0158] In some examples, to support the determination of release time, the release timing indicator manager 745 may be configured as, or otherwise support, a component for receiving an indication of the release time in the DCI. In some examples, the release timing indicator manager 745 may be configured as, or otherwise support, a component for receiving a configuration signal that includes an indication of one or more tables associated with the available release time, wherein the determination of the release time is based on the configuration signal and the DCI. In some examples, the configuration signal includes at least one of a first RRC configuration signal configuring a set of semi-persistent resource timings, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0159] In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource timings occurring between the received DCI and the release time, based on communication and DCI. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for performing communication between the UE and the base station during one or more semi-persistent resource timings based on this identification. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource timings that begin before the release time and end after the release time, based on communication and DCI. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for performing communication between the UE and the base station during one or more semi-persistent resource timings based on this identification.

[0160] In some examples, to support the execution of communication, the resource timing usage manager 750 may be configured as, or otherwise support, a component for sending feedback messages associated with communication between the UE and the base station during one or more semi-persistent resource timings and based on a release time. These feedback messages indicate acknowledgment information for the one or more semi-persistent resource timings. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource timings that begin before the release time and end after the release time, based on communication and DCI. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for avoiding the execution of communication between the UE and the base station during one or more semi-persistent resource timings based on this identification. In some examples, to support the avoidance of communication, the resource timing usage manager 750 may be configured as, or otherwise support, a component for discarding communication executed during one or more semi-persistent resource timings. In some examples, to support the avoidance of communication, the resource timing usage manager 750 can be configured as, or otherwise support, a component for avoiding the transmission of feedback messages associated with dropped communication between the UE and the base station during one or more semi-persistent resource timings and based on the release time. The feedback messages indicate acknowledgment information for one or more semi-persistent resource timings.

[0161] In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource timings that begin at or after a release time based on communication and DCI. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for avoiding communication between the UE and the base station during one or more semi-persistent resource timings based on this identification. In some examples, the resource timing usage manager 750 may be configured as, or otherwise support, a component for sending a feedback message associated with communication between the UE and the base station based on a release time, the feedback message indicating confirmation information for one or more semi-persistent resource timings selected from a set of semi-persistent resource timings based on the release time and DCI.

[0162] In some examples, to support the determination of release time, the release time manager 755 may be configured as, or otherwise support, a component for determining the last symbol associated with the DCI. In some examples, to support the determination of release time, the release time manager 755 may be configured as, or otherwise support, a component for determining the release time based on the last symbol associated with the DCI and the DCI.

[0163] In some examples, the UE capability manager 760 can be configured as, or otherwise support, a component for sending UE capability messages that indicate the UE processing time associated with UE processing DCI, wherein the release time is based on the UE processing time.

[0164] In some examples, the release time is based on at least one of the symbol offset, micro-slot offset, slot offset, or a combination thereof between the DCI and the release time. In some examples, the set of semi-persistent resource timings includes downlink SPS resource timings, uplink CG resource timings, or both.

[0165] Figure 8 A schematic diagram of a system 800 including device 805 supporting semi-persistent resource release timing signaling is shown according to aspects of this disclosure. Device 805 may be an example of a component of device 505, device 605, or UE 115 described herein, or may include components of device 505, device 605, or UE 115 described herein. Device 805 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 805 may include components for bidirectional voice and data communication, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840, including components for transmitting and receiving communications. These components may communicate electronically via one or more buses (e.g., bus 845) or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0166] The I / O controller 810 can manage the input and output signals of the device 805. The I / O controller 810 can also manage peripheral devices not integrated into the device 805. In some cases, the I / O controller 810 can represent the physical connection or port to an external peripheral device. In some cases, the I / O controller 810 can use an operating system, such as... Or other known operating systems. Additionally or alternatively, the I / O controller 810 may represent, or interact with, a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via the I / O controller 810 or hardware components controlled by the I / O controller 810.

[0167] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825 capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825 described herein, or via a wired or wireless link. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem to modulate packets and provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be examples of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof described herein.

[0168] Memory 830 may include random access memory (RAM) and read-only memory (ROM). Memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 835 may not be directly executable by processor 840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 830 may contain a basic I / O system (BIOS) that can control basic hardware or software operations, such as interaction with peripheral components or devices.

[0169] Processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting semi-persistent resource release timing signaling). For example, device 805 or components of device 805 may include processor 840 and memory 830 coupled to processor 840, processor 840 and memory 830 being configured to perform the various functions described herein.

[0170] Communication manager 820 may support wireless communication at the UE according to examples as disclosed herein. For example, communication manager 820 may be configured as or otherwise support a component for performing communication between the UE and the base station based on a set of semi-persistent resource opportunities. Communication manager 820 may be configured as or otherwise support a component for receiving a DCI for releasing a set of semi-persistent resource opportunities. Communication manager 820 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource opportunities, wherein the release time of the set of semi-persistent resource opportunities is related to the reception time of the DCI. Communication manager 820 may be configured as or otherwise support a component for releasing a set of semi-persistent resource opportunities based on a DCI at a release time.

[0171] According to the examples described herein, by including or configuring a communication manager 820, device 805 can support techniques for reducing ambiguity between the base station and the UE regarding the timing of the release of semi-persistent resources. This can improve communication between the UE and the base station and reduce system overhead, unnecessary retransmissions, etc.

[0172] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). While the communication manager 820 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by processor 840, memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by processor 840 to cause device 805 to perform aspects of the semi-persistent resource release timing signaling as described herein, or processor 840 and memory 830 may be otherwise configured to perform or support these operations.

[0173] Figure 9 A block diagram 900 of an apparatus 905 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Apparatus 905 may be an example of an aspect of base station 105 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Apparatus 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0174] Receiver 910 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels regarding semi-persistent resource release timing signaling). The information may be transmitted to other components of device 905. Receiver 910 may use a single antenna or a collection of antennas.

[0175] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels regarding semi-persistent resource release timing signaling), user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may use a single antenna or a collection of multiple antennas.

[0176] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components for performing aspects of semi-persistent resource release timing signaling as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0177] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., as communication management circuitry). The hardware may include processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0178] Additionally or alternatively, in some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented as processor-executable code (e.g., as communication management software or firmware). If implemented as processor-executable code, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0179] In some examples, the communication manager 920 can be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 920 can receive information from the receiver 910, send information to the transmitter 915, or integrate with the receiver 910, transmitter 915, or a combination of both to receive information, send information, or perform various other operations as described herein.

[0180] Communication manager 920 may support wireless communication at a base station according to examples disclosed herein. For example, communication manager 920 may be configured as or otherwise support a component for performing communication between the base station and the UE based on a set of semi-persistent resource opportunities. Communication manager 920 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource opportunities for the UE to release, wherein the release time of the set of semi-persistent resource opportunities for the UE to release is related to the reception time of the DCI. Communication manager 920 may be configured as or otherwise support a component for transmitting the DCI for releasing the set of semi-persistent resource opportunities, wherein the set of semi-persistent resource opportunities is released at the UE based on the release time of the DCI.

[0181] According to the examples described herein, by including or configuring the communication manager 920, device 905 (e.g., a processor that controls or is otherwise coupled to receiver 910, transmitter 915, communication manager 920, or a combination thereof) can support techniques for improving UE power consumption, reducing overhead communication, and reducing ambiguity between the base station and the UE regarding HARQ-ACK feedback signaling.

[0182] Figure 10 A block diagram 1000 of a device 1005 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or base station 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0183] Receiver 1010 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels regarding semi-persistent resource release timing signaling). The information may be transmitted to other components of device 1005. Receiver 1010 may use a single antenna or a collection of antennas.

[0184] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels regarding semi-persistent resource release timing signaling), user data, control information, or any combination thereof. In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may use a single antenna or a collection of multiple antennas.

[0185] Device 1005 or its various components may be examples of parts for performing aspects of semi-persistent resource release timing signaling as described herein. For example, communication manager 1020 may include resource communication manager 1025, release timing manager 1030, release DCI manager 1035, or any combination thereof. Communication manager 1020 may be an example of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with receiver 1010, transmitter 1015, or both, to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or a combination thereof to receive information, transmit information, or perform various other operations as described herein.

[0186] Communication manager 1020 may support wireless communication at the base station according to examples disclosed herein. Resource communication manager 1025 may be configured as or otherwise support a component for performing communication between the base station and the UE based on a set of semi-persistent resource timings. Release time manager 1030 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource timings for the UE to release, wherein the release time of the set of semi-persistent resource timings for the UE is related to the reception time of the DCI. Release DCI manager 1035 may be configured as or otherwise support a component for transmitting the DCI for releasing the set of semi-persistent resource timings, wherein the set of semi-persistent resource timings is released at the UE based on the release time of the DCI.

[0187] Figure 11A block diagram 1100 of a communication manager 1120 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of parts for performing aspects of the semi-persistent resource release timing signaling as described herein. For example, the communication manager 1120 may include a resource communication manager 1125, a release timing manager 1130, a release DCI manager 1135, a release timing indication manager 1140, a resource usage manager 1145, a feedback manager 1150, a UE capability manager 1155, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0188] Communication manager 1120 may support wireless communication at the base station according to examples disclosed herein. Resource communication manager 1125 may be configured as or otherwise support a component for performing communication between the base station and the UE based on a set of semi-persistent resource timings. Release time manager 1130 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource timings for the UE to release, wherein the release time of the set of semi-persistent resource timings for the UE is related to the reception time of the DCI. Release DCI manager 1135 may be configured as or otherwise support a component for transmitting the DCI for releasing the set of semi-persistent resource timings, wherein the set of semi-persistent resource timings is released at the UE based on the release time of the DCI.

[0189] In some examples, the release time indication manager 1140 may be configured as, or otherwise support, a component for sending an indication of the release time in the DCI. In some examples, the release time indication manager 1140 may be configured as, or otherwise support, a component for sending a configuration signal that includes an indication of one or more tables associated with the available release time, wherein the release time is based on the configuration signal and the DCI. In some examples, the configuration signal includes at least one of a first RRC configuration signal configuring a set of semi-persistent resource timings, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0190] In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource opportunities occurring between the received DCI and the release time, based on communication and DCI. In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for performing communication between the base station and the UE during one or more semi-persistent resource opportunities based on that identification.

[0191] In some examples, the resource usage manager 1145 may be configured as, or otherwise support a component for identifying one or more semi-persistent resource periods that begin before the release time and end after the release time, based on communication and DCI. In some examples, the resource usage manager 1145 may be configured as, or otherwise support a component for performing communication between the base station and the UE during one or more semi-persistent resource periods based on this identification. In some examples, to support the performance of communication, the resource usage manager 1145 may be configured as, or otherwise support a component for receiving feedback messages associated with communication between the base station and the UE during one or more semi-persistent resource periods and based on the release time, the feedback messages indicating acknowledgment information for the one or more semi-persistent resource periods.

[0192] In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource moments that begin before the release time and end after the release time based on communication and DCI. In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for avoiding communication between the base station and the UE during one or more semi-persistent resource moments based on this identification.

[0193] In some examples, to support avoiding communication, the resource usage manager 1145 may be configured as, or otherwise support, a component for avoiding receiving feedback messages associated with dropped communication between the UE and the base station during one or more semi-persistent resource periods and based on a release time. The feedback messages indicate acknowledgment information for one or more semi-persistent resource periods. In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for identifying one or more semi-persistent resource periods that begin at or after the release time based on communication and DCI. In some examples, the resource usage manager 1145 may be configured as, or otherwise support, a component for avoiding communication between the base station and the UE during one or more semi-persistent resource periods based on this identification.

[0194] In some examples, the feedback manager 1150 may be configured as or otherwise support a component for receiving feedback messages associated with communication between the base station and the UE based on the release time, the feedback messages indicating confirmation information for one or more semi-persistent resource timings selected based on the release time and DCI from a set of semi-persistent resource timings.

[0195] In some examples, to support the determination of release time, the release time manager 1130 may be configured as, or otherwise support, a component for determining the last symbol associated with the DCI. In some examples, to support the determination of release time, the release time manager 1130 may be configured as, or otherwise support, a component for determining the release time based on the last symbol associated with the DCI and the DCI.

[0196] In some examples, the UE capability manager 1155 may be configured as, or otherwise support, a component for receiving UE capability messages indicating a UE processing time associated with UE processing DCI, wherein the release time is based on the UE processing time. In some examples, the release time is based on at least one of a symbol offset, a microslot offset, a slot offset, or a combination thereof between the DCI and the release time. In some examples, the set of semi-persistent resource timings includes downlink SPS resource timings, uplink CG resource timings, or both.

[0197] Figure 12 A schematic diagram of a system 1200 including device 1205 supporting semi-persistent resource release timing signaling is shown according to aspects of this disclosure. Device 1205 may be an example of a component of device 905, device 1005, or base station 105 described herein, or may include a component of device 905, device 1005, or base station 105 described herein. Device 1205 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, a network communication manager 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, a processor 840, and an inter-station communication manager 1245. These components may communicate electronically via one or more buses (e.g., bus 1250) or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0198] The network communication manager 1210 can manage (e.g., via one or more wired backhaul links) communication with the core network 130. For example, the network communication manager 1210 can manage the transmission of data communication for client devices (such as one or more UEs 115).

[0199] In some cases, device 1205 may include a single antenna 1225. However, in other cases, device 1205 may have more than one antenna 1225 capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225 described herein, or via a wired or wireless link. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem to modulate packets and provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof described herein.

[0200] Memory 1230 may include RAM and ROM. Memory 1230 may store computer-readable, computer-executable code 1235, including instructions that, when executed by processor 1240, cause device 1205 to perform the various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1230 may contain BIOS, etc., which can control basic hardware or software operations, such as interaction with peripheral components or devices.

[0201] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting semi-persistent resource release timing signaling). For example, device 1205 or components of device 1205 may include processor 1240 and memory 1230 coupled to processor 1240, processor 1240 and memory 1230 being configured to perform the various functions described herein.

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

[0203] Communication manager 1220 may support wireless communication at a base station according to examples disclosed herein. For example, communication manager 1220 may be configured as or otherwise support a component for performing communication between the base station and the UE based on a set of semi-persistent resource timings. Communication manager 1220 may be configured as or otherwise support a component for determining the release time of the set of semi-persistent resource timings for the UE to release, wherein the release time of the set of semi-persistent resource timings for the UE to release is related to the reception time of the DCI. Communication manager 1220 may be configured as or otherwise support a component for transmitting the DCI for releasing the set of semi-persistent resource timings, wherein the set of semi-persistent resource timings is released at the UE based on the release time of the DCI.

[0204] According to the examples described herein, by including or configuring the communication manager 1220, device 1205 can support techniques for reducing ambiguity between the base station and the UE regarding the timing of the release of semi-persistent resources. This can improve communication between the UE and the base station and reduce system overhead, unnecessary retransmissions, etc.

[0205] In some examples, the communication manager 1220 may be configured to use or otherwise cooperate with transceiver 1215, one or more antennas 1225, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). While the communication manager 1220 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by processor 1240, memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions executable by processor 1240 to cause device 1205 to perform aspects of the semi-persistent resource release timing signaling as described herein, or processor 1240 and memory 1230 may be otherwise configured to perform or support these operations.

[0206] Figure 13A flowchart illustrating a method 1300 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be performed by, as referenced... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the described function.

[0207] At 1305, the method may include performing communication between the UE and the base station based on a set of semi-persistent resource timings. The operation of 1305 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by references... Figure 7 The resource communication manager 725 described is used for execution.

[0208] In 1310, the method may include a DCI that receives a set of opportunities to release semi-persistent resources. The operations of 1310 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be derived from references... Figure 7 The description describes how to release the DCI manager 730 for execution.

[0209] In 1315, the method may include determining a release time for a set of opportunities to release semi-persistent resources, wherein the release time of the set of opportunities to release semi-persistent resources is related to the reception time of the DCI. The operation of 1315 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 7 The described release timing manager 735 is used to execute this.

[0210] In 1320, the method may include a set of release times for semi-persistent resources based on DCI at release time. The operations of 1320 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be derived from references... Figure 7 The described release manager 740 is used to execute this.

[0211] Figure 14 A flowchart illustrating a method 1400 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be performed by, as referenced... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the described function.

[0212] At 1405, the method may include performing communication between the UE and the base station based on a set of semi-persistent resource timings. The operation of 1405 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be derived from references... Figure 7 The resource communication manager 725 described is used for execution.

[0213] In 1410, the method may include a DCI that receives a set of opportunities to release semi-persistent resources. The operations of 1410 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be derived from references... Figure 7 The description describes how to release the DCI manager 730 for execution.

[0214] In 1415, the method may include determining a release time for a set of opportunities to release semi-persistent resources, wherein the release time of the set of opportunities to release semi-persistent resources is related to the reception time of the DCI. The operation of 1415 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 7 The described release timing manager 735 is used to execute this.

[0215] In 1420, the method may include a set of release times for semi-persistent resources based on DCI at release time. The operations of 1420 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be derived from references... Figure 7 The described release manager 740 is used to execute this.

[0216] At 1425, the method may include receiving an indication of the release time in the DCI. The operation of 1425 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1425 may be derived from references... Figure 7 The described release timing instruction manager 745 is used to execute it.

[0217] Figure 15 A flowchart illustrating a method 1500 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the described function.

[0218] In 1505, the method may include receiving a configuration signal including an indication of one or more tables associated with the available release time, wherein the release time is determined based on the configuration signal and the DCI. Operation of 1505 can be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by references... Figure 7 The described release timing instruction manager 745 is used to execute it.

[0219] In 1510, the method may include performing communication between the UE and the base station based on a set of semi-persistent resource timings. The operation of 1510 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 7 The resource communication manager 725 described is used for execution.

[0220] In 1515, the method may include a DCI that receives a set of opportunities to release semi-persistent resources. The operations of 1515 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be derived from references... Figure 7 The description describes how to release the DCI manager 730 for execution.

[0221] In 1520, the method may include determining a release time for a set of opportunities to release semi-persistent resources, wherein the release time of the set of opportunities to release semi-persistent resources is related to the reception time of the DCI. The operation of 1520 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 7 The described release timing manager 735 is used to execute this.

[0222] In section 1525, the method may include a set of timings for releasing semi-persistent resources based on DCI at release time. The operations of section 1525 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of section 1525 may be derived from references... Figure 7 The described release manager 740 is used to execute this.

[0223] Figure 16 A flowchart illustrating a method 1600 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Operation of method 1600 can be implemented by a base station or its components as described herein. For example, operation of method 1600 can be performed by [reference to...] Figures 1 to 4 and Figures 9 to 12 The described base station 105 performs this function. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the described function. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the described function.

[0224] In step 1605, the method may include performing communication between the base station and the UE based on a set of semi-persistent resource timings. The operation of step 1605 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of step 1605 may be derived from references... Figure 11 The resource communication manager 1125 described is used to execute this.

[0225] In 1610, the method may include determining a release time for a set of timings for the UE to release semi-persistent resources, wherein the release time of the set of timings for the UE to release semi-persistent resources is related to the DCI reception time. The operation of 1610 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 11 The described release time manager 1130 is used to execute.

[0226] In 1615, the method may include sending a DCI of a set of release opportunities for semi-persistent resources, wherein the set of release opportunities for semi-persistent resources is based on the DCI being released at the UE at the release time. The operation of 1615 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by references... Figure 11 The description describes the release of DCI manager 1135 for execution.

[0227] Figure 17 A flowchart illustrating a method 1700 supporting semi-persistent resource release timing signaling according to aspects of this disclosure is shown. Operation of method 1700 can be implemented by a base station or its components as described herein. For example, operation of method 1700 can be performed by [reference to...] Figures 1 to 4 and Figures 9 to 12 The described base station 105 performs this function. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the described function. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the described function.

[0228] In 1705, the method may include performing communication between the base station and the UE based on a set of semi-persistent resource timings. The operation of 1705 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 11 The resource communication manager 1125 described is used to execute this.

[0229] In 1710, the method may include determining a release time for a set of timings for the UE to release semi-persistent resources, wherein the release time of the set of timings for the UE to release semi-persistent resources is related to the DCI reception time. The operation of 1710 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 11The described release time manager 1130 is used to execute.

[0230] In 1715, the method may include sending a DCI of a set of release opportunities for semi-persistent resources, wherein the set of release opportunities for semi-persistent resources is based on the DCI being released at the UE at the release time. The operation of 1715 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be provided by references... Figure 11 The description describes the release of DCI manager 1135 for execution.

[0231] In 1720, the method may include identifying one or more semi-persistent resource opportunities occurring between the DCI reception time and the release time based on communication and DCI. The operation of 1720 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 11 The described resource uses Manager 1145 to execute.

[0232] In 1725, the method may include performing communication between the base station and the UE during one or more semi-persistent resource opportunities based on the identification. Operation of 1725 can be performed according to examples as disclosed herein. In some examples, aspects of operation of 1725 may be derived from references... Figure 11 The described resource uses Manager 1145 to execute.

[0233] The following provides an overview of aspects of this disclosure:

[0234] Aspect 1: A method for performing wireless communication at a UE, comprising: performing communication between the UE and a base station based at least in part on a set of semi-persistent resource timings; receiving downlink control information for releasing the set of semi-persistent resource timings; determining a release time for releasing the set of semi-persistent resource timings, wherein the release time for releasing the set of semi-persistent resource timings is related to a reception time of the downlink control information; and releasing the set of semi-persistent resource timings at the release time based at least in part on the downlink control information.

[0235] Aspect 2: According to the method of aspect 1, determining the release time includes: receiving an indication of the release time in the downlink control information.

[0236] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: receiving a configuration signal including an indication of one or more tables associated with the available release time, wherein the release time is determined at least in part based on the configuration signal and the downlink control information.

[0237] Aspect 4: According to the method of aspect 3, the configuration signal includes at least one of the following: a first RRC configuration signal for configuring the set of semi-persistent resource timings, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0238] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: identifying, at least in part, one or more semi-persistent resource opportunities occurring between the receipt of the downlink control information and the release time based on the communication and the downlink control information; and performing the communication between the UE and the base station during the one or more semi-persistent resource opportunities based at least in part on the identification.

[0239] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: identifying, at least in part, one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the downlink control information; and performing the communication between the UE and the base station during the one or more semi-persistent resource opportunities based at least in part on the identification.

[0240] Aspect 7: According to the method of aspect 6, performing the communication includes: sending a feedback message associated with the communication between the UE and the base station during the one or more semi-persistent resource timings and at least in part based on the release time, the feedback message indicating confirmation information for the one or more semi-persistent resource timings.

[0241] Aspect 8: The method according to any one of Aspects 1 to 5 further includes: identifying, at least in part, one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the downlink control information; and avoiding the communication between the UE and the base station during the one or more semi-persistent resource opportunities based at least in part on the identification.

[0242] Aspect 9: According to the method of Aspect 8, avoiding the execution of the communication includes: discarding the communication executed during the one or more semi-persistent resource opportunities; and avoiding sending a feedback message associated with the discarded communication between the UE and the base station during the one or more semi-persistent resource opportunities and at least in part based on the release time, the feedback message indicating confirmation information for the one or more semi-persistent resource opportunities.

[0243] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: identifying one or more semi-persistent resource timings that begin at or after the release time, at least in part based on the communication and the downlink control information; and avoiding the communication between the UE and the base station during the one or more semi-persistent resource timings, at least in part based on the identification.

[0244] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: sending a feedback message associated with the communication between the UE and the base station, at least in part based on the release time, the feedback message indicating confirmation information for one or more semi-persistent resource timings selected in the set of semi-persistent resource timings, at least in part based on the release time and the downlink control information.

[0245] Aspect 12: The method according to any one of Aspects 1 to 11, wherein determining the release time includes: determining the last symbol associated with the downlink control information; and determining the release time based at least in part on the last symbol associated with the downlink control information and the downlink control information.

[0246] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: sending a UE capability message indicating a UE processing time associated with the UE processing the downlink control information, wherein the release time is at least partially based on the UE processing time.

[0247] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the release time is based on at least one of the symbol offset, micro-slot offset, slot offset, or combination thereof between the downlink control information and the release time.

[0248] Aspect 15: According to any one of Aspects 1 to 14, the set of semi-persistent resource timings includes downlink SPS resource timings, uplink CG resource timings, or both.

[0249] Aspect 16: A method for wireless communication at a base station, comprising: performing communication between the base station and a UE based at least in part on a set of semi-persistent resource timings; determining a release time for the set of semi-persistent resource timings for the UE to release, wherein the release time of the set of semi-persistent resource timings for the UE is related to a reception time of downlink control information; and transmitting the downlink control information for releasing the set of semi-persistent resource timings, wherein the set of semi-persistent resource timings is released at the UE at the release time based at least in part on the downlink control information.

[0250] Aspect 17: The method according to aspect 16 further includes: sending an indication of the release time in the downlink control information.

[0251] Aspect 18: The method according to any one of Aspects 16 to 17 further includes: sending a configuration signal including an indication of one or more tables associated with an available release time, wherein the release time is based at least in part on the configuration signal and the downlink control information.

[0252] Aspect 19: According to the method of aspect 18, the configuration signal includes at least one of the following: a first RRC configuration signal for configuring the set of semi-persistent resource timings, a second RRC configuration signal different from the first RRC configuration signal, a MAC CE, or a combination thereof.

[0253] Aspect 20: The method according to any one of Aspects 16 to 19 further includes: identifying, at least in part, one or more semi-persistent resource opportunities occurring between the receipt of the downlink control information and the release time based on the communication and the downlink control information; and performing the communication between the base station and the UE, at least in part, based on the identification during the one or more semi-persistent resource opportunities.

[0254] Aspect 21: The method according to any one of Aspects 16 to 20 further includes: identifying, at least in part, one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the downlink control information; and performing the communication between the base station and the UE, at least in part, based on the identification during the one or more semi-persistent resource opportunities.

[0255] Aspect 22: According to the method of aspect 21, performing the communication includes: receiving a feedback message associated with the communication between the base station and the UE during the one or more semi-persistent resource timings and at least in part based on the release time, the feedback message indicating confirmation information for the one or more semi-persistent resource timings.

[0256] Aspect 23: The method according to any one of Aspects 16 to 20 further includes: identifying, at least in part, one or more semi-persistent resource opportunities that begin before the release time and end after the release time based on the communication and the downlink control information; and avoiding the communication between the base station and the UE during the one or more semi-persistent resource opportunities based at least in part on the identification.

[0257] Aspect 24: According to the method of aspect 23, avoiding communication includes: avoiding receiving feedback messages associated with dropped communication between the UE and the base station during the one or more semi-persistent resource timings and at least in part based on the release time, the feedback messages indicating confirmation information for the one or more semi-persistent resource timings.

[0258] Aspect 25: The method according to any one of Aspects 16 to 24 further includes: identifying one or more semi-persistent resource timings that begin at or after the release time, at least in part based on the communication and the downlink control information; and avoiding the communication between the base station and the UE during the one or more semi-persistent resource timings, at least in part based on the identification.

[0259] Aspect 26: The method according to any one of Aspects 16 to 25 further includes: receiving, at least in part, a feedback message associated with the communication between the base station and the UE based on the release time, the feedback message indicating confirmation information for one or more semi-persistent resource timings selected, at least in part, based on the release time and the downlink control information, from the set of semi-persistent resource timings.

[0260] Aspect 27: The method according to any one of Aspects 16 to 26, wherein determining the release time includes: determining the last symbol associated with the downlink control information; and determining the release time based at least in part on the last symbol associated with the downlink control information and the downlink control information.

[0261] Aspect 28: The method according to any one of Aspects 16 to 27 further includes: receiving a UE capability message indicating a UE processing time associated with the UE processing the downlink control information, wherein the release time is at least partially based on the UE processing time.

[0262] Aspect 29: The method of any one of Aspects 16 to 28, wherein the release time is based on at least one of the symbol offset, micro-slot offset, slot offset, or combination thereof between the downlink control information and the release time.

[0263] Aspect 30: According to any one of Aspects 16 to 29, the set of semi-persistent resource timings includes downlink SPS resource timings, uplink CG resource timings, or both.

[0264] Aspect 31: An apparatus for wireless communication at a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform any of the methods of aspects 1 to 15.

[0265] Aspect 32: An apparatus for wireless communication at a UE, comprising at least one component for performing the method of any one of Aspects 1 to 15.

[0266] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform any of the methods of aspects 1 to 15.

[0267] Aspect 34: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform any of the methods of aspects 16 to 30.

[0268] Aspect 35: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of aspects 16 to 30.

[0269] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform any of the methods of aspects 16 to 30.

[0270] It should be noted that the methods described herein depict possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0271] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems are described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR can be used in most descriptions, the techniques described herein can be applied beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0272] The information and signals described herein can be represented using any of a variety of different processes and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0273] The various exemplary blocks and components described in connection with this disclosure can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0274] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in different locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0275] Computer-readable media include both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store required program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave) are all included in the definition of computer-readable media. As used herein, disks and discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. The above combinations also fall within the scope of computer-readable media.

[0276] As used herein, the word "or" (e.g., a list of items ending with phrases such as "at least one of..." or "one or more of...") in the claims indicates an inclusive list, such that a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, the phrase "based on" as used herein should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0277] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, different components of the same type can be distinguished by a dash immediately following the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the specification, this specification applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0278] The specification described herein, in conjunction with the accompanying drawings, describes exemplary configurations and does not represent all examples that may be implemented or fall within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration," and not "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0279] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions, stored in the memory and executable by the processor, enable the device to: The communication between the UE and the network device is performed at least in part based on a set of semi-persistent resource opportunities; Receive downlink control information, the downlink control information including an indication of the set of release timings for semi-persistent resources, and including an indication of the time offset between the last symbol of the downlink control information and the release time of the set of release timings for semi-persistent resources; The release time of the set of opportunities for releasing semi-persistent resources is determined at least in part based on the time offset value and the last symbol of the downlink control information; and The set of times for releasing semi-persistent resources at the release time is based at least in part on the indication of the time offset value in the downlink control information.

2. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Receive a configuration signal including an indication of one or more tables associated with available time offset values ​​including the time offset value, wherein the release time is determined at least in part based on the configuration signal and the downlink control information.

3. The apparatus of claim 2, wherein the configuration signal includes at least one of the following: a first Radio Resource Control (RRC) configuration signal for configuring the set of semi-persistent resource timings, a second RRC configuration signal different from the first RRC configuration signal, a Media Access Control (MAC) element (CE), or a combination thereof.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource occurrences between the receipt of the downlink control information and the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the UE and the network device is performed at least in part based on the identification during one or more semi-persistent resource opportunities.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events that begin before the release time and end after the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the UE and the network device is performed at least in part based on the identification during one or more semi-persistent resource opportunities.

6. The apparatus of claim 5, wherein the instructions for performing the communication are executable by the processor to cause the apparatus to: A feedback message associated with the communication between the UE and the network device is sent during the one or more semi-persistent resource opportunities and at least in part based on the release time. The feedback message indicates confirmation information for the one or more semi-persistent resource opportunities.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events that begin before the release time and end after the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the UE and the network device is avoided at least in part based on the identification during one or more semi-persistent resource opportunities.

8. The apparatus of claim 7, wherein the instruction to avoid performing the communication can be executed by the processor to cause the apparatus to: Discard communications performed during the one or more semi-persistent resource events; and During the one or more semi-persistent resource opportunities and at least in part based on the release time, feedback messages associated with dropped communications between the UE and the network device are avoided, the feedback messages indicating confirmation information for the one or more semi-persistent resource opportunities.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events, starting at or after the release time, is identified at least in part based on the communication and the downlink control information; and The communication between the UE and the network device is avoided at least in part based on the identification during one or more semi-persistent resource opportunities.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A feedback message associated with the communication between the UE and the network device is sent at least in part based on the release time, the feedback message indicating confirmation information for one or more semi-persistent resource opportunities selected at least in part based on the release time and the downlink control information from the set of semi-persistent resource opportunities.

11. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Send a UE capability message indicating the UE processing time associated with the UE processing the downlink control information, wherein the time offset value is at least partially based on the UE processing time.

12. The apparatus of claim 1, wherein the time offset value includes at least one of the following: symbol offset after the last symbol of the downlink control information, micro-slot offset, slot offset, or a combination thereof.

13. The apparatus of claim 1, wherein the set of semi-persistent resource opportunities includes downlink semi-persistent scheduling (SPS) resource opportunities, uplink configuration grant (CG) resource opportunities, or both.

14. The apparatus of claim 1, wherein the time offset value is greater than or equal to a default processing time, and wherein the default processing time corresponds to the number of times the UE receives, processes, and responds to the downlink control information.

15. An apparatus for wireless communication at a network device, comprising: processor; Memory coupled to the processor; as well as Instructions, stored in the memory and executable by the processor, enable the device to: The communication between the network device and the user equipment (UE) is performed at least in part based on a set of semi-persistent resource opportunities; The release time of the set of conditions for the UE to release semi-persistent resources is determined, based at least in part on the time offset value and the last symbol of the downlink control information. and The downlink control information is sent, the downlink control information including an indication of the set of semi-persistent resource release opportunities and an indication of the time offset value, wherein the set of semi-persistent resource release opportunities is released at the UE at the release time based on the time offset value in the downlink control information and the last symbol of the downlink control information.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: Send a configuration signal including an indication of one or more tables associated with an available time offset value including the time offset value, wherein the release time is based at least in part on the configuration signal and the downlink control information.

17. The apparatus of claim 16, wherein the configuration signal comprises at least one of the following: a first Radio Resource Control (RRC) configuration signal configuring the set of semi-persistent resource timings; a second RRC configuration signal different from the first RRC configuration signal; a Media Access Control (MAC) element (CE); or a combination thereof.

18. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource occurrences between the receipt of the downlink control information and the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the network device and the UE is performed at least in part based on the identification during one or more semi-persistent resource opportunities.

19. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events that begin before the release time and end after the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the network device and the UE is performed at least in part based on the identification during one or more semi-persistent resource opportunities.

20. The apparatus of claim 19, wherein the instructions for performing the communication are executable by the processor to cause the apparatus to: During the one or more semi-persistent resource timings and at least in part based on the release time, a feedback message associated with the communication between the network device and the UE is received, the feedback message indicating confirmation information for the one or more semi-persistent resource timings.

21. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events that begin before the release time and end after the release time is identified, at least in part, based on the communication and the downlink control information; and The communication between the network device and the UE is avoided at least in part based on the identification during one or more semi-persistent resource opportunities.

22. The apparatus of claim 21, wherein the instruction to avoid performing the communication can be executed by the processor to cause the apparatus to: During the one or more semi-persistent resource opportunities and at least in part based on the release time, feedback messages associated with dropped communications between the UE and the network device are avoided, the feedback messages indicating confirmation information for the one or more semi-persistent resource opportunities.

23. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The timing of one or more semi-persistent resource events, starting at or after the release time, is identified at least in part based on the communication and the downlink control information; and The communication between the network device and the UE is avoided at least in part based on the identification during one or more semi-persistent resource opportunities.

24. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The system receives, at least in part, a feedback message associated with the communication between the network device and the UE, based on the release time. The feedback message indicates confirmation information for one or more semi-persistent resource opportunities selected, at least in part, based on the release time and the downlink control information, from the set of semi-persistent resource opportunities.

25. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: Receive a UE capability message indicating a UE processing time associated with the UE processing the downlink control information, wherein the time offset value is at least partially based on the UE processing time.

26. The apparatus of claim 15, wherein the time offset value is greater than or equal to a default processing time, and wherein the default processing time corresponds to the number of times the UE receives, processes, and responds to the downlink control information.

27. A method for conducting wireless communication at a user equipment (UE), comprising: The communication between the UE and the network device is performed at least in part based on a set of semi-persistent resource opportunities; Receive downlink control information, the downlink control information including an indication of the set of release timings for semi-persistent resources, and including an indication of the time offset between the last symbol of the downlink control information and the release time of the set of release timings for semi-persistent resources; The release time of the set of opportunities for releasing semi-persistent resources is determined at least in part based on the time offset value and the last symbol of the downlink control information; and The set of times for releasing semi-persistent resources at the release time is based at least in part on the indication of the time offset value in the downlink control information.

28. The method of claim 27, wherein the time offset value is greater than or equal to the default processing time, and wherein the default processing time corresponds to the number of times the UE receives, processes, and responds to the downlink control information.

29. A method for wireless communication at a network device, comprising: The communication between the network device and the user equipment (UE) is performed at least in part based on a set of semi-persistent resource opportunities; The release time of the set of conditions for the UE to release semi-persistent resources is determined, based at least in part on the time offset value and the last symbol of the downlink control information. and The downlink control information is sent, the downlink control information including an indication of the set of semi-persistent resource release opportunities and an indication of the time offset value, wherein the set of semi-persistent resource release opportunities is released at the UE at the release time based on the time offset value in the downlink control information and the last symbol of the downlink control information.

30. The method of claim 29, wherein the time offset value is greater than or equal to the default processing time, and wherein the default processing time corresponds to the number of times the UE receives, processes, and responds to the downlink control information.

31. An apparatus for wireless communication at a user equipment (UE), comprising components for performing the method according to any one of claims 27-28.

32. An apparatus for wireless communication at a network device, comprising components for performing the method according to any one of claims 29-30.

33. A computer-readable medium having one or more computer instructions recorded thereon, which, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the method according to any one of claims 27-28.

34. A computer-readable medium having one or more computer instructions recorded thereon, which, when executed by one or more processors of a network device, cause the one or more processors to perform the method according to any one of claims 29-30.

35. A computer program product comprising one or more computer instructions, which, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the method according to any one of claims 27-28.

36. A computer program product comprising one or more computer instructions, which, when executed by one or more processors of a network device, cause the one or more processors to perform the method according to any one of claims 29-30.

Images