Management of overlapping semi-persistent scheduling (SPS) configured physical downlink shared channel (PDSCH) transmission occasions

By identifying and managing the timing of SPS PDSCH transmissions in a wireless communication system and applying a conflict avoidance process, the problem of overlapping transmission timing conflicts is resolved, thereby improving resource utilization and communication efficiency.

CN116569633BActive Publication Date: 2026-04-21QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
QUALCOMM INC
Filing Date
2021-07-30
Publication Date
2026-04-21

AI Technical Summary

Technical Problem

In wireless communication systems, existing technologies struggle to effectively manage and resolve conflicts in the transmission timing of Physical Downlink Shared Channel (PDSCH) with overlapping Semi-Persistent Scheduling (SPS) configurations, leading to resource waste and reduced communication efficiency.

Method used

User equipment (UE) identifies and manages multiple SPS PDSCH transmission opportunities, applies the SPS PDSCH transmission opportunity conflict avoidance process, and adjusts the transmission opportunities in response to SPS release or activation information to avoid conflicts, thereby ensuring the effective utilization of resources.

Benefits of technology

It improves the resource utilization of wireless communication systems, reduces transmission timing conflicts, and enhances communication efficiency and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116569633B_ABST
    Figure CN116569633B_ABST
Patent Text Reader

Abstract

Some aspects of this disclosure disclose methods and systems related to managing overlapping Physical Downlink Shared Channel (PDSCH) transmission timings configured with Semi-Persistent Scheduling (SPS). In some aspects, a User Equipment (UE) can identify one or more SPS PDSCH transmission timings in a time slot, and receive from a Base Station (BS) via a Physical Downlink Control Channel (PDCCH) an SPS release configured to release the SPS configuration, including a configuration index, at the UE. The UE can then perform an SPS PDSCH transmission timing conflict avoidance procedure while releasing the SPS PDSCH transmission timings to manage overlapping SPS PDSCH transmission timings.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Patent Application No. 17 / 444,024, filed July 29, 2021, and U.S. Provisional Patent Application No. 63 / 062,793, filed August 7, 2020, the entire contents of which are incorporated herein by reference, as fully set forth below, and for all applicable purposes. Technical Field

[0003] In summary, the following text relates to wireless communication, and more specifically, to the management of overlapping Physical Downlink Shared Channel (PDSCH) transmission timings configured with Semi-Persistent Scheduling (SPS). 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 (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, 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 base station or network access node simultaneously supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)).

[0005] In wireless communication systems operating according to 3GPP Releases 15 and 16, transmissions on one or more channels are scheduled to allow multiple devices to communicate using one or more channels. Scheduling is the process of allocating resources for transmitting data. New Radio (NR) scheduling is determined by the network (e.g., gNodeB or gNB) and by the user equipment (UE) following network instructions. The overall scheduling mechanism in NR is similar to Long Term Evolution (LTE) scheduling, but NR has a finer granularity compared to LTE, especially in terms of time-domain scheduling at the physical layer. There are two types of scheduling for downlink communication (e.g., from gNodeB to UE). One is called "dynamic scheduling," and the other is called SPS (semi-persistent scheduling). Dynamic scheduling is a mechanism in which each and every Physical Downlink Shared Channel (PDSCH) is scheduled via Downlink Control Indicators or Downlink Control Information (DCI). SPS is a mechanism in which PDSCH transmissions are scheduled via RRC messages (or DCI). PDSCHs are divided into time slots in which data is transmitted. User data services are transmitted between the gNodeB and the UE in the PDSCH, and the UE sends necessary acknowledgment / negative acknowledgment (ACK / NACK) reports at specified times on the uplink channel. Summary of the Invention

[0006] The following outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This overview is not a general summary of all anticipated features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in an overview form as a prelude to the more detailed description that follows.

[0007] Some aspects of this disclosure disclose a method for wireless communication performed by a user equipment (UE). The method includes: identifying multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and receiving from a base station (BS) and via a physical downlink control channel (PDCCH) an SPS release configured to release a semi-persistent scheduling (SPS) configuration including a configuration index at the UE. In some aspects, the SPS configuration may be configured to schedule an SPS PDSCH transmission opportunity associated with a configuration index among multiple SPS PDSCH transmission opportunities in a time slot. The method further includes: performing a first action or a second action in response to receiving the SPS release. The first action includes releasing the SPS PDSCH transmission opportunity associated with the configuration index, followed by applying a first SPS PDSCH transmission opportunity conflict avoidance procedure to a first set of SPS PDSCH transmission opportunities, wherein the first set of SPS PDSCH transmission opportunities includes multiple SPS PDSCH transmission opportunities (e.g., those remaining after releasing the SPS PDSCH transmission opportunity associated with the configuration index). The second action involves applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set, and then releasing the SPS PDSCH transmission timing associated with the configuration index, wherein the second SPS PDSCH transmission timing set includes multiple SPS PDSCH transmission timings.

[0008] In some aspects, a method of wireless communication performed by a user equipment (UE) includes identifying one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and receiving from a base station (BS) and via a physical downlink control channel (PDCCH) SPS activation downlink control information (DCI) configured to activate a semi-persistent scheduling (SPS) configuration at the UE. In some aspects, the SPS configuration may include a configuration index and be configured to schedule SPS PDSCH transmission opportunities associated with the configuration index. Some aspects of the method also include, in response to receiving SPS activation, activating or reactivating an SPS PDSCH transmission opportunity associated with the configuration index based on: a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transmission opportunity in the same time slot as the SPS PDSCH transmission opportunity associated with the configuration index; or a comparison of a first result of applying a first SPS PDSCH transmission opportunity conflict avoidance procedure with a second result of applying a second SPS PDSCH transmission opportunity conflict avoidance procedure. In this respect, a first SPS PDSCH transmission timing conflict avoidance process can be applied to a first SPS PDSCH transmission timing set that includes one or more SPS PDSCH transmission timings; and a second SPS PDSCH transmission timing conflict avoidance process can be applied to a second SPS PDSCH transmission timing set that includes SPS PDSCH transmission timings associated with a configuration index and one or more SPS PDSCH transmission timings.

[0009] Some aspects of this disclosure disclose a user equipment (UE) including a transceiver and a processor. In some aspects, the processor is configured to identify multiple Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) transmission opportunities in a time slot. Further, the transceiver may be configured to receive, from a base station (BS) and via a Physical Downlink Control Channel (PDCCH), an SPS release configured to release a SPS configuration including a configuration index at the UE. In some aspects, the SPS configuration may be configured to schedule an SPS PDSCH transmission opportunity associated with a configuration index among multiple SPS PDSCH transmission opportunities in a time slot. In some aspects, the processor may also be configured to perform the first or second action described above in response to receiving an SPS release.

[0010] Some aspects of this disclosure disclose a user equipment (UE) including a transceiver and a processor. In some aspects, the processor is configured to identify one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot. Further, the transceiver may be configured to receive, from a base station (BS) and via a physical downlink control channel (PDCCH), SPS activated downlink control information (DCI) configured to activate a semi-persistent scheduling (SPS) configuration at the UE, the SPS configuration including a configuration index and configured to schedule SPSPDSCH transmission opportunities associated with the configuration index, and the processor is also configured to respond to receiving SPS activation. In some aspects, the processor can be configured to activate or reactivate an SPS PDSCH transport timing associated with a configuration index based on: a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transport timing in the same time slot as the SPS PDSCH transport timing associated with the configuration index; or a comparison of a first result of applying a first SPS PDSCH transport timing conflict avoidance procedure with a second result of applying a second SPS PDSCH transport timing conflict avoidance procedure, wherein the first SPS PDSCH transport timing conflict avoidance procedure is applied to a first set of SPS PDSCH transport timings including one or more SPS PDSCH transport timings; and the second SPS PDSCH transport timing conflict avoidance procedure is applied to a second set of SPS PDSCH transport timings, the second set of SPS PDSCH transport timings including the SPS PDSCH transport timing associated with the configuration index and one or more SPS PDSCH transport timings.

[0011] Some aspects of this disclosure disclose a non-transitory computer-readable medium (CRM) having program code recorded thereon. In some aspects, the program code includes code for causing a user equipment (UE) to identify a plurality of semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and code for causing the UE to receive from a base station (BS) and via a physical downlink control channel (PDCCH) an SPS release configured to release a semi-persistent scheduling (SPS) configuration including a configuration index at the UE, wherein the SPS configuration is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among a plurality of SPS PDSCH transmission opportunities in a time slot. In some aspects, the program code includes code for causing the UE to perform the first or second action described above in response to receiving the SPS release.

[0012] Some aspects of this disclosure disclose a non-transitory computer-readable medium (CRM) having program code recorded thereon. In some aspects, the program code includes code for causing a user equipment (UE) to identify one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and code for causing the UE to receive SPS activated downlink control information (DCI) configured to activate the semi-persistent scheduling (SPS) configuration at the UE from a base station (BS) and via a physical downlink control channel (PDCCH). In some aspects, the SPS configuration includes a configuration index and is configured to schedule SPS PDSCH transmission opportunities associated with the configuration index. The program code also includes code for causing the UE to activate or reactivate an SPSPDSCH transmission timing associated with a configuration index in response to receiving SPS activation, based on: a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transmission timing in the same time slot as the SPS PDSCH transmission timing associated with the configuration index; or a comparison of a first result of applying a first SPS PDSCH transmission timing conflict avoidance procedure with a second result of applying a second SPS PDSCH transmission timing conflict avoidance procedure, wherein the first SPS PDSCH transmission timing conflict avoidance procedure is applied to a first set of SPS PDSCH transmission timings including one or more SPS PDSCH transmission timings; and the second SPS PDSCH transmission timing conflict avoidance procedure is applied to a second set of SPS PDSCH transmission timings, the second set of SPSPDSCH transmission timings including the SPS PDSCH transmission timings associated with the configuration index and one or more SPSPDSCH transmission timings.

[0013] Some aspects of this disclosure disclose a user equipment (UE) including: a unit for identifying multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and a unit for receiving from a base station (BS) and via a physical downlink control channel (PDCCH) an SPS release configured to release a semi-persistent scheduling (SPS) configuration including a configuration index at the UE, wherein the SPS configuration is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among multiple SPS PDSCH transmission opportunities in a time slot. The UE also includes a unit for performing the first or second action described above in response to receiving the SPS release.

[0014] Some aspects of this disclosure disclose a user equipment (UE) including: a unit for identifying one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; and a unit for receiving from a base station (BS) and via a physical downlink control channel (PDCCH) SPS activated downlink control information (DCI) configured to activate a semi-persistent scheduling (SPS) configuration at the UE, wherein the SPS configuration includes a configuration index and is configured to schedule SPS PDSCH transmission opportunities associated with the configuration index. The UE also includes the ability to activate or reactivate an SPS PDSCH transmission timing associated with a configuration index in response to receiving SPS activation, based on: a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transmission timing in the same time slot as the SPS PDSCH transmission timing associated with the configuration index; or a comparison of a first result of applying a first SPS PDSCH transmission timing conflict avoidance procedure with a second result of applying a second SPS PDSCH transmission timing conflict avoidance procedure, wherein the first SPS PDSCH transmission timing conflict avoidance procedure is applied to a first set of SPS PDSCH transmission timings including one or more SPS PDSCH transmission timings; and the second SPS PDSCH transmission timing conflict avoidance procedure is applied to a second set of SPS PDSCH transmission timings, the second set of SPS PDSCH transmission timings including the SPS PDSCH transmission timing associated with the configuration index and one or more SPS PDSCH transmission timings.

[0015] Other aspects, features, and embodiments will become apparent to those skilled in the art after reviewing the following description of specific exemplary embodiments in conjunction with the accompanying drawings. While features may be discussed hereinafter with respect to certain embodiments and drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used according to the various embodiments discussed herein. Similarly, while exemplary embodiments may be discussed hereinafter as embodiments of devices, systems, or methods, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0016] Figure 1 This illustrates some aspects of wireless communication networks according to this disclosure.

[0017] Figure 2This illustration shows an example diagram of an organization utilizing radio resources in an air interface employing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects of this disclosure.

[0018] Figure 3 An example illustration is provided showing the timing of overlapping Physical Downlink Shared Channel (PDSCH) transmissions configured via Semi-Persistent Scheduling (SPS) in accordance with some aspects of this disclosure.

[0019] Figure 4 An example illustration is shown of managing overlapping PDSCH transmission timings configured by SPS, according to some aspects of this disclosure.

[0020] Figure 5 An example illustration is shown of managing overlapping PDSCH transmission timings configured by SPS, according to some aspects of this disclosure.

[0021] Figure 6 An example illustration is shown of managing overlapping PDSCH transmission timings configured by SPS, according to some aspects of this disclosure.

[0022] Figure 7 An example illustration is shown of managing overlapping PDSCH transmission timings configured by SPS, according to some aspects of this disclosure.

[0023] Figure 8 This is a block diagram of a user equipment (UE) based on some aspects of this disclosure.

[0024] Figure 9 This is a block diagram of an exemplary base station (BS) based on various aspects of this disclosure.

[0025] Figure 10 A flowchart illustrating a wireless communication method according to some aspects of this disclosure is shown.

[0026] Figure 11 A flowchart illustrating a wireless communication method according to some aspects of this disclosure is provided. Detailed Implementation

[0027] The detailed description described below, in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be implemented. To provide a full understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some cases, to avoid obscuring these concepts, well-known structures and components are shown in block diagram form.

[0028] This disclosure generally relates to wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus can be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, fifth-generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" are used interchangeably.

[0029] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and Flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are either known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration among various telecommunications association groups aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond, which involve shared access to the radio spectrum between networks using some new and different radio access technologies or radio air interfaces.

[0030] In particular, 5G networks are expected to enable diverse deployments, diverse spectrum, and diverse services and devices using a unified OFDM-based air interface. To achieve these goals, in addition to the development of new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are considered. 5G NR will be able to extend to provide coverage for: (1) for ultra-high density (e.g., ~1M nodes / km) 2(1) Coverage for large-scale Internet of Things (IoT) with ultra-low complexity (e.g., ~10 s bits / second), ultra-low energy (e.g., ~10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) Coverage for mission-critical control with strong security for protecting sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 ms), and coverage for users with a wide range of mobility or lack of mobility; and (3) Coverage with enhanced mobile broadband, including extremely high capacity (e.g., ~10 Tbps / km). 2 Extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with improved discovery and optimization.

[0031] 5G NR communication systems can be implemented using optimized OFDM-based waveforms with scalable digital schemes (numerology) and transmission time intervals (TTI). Additional features may include a common, flexible framework for efficiently multiplexing services and features using dynamic, low-latency Time Division Duplex (TDD) / Frequency Division Duplex (FDD) designs; and improved wireless technologies such as massive MIMO, robust millimeter-wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital schemes in 5G NR (with scaling of subcarrier spacing (SCS)) efficiently addresses the operation of diverse services across diverse spectrum and deployments. For example, in various outdoor and macro coverage deployments using FDD / TDD implementations below 3 GHz, the SCS can occur at 15 kHz, for example, over bandwidths (BW) of 5, 10, or 20 MHz. For various other outdoor and small cell coverage deployments using TDD above 3 GHz, the SCS can be deployed at 30 kHz over an 80 / 100 MHz band. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, the SCS can be deployed at 60 kHz over a 160 MHz band. Finally, for various deployments utilizing mmWave components of TDD at 28 GHz, the SCS can be deployed at 120 kHz over a 500 MHz band.

[0032] 5G NR's scalable digital schemes facilitate scalable TTIs for diverse latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to begin at symbol boundaries. 5G NR also anticipates self-contained, integrated subframe designs with uplink (UL) / downlink (DL) scheduling information, data, and acknowledgments within the same subframe. These self-contained, integrated subframes support communication in unlicensed or contention-based shared spectrum, and adaptive UL / downlink (which can be flexibly configured per cell to dynamically switch between UL and DL to meet current service demands).

[0033] The following further describes various other aspects and features of this disclosure. It should be apparent that the teachings herein can be embodied in a wide variety of forms, and that any specific structure, function, or both disclosed herein are merely representative and not limiting. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and that two or more of these aspects can be combined in various ways. For example, an apparatus or a method can be implemented using any number of the aspects set forth herein. Furthermore, such an apparatus or a method can be implemented using structures, functions, or structures and functions other than or different from one or more of the aspects set forth herein. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. Furthermore, an aspect may include at least one element of the claims.

[0034] In wireless communication networks operating according to 3GPP Releases 15 and 16, multiple active semi-persistent scheduling (SPS) configurations for a given bandwidth portion (BWP) of a serving cell can be supported to enhance reliability and reduce latency for data services or service types such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), etc. The maximum number of permitted (CG) configurations per BWP of the serving cell is 12, and user equipment (UE) can have multiple SPS configurations (and a single SPS configuration can be shared among several UEs). A base station (e.g., gNB) can activate or deactivate SPS configurations via downlink control information (DCI). In some cases, a base station can activate an SPS configuration individually, for example, by activating a DCI (e.g., DCI formats 0_0, 0_1, and 0_2), but not jointly. That is, joint activation of multiple SPS configurations may not be supported. The DCI activating an SPS configuration may include a Hybrid Automatic Repeat Request (HARQ) Procedure Number (HPN) field, which indicates the configuration index of the SPS configuration being activated via the DCI. In some cases, up to four least significant bits of the HPN field may be present to indicate the SPS configuration being activated. In 3GPP Release 16, the minimum SPS period was reduced to one slot.

[0035] In some cases, joint and individual releases of multiple SPS configurations for a given BWP of the serving cell can be supported. For example, a base station can send a release DCI (e.g., DCI format 0_0, 0_1, and 0_2) including a configuration index to identify the SPS configuration to be released via the DCI. In some cases, up to four least significant bits of the HPN field can be present to indicate the SPS configuration being released (e.g., individually or jointly) via the release DCI. In the case of an individual release of an SPS configuration, the HPN in the release DCI can indicate the index of the SPS configuration that can be released via the release DCI. In the case of a joint release of multiple SPS configurations via a single DCI, and where the state table is a higher-level configuration, states can be used to indicate the single or multiple SPS configurations to be released, where each state can be mapped to a single or multiple SPS configurations. In the case of no higher-level configuration states, individual releases can be used, where the release can correspond to the SPS configuration index indicated by the release DCI. The code point via the HPN can be mapped to a row index of the configured state table. For example, row 0 of the RRC table used for the joint release of SPS configuration can be mapped to configuration indices 1 and 3, row 1 can be mapped to configuration indices 0 and 2, and row 2 can be mapped to configuration index 4.

[0036] Typically, a UE can send a HARQ acknowledgment (ACK) or negative acknowledgment (NACK) to the base station to notify the base station of the successful or unsuccessful arrival of data sent to the UE (e.g., via the Physical Downlink Shared Channel (PDSCH)). HARQ is a technique well known to those skilled in the art, where the integrity of packet transmission can be verified for accuracy at the receiving end, for example, using any suitable integrity verification mechanism, such as checksum or Cyclic Redundancy Check (CRC). If the integrity of the transmission is confirmed, an ACK can be sent; otherwise, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement appending, incremental redundancy, etc.

[0037] For Type 1 and Type 2 HARQ-ACK codebook constructions, a HARQ-ACK bit can be generated for the release of a transmission timing configured by SPS using the joint release DCI (e.g., SPS PDSCH release). The HARQ-ACK codebook can refer to a mechanism for sending multiple ACK / NACK bits in the same transmission, such as determining the number and order of ACK / NACK bits. The position of the HARQ-ACK bit for the SPS PDSCH release using a separate release DCI can be derived based on the TDRA table row index indicated in the active DCI and the PDSCH-to-HARQ timing indicator K1 indicated in the release DCI.

[0038] In some cases, multiple SPS-configured PDSCHs (hereinafter referred to herein as "SPS-configured PDSCH transmission opportunities") configured with different SPS configurations may overlap in time slots. The UE can follow an SPS PDSCH transmission opportunity conflict avoidance procedure (hereinafter referred to as the "SPS PDSCH conflict avoidance procedure") to resolve potential conflicts (i.e., overlaps) between overlapping SPS PDSCH transmission opportunities, so that the UE can determine non-overlapping SPS PDSCH transmission opportunities for receiving data or transmissions from the base station to which the UE is connected. In some cases, the number of non-overlapping SPS PDSCH transmission opportunities may depend on the UE's capabilities. To determine the non-overlapping SPS PDSCH transmission timing for receiving transmissions based on multiple overlapping SPS PDSCH transmission timings (e.g., SPS-configured PDSCH transmission timings that may not have corresponding PDCCH transmissions), the UE may perform the following steps after resolving overlaps with symbols in the time slot indicated as uplinks by tdd-UL-DL-ConfigurationCommon (tdd-UL-DL-Common Configuration) or tdd-UL-DL-ConfigurationDedicated (tdd-UL-DL-Dedicated Configuration). At step 0, the UE may set j = 0, where j is the number of PDSCHs(multiple) selected for decoding. Q is the set of active PDSCHs in the time slot that do not have corresponding PDCCH transmissions. At step 1, the UE may receive a PDSCH with the lowest configured SPS configuration index in Q, and set j = j + 1. Further, the UE may designate the received PDSCH as a survivor PDSCH. At step 2, the surviving PDSCH from step 1, as well as any other PDSCH(s) that overlap (even partially overlap) with the surviving PDSCH from step 1, can be excluded from Q. At step 3, the UE can repeat steps 1 and 2 until Q is empty or j equals the number of unicast PDSCHs supported by the UE in the time slot. The SPS PDSCH collision avoidance procedure is further discussed in the following document: 3GPP document TS 38.214, entitled “Technical Specification 5G; NR; Physical layer procedures for data (3GPP TS 38.214 version 16.2.0 Release 16)”, the entire contents of which are incorporated herein by reference in July 2020.

[0039] When releasing an SPS configuration for a transmission opportunity scheduled via PDSCH (i.e., releasing a "SPSPDSCH" or "SPS-configured PDSCH transmission opportunity"), the SPS release (instead referred to herein as "SPS release PDCCH") can be sent to the UE via the PDCCH and can occur in the same time slot as the SPSPDSCH (e.g., in the radio frame structure of a 5G network). In some aspects, it will be understood that what is scheduled is an SPS-configured PDSCH transmission opportunity, and not an actual transmission. Whether a transmission occurs may depend on whether the SPS-configured PDSCH transmission opportunity overlaps with other SPS-configured PDSCH transmission opportunities and how the UE resolves overlaps, conflicts, or contradictions, as discussed in this disclosure. The SPS release can occur before the end or termination of reception by the UE in the same time slot for an SPS PDSCH with an SPS configuration to be released via SPS release. In other words, the UE can support receiving the SPS release PDCCH before the end of the reception of the SPS PDSCH with the same SPS configuration corresponding to the SPS release PDCCH. If the HARQ-ACK for the SPS release and the SPS PDSCH reception will map to the same Physical Uplink Control Channel (PUCCH), then a one-bit HARQ-ACK can be generated for the SPS release, and the UE may not expect to receive the SPS PDSCH (e.g., no data or SPS PDSCH is received at the UE). Furthermore, if the HARQ-ACK for the SPS release and the SPS PDSCH reception will map to the same PUCCH, then the SPS release may not be received after the end or termination of the reception of the SPS PDSCH with the SPS configuration to be released via SPS release in the same time slot.

[0040] In 3GPP Release 15, the UE can generate a Type 1 HARQ-ACK codebook based on the corresponding time-domain timing of the PDSCH. Furthermore, the UE can report a 1-bit HARQ-ACK for the SPS PDCCH. In this case, there may be no PDSCH timing for the SPS release of the PDCCH. To report the HARQ-ACK for the SPS release of the PDCCH, the UE can place the HARQ-ACK in the HARQ-ACK codebook at the position corresponding to the corresponding PDSCH timing. That is, the position in the Type 1 HARQ-ACK codebook for the HARQ-ACK information corresponding to a single SPS PDSCH release can be the same as the position for the corresponding SPS PDSCH reception. Furthermore, the position in the Type 1 HARQ-ACK codebook for the HARQ-ACK information corresponding to multiple SPS PDSCH releases via a single DCI format can be the same as the position for the corresponding SPS PDSCH reception with the lowest SPS configuration index among the multiple SPS PDSCH releases. Additional details relating to SPS and HARQ-ACK feedback for SPS are discussed in the following document: 3GPP document TS 38.213, entitled “Technical Specification 5G; NR; Physical layer procedures for control (3GPP TS38.213 version 16.2.0 Release 16)”, the entire contents of which are incorporated herein by reference in July 2020.

[0041] As discussed above, the UE can receive multiple SPS-configured PDSCH transmission opportunities (i.e., multiple SPS-configured PDSCH transmission opportunities associated with different SPS configurations that may overlap in time slots) and can follow the SPS PDSCH conflict avoidance procedure to resolve conflicts that may occur between overlapping SPS PDSCH transmission opportunities, so that the UE can determine non-overlapping SPS PDSCH transmission opportunities for receiving data or transmissions from the base station to which the UE is connected. Furthermore, the UE can also receive an SPS release PDCCH including a configuration index or an SPS release PDCCH associated with a configuration index, the SPS release PDCCH being configured to release SPS-configured PDSCH transmission opportunities with the same configuration index among the multiple SPS-configured PDSCH transmission opportunities. In such a situation, there may be ambiguity regarding which occurs first, because applying the SPS PDSCH collision avoidance process first, followed by releasing the SPS-configured PDSCH transmission timing with the configuration index first, may leave different non-overlapping SPS PDSCH transmission timings compared to first releasing the SPS-configured PDSCH transmission timing with the configuration index first, followed by applying the SPS PDSCH collision avoidance process. Various aspects of this disclosure provide solutions for these and related scenarios associated with managing overlapping SPS-configured Physical Downlink Shared Channel (PDSCH) transmission timings.

[0042] While aspects and embodiments are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or uses may arise via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations can exist. Implementations can range from a spectrum of chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessary include additional components and features for the implementation and enforcement of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors(s), interleavers, adders / summers, etc.). It is intended that the innovations described herein be implemented in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of different sizes, shapes, and constructions.

[0043] Figure 1 An example wireless communication network 100 is illustrated according to some aspects of this disclosure. 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 improved 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, or communication with low-cost and low-complexity devices, or any combination thereof.

[0044] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or 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, on which UE 115 and base station 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographical area on which base station 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0045] 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 a device of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein may be able to communicate 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). Figure 1 As shown.

[0046] Base station 105 can communicate with core network 130, communicate with each other, or perform both of the above operations. For example, base station 105 can interface with core network 130 through one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both of the above operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0047] 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 transceiver, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB, evolved NodeB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), home NodeB, home eNodeB, or some other suitable term.

[0048] 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, and other examples. 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, and other examples, which may be implemented in various articles such as electrical appliances, vehicles, meters, and other examples.

[0049] The UE 115 described in this document may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as repeaters, as well as base station 105 and network devices (including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations and other examples) Figure 1 As shown.

[0050] UE 115 and base station 105 can communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency 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 of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for 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 operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0051] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition signaling or control signaling to coordinate operation against 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 (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. The carrier may operate in standalone mode, where initial acquisition and connection can be performed by UE 115 via the carrier, or the carrier may operate in non-standalone mode, where connection is anchored using different carriers (e.g., the same or different radio access technologies).

[0052] 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).

[0053] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a defined number of bandwidths 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) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configurable to support communication over 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 on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0054] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Extended OFDM (DFT-S-OFDM). In a system employing MCM, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried through each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for UE 115 can potentially be. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0055] It can support one or more digital schemes (numerologies) for a carrier, where the digital scheme can include subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured to have multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be limited to one or more active BWPs.

[0056] The time interval for base station 105 or UE 115 can be in the form of a basic time unit (which may, for example, refer to T). s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N. f It can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resource 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).

[0057] 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 a number of 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 a number of symbol periods (e.g., depending on the length of the cyclic prefix added before 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. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0058] Subframes, time slots, micro-slots, or symbols can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain), and can be referred to as transmission time intervals (TTIs). In some examples, the duration of a TTI (e.g., the number of symbol periods in a TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0059] Additionally, it's important to note that the subcarrier spacing (SCS) has an impact on the number of symbols (such as OFDM symbols) within a subframe. Specifically, as the SCS spacing widens or increases, the time slot length will shorten. For example, a scheduling cell (e.g., a base station or gNB) might have an SCS of 15 kHz (i.e., the spacing parameter μ = 0 in a known spacing digital scheme, where the SCS or frequency spacing Δf is determined by the equation Δf = 2). μ(determined by x 15kHz), 15kHz SCS is typically the shortest SCS interval used, and a scheduled cell (e.g., UE) can utilize a 120kHz SCS (i.e., interval parameter μ = 3 in a known interval numbering scheme) (for the purposes of this example), but those skilled in the art will understand that this disclosure applies to any SCS interval within a number of SCS intervals. In known systems, a 15kHz SCS will generate a (1) millisecond (ms) time slot, which can also constitute the entire 1ms subframe. A 120kHz SCS will generate eight time slots with a duration of 1 / 8 or 0.125ms within the 1ms subframe. These time slots can represent eight PDSCH transmissions in the scheduled cell via PDCCH scheduling in the scheduling cell. It is worth noting that in this example, when 15kHz SCS and 120kHz SCS are used for two cells respectively, a single time slot of the scheduling cell overlaps temporally with eight time slots of the scheduled cell. However, other SCS values ​​will result in other digital schemes and overlaps, such as in the example of 15kHz SCS in the scheduling cell and 60kHz SCS in the scheduled cell (i.e., μ=2), where one time slot of the scheduling cell overlaps with four time slots of the scheduled cell.

[0060] Physical channels can be multiplexed on a carrier using various techniques. For example, physical control channels and physical data channels can be multiplexed on a downlink carrier using one or more of time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by the number of 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., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search for control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. The aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set configured to send control information to a specific UE 115.

[0061] 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., on a carrier) for communication 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), or others). 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 the logical communication entity operates. Depending on various factors (such as the capabilities of base station 105), such cells may 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, or external space between or overlapping geographic coverage areas 110, and other examples.

[0062] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-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 residence 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.

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

[0064] In some examples, base station 105 may be mobile, and therefore 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.

[0065] 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 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0066] Some UE 115s (e.g., MTC or IoT devices) can be low-cost or low-complexity devices, and can be prepared for 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 such information to a central server or application that utilizes the information or presents it to humans interacting with the application. Some UE 115s 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, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0067] Some UE 115s can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception instead of simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, when 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.

[0068] 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 can include private or group communication, and can be supported through one or more mission-critical services such as Mission-Critical Push-to-Talk (MCPTT), Mission-Critical Video (MCVideo), or Mission-Critical Data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can 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.

[0069] In some examples, UE 115 may also be able to communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UEs 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 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, groups of UEs 115s communicating via D2D communication may 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 UEs 115 without involving base station 105.

[0070] 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, the vehicle may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. The vehicle may signal information relating to traffic conditions, signal control, weather, safety, emergencies, or any other information relating to the V2X system. In some examples, a vehicle in a V2X system may communicate with roadside infrastructure (such as a roadside unit), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0071] 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, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to network operator IP service 150. Carrier IP services 150 may include access to the Internet, (multiple) intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0072] 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 transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport 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 headends and ANCs) or combined into a single network device (e.g., base station 105).

[0073] 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 extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently penetrating structures to provide service to the UE 115 located indoors via a macrocell. Transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to the transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum, such as the High Frequency (HF) or Very High Frequency (VHF) portions.

[0074] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to 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 respective devices can be smaller and more closely spaced compared to UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, EHF transmissions may suffer even greater atmospheric attenuation and shorter distances compared to SHF or UHF transmissions. The techniques disclosed herein can be employed for transmissions using one or more different frequency regions, and the designated use of frequency bands spanning those frequency regions may vary depending on the country or regulatory authority.

[0075] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency 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 frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0076] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to 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 (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in various geographical locations. Base station 105 may have an antenna array having a number of rows and columns of antenna ports that base station 105 can use to support beamforming of communications with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0077] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be called 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) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0078] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to form or guide antenna beams (e.g., transmit beams, receive beams) 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 relative to a specific orientation of the antenna array experience constructive interference, while other signals 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 the device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0079] As part of beamforming operations, base station 105 or UE 115 may use beam scanning techniques. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform 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 sets of beamforming weights 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 transmissions or receptions by base station 105.

[0080] Some signals (such as data signals associated with a specific receiving device) may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with the 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 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 that has the highest signal quality or otherwise acceptable signal quality.

[0081] In some examples, transmissions performed by a device (e.g., by base station 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate combined beams for transmissions (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams spanning the system bandwidth or one or more subbands. Base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback on beam selection, which may be a precoding 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 in relation 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 beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

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

[0083] 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 transmission over 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 the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0084] 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 used to increase the likelihood of data being correctly received on 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 throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0085] UE 115 can select values ​​for scheduling or time slot offset parameters in a radio frame structure representing resources (e.g., time-frequency resources) for signal communication between UE 115 and base station 105. The requested values ​​for the parameter set are at least partially based on system state information of UE 115 and attributes related to the operability or activity mode of an application performed or operated on UE 115. UE 115 can send the selected values ​​for the parameter set to base station 105. UE 115 can receive values ​​configured for the time slot offset parameter set for UE 115, at least partially, in response to the selected values ​​for the parameter set sent to base station 105. UE 115 can then communicate with base station 105 according to the configured parameters.

[0086] Figure 2This illustration shows an example diagram of the organization of radio resources in an air interface utilizing Orthogonal Frequency Division Multiplexing (OFDM) according to some aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to, for example, DFT-s-OFDMA or SC-FDMA waveforms in essentially the same manner as described herein. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA or SC-FDMA waveforms. Figure 2 The diagram shows an expanded view of an exemplary subframe 202, illustrating the OFDM resource grid. However, as will be readily apparent to those skilled in the art, the PHY transmission structure for any particular application can differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction, in OFDM symbols; and frequency is in the vertical direction, in subcarriers of a carrier.

[0087] The radio frame structure or resource grid 204 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding multiple of resource grids 204 can be available for communication. Resource grid 204 is divided into multiple resource elements (REs) 206. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs may be called a physical resource block (PRB) or more simply a resource block (RB) 208, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number independent of the digital scheme used. In some examples, depending on the digital scheme, an RB may include any appropriate number of consecutive OFDM symbols in the time domain. Within this disclosure, in some aspects it may be assumed that a single RB (such as RB208) corresponds entirely to a single communication direction (transmission or reception for a given device).

[0088] Scheduling for downlink, uplink, or sidelink transmissions by a UE or sidelink device (hereinafter collectively referred to as UE) typically involves scheduling one or more resource elements 206 within one or more subbands. Therefore, the UE typically utilizes only a subset of the resource grid 204. In some examples, an RB can be the smallest unit of resources that can be allocated to the UE. Therefore, the more RBs scheduled for the UE, and the more sophisticated the modulation scheme selected for the air interface, the higher the data rate for the UE. RBs can be scheduled by the base station (e.g., gNB, eNB, etc.) or by the UE / sidelink device implementing D2D sidelink communication.

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

[0090] Based on some examples, a frame can refer to a duration of 10 ms, where each frame is subdivided into 10 subframes, each 1 ms in length. Each 1 ms subframe may include one or more adjacent time slots. Figure 2 In the example shown, subframe 202 includes four time slots 210 as an illustrative example. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., 1, 2, or 3 OFDM symbols). These micro-time slots or shortened TTIs may, in some cases, be transmitted using resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0091] An expanded view of time slot 210 shows the time slot as including a control region 212 and a data region 314. Typically, control region 312 may carry a control channel (e.g., PDCCH), and data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, the time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 2The simple structure shown is merely exemplary in nature, and different time slot structures can be utilized, and different time slot structures can include one or more of each of the control region(s) and data region(s).

[0092] Although not in Figure 2 As shown, each RE 206 within RB 208 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 206 within RB 208 can also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), or sounding reference signals (SRS). These pilot or reference signals can prepare the receiving equipment for channel estimation of the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0093] In some examples, time slot 210 can be used for broadcast or unicast communication. For example, broadcast, multicast, or multicast communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast communication is delivered to multiple intended receiving device devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0094] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 206 (e.g., within control area 212) to carry DL control information destined for one or more scheduled entities (e.g., UEs). The DL control information includes one or more DL control channels, such as PBCH; PSS; SSS; Physical Control Format Indicator Channel (PCFICH); Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH); and / or Physical Downlink Control Channel (PDCCH), etc. The PCFICH provides information to assist the receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), which includes, but is not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, permission, and / or assignment of REs for DL ​​and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those skilled in the art, in which the integrity of packet transmission can be verified for accuracy at the receiving end, for example using any suitable integrity verification mechanism, such as checksum or cyclic redundancy check (CRC). If the integrity of the transmission is verified, an ACK can be sent; otherwise, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement appending, incremental redundancy, etc.

[0095] In UL transmissions, the scheduled entity may use one or more RE 306s to carry UL control information (UCI) destined for the scheduling entity. The UCI includes one or more UL control channels, such as the Physical Uplink Control Channel (PUCCH). The UCI can include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the UCI, the scheduling entity may send downlink control information (DCI), which can schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, Channel State Feedback (CSF), or any other suitable UCI.

[0096] In addition to control information, one or more REs 206 (e.g., within data area 214) can be allocated for user data services. Such services can be carried on one or more traffic channels (such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions, or the Physical Uplink Shared Channel (PUSCH) for UL transmissions). In some examples, one or more REs 206 within data area 214 can be configured to carry a System Information Block (SIB), carrying information that enables access to a given cell.

[0097] In an example of sidelink communication on a sidelink carrier via the PC5 interface, the control area 212 of time slot 210 may include a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a V2X or other sidelink device) to a set of one or more other receiving sidelink devices. The PSCCH may include HARQ feedback information (e.g., ACK / NACK), which can be used to indicate whether retransmission is required or not on the sidelink. The data area 214 of time slot 210 may include a Physical Sidelink Shared Channel (PSSCH), which includes data transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device.

[0098] The physical channels described above are typically multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS) (which can correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0099] The channels or carriers described above are not necessarily all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity (e.g., one of one or more UEs 106), and those skilled in the art will recognize that other channels or carriers, such as other service, control and feedback channels, may be used in addition to the channels or carriers shown.

[0100] Figure 3This illustration shows examples of managing overlapping Physical Downlink Shared Channel (PDSCH) transmission timings configured with Semi-Persistent Scheduling (SPS) according to some aspects of this disclosure. In some aspects, the UE receives an SPS release PDCCH from the base station (BS) and via the Physical Downlink Control Channel (PDCCH), the SPS release PDCCH being configured to release the SPS configuration at the UE. In some cases, the SPS configuration may include a configuration index or be associated with a configuration index, and may be configured to schedule SPS PDSCH transmission timings associated with the same configuration index within a time slot. In some cases, a time slot may also have multiple SPS-configured PDSCH transmission timings (also referred to as SPS PDSCH transmission timings without corresponding PDCCH transmissions), some of which may overlap with each other and / or overlap with SPS PDSCH transmission timings associated with the configuration index of the SPS release. Multiple SPS-configured PDSCH transmission timings may be configured through different SPS configurations (i.e., through SPS configurations with different configuration indices). For example, Figure 3 The illustration shows an example of SPS release 302, which is received by the UE in a time slot and includes or is associated with a configuration index (e.g., index = 0). SPS release can be configured to release an SPS configuration configured for an SPS PDSCH transmission timing 304 associated with the same configuration index = 0. In some aspects, the same time slot may also include multiple transmission timings 306, 308, 310, and 312, each configured with an SPS configuration including or associated with a different configuration index.

[0101] In some aspects, SPS release can be configured to jointly release multiple SPS configurations. Although the discussion in this disclosure is presented in the context of individual SPS configuration releases, i.e., SPS configurations are released via individual SPS release PDCCHs, the same aspects apply when SPS release PDCCHs jointly release multiple SPS configurations. That is, all the techniques discussed throughout this disclosure for managing the timing of SPS-configured PDSCH transmissions can be applied to situations where SPS release PDCCHs jointly release two or more SPS PDSCHs among multiple PDSCHs in a time slot.

[0102] In some respects, the UE can resolve conflicts or contradictions arising from overlapping PDSCH transmission times configured by SPS by first releasing the SPS PDSCH transmission time associated with the same configuration index as the SPS release, and then applying the SPS PDSCH conflict avoidance procedure to the remaining SPS PDSCH transmission times (i.e., SPS PDSCH transmission times without corresponding PDCCH transmissions), as discussed above. In other words, if there are more than one PDSCH in the serving cell, each without a corresponding PDCCH transmission, in the time slot, after resolving overlaps with symbols in the time slot indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and after removing PDSCHs due to the SPS release of PDCCHs received in the time slot, the UE can receive one or more PDSCHs without corresponding PDCCH transmissions in the time slot by applying the SPS PDSCH conflict avoidance procedure mentioned above, as discussed below. Figure 3 As shown.

[0103] exist Figure 3 When the UE receives an SPS release 302 with configuration index 0, it first releases the SPS-configured PDSCH transmission opportunity 304 associated with configuration index 0, as indicated by “X” and ①, to indicate that the SPS-configured PDSCH transmission opportunity 304 is the first to be released. The UE can then apply the SPS PDSCH conflict avoidance procedure to the remaining SPS-configured PDSCH transmission opportunities 306, 308, 310, and 312 in the time slot after the release of the SPS-configured PDSCH transmission opportunity 304. The first step of the process is to release or remove the SPS-configured PDSCH transmission timing 308 that overlaps with the SPS-configured PDSCH transmission timing 306 (which has the lowest configuration index among all remaining SPS-configured PDSCH transmission timings 306, 308, 310 and 312 in the time slot after the release of the SPS-configured PDSCH transmission timing 304), as indicated by “X” and ②, to indicate that the SPS-configured PDSCH transmission timing 304 is the second one to be released or removed. Figure 3It is shown that only one SPS-configured PDSCH transmission timing 308 overlaps 314 with an SPS-configured PDSCH transmission timing 306 (which has the lowest configuration index among all remaining SPS-configured PDSCH transmission timings 306, 308, 310, and 312 in the time slot after the release of the SPS-configured PDSCH transmission timing 304). However, it will be understood that Figure 3 This is an example illustration, and it shows that multiple SPS-configured PDSCH transmission opportunities may exist that overlap with the SPS-configured PDSCH transmission opportunity 306. In this case, all overlapping SPS-configured PDSCH transmission opportunities can be released or removed. According to this procedure, the UE can then receive transmissions via the SPS-configured PDSCH transmission opportunity 306 (but not via the released or removed SPS-configured PDSCH transmission opportunity 308).

[0104] Following this step, after the release of the SPS-configured PDSCH transmission opportunity 304, among the remaining set of SPS-configured PDSCH transmission opportunities 306, 308, 310, and 312 in the time slot, there may still be additional overlapping SPS-configured PDSCH transmission opportunities remaining, such as in Figure 3 The SPS-configured PDSCH transmission times 310 and 312 are shown. In such a case, the above steps are then repeated until there are no remaining SPS PDSCH transmission times in the set of remaining SPS-configured PDSCH transmission times in the time slot after the release of the SPS-configured PDSCH transmission times. Accordingly, according to this process, among the remaining SPS-configured PDSCH transmission times 310 and 312, the SPS-configured PDSCH transmission time 312 that overlaps with (e.g., among the remaining SPS-configured PDSCH transmission times 310 and 312) the SPS-configured PDSCH transmission time 310 with the lowest configuration index can be released or removed, as indicated by “X” and ③, to indicate that the SPS-configured PDSCH transmission time 304 is the third one to be released or removed. According to this process, the UE can then receive transmissions via the SPS-configured PDSCH transmission opportunity 310 (but not via the released or removed SPS-configured PDSCH transmission opportunity 312). Figure 3 It is shown that only one SPS-configured PDSCH transmission timing 312 overlaps 316 with an SPS-configured PDSCH transmission timing 310 (which has the lowest configuration index among the remaining SPS-configured PDSCH transmission timings 310 and 312). However, it will be understood that Figure 3This is an example illustration, and it shows that multiple SPS-configured PDSCH transmission opportunities may exist that overlap with the SPS-configured PDSCH transmission opportunity 310. In this case, all overlapping SPS-configured PDSCH transmission opportunities can also be released or removed. Accordingly, regarding Figure 3 The following steps resolve conflicts or contradictions in time slots caused by overlapping SPS-configured PDSCH transmission times: The UE determines non-overlapping SPS PDSCH transmission times 306 and 310 for receiving transmissions from the base station to which it is connected: First, the SPS PDSCH transmission time associated with the same configuration index as the one released by SPS; then, the SPS PDSCH conflict avoidance procedure is applied to the remaining SPS PDSCH transmission times. In other words, the UE can receive transmissions via SPS-configured PDSCH transmission times 306 and 310, but not via the remaining SPS-configured PDSCH transmission times (i.e., 304, 308, and 312). Alternatively, the UE can receive transmissions without using SPS-configured PDSCH transmission times 304, 308, and 312, or may not wish to receive or decode transmissions via SPS-configured PDSCH transmission times 304, 308, and 312, and may cancel these SPS-configured PDSCH transmission times.

[0105] Figure 4 This illustration shows examples of managing overlapping Physical Downlink Shared Channel (PDSCH) transmission timings configured with Semi-Persistent Scheduling (SPS) according to some aspects of this disclosure. In some aspects, the UE receives an SPS release PDCCH from the base station (BS) and via the Physical Downlink Control Channel (PDCCH), which is configured to release the SPS configuration at the UE. In some cases, the SPS configuration may include a configuration index or be associated with a configuration index, and may be configured to schedule SPS PDSCH transmission timings associated with the same configuration index in a time slot. In some cases, a time slot may also have multiple SPS-configured PDSCH transmission timings (also referred to as SPSPDSCH transmission timings without corresponding PDCCH transmissions), some of which may overlap with each other and / or overlap with SPSPDSCH transmission timings associated with the configuration index of the SPS release. Multiple SPS-configured PDSCH transmission timings may be configured through different SPS configurations (i.e., through SPS configurations with different configuration indices). For example, Figure 4The illustration shows an example of SPS release 402, which is received by the UE in a time slot and includes or is associated with a configuration index (e.g., index = 0). SPS release can be configured to release an SPS configuration configured for an SPS PDSCH transmission timing 404 associated with the same configuration index = 0. In some aspects, the same time slot may also include multiple transmission timings 406, 408, 410, and 412, each configured with an SPS configuration including or associated with a different configuration index.

[0106] In some aspects, the UE can resolve conflicts or contradictions arising from overlapping PDSCH transmission times configured by SPS by first applying the SPS PDSCH conflict avoidance procedure to all SPS PDSCH transmission times in the time slot (e.g., including SPS PDSCH transmission times associated with configuration indexes released by SPS and SPS PDSCH transmission times that do not have corresponding PDCCH transmissions), and then releasing SPS PDSCH transmission times associated with the same configuration indexes released by SPS. In other words, if there are more than one PDSCH in a time slot, each without a corresponding PDCCH transmission, on the serving cell, then after resolving overlap with symbols in that time slot indicated as uplink via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and before removing the PDSCH due to the release of the PDCCH by the SPS(s) received in that time slot, the UE receives one or more PDSCHs without a corresponding PDCCH transmission in that time slot by applying the SPS PDSCH conflict avoidance procedure mentioned above, as follows regarding... Figure 4 As shown. The UE can then release the SPS PDSCH transmission opportunity associated with the same configuration index as the SPS release, for example, if any remain after the application of the PDSCH collision avoidance procedure.

[0107] exist Figure 4In the process, after receiving an SPS release 402 with configuration index 0, the UE can apply the SPS PDSCH conflict avoidance procedure to all SPS-configured PDSCH transmission opportunities in the time slot, such as SPS PDSCH transmission opportunity 404 associated with the same configuration index as the SPS release, and SPS PDSCH transmission opportunities 406, 408, 410, and 412 that do not have corresponding PDCCH transmissions. The first step of this procedure is to release or remove SPS-configured PDSCH transmission opportunity 406 that overlaps 414 with SPS-configured PDSCH transmission opportunity 404 (which has the lowest configuration index among all SPS-configured PDSCH transmission opportunities 404, 406, 408, 410, and 412), as indicated by “X” and ①, to indicate that SPS-configured PDSCH transmission opportunity 406 is the first to be released or removed. Figure 4 It is shown that only one SPS-configured PDSCH transmission timing 406 overlaps with SPS-configured PDSCH transmission timing 404 (which has the lowest configuration index among all SPS-configured PDSCH transmission timings 404, 406, 408, 410, and 412) 414. However, it will be understood that Figure 4 This is an example illustration, and it illustrates that multiple SPS-configured PDSCH transmission opportunities may exist that overlap with the SPS-configured PDSCH transmission opportunity 404. In such cases, all overlapping SPS-configured PDSCH transmission opportunities can be released or removed. According to this procedure, the UE can then receive transmissions via the SPS-configured PDSCH transmission opportunity 404, unless it is released via SPS release (discussed below). However, transmissions may not be received via the released or removed SPS-configured PDSCH transmission opportunity 406.

[0108] Following this step, there may still be remaining additional overlapping SPS-configured PDSCH transmission opportunities in the time slot, such as remaining SPS-configured PDSCH transmission opportunities 408, 410, and 412 (i.e., SPS-configured PDSCH transmission opportunities that do not overlap with SPS-configured PDSCH transmission opportunity 404 and do not have a corresponding PDCCH). In such cases, the above steps are then repeated until there are no remaining overlapping SPS PDSCH transmission opportunities in the time slot. Accordingly, according to this process, the next step is to determine whether there are any SPS PDSCH transmission opportunities that overlap with the SPS-configured PDSCH transmission time 408 with the lowest configuration index among the remaining SPS-configured PDSCH transmission opportunities 408, 410, and 412. There are no such overlapping SPS-configured PDSCH transmission opportunities. Further, the UE can receive transmissions via SPS-configured PDSCH transmission opportunity 408.

[0109] In some aspects, according to this process, the next step is to determine whether there are any SPS PDSCH transmission opportunities that overlap with the remaining SPS-configured PDSCH transmission opportunities 410 with the lowest configuration index among the remaining SPS-configured PDSCH transmission opportunities 410 and 412. SPS-configured PDSCH transmission opportunity 412 overlaps with SPS-configured PDSCH transmission opportunity 410 by 416, and can thus be released or removed, as indicated by “X” and ②, to indicate that SPS-configured PDSCH transmission opportunity 412 is the second SPS-configured PDSCH transmission opportunity to be released or removed. According to this process, the UE can then receive transmissions via SPS-configured PDSCH transmission opportunity 410 (but not via the released or removed SPS-configured PDSCH transmission opportunity 412). Figure 4 This illustrates that only one SPS-configured PDSCH transmission timing 412 overlaps 416 with an SPS-configured PDSCH transmission timing 410 (which has the lowest configuration index among the remaining SPS-configured PDSCH transmission timings 410 and 412). However, it will be understood that... Figure 4 This is an example illustration, and multiple SPS-configured PDSCH transmission opportunities may exist that overlap with the SPS-configured PDSCH transmission opportunity 410. In this case, all overlapping SPS-configured PDSCH transmission opportunities can also be released or removed.

[0110] In some aspects, after applying the SPS PDSCH collision avoidance procedure to all SPS-configured PDSCH transmission opportunities in a time slot (e.g., SPS-configured PDSCH transmission opportunities 404, 406, 408, 410, and 412), the UE may, in response to receiving SPS release 402, release the SPS-configured PDSCH transmission opportunity 404 associated with configuration index 0, such as using “X” and The instruction indicates that the SPS-configured PDSCH transmission opportunity 404 is released after n-1 releases following the removal of the SPS-configured PDSCH transmission opportunity as a result of the SPS PDSCH collision avoidance process. Accordingly, regarding Figure 4 The following steps resolve conflicts or inconsistencies in time slots caused by overlapping SPS-configured PDSCH transmission times: The UE determines non-overlapping SPS PDSCH transmission times 408 and 410 for receiving transmissions from the base station to which the UE is connected: First, the SPS PDSCH conflict avoidance procedure is applied to all SPS PDSCH transmission times in the time slot (e.g., including SPS PDSCH transmission times associated with the configuration index released by the SPS and SPS PDSCH transmission times without corresponding PDCCH transmissions). Then, the SPS PDSCH transmission times associated with the same configuration index as the configuration index released by the SPS are released. In other words, the UE can receive transmissions via SPS-configured PDSCH transmission times 408 and 410, but not via the remaining SPS-configured PDSCH transmission times (i.e., 404, 406, and 412). In other words, the UE may receive transmissions without using the SPS-configured PDSCH transmission times 404, 406, and 412, or may not wish to receive or decode transmissions via the SPS-configured PDSCH transmission times 404, 406, and 412, and may cancel these SPS-configured PDSCH transmission times.

[0111] It should be noted that these results are related to... Figure 3 The results obtained are different. That is, non-overlapping SPS-configured PDSCH transmission opportunities are obtained by first releasing the SPS PDSCH transmission opportunities associated with the same configuration index as the one released by SPS, and then applying the SPS PDSCH conflict avoidance procedure to the remaining SPS PDSCH transmission opportunities (e.g., Figure 3306 and 310 in the text) are different from those non-overlapping SPS-configured PDSCH transmission opportunities obtained by first applying the SPS PDSCH collision avoidance procedure to all SPS PDSCH transmission opportunities in the time slot, and then releasing SPSPDSCH transmission opportunities associated with the same configuration index as the configuration index released by SPS (e.g., Figure 4 (408 and 410 in the middle).

[0112] Figure 5 This illustration shows examples of the management of overlapping Physical Downlink Shared Channel (PDSCH) transmission timings configured via Semi-Persistent Scheduling (SPS) according to some aspects of this disclosure. In some aspects, the UE resolves potential conflicts or discrepancies arising from overlapping SPS-configured PDSCH transmission timings by first releasing SPS PDSCH transmission timings associated with the same configuration index as the SPS release and then applying an SPS PDSCH conflict avoidance procedure to the SPS PDSCH transmission timings (e.g., the remaining SPS PDSCH transmission timings after release) or by reversing this order by first applying the SPS PDSCH conflict avoidance procedure to all SPS PDSCH transmission timings in the time slot and then releasing SPSPDSCH transmission timings associated with the same configuration index as the SPS release (referred to as "Option 2"). This can depend on the separation or distance between the reception of the SPS release and the earliest start symbol of the SPS-configured PDSCH transmission timings in the time slot. For example, Figure 5 The diagram illustrates a UE receiving an SPS release PDCCH 502, configured to release the SPS configuration at the UE, from a base station (BS) via the physical downlink control channel (PDCCH) in a time slot. In some cases, the SPS configuration may include a configuration index (e.g., 0) or associated with a configuration index (e.g., 0), and may be configured to schedule SPS PDSCH transmission opportunities associated with the same configuration index in the same time slot or subsequent time slots (504). In some cases, the same time slot or subsequent time slots (506, 508, and 510) may also have multiple SPS-configured PDSCH transmission opportunities, which may be configured through different SPS configurations (i.e., through SPS configurations with different configuration indices).

[0113] In some aspects, when SPS release 502 is received more than a threshold number of symbols N before the earliest start symbol of the SPS-configured PDSCH transmission timing, the UE can select option 1. That is, if the separation or distance 512 between the reception or end of SPS release 502 and the start of the first SPS PDSCH transmission timing 504 among multiple SPS PDSCH transmission timings 504, 506, 508, and 510 is greater than the threshold number of symbols N, the UE can select option 1, i.e., first release the SPS PDSCH transmission timing associated with the same configuration index as the SPS release, and then apply the SPS PDSCH collision avoidance procedure to the remaining SPS PDSCH transmission timings. On the other hand, in some aspects, when SPS release 502 is received within a threshold number of symbols N before the earliest start symbol of the SPS-configured PDSCH transmission timing, the UE can select option 2. In other words, if the separation or distance 512 between the reception or termination of SPS release 502 and the start of the first SPS PDSCH transmission opportunity 504 among multiple SPS PDSCH transmission opportunities 504, 506, 508, and 510 is within the threshold symbol number N, the UE can select option 2, i.e., by first applying the SPS PDSCH collision avoidance procedure to all SPS PDSCH transmission opportunities in the time slot, and then releasing the SPS PDSCH transmission opportunity associated with the same configuration index as the SPS release. In some aspects, as described above, SPS release 502 may be received in a time slot preceding the time slot containing multiple SPS PDSCH transmission opportunities 504, 506, 508, and 510. In some aspects, the threshold symbol number N may be a natural number in the range of 7 to 14. For example, the threshold symbol number N may be 7. For example, the threshold symbol number N may be 14.

[0114] In some aspects, after identifying the non-overlapping, SPS-configured PDSCH transmission timing for receiving transmissions from the base station to which the UE is connected (as mentioned above regarding...) Figure 3 , Figure 4 or Figure 5As discussed above, if the UE is configured with a semi-static HARQ-ACK codebook (i.e., a Type 1 HARQ-ACK codebook), the UE may not expect, or does not expect, for HARQ-ACKs released for SPS and for HARQ-ACKs for surviving SPS-configured PDSCH transmission opportunities (i.e., the remaining SPS-configured PDSCH transmission opportunities after Option 1 or Option 2 discussed above) to be mapped to the same position in the HARQ-ACK codebook. In other words, if the UE recognizes that a HARQ-ACK for an SPS-released HARQ-ACK and a HARQ-ACK for a non-overlapping SPS-configured PDSCH transmission opportunity that the UE could use for transmission in a non-overlapping SPS-configured PDSCH transmission opportunity are scheduled to the same position in the HARQ-ACK codebook, the UE can recognize that a scheduling error has occurred. For example, in recognizing that regarding... Figure 3 The PDSCH transmission timing configured by SPS is 306 and 310 or about Figure 4 Following the SPS-configured PDSCH transmission timings 408 and 410, a UE configured with a Type 1 HARQ-ACK codebook does not expect HARQ-ACKs released for SPS and HARQ-ACKs for SPS-configured PDSCH transmission timings 306, 310, 408, or 410 to map to the same position in the HARQ-ACK codebook. In other words, if a HARQ-ACK released for SPS and a HARQ-ACK for any of the SPS-configured PDSCH transmission timings 306, 310, 408, and 410 map to the same position in the Type 1 HARQ-ACK codebook associated with the UE, the UE can identify a scheduling error.

[0115] Figure 6This illustration demonstrates examples of managing overlapping Physical Downlink Shared Channel (PDSCH) transmission opportunities configured via Semi-Persistent Scheduling (SPS) according to some aspects of this disclosure. In some aspects, the UE may be scheduled with multiple SPS-configured PDSCH transmission opportunities configured with different SPS configurations, i.e., where the SPS configurations have different configuration indices or are associated with different configuration indices. These SPS PDSCH transmission opportunities may be referred to as SPS PDSCH transmission opportunities without corresponding PDCCH transmissions. In some cases, these SPS PDSCH transmission opportunities without corresponding PDCCH transmissions may overlap with each other. In some aspects, the UE may also receive an SPS activation / reactivation PDCCH from the base station (BS) and via the Physical Downlink Control Channel (PDCCH), the SPS activation / reactivation PDCCH being associated with a configuration index and an SPS configuration configured to activate or reactivate an SPS-configured PDSCH transmission opportunity at the UE, which differs from multiple SPS-configured PDSCH transmission opportunities and the configuration index associated with the SPS activation / reactivation PDCCH. For example, Figure 6 Three SPS-configured PDSCH transmission opportunities 606, 608, and 610 with different configuration indices are shown, and the UE can receive an SPS-activated / reactivated PDCCH 602 from the BS. The SPS-activated / reactivated PDCCH 602 includes a configuration index (i.e., 0) or an SPS-configured PDSCH transmission opportunity 604 associated with the same configuration index (i.e., 0) and configured to be activated or reactivated.

[0116] In some cases, the presence of an activated / reactivated SPS PDSCH transmission timing (i.e., multiple SPS-configured PDSCH transmission timings 606, 608, and 610) with the same configuration index as the SPS-activated / reactivated PDSCH or associated with the same configuration index as the SPS-activated / reactivated PDSCH in a time slot with no corresponding PDSCH transmission (i.e., activated or reactivated SPS-configured PDSCH transmission timing 604) can alter the resolution of conflicts or contradictions that may arise from the overlap of SPS-configured PDSCH transmission timings (and in some cases, where the activated or reactivated SPS PDSCH transmission timing has the same configuration index as the SPS-activated / reactivated PDSCH). In other words, in some cases, the result of the UE applying the SPS PDSCH conflict avoidance procedure to an SPS-configured PDSCH transmission timing that does not have a corresponding PDCCH transmission, followed by activation or reactivation of an SPS PDSCH transmission timing with the same configuration index as the SPS-activated / reactivated PDCCH (referred to herein as "Option A"), may differ from the result of first activating or reactivating an SPS PDSCH transmission timing with the same configuration index as the SPS-activated / reactivated PDCCH, followed by applying the SPS PDSCH conflict avoidance procedure to an SPS-configured PDSCH transmission timing that does not have a corresponding PDCCH transmission, and an activated or reactivated SPS PDSCH transmission timing with the same configuration index as the SPS-activated / reactivated PDCCH (referred to herein as "Option B"). In some cases, particularly when the activation or reactivation of an SPS PDSCH transmission timing associated with the same configuration index as the SPS-activated / reactivated PDSCH occurs within a threshold symbol number N of the earliest start symbol of an SPS-configured PDSCH transmission timing that does not have a corresponding PDCCH transmission, the UE may not have sufficient time to re-determine the resolution of conflicts or contradictions that may arise from the overlap of SPS-configured PDSCH transmission timings in the time slot. In some aspects, the threshold symbol number N can be a natural number in the range of 7 to 14. For example, the threshold symbol number N can be 7. For example, the threshold symbol number N can be 14.

[0117] Accordingly, in some aspects, unless the SPS-activated / reactivated PDCCH ends at least N symbols before the earliest start symbol of an SPS-configured PDSCH transmission timing without corresponding PDCCH transmission, and / or the existence of an activated or reactivated SPS-configured PDSCH transmission timing does not affect the resolution of conflicts or contradictions caused by overlapping SPS PDSCH transmission timings without corresponding PDCCH transmission, the UE may not decode or not decode activated or reactivated SPS-configured PDSCH transmission timings and / or SPS-configured PDSCH transmission timings without corresponding PDCCH transmission. That is, if the existence of SPS-activated / reactivated PDCCH affects the resolution of conflicts or contradictions caused by overlapping SPS PDSCH transmission timings without corresponding PDCCH transmission, the UE may not expect or not desire receiving an SPS-activated / reactivated PDCCH ending at less than or equal to N symbols before the earliest start symbol of an SPS-configured PDSCH transmission timing without corresponding PDCCH transmission. When this happens, i.e., the UE receives an SPS activation / reactivation PDCCH within N symbols, the UE can determine that a scheduling error has occurred. Figure 6 The existence of an activated or reactivated SPS-configured PDSCH transmission opportunity (i.e., an SPS-configured PDSCH transmission opportunity with the same configuration index as the SPS-activated / reactivated PDCCH) can be addressed by, for example, by applying the SPS PDSCH conflict avoidance process to SPS-configured PDSCH transmission opportunities that do not have a corresponding PDCCH transmission, as well as to activated or reactivated SPS PDSCH transmission opportunities with the same configuration index as the SPS-activated / reactivated PDCCH.

[0118] exist Figure 6In the above, the result of "Option A" (i.e., the UE applies the SPS PDSCH conflict avoidance procedure to SPS-configured PDSCH transmission opportunities 606, 608, and 610 that do not have corresponding PDCCH transmissions, followed by the activation or reactivation of SPS PDSCH transmission opportunity 604 that has the same configuration index as the SPS activated / reactivated PDCCH) is the same as the result of "Option B" (i.e., first activate or reactivate SPS PDSCH transmission opportunity 604 that has the same configuration index as the SPS activated / reactivated PDCCH, followed by the application of the SPS PDSCH conflict avoidance procedure to SPS-configured PDSCH transmission opportunities 606, 608, and 610 that do not have corresponding PDCCH transmissions, as well as the activated or reactivated SPS PDSCH transmission opportunity 604). This is because the results of both "Option A" and "Option B" are the same, namely, the SPS-configured PDSCH transmission timings 604, 606, and 610 can be used for transmissions to the UE (e.g., for transmissions from the BS, the UE can or can perform decoding of these SPS-configured PDSCH transmission timings), while the SPS-configured PDSCH transmission timing 608 is released for overlap with the SPS PDSCH transmission timing 606 at 612 (e.g., for transmissions from the BS, the UE can or can not decode this SPS-configured PDSCH transmission timing).

[0119] Figure 7 This illustrates the aspect where the SPS activation / reactivation of the PDCCH ends before the earliest start symbol of an SPS-configured PDSCH transmission timing that does not have a corresponding PDCCH transmission. That is, the separation or distance between the reception of the SPS activation / reactivation of the PDCCH 702 and the earliest start symbol of the SPS-configured PDSCH transmission timing 706, 708, which does not have a corresponding PDCCH transmission, is at least the threshold symbol number N. In such a case, the UE can apply the SPS PDSCH collision avoidance procedure to the SPS-configured PDSCH transmission timings 706, 708, which do not have a corresponding PDCCH transmission, and to the activated or reactivated SPS PDSCH transmission timing 704. Figure 7 In the example aspect shown, according to the first step of the process, the UE releases or removes the SPS-configured PDSCH transmission timing 706 that overlaps with the SPS PDSCH transmission timing 704 which has the minimum configuration index (i.e., 0) or is associated with the minimum configuration index (i.e., 0), leaving the SPS PDSCH transmission timings 704 and 708 for transmission to the UE.

[0120] In some aspects, if the SPS activation / reactivation of PDCCH ends within a threshold number of symbols N of the earliest start symbol of the SPS-configured PDSCH transmission timing that does not have a corresponding PDCCH transmission, i.e., if the separation or distance between the reception of SPS activation / reactivation of PDCCH 702 and the earliest start symbol of the SPS-configured PDSCH transmission timing 706 that does not have a corresponding PDCCH transmission is less than the threshold number of symbols N, then the UE may not or does not decode the activated or reactivated SPS-configured PDSCH transmission timing 704 and / or the SPS-configured PDSCH transmission timings 706 and 708 that do not have a corresponding PDCCH transmission. In some aspects, when the separation or distance is less than the threshold symbol number N, the UE may not expect or desire decoding of the activated or reactivated SPS-configured PDSCH transmission timing 704 because the activated or reactivated SPS-configured PDSCH transmission timing 704 overlaps with the SPS-configured PDSCH transmission timing 706, which will not have been released or removed as a result of the SPS PDSCH collision avoidance process if there is no activated or reactivated SPS-configured PDSCH transmission timing 704 in the time slot. In some aspects, the threshold symbol number N can be a natural number in the range of 7 to 14. For example, the threshold symbol number N can be 7.

[0121] Figure 8 This is a block diagram of an exemplary UE 800 based on some aspects of this disclosure. UE 800 may be as described above. Figure 1 The UE 115 in the network 100 discussed herein. As shown, the UE 800 may include a processor 802, a memory 804, an SPS PDSCH overlap management (SOM) module 808, a transceiver 810 including a modem subsystem 812 and an RF unit 814, and one or more antennas 816. These components may communicate with each other directly or indirectly, for example, via one or more buses.

[0122] Processor 802 may have various features as a particular type of processor. For example, these may include a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein. Processor 802 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0123] Memory 804 may include cache memory (e.g., cache memory of processor 802), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or combinations of different types of memory. In some aspects, memory 804 may include a non-transitory computer-readable medium. Memory 804 may store instructions 806. Instructions 806 may include, when executed by processor 802, causing processor 802 to perform the operations described herein (e.g., ...). Figures 1-7 Instructions (in various aspects). Instruction 806 can also be referred to as program code. Program code can be used to cause a wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 802) to control or command the wireless communication device to do so. The terms "instruction" and "code" should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms "instruction" and "code" can refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instruction" and "code" can include a single computer-readable statement or multiple computer-readable statements.

[0124] The SOM module 808 can be implemented via hardware, software, or a combination thereof. For example, the SOM module 808 can be implemented as a processor, circuitry, and / or instructions 806 stored in memory 804 and executed by processor 802. In some examples, the SOM module 808 can be integrated within the modem subsystem 812. For example, the SOM module 808 can be implemented by a combination of software components and hardware components (e.g., logic gates and circuitry) within the modem subsystem 812 (e.g., executed by a DSP or general-purpose processor). The SOM module 808 can be used in various aspects of this disclosure, for example, Figures 1-7The SOM module 808 can be configured to identify multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot, and to receive from the base station (BS) and via the physical downlink control channel (PDCCH) a semi-persistent scheduling (SPS) release configured to release the SPS configuration, including a configuration index, at the UE. In some aspects, the SPS configuration can be configured to schedule an SPS PDSCH transmission opportunity associated with a configuration index among multiple SPS PDSCH transmission opportunities in a time slot. In response to receiving the SPS release, the SOM module 808 can perform a first action, which is to release the SPS PDSCH transmission opportunity associated with the configuration index, and then apply a first SPS PDSCH transmission opportunity conflict avoidance procedure to a first set of SPS PDSCH transmission opportunities, wherein the first set of SPS PDSCH transmission opportunities may include the remaining SPS PDSCH transmission opportunities among multiple SPS PDSCH transmission opportunities after the release of the SPS PDSCH transmission opportunity associated with the configuration index. Alternatively, the SOM module 808 may perform a second action in response to receiving an SPS release, which is to apply a second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set and then release the SPS PDSCH transmission timing associated with the configuration index, wherein the second SPS PDSCH transmission timing set may include multiple SPS PDSCH transmission timings.

[0125] In some aspects, the SOM module 808 can identify one or more Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) transmission opportunities in a time slot, and receive from the base station (BS) and via the Physical Downlink Control Channel (PDCCH) SPS-Activated Downlink Control Information (DCI) configured to activate the SPS configuration at the UE, wherein the SPS-Activated DCI is activated. In some aspects, the SPS configuration may include a configuration index and be configured to schedule SPS PDSCH transmission opportunities associated with the configuration index. In some aspects, the SOM module 808 may, in response to receiving an SPS activation, activate or reactivate an SPS PDSCH transmission timing associated with the configuration index based on: i) a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transmission timing in the same time slot as the SPS PDSCH transmission timing associated with the configuration index; or ii) a comparison of a first result of applying a first SPS PDSCH transmission timing conflict avoidance procedure with a second result of applying a second SPS PDSCH transmission timing conflict avoidance procedure, wherein the first SPS PDSCH transmission timing conflict avoidance procedure is applied to a first set of SPS PDSCH transmission timings including one or more SPS PDSCH transmission timings, and the second SPS PDSCH transmission timing conflict avoidance procedure is applied to a second set of SPS PDSCH transmission timings, the second set of SPS PDSCH transmission timings including the SPS PDSCH transmission timing associated with the configuration index and one or more SPS PDSCH transmission timings.

[0126] As shown, transceiver 810 may include modem subsystem 812 and RF unit 814. Transceiver 810 may be configured to communicate bidirectionally with other devices, such as UE 115 and / or another core network element. Modem subsystem 812 may be configured to modulate and / or encode data according to MCS (e.g., LDPC coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). RF unit 814 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PSBCH, sidelink RMSI, PSSCH, PSCCH, PSFCH, PC5-RRC configuration, control commands) transmitted from modem subsystem 812 (regarding outbound transmissions) or originating from another source (such as UE 115). RF unit 814 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 810, modem subsystem 812 and / or RF unit 814 may be separate devices coupled together at UE 115 to enable UE 115 to communicate with other devices.

[0127] RF unit 814 can provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may contain one or more data packets and other information)) to antenna 816 for transmission to one or more other devices. According to some aspects of this disclosure, this may include, for example, the transmission of information to complete attachment to a network and communication with the residing UE 115. Antenna 816 can also receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at transceiver 810. Transceiver 810 can provide demodulated and decoded data (e.g., PSCCH, PSSCH, PSFCH, measurement data, and / or sensor data logs) to SOM module 808 for processing. Antenna 816 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0128] In some aspects, transceiver 810 is configured to communicate with a base station to receive a semi-persistent scheduling (SPS) release from the base station (BS) and via a physical downlink control channel (PDCCH). The SPS release is configured to release an SPS configuration including a configuration index at the UE, wherein the SPS configuration is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among multiple SPS PDSCH transmission opportunities in a time slot. In some aspects, transceiver 810 is configured to communicate with a base station to receive SPS activated downlink control information (DCI) from the base station (BS) and via a physical downlink control channel (PDCCH), configured to activate the semi-persistent scheduling (SPS) configuration at the UE, wherein the SPS configuration includes a configuration index and is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index.

[0129] In one aspect, UE 1300 may include multiple transceivers 510 implementing different RATs (e.g., NR and LTE). In another aspect, UE 1300 may include a single transceiver 1310 implementing multiple RATs (e.g., NR and LTE). In yet another aspect, transceiver 1310 may include various components, wherein different combinations of components can implement different RATs.

[0130] Figure 9 This is a block diagram of an exemplary base station (BS) 900 according to some aspects of this disclosure. The BS 900 may be as described above. Figure 1 The BS 105 discussed herein. As shown, the BS 900 may include a processor 902, a memory 904, an SOM module 908, a transceiver 910 including a modem subsystem 912 and a radio frequency (RF) unit 914, and one or more antennas 916. These components may communicate with each other directly or indirectly, for example, via one or more buses.

[0131] Processor 902 may include a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein. Processor 902 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0132] Memory 904 may include cache memory (e.g., cache memory of processor 902), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard disk drives, other forms of volatile and non-volatile memory, or combinations of different types of memory. In one aspect, memory 904 includes a non-transitory computer-readable medium. Memory 904 may store or have instructions 906 recorded thereon. Instructions 906 may include, when executed by processor 902, causing processor 902 to perform aspects of this document combined with the present disclosure (e.g., ...). Figures 1-7 The instructions (906) describe the operations in various aspects. Instruction 906 can also be called program code, which can be broadly interpreted as including any type of computer-readable statements (multiple statements), as described above regarding... Figure 6 Discussed.

[0133] The SOM module 908 can be implemented via hardware, software, or a combination thereof. For example, the SOM module 908 can be implemented as a processor, circuitry, and / or instructions 906 stored in memory 904 and executed by processor 902. In some examples, the SOM module 908 can be integrated within the modem subsystem 712. For example, the SOM module 908 can be implemented by a combination of software components and hardware components (e.g., logic gates and circuitry) within the modem subsystem 912 (e.g., executed by a DSP or general-purpose processor). The SOM module 908 can be used in various aspects of this disclosure, such as... Figures 1-7 All aspects.

[0134] As shown, transceiver 910 may include modem subsystem 912 and RF unit 914. Transceiver 910 may be configured to communicate bidirectionally with other devices, such as BS 105. Modem subsystem 912 may be configured to modulate and / or encode data from memory 904 according to a modulation and coding scheme (MCS) (e.g., low-density parity-check (LDPC) coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). RF unit 914 may be configured to process modulated / encoded data (e.g., PUSCH signals, UL data, SRS, UE capability reports, RI reports) transmitted from modem subsystem 912 (regarding outbound transmissions) or originating from another source (such as UE 115 or BS 105) (e.g., performing analog-to-digital conversion or digital-to-analog conversion, etc.). RF unit 914 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in transceiver 910, modem subsystem 912 and RF unit 914 can be separate devices coupled together at BS 900 so that BS 900 can communicate with other devices.

[0135] RF unit 914 can provide modulated and / or processed data (e.g., data packets (or more generally, data messages containing one or more data packets and other information)) to antenna 916 for transmission to one or more other devices. Antenna 916 can also receive data messages transmitted from other devices. Antenna 916 can provide the received data messages for processing and / or demodulation at transceiver 910. Transceiver 910 can provide demodulated and decoded data (e.g., PDSCH signals, PDCCH, DL data, SRS resource configuration, SRS resource activation, SRS resource deactivation) to SOM module 908. Antenna 916 may include multiple antennas of similar or different designs to maintain multiple transmission links. RF unit 914 can configure antenna 916.

[0136] In one aspect, the BS 900 may include multiple transceivers 910 implementing different RATs (e.g., NR and LTE). In another aspect, the BS 900 may include a single transceiver 910 implementing multiple RATs (e.g., NR and LTE). In yet another aspect, the transceiver 910 may include various components, wherein different combinations of components can implement different RATs.

[0137] Figure 10This is a flowchart of a wireless communication method 1000 according to some aspects of this disclosure. Aspects of method 1000 may be performed by a computing device of a wireless communication device (e.g., a processor, processing circuitry, and / or other suitable components) or other suitable units for performing these steps. For example, a wireless communication device (such as UE 115) may utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812, and one or more antennas 816) to perform the steps of method 1000. As shown, method 1000 includes a number of enumerated steps, but aspects of method 1000 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0138] At box 1010, the UE (e.g., UE 115) can identify multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot. In some cases, the UE can utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812, and one or more antennas 816) to identify multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot.

[0139] At block 1020, the UE can receive from the base station (BS) and via the physical downlink control channel (PDCCH) an SPS release configured to release a semi-persistent scheduling (SPS) configuration including a configuration index at the UE. In some aspects, the SPS configuration can be configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among multiple SPS PDSCH transmission opportunities in a time slot. In some cases, the UE can utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812, and one or more antennas 816) to receive from the base station (BS) and via the physical downlink control channel (PDCCH) an SPS release configured to release a semi-persistent scheduling (SPS) configuration including a configuration index at the UE.

[0140] At block 1030, the UE (e.g., UE 115) may perform one of two actions in response to receiving an SPS release. At block 1030a, the first action includes releasing the SPS PDSCH transmission opportunity associated with the configuration index, followed by applying a first SPS PDSCH transmission opportunity conflict avoidance procedure to a first set of SPS PDSCH transmission opportunities. In some aspects, the first set of SPS PDSCH transmission opportunities includes the remaining SPS PDSCH transmission opportunities from a plurality of SPS PDSCH transmission opportunities after the release of the SPS PDSCH transmission opportunity associated with the configuration index. At block 1030b, the second action includes applying a second SPS PDSCH transmission opportunity conflict avoidance procedure to a second set of SPS PDSCH transmission opportunities, followed by releasing the SPS PDSCH transmission opportunity associated with the configuration index. In some aspects, the second set of SPS PDSCH transmission opportunities includes a plurality of SPSPDSCH transmission opportunities. In some cases, the UE may utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812 and one or more antennas 816) to perform the actions of blocks 1030a and 1030b.

[0141] In some aspects of method 1000, when the SPS release is received at least a threshold number of symbols prior to the start of the earliest SPS PDSCH transmission opportunity among multiple SPS PDSCH transmission opportunities, the UE may perform a first action in response to receiving the SPS release. Further, the threshold number of symbols may be 14. In some aspects, when the SPS release is received less than N symbols prior to the start of the earliest SPS PDSCH transmission opportunity among multiple SPS PDSCH transmission opportunities, the UE performs a second action. Further, the SPS release may be received in a time slot preceding a time slot containing multiple SPS PDSCH transmission opportunities.

[0142] In some aspects, the Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for SPS release is sent at a different location in the HARQ-ACK codebook than those locations used for multiple SPS PDSCH transmission opportunities. That is, in some cases, the HARQ-ACK for SPS release is not sent at the same location in the HARQ-ACK codebook as the location used for sending the HARQ-ACK for any remaining SPS PDSCH transmission opportunities after performing the first or second action, or vice versa. In some aspects, the HARQ-ACK codebook is a Type 1 HARQ-ACK codebook. Some aspects of method 1000 also include determining that a Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for an SPS release is scheduled at the same position in the HARQ-ACK codebook as a HARQ-ACK scheduled for any remaining SPS PDSCH transmission opportunity after performing a first action or performing a second action in a plurality of SPS PDSCH transmission opportunities; and in response to said determination, identifying that a HARQ-ACK scheduling error has occurred.

[0143] In some aspects of method 1000, applying a first SPS PDSCH transmission timing conflict avoidance procedure to a first SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings associated with the minimum configuration index in the first SPS PDSCH transmission timing set. Further, applying a second SPS PDSCH transmission timing conflict avoidance procedure to a second SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the second SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings associated with the minimum configuration index in the second SPS PDSCH transmission timing set. Additionally, a second action includes applying a second SPS PDSCH transmission timing conflict avoidance procedure to the second SPS PDSCH transmission timing set, and subsequently, if any remain after executing the second SPS PDSCH transmission timing conflict avoidance procedure, releasing the SPS PDSCH transmission timings associated with the configuration index.

[0144] Figure 11This is a flowchart of a wireless communication method 1100 according to some aspects of this disclosure. Aspects of method 1100 may be performed by a computing device of a wireless communication device (e.g., a processor, processing circuitry, and / or other suitable components) or other suitable units for performing these steps. For example, a wireless communication device (such as UE 115) may utilize one or more components (such as processor 1302, memory 1304, SPS release module 1308, transceiver 1310, modem 312, and one or more antennas 1316) to perform the steps of method 1100. As shown, method 1100 includes a number of enumerated steps, but aspects of method 1100 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0145] In box 1110, the UE (e.g., UE 115) can identify multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot. In some cases, the UE can utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812, and one or more antennas 816) to identify multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot.

[0146] At block 1120, the UE can receive SPS-Activated Downlink Control Information (DCI) configured to activate a Semi-Persistent Scheduling (SPS) configuration at the UE, from the base station (BS) and via the Physical Downlink Control Channel (PDCCH). In some aspects, the SPS configuration includes a configuration index and is configured to schedule SPS PDSCH transmission opportunities associated with the configuration index. In some cases, the UE can utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812, and one or more antennas 816) to determine whether to receive data transmission via at least one of a plurality of SPS PDSCH transmission opportunities in response to receiving an SPS release.

[0147] At box 1130, the UE may, in response to receiving SPS activation, activate or reactivate an SPS PDSCH transmission opportunity associated with a configuration index based on: (i) a separation in a symbol between the end of the SPS activation DCI and the start of the earliest SPS PDSCH transmission opportunity in the same time slot as the SPS PDSCH transmission opportunity associated with the configuration index; or (ii) a comparison of a first result of applying a first SPS PDSCH transmission opportunity conflict avoidance procedure with a second result of applying a second SPS PDSCH transmission opportunity conflict avoidance procedure, wherein the first SPS PDSCH transmission opportunity conflict avoidance procedure is applied to a first set of SPS PDSCH transmission opportunities comprising multiple SPS PDSCH transmission opportunities, and the second SPS PDSCH transmission opportunity conflict avoidance procedure is applied to a second set of SPS PDSCH transmission opportunities comprising the SPS PDSCH transmission opportunity associated with the configuration index and multiple SPS PDSCH transmission opportunities. In some cases, the UE may utilize one or more components (such as processor 802, memory 804, SOM module 808, transceiver 810, modem 812 and one or more antennas 816) to determine whether to receive data transmission via at least one of a plurality of SPS PDSCH transmission opportunities in response to a receive SPS release.

[0148] In some aspects of method 1100, activation or reactivation based on separation in symbols includes activating or reactivating an SPS PDSCH transmission timing associated with a configuration index when the separation in symbols is not less than a threshold number of symbols. Method 1100 may further include determining that the separation in symbols between the end of the SPS activated DCI and the start of the earliest SPS PDSCH transmission timing is less than a threshold number of symbols; and identifying, in response to the determination, that an SPS PDSCH transmission timing scheduling error has occurred. In some aspects, the threshold number of symbols is 14. In some aspects, activation or reactivation based on a comparison of a first result and a second result includes activating or reactivating an SPS PDSCH transmission timing associated with a configuration index when the comparison indicates that the first result is the same as the second result.

[0149] This disclosure contains some aspects of the record.

[0150] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: identifying a plurality of semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; receiving from a base station (BS) and via a physical downlink control channel (PDCCH) an SPS release configured to release at the UE a semi-persistent scheduling (SPS) configuration including a configuration index, the SPS configuration being configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among a plurality of SPS PDSCH transmission opportunities in a time slot; and, in response to receiving the SPS release, performing: a first action, which releases the SPS PDSCH transmission opportunity associated with the configuration index and subsequently applies a first SPS PDSCH transmission opportunity conflict avoidance procedure to a first set of SPS PDSCH transmission opportunities, the first set of SPS PDSCH transmission opportunities including the remaining SPS PDSCH transmission opportunities among a plurality of SPS PDSCH transmission opportunities after the release of the SPS PDSCH transmission opportunity associated with the configuration index; or a second action, which applies a second SPS PDSCH transmission opportunity conflict avoidance procedure to a second SPS PDSCH transmission opportunity. The PDSCH transmission timing set is then released, and the SPS PDSCH transmission timing associated with the configuration index is released. The second SPS PDSCH transmission timing set includes multiple SPS PDSCH transmission timings.

[0151] Aspect 2: According to the method of Aspect 1, wherein when the SPS release is received at least a threshold number of symbols prior to the start of the earliest SPS PDSCH transmission timing among a plurality of SPS PDSCH transmission timings, the UE performs a first action in response to receiving the SPS release.

[0152] Aspect 3: According to the method of aspect 2, the number of threshold symbols is 14.

[0153] Aspect 4: According to the method of any of Aspects 1-3, wherein when the SPS release is received less than N symbols before the start of the earliest SPS PDSCH transmission timing among multiple SPSPDSCH transmission timings, the UE performs the second action.

[0154] Aspect 5: The method according to any of Aspects 1-4, wherein the SPS release is received in a time slot preceding a time slot containing multiple SPSPDSCH transmission opportunities.

[0155] Aspect 6: The method according to any of Aspects 1-5, wherein the Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for SPS release is sent at a position in the HARQ-ACK codebook that is different from those positions used for multiple SPS PDSCH transmission timings.

[0156] Aspect 7: The method according to any of Aspects 1-6 further includes: determining that a Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for an SPS release is scheduled at the same position in the HARQ-ACK codebook as the position in the HARQ-ACK codebook for a HARQ-ACK scheduled for any remaining SPSPDSCH transmission opportunity after performing the first action or the second action in a plurality of SPS PDSCH transmission opportunities; and in response to the determination, identifying that a HARQ-ACK scheduling error has occurred.

[0157] Aspect 8: According to the method of aspect 6 or aspect 7, where the HARQ-ACK codebook is a type 1 HARQ-ACK codebook.

[0158] Aspect 9: The method according to any of Aspects 1-8, wherein applying the first SPS PDSCH transmission timing conflict avoidance process to the first SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set associated with the minimum configuration index.

[0159] Aspect 10: The method according to any of Aspects 1-9, wherein applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the second SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings in the second SPS PDSCH transmission timing set associated with the minimum configuration index.

[0160] Aspect 11: The method according to any of Aspects 1-10, wherein the second action includes: applying a second SPSPDSCH transmission timing conflict avoidance process to a second SPSPDSCH transmission timing set, and subsequently releasing the SPSPDSCH transmission timing associated with the configuration index if any remain after the execution of the second SPSPDSCH transmission timing conflict avoidance process.

[0161] Aspect 12: A method of wireless communication performed by a user equipment (UE), the method comprising: identifying one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities in a time slot; receiving from a base station (BS) and via a physical downlink control channel (PDCCH) an SPS activated downlink control information (DCI) configured to activate a semi-persistent scheduling (SPS) configuration at the UE, the SPS configuration including a configuration index and configured to schedule SPS PDSCH transmission opportunities associated with the configuration index; and, in response to receiving SPS activation, activating or reactivating the SPS PDSCH transmission opportunities associated with the configuration index based on: a separation in a symbol between the end of the SPS activated DCI and the start of the earliest SPS PDSCH transmission opportunity in the same time slot as the SPS PDSCH transmission opportunity associated with the configuration index; or a first result of applying a first SPS PDSCH transmission opportunity conflict avoidance process and applying a second SPS... A comparison of the second results of the PDSCH transmission timing conflict avoidance process, wherein the first SPS PDSCH transmission timing conflict avoidance process is applied to a first SPS PDSCH transmission timing set including one or more SPS PDSCH transmission timings; and the second SPS PDSCH transmission timing conflict avoidance process is applied to a second SPS PDSCH transmission timing set, which includes SPS PDSCH transmission timings associated with a configuration index and one or more SPS PDSCH transmission timings.

[0162] Aspect 13: According to the method of aspect 12, wherein activation or reactivation based on separation in symbols includes activating or reactivating the SPSPDSCH transmission timing associated with the configuration index when the separation in symbols is not less than the threshold number of symbols.

[0163] Aspect 14: The method according to aspect 12 or aspect 13 further includes: determining that the separation in symbols between the end of the SPS-activated DCI and the start of the earliest SPS PDSCH transmission timing is less than a threshold number of symbols; and identifying, in response to the determination, that a scheduling error has occurred.

[0164] Aspect 15: According to the method of aspect 13 or aspect 14, the number of threshold symbols is 14.

[0165] Aspect 16: The method according to any of Aspects 12-15, wherein activating or reactivating based on a comparison of a first result and a second result includes: activating or reactivating the SPS PDSCH transmission timing associated with the configuration index when the comparison indicates that the first result is the same as the second result.

[0166] Aspect 17: The method according to any of aspects 12-16 further includes: identifying that a scheduling error has occurred when the first result differs from the second result.

[0167] Aspect 18: A user equipment (UE) comprising: a memory; a processor coupled to the memory; and a transceiver coupled to the processor, the UE being configured to perform a method according to aspects 1-11.

[0168] Aspect 19: A user equipment (UE) includes: a memory; a processor coupled to the memory; and a transceiver coupled to the processor, the UE being configured to perform methods according to aspects 12-17.

[0169] Aspect 20: A user equipment (UE) including a unit for performing the method according to aspects 1-11.

[0170] Aspect 21: A user equipment (UE) including a unit for performing a method according to aspects 12-17.

[0171] Aspect 22: A non-transitory computer-readable medium (CRM) having program code recorded thereon, the program code including code for causing a UE to perform a method according to aspects 1-11.

[0172] Aspect 23: A non-transitory computer-readable medium (CRM) having program code recorded thereon, the program code including code for causing a UE to perform a method according to aspects 12-17.

[0173] It should be noted that the methods described in this paper describe possible implementations, and that the operations and steps can be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0174] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described 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.

[0175] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0176] The various illustrative blocks and components described in connection with the disclosure herein may 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. A 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).

[0177] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or code on or transmitted through a computer-readable medium. 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 may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0178] Computer-readable media include both non-transitory computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read-only memory (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 desired program code units 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. Additionally, 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, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, where disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

[0179] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference 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 way as the phrase "at least partially based on".

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

[0181] This document describes exemplary configurations with reference to the accompanying drawings, and does not represent all examples that can be implemented or are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Identify the transmission timing of multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmissions within a time slot; The SPS release, configured to release the semi-persistent scheduling (SPS) configuration including the configuration index, is received from the base station (BS) and via the physical downlink control channel (PDCCH). The SPS configuration is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among the plurality of SPS PDSCH transmission opportunities in the time slot; and In response to receiving the SPS release, the following actions are performed: The first action involves releasing the SPS PDSCH transmission opportunity associated with the configuration index, followed by applying a first SPS PDSCH transmission opportunity conflict avoidance process to the first SPS PDSCH transmission opportunity set. The first SPS PDSCH transmission timing set includes the remaining SPS PDSCH transmission timings among the plurality of SPS PDSCH transmission timings after the release of the SPS PDSCH transmission timing associated with the configuration index, wherein the UE performs the first action in response to receiving the SPS release when the SPS release is received by at least a threshold number of symbols prior to the start of the earliest SPS PDSCH transmission timing among the plurality of SPS PDSCH transmission timings; or The second action involves applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set, and then releasing the SPS PDSCH transmission timing associated with the configuration index. The second SPS PDSCH transmission timing set includes the plurality of SPS PDSCH transmission timings.

2. The method according to claim 1, wherein, The number of threshold symbols is 14.

3. The method according to claim 1, wherein, The SPS release is received in a time slot preceding the time slot containing the multiple SPS PDSCH transmission opportunities.

4. The method according to claim 1, wherein, The UE performs the second action when the SPS release is received less than N symbols before the start of the earliest SPS PDSCH transmission timing among the plurality of SPS PDSCH transmission timings.

5. The method according to claim 1, wherein, The Hybrid Automatic Request (HARQ) acknowledgment (ACK) for the SPS release is sent at a location in the HARQ-ACK codebook that is different from those locations used for the timing of the plurality of SPS PDSCH transmissions.

6. The method according to claim 5, wherein, The HARQ-ACK codebook is a Type 1 HARQ-ACK codebook.

7. The method according to claim 1, further comprising: The Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for the SPS release is determined to be scheduled in the same position in the HARQ-ACK codebook as the position in the HARQ-ACK codebook scheduled for any remaining SPS PDSCH transmission timings after the execution of the first action or the execution of the second action. as well as In response to determining that the HARQ ACK for the SPS release is scheduled in the same position in the HARQ-ACK codebook as the HARQ-ACK for any remaining SPS PDSCH transmission timing after the execution of the first action or the execution of the second action in the plurality of SPS PDSCH transmission timings, a HARQ-ACK scheduling error is identified.

8. The method according to claim 1, wherein, Applying the first SPS PDSCH transmission timing conflict avoidance procedure to the first SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set associated with the minimum configuration index.

9. The method according to claim 1, wherein, Applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set includes releasing SPSPDSCH transmission timings in the second SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings associated with the minimum configuration index in the second SPS PDSCH transmission timing set.

10. The method according to claim 1, wherein, The second action includes applying the second SPS PDSCH transmission timing conflict avoidance procedure to the second SPS PDSCH transmission timing set, and then releasing the SPSPDSCH transmission timing associated with the configuration index if any remain after the execution of the second SPS PDSCH transmission timing conflict avoidance procedure.

11. A method for wireless communication performed by a user equipment (UE), the method comprising: Identify one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot; Receive SPS-Activated Downlink Control Information (DCI) from the base station (BS) and via the Physical Downlink Control Channel (PDCCH), configured to activate Semi-Persistent Scheduling (SPS) at the UE. The SPS configuration includes a configuration index and is configured to schedule SPS PDSCH transmissions associated with the configuration index; and In response to receiving the SPS activation, the SPS PDSCH transmission timing associated with the configuration index is activated or reactivated based on the following: The separation in symbols between the end of the SPS activated DCI and the start of the earliest SPS PDSCH transmission opportunity in the same time slot as the SPS PDSCH transmission opportunity associated with the configuration index; or A comparison of the first result obtained by applying the first SPS PDSCH transmission timing conflict avoidance procedure and the second result obtained by applying the second SPS PDSCH transmission timing conflict avoidance procedure. The first SPS PDSCH transmission timing conflict avoidance process is applied to a first SPS PDSCH transmission timing set including the one or more SPS PDSCH transmission timings; and The second SPS PDSCH transmission timing conflict avoidance process is applied to a second SPS PDSCH transmission timing set, which includes the SPS PDSCH transmission timing associated with the configuration index and the one or more SPS PDSCH transmission timings. Specifically, activating or reactivating based on the comparison of the first result and the second result includes activating or reactivating the SPS PDSCH transmission timing associated with the configuration index when the comparison indicates that the first result is the same as the second result.

12. The method according to claim 11, wherein, The activation or reactivation based on the separation in the symbols includes activating or reactivating the SPS PDSCH transmission timing associated with the configuration index when the separation in the symbols is not less than the threshold number of symbols.

13. The method according to claim 12, wherein, The number of threshold symbols is 14.

14. The method of claim 11, further comprising: The separation in symbols between the end of the SPS-activated DCI and the start of the earliest SPS PDSCH transmission timing is determined to be less than a threshold number of symbols; as well as A scheduling error is identified in response to determining that the separation in symbols between the end of the SPS-activated DCI and the start of the earliest SPS PDSCH transmission timing is less than the threshold number of symbols.

15. The method of claim 11, further comprising identifying a scheduling error when the first result differs from the second result.

16. A user equipment (UE), comprising: The processor is configured as follows: Identify the transmission timing of multiple semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmissions within a time slot; The transceiver is configured as follows: The SPS release, configured to release the semi-persistent scheduling (SPS) configuration including the configuration index, is received from the base station (BS) and via the physical downlink control channel (PDCCH). The SPS configuration is configured to schedule an SPS PDSCH transmission opportunity associated with the configuration index among the plurality of SPS PDSCH transmission opportunities in the time slot, and the processor is further configured to execute in response to receiving the SPS release: The first action involves releasing the SPS PDSCH transmission opportunity associated with the configuration index, followed by applying a first SPS PDSCH transmission opportunity conflict avoidance process to the first SPS PDSCH transmission opportunity set. The first SPS PDSCH transmission timing set includes the remaining SPS PDSCH transmission timings among the plurality of SPS PDSCH transmission timings after the release of the SPS PDSCH transmission timing associated with the configuration index, wherein the UE performs the first action in response to receiving the SPS release when the SPS release is received by at least a threshold number of symbols prior to the start of the earliest SPS PDSCH transmission timing among the plurality of SPS PDSCH transmission timings; or The second action involves applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set, and then releasing the SPS PDSCH transmission timing associated with the configuration index. The second SPS PDSCH transmission timing set includes the plurality of SPS PDSCH transmission timings.

17. The UE according to claim 16, wherein, The UE performs the second action when the SPS release is received less than N symbols before the start of the earliest SPS PDSCH transmission timing among the plurality of SPS PDSCH transmission timings.

18. The UE according to claim 16, wherein, The Hybrid Automatic Request (HARQ) acknowledgment (ACK) for the SPS release is sent at a location in the HARQ-ACK codebook that is different from those locations used for the timing of the plurality of SPS PDSCH transmissions.

19. The UE according to claim 16, wherein, The processor is also configured to: The Hybrid Automatic Request (HARQ) Acknowledgment (ACK) for the SPS release is determined to be scheduled in the same position in the HARQ-ACK codebook as the position in the HARQ-ACK codebook scheduled for any remaining SPS PDSCH transmission timings after the execution of the first action or the execution of the second action. as well as In response to determining that the HARQ ACK for the SPS release is scheduled in the same position in the HARQ-ACK codebook as the HARQ-ACK for any remaining SPS PDSCH transmission timing after the execution of the first action or the execution of the second action in the plurality of SPS PDSCH transmission timings, a HARQ-ACK scheduling error is identified.

20. The UE according to claim 16, wherein, Applying the first SPS PDSCH transmission timing conflict avoidance procedure to the first SPS PDSCH transmission timing set includes releasing SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings in the first SPS PDSCH transmission timing set associated with the minimum configuration index.

21. The UE according to claim 16, wherein, Applying the second SPS PDSCH transmission timing conflict avoidance process to the second SPS PDSCH transmission timing set includes releasing SPSPDSCH transmission timings in the second SPS PDSCH transmission timing set that overlap with SPS PDSCH transmission timings associated with the minimum configuration index in the second SPS PDSCH transmission timing set.

22. The UE according to claim 16, wherein, The second action includes applying the second SPS PDSCH transmission timing conflict avoidance procedure to the second SPS PDSCH transmission timing set, and then releasing the SPSPDSCH transmission timing associated with the configuration index if any remain after the execution of the second SPS PDSCH transmission timing conflict avoidance procedure.

23. A user equipment (UE), comprising: The processor is configured as follows: Identify one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) transmission opportunities within a time slot; The transceiver is configured as follows: Receive SPS-Activated Downlink Control Information (DCI) from the base station (BS) and via the Physical Downlink Control Channel (PDCCH), configured to activate Semi-Persistent Scheduling (SPS) at the UE. The SPS configuration includes a configuration index and is configured to schedule SPS PDSCH transmission timings associated with the configuration index. The processor is also configured to perform the following operations in response to receiving the SPS activation: The SPS PDSCH transmission timing associated with the configuration index is activated or reactivated based on the following: The separation in symbols between the end of the SPS activated DCI and the start of the earliest SPS PDSCH transmission opportunity in the same time slot as the SPS PDSCH transmission opportunity associated with the configuration index; or A comparison of the first result obtained by applying the first SPS PDSCH transmission timing conflict avoidance procedure and the second result obtained by applying the second SPS PDSCH transmission timing conflict avoidance procedure. The first SPS PDSCH transmission timing conflict avoidance process is applied to a first SPS PDSCH transmission timing set including the one or more SPS PDSCH transmission timings; and The second SPS PDSCH transmission timing conflict avoidance process is applied to a second SPS PDSCH transmission timing set, which includes the SPS PDSCH transmission timing associated with the configuration index and the one or more SPS PDSCH transmission timings. The processor is further configured to activate or reactivate the SPS PDSCH transmission timing associated with the configuration index when the comparison indicates that the first result is the same as the second result.

24. The UE according to claim 23, wherein, The processor is also configured to activate or reactivate the SPS PDSCH transmission timing associated with the configuration index when the separation in the symbols is not less than the threshold number of symbols.

25. The UE according to claim 23, wherein, The processor is also configured to: The separation in symbols between the end of the SPS-activated DCI and the start of the earliest SPS PDSCH transmission timing is determined to be less than a threshold number of symbols; as well as A scheduling error is identified in response to determining that the separation in symbols between the end of the SPS-activated DCI and the start of the earliest SPS PDSCH transmission timing is less than the threshold number of symbols.

26. The UE according to claim 23, wherein, The processor is also configured to identify a scheduling error when the first result differs from the second result.