Semi-Persistent Scheduling (SPS) Reception for Restricted-Capability Devices

Abstract

Wireless communication devices, systems, and methods related to downlink control information (DCI) monitoring and semi-persistent scheduling (SPS) reception for devices with limited capabilities are provided. For example, a method of wireless communication performed by a user equipment may include: receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; monitoring for an SPS release and downlink data communication in a time slot scheduled for downlink data communication; and sending an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of U.S. Patent Application No. 17 / 183,559, filed on February 24, 2021, and U.S. Provisional Patent Application No. 62 / 983,571, filed on February 28, 2020; U.S. Provisional Patent Application No. 63 / 008,613, filed on April 10, 2020; and U.S. Provisional Patent Application No. 63 / 025,588, filed on May 15, 2020. The entire contents of these applications are incorporated herein by reference as if fully set forth below for all applicable purposes. Technical Field

[0003] The techniques discussed herein generally relate to wireless communication systems, and more specifically, to downlink scheduling techniques, including semi - persistent scheduling (SPS) grants and releases, applicable to both restricted - capability devices and non - restricted - capability devices. Background Art

[0004] 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 the one or more channels. Scheduling is the process of allocating resources for data transmission. New Radio (NR) scheduling is specified by the network (e.g., gNodeB or gNB), and the user equipment (UE) only follows the scheduling indicated by the network. The overall scheduling mechanism in NR is similar to that in Long Term Evolution (LTE), but NR has a finer granularity than 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 by a Downlink Control Indicator or Downlink Control Information (DCI). SPS is a mechanism in which PDSCH transmissions are scheduled via an RRC message (or DCI). The PDSCH is divided into time slots in which data is transmitted.

[0005] In the Physical Downlink Shared Channel (PDSCH), user data traffic is transmitted between the gNodeB and the UE, and the UE transmits the necessary Acknowledgment / Negative Acknowledgment (ACK / NACK) reports on the uplink channel at a specified time.

[0006] In 3GPP Release 15, if a UE does not indicate the ability to receive more than one unicast PDSCH per time slot, the UE does not expect to receive an SPS PDSCH release indicator and a unicast PDSCH symbol in the same time slot. However, 3GPP Release 16 defines an SPS configuration with a minimum period of one time slot. In the present specification, under a type-1 CB structure, it is not possible to release SPS in the same time slot in which a restricted-capability UE is configured to receive SPS PDSCH symbols. For example, the UE may not be able to receive a unicast PDSCH symbol and an SPS release indicator in the same time slot because it will not be able to transmit ACK / NACK for the unicast PDSCH symbol and the SPS release indicator within the time slot. Therefore, a solution is needed to allow the UE to receive an SPS release indicator within a time slot having downlink communication scheduled for the UE (such as a unicast PDSCH associated with dynamic grant and / or SPS grant). SUMMARY OF THE DISCLOSURE

[0007] Some aspects of the present disclosure are outlined below to provide a basic understanding of the technologies discussed. This summary is not an extensive review of all contemplated features of the present disclosure and is neither intended to identify key or critical elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a summary form as a prelude to the more detailed description that is presented later.

[0008] Semi-persistent scheduling (SPS) can be used to reduce the control channel overhead of communications that require radio resource allocation at regular scheduling intervals, such as voice, video, gaming, etc. In this regard, an SPS grant can indicate to the UE the allocated radio resources and the associated period. The period range of an SPS grant can be from 1 time slot (or sub-slot) to 1 second or longer, including any value therebetween. A particular period can be determined by the type of data being transmitted and its associated communication interval requirements.

[0009] Aspects of the present disclosure provide mechanisms for allowing a UE to receive an SPS release within a time slot having downlink data communication scheduled for the UE (e.g., unicast PDSCH associated with dynamic grant and / or SPS grant). In some instances, the UE is a limited-capability device configured to receive a single physical downlink shared channel (PDSCH) communication per time slot. In this regard, the UE may be configured to provide only a single ACK / NACK per time slot. Thus, in the case where a limited-capability UE is sent an SPS release in a time slot that is also scheduled for downlink data communication, the UE cannot provide ACK / NACK for both the SPS release and the scheduled downlink data. Correlatively, if a limited-capability UE is assigned an SPS grant with a period of one time slot, the UE will be scheduled to receive downlink data communication in each time slot. In such a case, although the limited-capability UE may be able to monitor both the SPS release (in the PDCCH) and the downlink data communication (in the PDSCH) in a particular time slot, it may not be able to provide ACK / NACK for both of them. Aspects of the present disclosure provide solutions to these and other scenarios associated with handling an SPS release in a time slot (or sub-slot) scheduled for downlink data communication. While aspects of the present disclosure have particular benefits in the context of limited-capability UEs, it should be understood that these concepts can be applied in a similar manner to fully-capable UEs to achieve similar benefits. In this regard, some aspects of the present disclosure are particularly suitable for fully-capable UEs (e.g., UEs that can receive multiple PDSCH communications and provide multiple associated ACK / NACKs per time slot).

[0010] In one aspect of the present disclosure, a method of wireless communication performed by a user equipment includes: receiving, from a base station, a semi-persistent scheduling (SPS) grant that indicates a period; monitoring, in a time slot scheduled for downlink data communication, an SPS release and the downlink data communication; and sending, based on the monitoring, an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station.

[0011] In an additional aspect of the present disclosure, a method of wireless communication performed by a base station includes: sending, to a user equipment, a semi-persistent scheduling (SPS) grant that indicates a period; sending, in a time slot scheduled for downlink data communication of the user equipment, an SPS release; and monitoring, in the time slot, an acknowledgement (ACK) or a negative acknowledgement (NACK) from the user equipment.

[0012] In an additional aspect of the present disclosure, a user equipment includes a transceiver configured to: receive a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; and a processor in communication with the transceiver, the processor configured to: monitor an SPS release and the downlink data communication in a time slot scheduled for downlink data communication; wherein the transceiver is further configured to send an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

[0013] In another aspect of the present disclosure, a base station includes a transceiver configured to: send a semi-persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; and send an SPS release in a time slot scheduled for downlink data communication for the user equipment; and a processor in communication with the transceiver, the processor configured to: monitor an acknowledgement (ACK) or a negative acknowledgement (NACK) from the user equipment in the time slot.

[0014] In an additional aspect of the present disclosure, a user equipment includes means for receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; means for monitoring an SPS release and downlink data communication in a time slot scheduled for downlink data communication; and means for sending an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

[0015] In an additional aspect of the present disclosure, a base station includes means for sending a semi-persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; means for sending an SPS release in a time slot scheduled for downlink data communication for the user equipment; and means for monitoring an acknowledgement (ACK) or a negative acknowledgement (NACK) from the user equipment in the time slot.

[0016] In an additional aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon for wireless communication by a user equipment, the program code including code for causing the user equipment to receive a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; code for causing the user equipment to monitor an SPS release and the downlink data communication in a time slot scheduled for downlink data communication; and code for causing the user equipment to send an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

[0017] In an additional aspect of the present disclosure, a non - transitory computer - readable medium has program code recorded thereon for wireless communication by a base station, the program code including code for causing the base station to send a semi - persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; code for causing the base station to send an SPS release in a time slot scheduled for downlink data communication for the user equipment; and code for causing the base station to monitor an acknowledgement (ACK) or negative acknowledgement (NACK) from the user equipment in the time slot.

[0018] Other aspects, features, and advantages of the present invention will become apparent to those of ordinary skill in the art upon reading the following description of specific exemplary embodiments of the invention in conjunction with the accompanying drawings. While the features of the present invention may be discussed with respect to certain examples and figures below, all embodiments of the present invention 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 in accordance with various other embodiments of the present invention discussed herein. In a similar manner, while exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a schematic diagram of a wireless communication system.

[0020] Figure 2 is a conceptual illustration of an example of a radio access network.

[0021] Figure 3 illustrates the organization of wireless resources in an air interface using orthogonal frequency - division multiplexing (OFDM).

[0022] Figure 4 illustrates an example of a time - slot structure in a CA system using cross - carrier scheduling, where the scheduling entity and the scheduled entity have different sub - carrier spacings (SCSs).

[0023] Figure 5 illustrates a scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0024] Figure 6 illustrates a scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0025] Figure 7 illustrates a scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0026] Figure 8Shows the scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0027] Figure 9 Shows the scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0028] Figure 10A Shows the scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0029] Figure 10B Shows the scheduling / transmission configuration of a wireless communication method according to some aspects of the present disclosure.

[0030] Figure 11 Is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.

[0031] Figure 12 Is a block diagram of an exemplary base station (BS) according to aspects of the present disclosure.

[0032] Figure 13 Shows a flowchart of a wireless communication method according to some aspects of the present disclosure.

[0033] Figure 14 Shows a flowchart of a wireless communication method according to some aspects of the present disclosure.

[0034] Figure 15 Shows a flowchart of a wireless communication method according to some aspects of the present disclosure. Detailed Description

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

[0036] While aspects and embodiments have been described by way of illustration of some examples in this application, those skilled in the art will understand that additional implementations and usage scenarios may occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and / or use cases can be implemented through integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, various applicability of the described innovations may occur. The scope of implementation can range from 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 innovation. In some practical settings, devices incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of different sizes, shapes, and configurations.

[0037] The various concepts presented throughout this disclosure can be implemented across a variety of telecommunications systems, network architectures, and communication standards. Now refer to Figure 1 , as a non-limiting illustrative example, aspects of this disclosure are described with reference to wireless communication system 100. Wireless communication system 100 includes three interacting domains: core network 102, radio access network (RAN) 104, and user equipment (UE) 106. With the aid of wireless communication system 100, UE 106 can achieve data communication with an external data network 110 (e.g., but not limited to, the Internet).

[0038] RAN 104 can implement any suitable one or more wireless communication technologies to provide wireless access to UE 106. As an example, RAN 104 can operate according to the New Radio (NR) specification of the 3rd Generation Partnership Project (3GPP) (commonly referred to as 5G). As another example, RAN 104 can operate under a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as LTE). 3GPP refers to this hybrid RAN as the next-generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0039] As shown in the figure, the RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station is a network element in a radio access network that is responsible for transmitting to and receiving from the radio of a UE in one or more cells. In different technologies, standards, or contexts, a base station may be differently referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), or some other suitable term.

[0040] The radio access network 104 is further shown to support wireless communication of a plurality of mobile devices. In the 3GPP standard, a mobile device may be referred to as a user equipment (UE), but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, mobile phone, terminal, user agent, mobile client, client, or some other suitable term. A UE may be a device that provides access to network services to a user.

[0041] In this document, a "mobile" device does not necessarily have to be capable of movement and can be stationary. The term mobile device or mobile equipment refers generically to a variety of devices and technologies. A UE can include multiple hardware structural components whose size, shape, and arrangement facilitate communication; these components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and various embedded systems, such as those corresponding to the "Internet of Things" (IoT). A mobile device can also be an automobile or other vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, an unmanned aerial vehicle, a multi-rotor helicopter, a quadcopter, a remote control device, consumer and / or wearable devices, such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. A mobile device can also be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. A mobile device can also be a smart energy device, a security device, a solar panel or solar panel array, a municipal infrastructure device that controls electricity (e.g., a smart grid), lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; an agricultural device; a military defense device, a vehicle, an aircraft, a ship, and a weapon, etc. Additionally, a mobile device can provide connected medical or telemedicine support, e.g., telehealthcare. A telehealth device can include a telehealth monitoring device and a telehealth management device, and its communication can be given priority processing or priority access over other types of information, e.g., in terms of priority access for critical service data transmission and / or the associated QoS of critical service data transmission.

[0042] The wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) via the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission initiated at a scheduling entity (described further below; e.g., base station 108). Another way to describe this scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term uplink can refer to a point-to-point transmission initiated at a scheduled entity (described further below; e.g., UE 106).

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

[0044] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity and schedule resources for one or more scheduled entities (e.g., one or more other UEs).

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

[0046] Generally, the base station 108 can include a backhaul interface for communicating with the backhaul portion 120 of the wireless communication system. The backhaul 120 can provide a link between the base station 108 and the core network 102. Additionally, in some examples, the backhaul network can provide an interconnection between the various base stations 108. Various types of backhaul interfaces can be used, such as direct physical connections, virtual networks, etc., using any suitable transport network.

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

[0048] Now referring Figure 2 , by way of example and not limitation, a schematic illustration of the RAN 200 is provided. In some examples, the RAN200 can be related to the above and Figure 1is the same as the RAN 104 shown. The geographical area covered by the RAN 200 can be divided into cellular areas (cells), which can be uniquely identified by user equipment (UE) based on the identification broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cell 208 are shown, and each cell can include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. The radio links within a sector can be identified by a single logical identification belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by an antenna group, with each antenna responsible for communicating with UEs in a part of the cell.

[0049] In Figure 2 two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH through a feeder cable. In the example shown, cells 202, 204, and 126 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in small cell 208 (e.g., micro cell, pico cell, femto cell, home base station, home node B, home eNode B, gNode B, or gNB, etc.) that may overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports a cell with a relatively small size. The cell size can be determined according to system design and component constraints.

[0050] It should be understood that the radio access network 200 can include any number of radio base stations and cells. In addition, relay nodes can be deployed to expand the size or coverage area of a given cell. Base stations 210, 212, 214, 218 provide a wireless access point to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be the same as the base station / scheduling entity 108 described above and Figure 1 shown in

[0051] Figure 2 also includes a quadcopter or unmanned aerial vehicle 220, which can be configured to be used as a base station. That is, in some examples, a cell is not necessarily stationary, and the geographical area of the cell can move according to the position of a mobile base station such as the quadcopter 220.

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

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

[0054] On the other hand, in the RAN 200, sidelink signals may be used between UEs without relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) may use peer-to-peer (P2P) or sidelink signal 227 to communicate with each other without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is shown communicating with UEs 240 and 242. Here, UE 238 may act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 may act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE may act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, in addition to communicating with scheduling entity 238, UEs 240 and 242 may optionally communicate directly with each other. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, P2P configuration, or mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.

[0055] In the radio access network 200, the ability of a UE to communicate while moving regardless of its location is referred to as mobility. The various physical channels between the UE and the radio access network are typically managed by an access and mobility management function (AMF, not shown, Figure 1Established, maintained, and released under the control of a part of the core network 102, this function may include a security context management function (SCMF) that manages the security context of the control plane and user plane functions, and a security anchor function (SEAF) that performs authentication.

[0056] In various aspects of the present disclosure, the radio access network 200 may utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., transfer the connection of the UE from one radio channel to another radio channel). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signals from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this period, if the UE moves from one cell to another cell, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell within a given amount of time, the UE may perform a handover or handoff from the serving cell to the neighboring (target) cell. For example, the UE 224 (illustrated as a vehicle, although any suitable form of UE may be used) may move from the geographical area corresponding to its serving cell 202 to the geographical area corresponding to the neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this situation to its serving base station 210. In response, the UE 224 may receive a handover command, and the UE may perform a handover to the cell 206.

[0057] In a network configured for UL-based mobility, UL reference signals from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to the derived timing, transmit uplink pilots or reference signals. The uplink pilot signals transmitted by a UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of the cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell of UE 224. As UE 224 moves through the radio access network 200, the network can continue to monitor the uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signal measured by an adjacent cell exceeds the signal strength or quality measured by the serving cell, the network 200 can switch UE 224 from the serving cell to the adjacent cell, with or without notifying UE 224.

[0058] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be unified, the synchronization signals may not identify a specific cell, but may identify a zone of multiple cells operating at the same frequency and / or the same timing. Implementing zones in a 5G network or other next-generation communication network enables an UL-based mobility framework and improves the efficiency of UEs and the network because the number of mobility messages that need to be exchanged between UEs and the network can be reduced.

[0059] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically achieved by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although some technical rules typically still need to be followed to access unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum may be between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, e.g., to obtain access under suitable conditions determined by the license holder.

[0060] The air interface in radio access network 200 may utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where two endpoints can communicate with each other bidirectionally. Full duplex means that the two endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full duplex channel typically relies on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full duplex emulation is typically achieved for a wireless link by utilizing frequency division duplexing (FDD) or time division duplexing (TDD). In FDD, the transmission operations in different directions occur at different carrier frequencies. In TDD, the transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very rapidly, such as several times per time slot.

[0061] The air interface in radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) (also known as single carrier FDMA (SC-FDMA)) with CP. However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes may be utilized to provide. Additionally, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes may be utilized to provide multiplexing for DL transmissions from base station 210 to UEs 222 and 224.

[0062] Reference will be made to Figure 3 the OFDM waveform schematically shown in to describe various aspects of the present disclosure. Those of ordinary skill in the art should understand that the various aspects of the present disclosure can be applied in substantially the same manner as described below to the DFT-s-OFDMA waveform. That is, although for clarity some examples of the present disclosure may focus on OFDM links, it should be understood that the same principles can also be applied to the DFT-s-OFDMA waveform.

[0063] As mentioned in this disclosure, a frame refers to a 10 ms duration for wireless transmission. Each frame includes 10 sub - frames, each sub - frame being 1 ms. On a given carrier, there can be one set of frames in the UL and another set of frames in the DL. Now referring to Figure 3 , an expanded view of an exemplary DL sub - frame 302 is shown, which shows an OFDM resource grid 304. However, as will be readily understood by those skilled in the art, depending on many factors, the PHY transmission structure for any particular application can be different from the example described here. Here, time is in the horizontal direction, in units of OFDM symbols; frequency is in the vertical direction, in units of sub - carriers or tones.

[0064] The resource grid 304 can be used to schematically represent the time - frequency resources of a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 304 can be used for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE is 1 sub - carrier × 1 symbol, which 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 can be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of consecutive sub - carriers in the frequency domain. In one example, an RB can include 12 sub - carriers, the number being independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In this disclosure, it is assumed that a single RB such as RB 308 fully corresponds to a single communication direction (either transmit or receive for a given device).

[0065] UEs typically utilize only a subset of the resource grid 304. An RB can be the smallest resource unit that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. In this illustration, RB 308 is shown as occupying less than the entire bandwidth of sub - frame 302, and some sub - carriers are shown above and below RB 308. In a given implementation, sub - frame 302 can have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this illustration, RB 308 is shown as occupying less than the entire duration of sub - frame 302, although this is merely one possible example.

[0066] Each 1 ms sub - frame 302 can include one or more adjacent time slots. As an illustrative example, in Figure 3In the example shown, a subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols having a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini - time slots having a shorter duration (e.g., one or two OFDM symbols). In some instances, these mini - time slots may occupy resources scheduled for ongoing time - slot transmissions for the same or different UEs to transmit.

[0067] An enlarged view of one of the time slots 310 shows a time slot 310 including a control region 312 and a data region 314. Generally, the control region 312 may carry a control channel (e.g., PDCCH), and the data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all - DL, all - UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary in nature, different time - slot structures may be utilized, and each of the (multiple) control regions and (multiple) data regions may include one or more.

[0068] Although Figure 3 not shown, each RE 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other RE 306 within the RB 308 may also carry pilots or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), or sounding reference signals (SRS). These pilots or reference signals may provide channel estimation of the corresponding channels to the receiving device, which may enable coherent demodulation / detection of the control and / or data channels within the RB 308.

[0069] In DL transmission, a transmitting device (e.g., the scheduling entity 108) may allocate one or more REs 306 (e.g., within the control region 312) to one or more scheduled entities 106 to carry DL control information 114 including 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), including but not limited to power control commands, scheduling information, grants, and / or allocation of REs for DL and UL transmissions. The PHICH carries HARQ feedback transmissions, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, where the integrity of a packet transmission can be checked at the receiving side, e.g., using any suitable integrity check mechanism such as a checksum or a cyclic redundancy check (CRC) to ensure accuracy. If the integrity of the transmission is confirmed, an ACK may be sent, while if not confirmed, a NACK may be sent. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

[0070] In UL transmission, a transmitting device (e.g., the scheduled entity 106) may utilize one or more REs 306 to carry UL control information 118 including one or more UL control channels (such as the Physical Uplink Control Channel (PUCCH)) to the scheduling entity 108. The UL control information may 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 control information 118 may include a scheduling request (SR), e.g., a request for the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR sent on the control channel 118, the scheduling entity 108 may send downlink control information 114, and the downlink control information 114 may schedule resources for uplink packet transmission. The UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.

[0071] In addition to control information, one or more resource elements (REs) 306 can be allocated for user data or traffic data (e.g., within data region 314). Such traffic can be carried on one or more traffic channels, such as, for DL transmission, on the physical downlink shared channel (PDSCH); or for UL transmission, on the physical uplink shared channel (PUSCH). In some examples, one or more REs 306 within data region 314 can be configured to carry a system information block (SIB) that carries information enabling access to a given cell.

[0072] The channels or carriers described above and shown in Figures 1-3 are not necessarily all of the channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106. Those of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, can be used in addition to those shown.

[0073] These physical channels are typically multiplexed and mapped to transport channels for processing at the media access control (MAC) layer. A transport channel carries an information block called a transport block (TB). Based on the modulation and coding scheme (MCS) and the number of resource blocks (RBs) in a given transmission, the transport block size (TBS), which can correspond to the number of information bits, can be a controlled parameter.

[0074] Turning to a specific example of the present disclosure, Figure 4 Example 400 of a time slot structure in a carrier aggregation (CA) system using cross-carrier scheduling is shown, where the corresponding scheduling entity and scheduled entity have different subcarrier spacings (SCSs). In this example, a designated serving cell (e.g., a gNB, a scheduling cell, or a scheduling entity such as Figure 1 entity 108 in Figure 4 or a primary serving cell (PSC)) schedules resources for a plurality of other cells (i.e., scheduled cells or secondary serving cells (SSCs)), which are typically up to eight cells. However, in the

[0075] example shown, for simplicity of illustration, the scheduling cell schedules only one cell. μdetermined at 15 kHz, which is typically the shortest SCS interval used, and the scheduled cell utilizes an SCS of 120 kHz (i.e., in a known set of interval parameters, the interval parameter μ = 3), but those skilled in the art will understand that the present disclosure is applicable to any of several SCS intervals. In a known system, an SCS of 15 kHz will result in a time slot of one (1) millisecond (ms), such as time slot 402, which can also constitute an entire 1 ms subframe. As shown at 404, an SCS of 120 kHz will result in eight time slots in a 1 ms subframe with a duration of 1 ms / 8 or 0.125 ms, time slots 0 through time slot 7 (i.e., reference numerals 406, 408, 410, 412, 414, 416, 418, and 420, respectively). These time slots 406 - 420 represent eight PDSCH transmissions in the scheduled cell, which are scheduled by the PDCCH in the scheduling cell (i.e., time slot 402 of the scheduling cell). For a typical wireless system in current 5G NR, Figure 4 The scenario shown will constitute a worst - case scenario, where the scheduling cell has an SCS of 15 kHz and the scheduled cell has an SCS of 120 kHz. Further note that in this example, when an SCS of 15 kHz and an SCS of 120 kHz are used for the two cells respectively, a single time slot 402 of the scheduling cell overlaps in time with eight (8) time slots (406 - 420) of the scheduled cell, but other SCS values will result in other parameter sets and overlaps, such as in the example of an SCS of 15 kHz in the scheduling cell and an SCS of 60 kHz (i.e., μ = 2) in the scheduled cell, where one scheduling cell time slot overlaps with four time slots of the scheduled cell.

[0076] For cross - carrier scheduling, the scheduling cell includes a PDCCH 422, which has a downlink control indicator (DCI) for DL reception and UL transmission used by the scheduled cell and other control information such as a time - slot format indicator, where the DCI is decoded from the PDCCH 422 of the scheduling cell. The SCS difference between the scheduling and the scheduled cells poses difficulties for UE decoding of the PDCCH 422. As can be seen from the figure, since the PDCCH 422 is typically located at the start of time slot 0 402, there can be significant latency and buffering experienced by the UE. Here, the DCI for all time slots of the scheduled cell is sent in the same PDCCH monitoring occasion, which results in the UE not being able to determine which DCI is designated for the control information in which time slot before the DCI is decoded. For example, the DCI for the last time slot of the scheduled cell (i.e., Figure 4 time slot 7 (420) in Figure 4The DCI in slot 0 (406)) is sent together in the same symbol set in the scheduled cell. The UE can decode the DCI of the last slot before decoding the DCI of the first slot. As a result, for the UE, there is a large timing delay for the UE to be able to decode the PDSCH sent in the first slot (i.e., slot 1 after slot 0). Therefore, this arrangement has a timing problem, especially since the UE needs to complete PDCCH decoding and DCI pruning and parsing quickly enough to allow the UE to complete decoding of the subsequent physical downlink shared channel PDSCH before the UL transmission time for ACK / NACK reporting. These resulting timing problems can lead to unnecessary NACK reports and further delays.

[0077] Figure 5 It shows the transmission of unicast PDSCH symbols and SPS release indicators within a single slot, which allows UE with limited capabilities to operate according to 3GPP Release 16. Specifically, this method allows the release of SPS in the same slot in which the UE receives the semi-persistent scheduled (SPS) PDSCH, for example, for an SPS period as low as 1 slot.

[0078] In one method, PDSCH slot 502 may include a first part 504, followed by a second part. The SPS PDSCH symbol (e.g., SPS start length indicator variable - SLIV) 508 may always be sent in the second part 506 of slot 502. The first part 504 can be used to send a release DCI (SPS release) 510 if necessary. In this way, when the UE receives the release DCI 510, it knows to release the SPS and can ignore the subsequent SPS symbols 508 within the same slot 502. In other cases where nothing is received within the first part 504, the UE can only receive the SPS symbols 508 in the second part 506. Note that the SPS symbols 508 appear early enough in the second part 506 of slot 502 to allow the UE to send ACK / NACK to the sender (e.g., gNodeB).

[0079] According to another aspect, the release DCI 510 can be sent within slot 502 at least Nx symbols before the start of the expected reception of the SPS symbols 508. Nx can be the number of symbols greater than or equal to zero (e.g., one symbol, two symbols, etc.). This allows the receiving UE to have enough time to send ACK / NACK.

[0080] As Figure 5As shown, the present disclosure provides a mechanism for allowing a UE to receive an SPS release within a time slot having scheduled downlink data communication. The scheduled downlink data communication can be a unicast PDSCH associated with dynamic grant and / or SPS grant. In some instances, the UE is a restricted-capability device configured to receive a single physical downlink shared channel (PDSCH) communication per time slot. In this regard, the UE can be configured to provide only a single ACK / NACK per time slot. As shown, the UE can monitor the PDCCH and PDSCH communication of time slot 502. For example, the UE can monitor a set of decoding candidates for the PDCCH (which can include the SPS release 510 and / or dynamic grant) for the associated DCI communication. The UE can then send a feedback message (e.g., ACK / NACK) on the PUCCH to the base station indicating whether the PDCCH communication was successfully detected and decoded.

[0081] When the restricted-capability UE detects the SPS release 510 in time slot 502, the UE does not expect to receive PDSCH communication in time slot 502. In this regard, since the UE is a restricted-capability device and can provide only a single ACK / NACK for time slot 502, the base station should not send both the SPS release 510 and downlink data communication in time slot 502. Thus, if the restricted-capability UE detects the SPS release 510 in time slot 502, it will not expect to receive any downlink data communication in time slot 502. In some instances, after receiving an SPS release in a time slot, the UE does not expect to receive downlink communication (including SPS PDSCH and / or dynamic PDSCH). In some instances, before the first symbol of a scheduled downlink data communication, the UE does not expect to receive an SPS release (e.g., SPS PDSCH and / or dynamic PDSCH) after a predetermined number of symbols.

[0082] As a result, the ACK / NACK provided by the UE for time slot 502 will be based on the detection and successful decoding of the SPS release 510. If the SPS release 510 is successfully decoded, the UE will send an ACK on the PUCCH, and if the SPS release is not detected and / or not successfully decoded, the UE will send a NACK. Since time slot 502 is scheduled for downlink data communication, in the case where the UE does not detect the SPS release 510 sent from the base station, the UE will monitor the scheduled downlink data communication in time slot 502. However, as described above, due to the limited capabilities of the UE, the base station will not send the scheduled downlink data communication in the same time slot as the SPS release 510. Therefore, the UE will not detect or successfully decode the scheduled downlink data communication in time slot 502. As a result, the UE will send a NACK to the base station via the PUCCH. Although the UE can send a NACK based on the failure to detect and successfully decode the scheduled downlink data communication, the base station can determine based on the NACK that the UE has not received the sent SPS release 510. Therefore, in response to receiving a NACK from the UE, the base station can implement a process for retransmitting the SPS release 510.

[0083] In some instances, the ACK / NACK feedback timing of the SPS release 510 is aligned with the ACK / NACK feedback timing of the scheduled downlink data communication of the time slot 502. For example, the SPS release may include downlink control information (DCI) that specifies the timing at which to send the ACK / NACK feedback (e.g., a specified number of symbols after receiving the SPS release on the PDCCH). The timing for sending the ACK / NACK for the SPS release 510 may be scheduled for the same time slot (or sub-slot) of the PUCCH as the ACK / NACK for the scheduled downlink data communication (e.g., dynamic grant and / or SPS grant). For example, the SPS PDSCH transmission may be activated by the SPS activation DCI, and both the SPS activation DCI and the SPS release DCI may be configured such that the respective acknowledgments are aligned. In other words, the ACK / NACK for the SPS release 510 and the HARQ ACK / NACK for the downlink data communication may be scheduled for the same time slot (or sub-slot) on the same codebook. By aligning the ACK / NACK feedback timing, the base station can monitor a single ACK / NACK response from the UE on the PUCCH. As described above, the base station can determine whether the UE has successfully received the SPS release 510 based on the single ACK / NACK, regardless of whether the UE sends the ACK / NACK based on the SPS release 510 or based on the scheduled downlink data communication. In this regard, when the SPS release 510 is detected and successfully decoded, the UE will send an ACK. When the SPS release 510 is detected but not successfully decoded, the UE will send a NACK. When the SPS release 510 is not detected, the UE may also send a NACK. For example, when the SPS release 510 is not detected or missed, the UE may monitor the scheduled downlink data communication. However, the base station will not send the scheduled downlink data communication and the SPS release 510 in the same time slot. Therefore, the UE will not detect or successfully decode the scheduled downlink data communication in the time slot 502 and will thus send the associated NACK. Since the ACK / NACK timing of the SPS release 510 and the ACK / NACK timing of the scheduled data communication are the same, the base station can determine whether the UE has successfully received the SPS release 510 based on the single ACK / NACK received.

[0084] It should be noted that this method is also beneficial for non-restricted-capability UEs. These can include UEs that are capable of receiving more than one PDSCH in the same time slot and / or are not restricted to a single ACK / NACK related to the transmission in the same time slot. For example, in the case where the scheduled downlink data communication in time slot 502 is a scheduled SPS downlink data communication and the SPS release 510 is configured to release the resources associated with the scheduled SPS downlink data communication, the UE does not expect to receive the SPS release 510 and the scheduled SPS downlink data communication in the same time slot. In some instances, the ACK / NACK feedback timing of the SPS release 510 is aligned with the ACK / NACK feedback timing of the scheduled SPS downlink data communication in time slot 502. For example, the timing for transmitting the ACK / NACK of the SPS release 510 received via the PDCCH can be scheduled for the same time slot (or sub-slot) of the PUCCH as the ACK / NACK for the scheduled SPS downlink data communication. By aligning the ACK / NACK feedback timing, the base station can monitor a single ACK / NACK response from the non-restricted-capability UE on the PUCCH. In a similar manner to the restricted-capability UE scenario, the base station can determine whether the non-restricted-capability UE has successfully received the SPS release 510 based on the single ACK / NACK, regardless of whether the UE sends the ACK / NACK based on the SPS release 510 or based on the scheduled SPS downlink data communication. In this regard, when the SPS release 510 is detected and successfully decoded, the non-restricted-capability UE will send an ACK. When the SPS release 510 is detected but not successfully decoded, the non-restricted-capability UE will send a NACK. When the SPS release 510 is not detected, the non-restricted-capability UE can also send a NACK. For example, when the SPS release 510 is not detected, the non-restricted-capability UE can monitor the scheduled SPS downlink data communication. However, the base station will not send both the scheduled SPS downlink data communication and the SPS release 510 in the same time slot. Therefore, the non-restricted-capability UE will not detect or successfully decode the scheduled SPS downlink data communication in time slot 502 and will thus send the associated NACK. Since the ACK / NACK timing of the SPS release 510 and the ACK / NACK timing of the scheduled SPS data communication are the same, the base station can determine whether the non-restricted-capability UE has successfully received the SPS release 510 based on the received single ACK / NACK.

[0085] In other words, for a non-restricted-capability UE, the UE does not expect to receive an SPS PDSCH in the same time slot as the configuration index being released by the SPS release PDCCH in the time slot, and the K1 indication in the SPS release and SPS activation is for the same (sub-) time slot for sending ACK / NACK on the PUCCH. For a non-restricted-capability UE, the UE does not expect the PDSCH to be only for the same SPS PDSCH (not for any PDSCH in the time slot), and when the K1 in the release and the K1 in the SPS PDSCH indicate the same (sub-) time slot. In some instances, the base station sets the K1 value such that the UE does not end up with out-of-order HARQ-ACK processing (e.g., the release PDCCH is before the PDSCH, but its HARQ-ACK is indicated to be sent after the HARQ-ACK of the PDSCH).

[0086] Figure 6-1 0 shows an example of how the mechanism shown and described in the context of Figure 5 allows a UE to receive an SPS release within a time slot with scheduled downlink data communication.

[0087] Figure 6 FIG. 10 shows a scheduling / transmission configuration 600 of a wireless communication method according to some aspects of the present disclosure. The scheduling / transmission configuration 600 shows a downlink control channel (PDCCH 605), a downlink data channel (PDSCH 610), and an uplink control channel (PUCCH 615). As further shown and discussed below, an SPS release 620, downlink data 625, and / or ACK / NACK 630 may be sent via the PDCCH 605, PDSCH 610, and / or PUCCH 615. The scheduling / transmission configuration 600 shows two time slots (time slot n and time slot n+1) with scheduled downlink data communication. In the example shown, each of the time slots (time slot n and time slot n+1) is associated with scheduled SPS downlink data communication indicated by SPS resources 640-a (time slot n) and SPS resources 640-b (time slot n+1). The SPS resources 640-a and 640-b may be associated with the same SPS grant (e.g., an SPS grant with a period of 1 time slot as shown), or may be associated with different SPS grants (e.g., SPS resource 640-a is associated with a first SPS grant and SPS resource 640-b is associated with a different second SPS grant).

[0088] In time slot n, the base station transmits downlink data 625-a associated with the scheduled SPS downlink data communication to the UE via PDSCH 610 using SPS resource 640-a. The UE transmits ACK / NACK 630-a via PUCCH 615 to indicate to the base station whether the downlink data 625-a has been successfully decoded. The timing (e.g., K1 value, PUCCH scheduling, etc.) and / or the codebook for ACK / NACK 630-a can be provided in and / or based on the SPS grant associated with the downlink data 625-a.

[0089] In time slot n+1, the base station transmits an SPS release 620-b to the UE via PDCCH 605. The UE transmits ACK / NACK 630-b to the base station via PUCCH 615. As shown, the timing of ACK / NACK 630-b can be configured such that the ACK / NACK for the SPS release 620-b is aligned with the ACK / NACK for the SPS resource 640-b in the same time slot (or sub-slot) of PUCCH 615. In this regard, the timing (e.g., K1 value, PUCCH scheduling, etc.) and / or the codebook for the ACK / NACK for the SPS release 620-b can be provided as part of the SPS release 620-b. The timing (e.g., K1 value, PUCCH scheduling, etc.) and / or the codebook for the ACK / NACK for the SPS resource 640-b can be provided in and / or based on the associated SPS grant. In some instances, the SPS release 620-b indicates to the UE to release the SPS resource 640-b associated with the SPS grant. In some instances, the SPS release 620-b indicates to the UE to release SPS resources other than the SPS resource 640-b (e.g., SPS resources associated with different SPS grants).

[0090] As described above, Figure 6The scheduling / transmission configuration 600 is applicable to both the limited-capability UE and the non-limited-capability UE. In this regard, the base station can determine whether the UE (limited or non-limited) has successfully received the SPS release 620-b based on a single ACK / NACK 630-b, regardless of whether the UE sends the ACK / NACK based on the SPS release 620-b or based on the scheduled SPS downlink data communication. In this regard, when the SPS release 620-b is detected and successfully decoded, the UE will send an ACK. When the SPS release 620-b is detected but not successfully decoded, the UE will send a NACK. When the SPS release 620-b is not detected, the UE may also send a NACK. For example, when the SPS release 620-b is not detected or missed, the UE can monitor the scheduled SPS downlink data communication on the SPS resource 640-b of the PDSCH 610. However, the base station will not send the scheduled SPS downlink data communication through the PDSCH 610 and the SPS release 510 through the PDCCH 605 in the same time slot (time slot n+1). Therefore, the UE will not detect or successfully decode the scheduled SPS downlink data communication and will thus send a NACK. Since the ACK / NACK timing for the SPS release 620-b and the ACK / NACK timing for the scheduled SPS data communication are the same on the PUCCH 615, the base station can determine whether the UE (limited or non-limited) has successfully received the SPS release 620-b based on the single received ACK / NACK.

[0091] Figure 7Illustrates scheduling / transmission configuration 700 of a wireless communication method according to some aspects of the present disclosure. Scheduling / transmission configuration 700 shows a downlink control channel (PDCCH 705), a downlink data channel (PDSCH 710), and an uplink control channel (PUCCH 715). As further shown and discussed below, an SPS release 720, downlink data 725, ACK / NACK 730, and / or downlink control information 735 may be sent via the PDCCH 705, PDSCH 710, and / or PUCCH 715. For example, DCI 735 may schedule a dynamic PDSCH transmission for a UE. Scheduling / transmission configuration 700 shows two time slots (time slot n and time slot n+1) with scheduled downlink data communication. In the illustrated example, each of the time slots (time slot n and time slot n+1) is associated with scheduled SPS downlink data communication indicated by SPS resource 740-a (time slot n) and SPS resource 740-b (time slot n+1). SPS resources 740-a and 740-b may be associated with the same SPS grant (e.g., an SPS grant with a period of 1 time slot as shown), or may be associated with different SPS grants (e.g., SPS resource 740-a is associated with a first SPS grant and SPS resource 740-b is associated with a different second SPS grant).

[0092] In time slot n, the base station sends an SPS release 720-a to the UE via PDCCH 705. The UE sends an ACK / NACK 730-a to the base station via PUCCH 715. As shown, the timing of the ACK / NACK 730-a can be configured such that the ACK / NACK for the SPS release 720-a is aligned with the ACK / NACK for the SPS resource 740-a in the same time slot (or sub-slot) of the PUCCH 715. In this regard, the timing (e.g., K1 value, PUCCH scheduling, etc.) and / or codebook of the ACK / NACK for the SPS release 720-a can be provided as part of the SPS release 720-a. The timing (e.g., K1 value, PUCCH scheduling, etc.) and / or codebook of the ACK / NACK for the SPS resource 740-a can be provided in and / or based on the associated SPS grant. The SPS release 720-a may indicate to the UE to release the SPS resource 740-b scheduled for time slot n+1. In some instances, the SPS release 720-a indicates to the UE to release the SPS resource 740-b and the SPS resource 740-a (e.g., where the SPS resources 740-a and 740-b are associated with a common SPS grant with a period of 1 time slot). In some instances, the SPS release 720-a indicates to the UE to release the SPS resource 740-b (or other SPS resource) associated with an SPS grant different from the SPS resource 740-a.

[0093] As shown in the figure, before the SPS resource 740-b is scheduled in time slot n+1, the base station sends an SPS release 720-a to the UE via the PDCCH 705. As a result, there is a time period 750 between the SPS release 720-a and the scheduling of the SPS resource 740-b in time slot n+1. In some instances, if the time period 750 meets a threshold, one or more of the previously scheduled SPS resources 740-b released by the SPS release 720-a or overlapping therewith can be used to schedule and transmit one or more other downlink data communications to the UE. On the other hand, if the time period 750 does not meet the threshold, the scheduled SPS resource 740-b released by the SPS release 720-a should not be used to schedule or transmit any downlink data communications to the UE. In some instances, the threshold for the time period 750 is the number of symbols (e.g., 5, 7, 8, 10, 12, 14, 16, 20, 24, 28, 32, or any other suitable number), the time length (e.g., 66 microseconds, 83 microseconds, 233 microseconds, 250 microseconds, 500 microseconds, or any other suitable time), and / or a combination thereof. In some instances, the threshold for the time period 750 is determined based on the capabilities of the UE (e.g., available processing resources, processing time of the PDCCH, processing time of the PDSCH, etc.). The UE can convey its capabilities (e.g., one or more PDSCHs per time slot, processing parameters, etc.) to the base station in a capability report. According to the present disclosure, the base station can utilize the capabilities of the UE to schedule communications with the UE.

[0094] In Figure 7 the example of, the time period 750 meets the threshold required to allow the use of the previously scheduled SPS resource 740-b to schedule and transmit one or more other downlink data communications to the UE. Accordingly, in time slot n+1, the downlink control information 735-b sent via the PDCCH 705 uses one or more of the SPS resources 740-b to schedule the downlink data 725-b. The SPS resource 740-b is released as a result of the SPS release 720-a, as indicated by the "X" of the SPS resource 740-b. Although Figure 7 illustrates an example where the SPS release 720-a is sent in a different time slot from the SPS resource 740-b being released, in other instances, the SPS release is sent in the same time slot as the SPS resource being released, and the time period 750 is evaluated in a similar manner to determine whether the previously scheduled SPS resource can be used to send other downlink data communications.

[0095] Figure 8A scheduling / transmission configuration 800 for a wireless communication method according to some aspects of the present disclosure is shown. The scheduling / transmission configuration 800 is similar in some aspects to the scheduling / transmission configuration 700 discussed above, but the scheduling / transmission configuration 800 shows an example where the time period between the SPS release and the scheduled SPS resource does not meet the threshold required to allow the use of or overlap with a previously scheduled SPS resource to schedule and transmit one or more other downlink data communications to a UE.

[0096] The scheduling / transmission configuration 800 shows a physical downlink control channel (PDCCH 805), a physical downlink data channel (PDSCH 810), and a physical uplink control channel (PUCCH 815). As further shown and discussed below, the SPS release 820, the downlink data 825, the ACK / NACK 830, and / or the downlink control information 835 (e.g., DCI for scheduling a dynamic PDSCH transmission for a UE) can be sent via the PDCCH 805, the PDSCH 810, and / or the PUCCH 815. The scheduling / transmission configuration 800 shows two time slots (time slot n and time slot n+1) with scheduled downlink data communications. In the example shown, each of the time slots (time slot n and time slot n+1) is associated with a scheduled SPS downlink data communication indicated by an SPS resource 840-a (time slot n) and an SPS resource 840-b (time slot n+1). The SPS resources 840-a and 840-b can be associated with the same SPS grant (e.g., an SPS grant with a period of 1 time slot as shown), or can be associated with different SPS grants (e.g., the SPS resource 840-a is associated with a first SPS grant and the SPS resource 840-b is associated with a different second SPS grant).

[0097] In time slot n, the base station sends an SPS release 820-a to the UE via the PDCCH 805. The UE sends an ACK / NACK 830-a to the base station via the PUCCH 815. As shown, the timing of the ACK / NACK 830-a can be configured such that the ACK / NACK for the SPS release 820-a is aligned with the ACK / NACK for the SPS resource 840-a in the same time slot (or sub-slot) of the PUCCH 815. In this regard, the timing (e.g., K1 value, PUCCH scheduling, etc.) and / or codebook of the ACK / NACK for the SPS release 820-a can be provided as part of the SPS release 820-a. The timing (e.g., K1 value, PUCCH scheduling, etc.) and / or codebook of the ACK / NACK for the SPS resource 840-a can be provided in and / or based on the associated SPS grant. The SPS release 820-a may indicate to the UE to release the SPS resource 840-b scheduled for time slot n+1. In some instances, the SPS release 820-a indicates to the UE to release the SPS resource 840-b and the SPS resource 840-a (e.g., where the SPS resources 840-a and 840-b are associated with a common SPS grant with a period of 1 time slot). In some instances, the SPS release 820-a indicates to the UE to release the SPS resource 840-b (or other SPS resource) associated with an SPS grant different from the SPS resource 840-a.

[0098] As shown in the figure, before the SPS resource 840-b is scheduled in time slot n+1, the base station sends an SPS release 820-a to the UE via the PDCCH 805. As a result, there is a time period 850 between the SPS release 820-a and the scheduling of the SPS resource 840-b in time slot n+1. In some instances, if the time period 850 meets a threshold, the previously scheduled SPS resource 840-b released by the SPS release 820-a can be used to schedule and send other downlink data communications to the UE. On the other hand, if the time period 850 does not meet the threshold, the scheduled SPS resource 840-b released by the SPS release 820-a should not be used to schedule or send any downlink data communications to the UE. In some instances, the threshold for the time period 850 is the number of symbols (e.g., 5, 7, 8, 10, 12, 14, 16, 20, 24, 28, 32, or any other suitable number), the length of time (e.g., 66 microseconds, 83 microseconds, 233 microseconds, 250 microseconds, 500 microseconds, or any other suitable time), or a combination thereof. In some instances, the threshold for the time period 850 is determined based on the capabilities of the UE (e.g., available processing resources, processing time of the PDCCH, processing time of the PDSCH, etc.). The UE can convey its capabilities (e.g., one or more PDSCHs per time slot, processing parameters, etc.) to the base station in a capability report. According to the present disclosure, the base station can utilize the capabilities of the UE to schedule communications with the UE.

[0099] In Figure 8 the example of, the time period 850 does not meet the threshold required to allow the use of the previously scheduled SPS resource 840-b to schedule and send (one or more) other downlink data communications to the UE. Therefore, in time slot n+1, the downlink control information 835-b and / or the associated downlink data 825-b sent via one or more of the SPS resources 840-b through the PDCCH 805 are not sent, as indicated by the respective "X". Although Figure 8 shows an example where the SPS release 820-a is sent in a time slot different from the SPS resource 840-b being released, in other cases, the SPS release is sent in the same time slot as the SPS resource being released, and the time period 850 is evaluated in a similar manner to determine whether the previously scheduled SPS resource can be used to send other downlink data communications.

[0100] Figure 9The scheduling / transmission configuration 900 of a wireless communication method according to some aspects of the present disclosure is shown. The scheduling / transmission configuration 900 shows a physical downlink control channel (PDCCH 905), a physical downlink data channel (PDSCH 910), and a physical uplink control channel (PUCCH 915). As further shown and discussed below, an SPS release 920, downlink data 925, ACK / NACK 930, and / or downlink control information 935 may be sent via the PDCCH 905, PDSCH 910, and / or PUCCH 915. The scheduling / transmission configuration 900 shows two time slots (time slot n and time slot n + 1) with scheduled downlink data communication. In the example shown, time slot n is associated with the communication of downlink data 925-a. In some instances, the downlink data 925-a is associated with a dynamic grant. For example, the downlink data 925-a may be associated with downlink control information 935-a sent via the PDCCH 905. Time slot n + 1 is associated with the scheduled SPS downlink data communication indicated by the SPS resource 940.

[0101] In time slot n, the base station sends an SPS release 920-a to the UE via the PDCCH 905. In this regard, in some instances, the SPS release 920-a may cover the scheduled downlink data 925-a. For example, in the case where the SPS grant is associated with a ultra-reliable low-latency communication (URLLC) service type and / or other communication with a higher priority than, for example, the downlink data 925-a for an enhanced mobile broadband (eMBB) service type, the acknowledgement of the URLLC SPS release 920-a may take precedence over the acknowledgement of the eMBB downlink data 925-a. In this regard, the UE may send an ACK / NAC930-a for the SPS release 920-a to the base station on the PUCCH 175. As shown, the timing of the ACK / NACK930-a may be configured such that the ACK / NACK for the SPS release 920-a is aligned with the ACK / NACK for the downlink data 925-a in the same time slot (or sub-slot) of the PUCCH 915. The SPS release 920-a may indicate to the UE to release the SPS resource 940 or other SPS resources scheduled for time slot n + 1.

[0102] In some instances, the base station prioritizes the SPS release 920-a over the downlink data 925-a and thus does not transmit the downlink data 925-a. In such a case, the ACK / NACK 930-a of the scheduling / transmission configuration 900 can operate in the same manner as the ACK / NACK of the scheduling / transmission configurations 600, 700, and 800 described above to indicate to the base station whether the UE has successfully detected and decoded the SPS release. In some instances, the base station transmits the SPS release 920-a and the downlink data 925-a during slot n. In such a case, if the UE detects the SPS release 920-a, the UE can transmit the ACK / NACK 930-a based on whether the SPS release 920-a has been successfully decoded. In some cases where both the SPS release 920-a and the downlink data 925-a are transmitted in the same slot, the base station can interpret the ACK / NACK 930-a in relation to the SPS release 920-a rather than the downlink data 925-a. For example, in a case where the ACK / NACK feedback for the URLLC SPS release and the eMBB data transmission would conflict in a slot, the UE can apply a priority rule and determine to transmit the ACK / NACK for the SPS release when the URLLC traffic is associated with a higher priority. In some instances, the UE can be configured to provide multiple ACK / NACKs per slot. Thus, in such a case, the UE can transmit an ACK / NACK for each of the SPS release 920-a and the downlink data 925-a as long as the PUCCH resources scheduled for each ACK / NACK are different. In some instances, the base station can set the timing of the ACK / NACK for the SPS release 920-a and the downlink data 925-a such that the ACK / NACKs are not aligned in the same slot (or sub-slot) of the PUCCH.

[0103] Figure 10A A scheduling / transmission configuration 1000 of a wireless communication method according to some aspects of the present disclosure is shown. As shown, the SPS release 1020 is sent by the base station to the UE a time period (N y ) before the scheduled SPS PDSCH 1008. In some instances, if the time period (N y ) meets a threshold, one or more other downlink data communications 1008 can be scheduled and transmitted to the UE using the previously scheduled SPS PDSCH resources or overlapping with the previously scheduled SPS PDSCH resources. For example, the dynamic authorization DCI 1035 can schedule a dynamic authorization PDSCH 1025 for one or more resources that overlap in time and / or frequency with the resources previously scheduled for the SPS PDSCH 1008. On the other hand, if the time period (N y) If the threshold is not met, the scheduled SPS PDSCH resources should not be used to schedule or transmit downlink data communication 1008 to the UE. For example, the base station may avoid transmitting the dynamic grant PDSCH 1025 (if the dynamic grant DCI 1035 has already been transmitted) and / or avoid transmitting the dynamic grant DCI 1035.

[0104] In some instances, the threshold for the time period (N y ) is the number of symbols (e.g., 5, 7, 8, 10, 12, 14, 16, 20, 24, 28, 32, or any other suitable number), the time length (e.g., 66 microseconds, 83 microseconds, 233 microseconds, 250 microseconds, 500 microseconds, or any other suitable time), and / or a combination thereof. In some instances, the threshold for the time period (N y ) is determined based on the UE's capabilities (e.g., available processing resources, PDCCH processing time, PDSCH processing time, etc.). In some instances, N y = T proc,1 where T proc,1 is the UE's PDSCH processing time. In some instances, the UE includes an indication of the PDSCH processing time in the capability report sent to the base station. In this regard, the capability report may also indicate that the UE is configured to receive one or more PDSCH communications per time slot.

[0105] Figure 10B Illustrates a scheduling / transmission configuration 1050 of a wireless communication method according to some aspects of the present disclosure. As shown, the base station sends an SPS release 1020 to the UE. The SPS release 1020 may include a release DCI and may be sent to the UE on the PDCCH. In some instances, the SPS release 1020 (e.g., the resource on which the base station sends the release DCI message or PDCCH) overlaps in time with a portion or completely with the scheduled SPS PDSCH 1008-a. In other instances, the SPS release 1020 is received before or after the scheduled SPS PDSCH 1008-a. As shown, the SPS release 1020 is received in the time period (N y ) before the scheduled SPS PDSCH 1008-b. In some instances, the time period (N y ) may be between the dynamic grant DCI (instead of the SPS release 1020) and the scheduled SPS PDSCH 1008-b.

[0106] In some instances, if the time period (N y) If the threshold is met, the resources of the scheduled SPS PDSCH 1008-b or resources overlapping with the resources of the scheduled SPS PDSCH 1008-b can be used to schedule and transmit one or more other downlink data communications to the UE. For example, the dynamic grant DCI 1035 can schedule the dynamic grant PDSCH 1025 for one or more resources that overlap in time and / or frequency with the resources previously scheduled for the SPS PDSCH 1008-b. In some instances, the threshold for the time period (N y ) is the number of symbols (e.g., 5, 7, 8, 10, 12, 14, 16, 20, 24, 28, 32, or any other suitable number), the time length (e.g., 66 microseconds, 83 microseconds, 233 microseconds, 250 microseconds, 500 microseconds, or any other suitable time), and / or a combination thereof. In some instances, the threshold for the time period (N y ) is determined based on the UE's capabilities (e.g., available processing resources, PDCCH processing time, PDSCH processing time, etc.). In some instances, N y = T proc,1 , where T proc,1 is the UE's PDSCH processing time. In some instances, the UE includes an indication of the PDSCH processing time in the capability report sent to the base station. In this regard, the capability report can also indicate that the UE is configured to receive one or more PDSCH communications per time slot.

[0107] As also shown, the scheduling / transmission configuration 1050 includes a dynamic grant DCI 1035 sent by the base station to the UE. In some instances, the dynamic grant DCI 1035 may schedule a dynamic grant PDSCH 1025 that overlaps with one or more resources of the scheduled SPS PDSCH 1008-b. The dynamic grant DCI 1035 is sent for at least a period of time (K1) associated with sending an ACK / NACK for the release DCI 1020, an ACK / NACK for the SPS PDSCH 1008-a, and / or the end of the scheduled SPS PDSCH 1008-a. In some instances, the UE does not expect to receive dynamic grant PDCCH communications (e.g., the dynamic grant DCI 1035) from the BS unless the period of time (K1) meets a threshold. In some instances, the threshold for the period of time (K1) is the number of symbols (e.g., 1, 2, 3, 4, 5, 7, 8, 10, 12, 14, 16, 20, 24, 28, 32, or any other suitable number), the length of time (e.g., 44 seconds, 66 microseconds, 83 microseconds, 233 microseconds, 250 microseconds, 500 microseconds, or any other suitable time), and / or a combination thereof. In some instances, the threshold for the period of time (K1) is determined based on the UE's capabilities (e.g., available processing resources, processing time for the PDCCH, processing time for the PDSCH, etc.). In some instances, the threshold for the period of time (K1) is based on the UE's capabilities plus a buffer (e.g., K1≥N1 + d, where N1 is associated with the UE's capabilities and d is the buffer, and in some instances, d≥0). In some instances, the UE includes an indication of the capabilities or associated timing (e.g., N1) in a capabilities report sent to the base station.

[0108] In some instances, if (1) the period of time (N) between the SPS release 1020 (or the dynamic grant DCI 1035) and the scheduled SPS PDSCH 1008-b y) meet the corresponding thresholds, and (2) the time period (K1) between the dynamic grant DCI 1035 and the ACK / NACK for the release DCI 1020, the ACK / NACK for the SPS PDSCH 1008-a, and / or the end of the scheduled SPS PDSCH 1008-a meets the corresponding thresholds, then other downlink data communications (e.g., the dynamic grant PDSCH 1025) can use or overlap with the resources of the scheduled SPS PDSCH 1008-b to be scheduled and sent to the UE. In this regard, in some instances, the BS waits to receive an ACK from the UE for the release DCI 1020 before sending the dynamic grant DCI 1035. Thus, when the BS receives an ACK from the UE for the release DCI 1020, the BS can send the dynamic grant DCI 1035, which indicates that one or more resources overlapping with the now released SPS PDSCH 1008-b will be used to send the dynamic grant PDSCH 1025 to the UE. On the other hand, if the UE does not receive and / or correctly decode the release DCI 1020, the UE can send a NACK for the SPS PDSCH 1008-a (or not send an ACK) to the BS. In turn, the BS can determine that the UE has not successfully received the release DCI and avoid scheduling a dynamic grant for the UE during the scheduled SPS PDSCH 1008-b, avoid sending the dynamic grant DCI 1035 to the UE, and / or avoid sending the dynamic grant PDSCH 1025 to the UE.

[0109] In addition, if the time period (N y ) and / or the time period (K1) do not meet the corresponding thresholds, then downlink data communications overlapping with the scheduled SPS PDSCH resource 1008-b should not be scheduled or sent to the UE. In this regard, when the thresholds of the time period (N y ) and / or the time period (K1) are not met, the BS can avoid sending the dynamic grant DCI 1035 and / or avoid sending the dynamic grant PDSCH 1025 (e.g., if the dynamic grant DCI 1035 has already been sent). In addition, when the time period (N y) and / or when the threshold of the time period (K1) is reached, the UE does not expect to receive the dynamic authorized PDSCH 1025 and may consider the dynamic authorization DCI 1035 as an error. For example, the UE may discard or ignore the information in the dynamic authorization DCI 1035. In this regard, the UE may not decode and / or attempt to decode the dynamic authorized PDSCH 1025 and / or send a NACK associated with the scheduled SPS PDSCH 1008-b. In this regard, the NACK associated with the scheduled SPS PDSCH 1008-b may indicate to the BS that the UE has not successfully received and / or decoded the dynamic authorization DCI 1035 and / or the dynamic authorized PDSCH 1025.

[0110] Figure 11 is a block diagram of an exemplary UE 1100 according to aspects of the present disclosure. The UE 1100 may be the UE 106 discussed above in Figure 1 As shown, the UE 1100 may include a processor 1102, a memory 1104, a downlink scheduling and SPS control module 1108, a transceiver 1110 including a modem subsystem 1112 and a radio frequency (RF) unit 1114, and one or more antennas 1116. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

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

[0112] The memory 1104 may include a cache memory (e.g., the cache memory of the processor 1102), a random access memory (RAM), a magnetoresistive RAM (MRAM), a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a flash memory, a solid state storage device, a hard disk drive, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one example, the memory 1104 includes a non-transitory computer-readable medium. The memory 1104 may store or record instructions 1106 thereon. The instructions 1106 may include, when executed by the processor 1102, causing the processor 1102 to perform the operations described herein in connection with aspects of the present disclosure (e.g., Figures 5-10B, aspects of 13 and 15) Instructions for the operations described with reference to UE 106. Instruction 1106 may also be referred to as program code. The program code can be used to cause a wireless communication device (or a particular component of the wireless communication device) to perform these operations, such as by causing one or more processors (e.g., processor 1102) to control or command the wireless communication device (or a particular component of the wireless communication device) to do so. The terms "instructions" and "code" should be interpreted broadly to include any type of computer-readable statement. For example, the terms "instructions" and "code" can refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" can include a single computer-readable statement or multiple computer-readable statements.

[0113] The downlink scheduling and SPS control module 1108 can be implemented via hardware, software, or a combination thereof. For example, the downlink scheduling and SPS control module 1108 can be implemented as a processor, circuitry, and / or instructions 1106 stored in the memory 1104 and executed by the processor 1102. In some examples, the downlink scheduling and SPS control module 1108 can be integrated within the modem subsystem 1112. For example, the downlink scheduling and SPS control module 1108 can be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 1112.

[0114] The downlink scheduling and SPS control module 1108 can be used in various aspects of the present disclosure, for example, Figures 5-10B , aspects of 13 and 15. The downlink scheduling and SPS control module 1108 is configured to communicate with other components of the UE 1100 to send a capability report, receive an SPS grant, process the SPS grant, monitor SPS downlink communication based on the SPS grant, monitor an SPS release, process the SPS release, release one or more resources based on the SPS release, monitor one or more downlink communications from a base station, perform PDCCH monitoring, perform PDSCH monitoring, send ACK / NACK, send PUCCH communication, determine whether a timer has expired, cancel the timer, determine whether a condition has occurred or been satisfied, and / or perform other functions related to power-saving configurations and wireless communication techniques associated with the UE described in the present disclosure.

[0115] As shown in the figure, the transceiver 1110 may include a modem subsystem 1112 and an RF unit 1114. The transceiver 1110 may be configured to communicate bidirectionally with other devices such as the BS 108. The modem subsystem 1112 may be configured to modulate and / or encode data from the memory 1104 and / or the downlink scheduling and SPS control module 1108 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.). The RF unit 1114 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / coded data (e.g., UL control information, UL data) of the transmission from the modem subsystem 1112 (on the outbound transmission) or originating from another source such as the UE 106 or the BS 108. The RF unit 1114 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 1110, the modem subsystem 1112 and the RF unit 1114 may be separate devices coupled together at the UE 106 to enable the UE 106 to communicate with other devices.

[0116] The RF unit 1114 may provide the modulated and / or processed data (e.g., data packets, or more generally, data messages that may include one or more data packets and other information) to the antenna 1116 for transmission to one or more other devices. The antenna 1116 may also receive data messages sent from other devices. The antenna 1116 may provide the received data messages for processing and / or demodulation at the transceiver 1110. The transceiver 1110 may provide the demodulated and decoded data (e.g., PDCCH signal, radio resource control (RRC) signal, media access control (MAC) control element (CE) signal, PDSCH signal, DL / UL scheduling grant, DL data, etc.) to the downlink scheduling and SPS control module 1108 for processing. The antenna 1116 may include multiple antennas with similar or different designs to maintain multiple transmission links. The RF unit 1114 may configure the antenna 1116. The RF unit 1114 and / or the transceiver 1110 may include components and / or circuits that can be dynamically powered on and / or off to save power. Additionally or alternatively, the RF unit 1114 and / or the transceiver 1110 may include components and / or circuits with multiple power states that can be configured to transition from one power state (e.g., a higher power state) to another power state (e.g., a lower power state) to save power.

[0117] In one example, the UE 1100 may include multiple transceivers 1110 that implement different RATs (e.g., NR and LTE). In some instances, the UE 1100 may include a single transceiver 1110 that implements multiple RATs (e.g., NR and LTE). In some instances, the transceiver 1110 may include various components, and different combinations of the components may implement different RATs.

[0118] Figure 12 is a block diagram of an exemplary BS 1200 according to aspects of the present disclosure. The BS 1200 may be the BS 108 discussed above in Figure 1 As shown, the BS 1200 may include a processor 1202, a memory 1204, a downlink scheduling and SPS control module 1208, a transceiver 1210 including a modem subsystem 1212 and an RF unit 1214, and one or more antennas 1216. These elements may communicate directly or indirectly with each other, e.g., via one or more buses.

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

[0120] The memory 1204 may include a cache (e.g., a cache of the processor 1202), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state storage devices, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some instances, the memory 1204 may include non-transitory computer-readable media. The memory 1204 may store instructions 1206. The instructions 1206 may include instructions that, when executed by the processor 1202, cause the processor 1202 to perform the operations described herein (e.g., Figures 5-10B and aspects of 14). The instructions 1206 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statement, as discussed above with reference to Figure 5 as discussed.

[0121] The downlink scheduling and SPS control module 1208 can be implemented via hardware, software, or a combination thereof. For example, the downlink scheduling and SPS control module 1208 can be implemented as a processor, circuitry, and / or instructions 1206 stored in the memory 1204 and executed by the processor 1202. In some examples, the downlink scheduling and SPS control module 1208 can be integrated in the modem subsystem 1212. For example, the downlink scheduling and SPS control module 1208 can be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 1212.

[0122] The downlink scheduling and SPS control module 1208 can be used in various aspects of the present disclosure, for example, Figures 5-10B and aspects of 14. The downlink scheduling and SPS control module 1208 can be configured to receive capability reports of one or more UEs, determine downlink data scheduling for one or more UEs, send SPS authorizations to one or more UEs, send downlink communications based on the SPS authorizations to one or more UEs, send SPS releases to one or more UEs, send one or more downlink communications to one or more UEs, send PDCCH communications, send PDSCH communications, monitor ACK / NACK from one or more UEs, perform PUCCH monitoring, determine whether a timer has expired, cancel the timer, determine whether a condition has occurred or been satisfied, and / or perform other functions related to power saving configurations and the radio communication technologies associated with the base station described in the present disclosure.

[0123] As shown, the transceiver 1210 can include a modem subsystem 1212 and an RF unit 1214. The transceiver 1210 can be configured to communicate bidirectionally with other devices such as the UEs 106 and / or 1100 and / or another core network element. The modem subsystem 1212 can be configured to modulate and / or encode data according to an MCS (e.g., LDPC coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). The RF unit 1214 can be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data of the transmission from the modem subsystem 1212 (on an outbound transmission) or from another source (such as the UEs 106 or 1100) (e.g., PDCCH signals, RRC signals, MACCE signals, PDSCH signals, etc.). The RF unit 1214 can also be configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 1210, the modem subsystem 1212 and / or the RF unit 1214 can be separate devices coupled together at the BS 108 to enable the BS 108 to communicate with other devices.

[0124] The RF unit 1214 may provide modulated and / or processed data (e.g., data packets, or more generally, data messages that may include one or more data packets and other information) to the antenna 1216 for transmission to one or more other devices. According to aspects of the present disclosure, this may include, for example, transmitting information to the UE 106 or 1100. The antenna 1216 may also receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at the transceiver 1210. The transceiver 1210 may provide demodulated and decoded data (e.g., RACH messages, ACK / NACK for PDCCH signals, UL data, ACK / NACK for DL data, etc.) to the downlink scheduling and SPS control module 1208 for processing. The antenna 1216 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0125] In one example, the BS 1200 may include multiple transceivers 510 that implement different RATs (e.g., NR and LTE). In some instances, the BS 1200 may include a single transceiver 510 that implements multiple RATs (e.g., NR and LTE). In some instances, the transceiver 510 may include various components, and different combinations of the components may implement different RATs.

[0126] Figure 13 is a flowchart of a communication method 1300 according to some aspects of the present disclosure. Aspects of the method 1300 may be performed by a wireless communication device (such as the UE 106 and / or 1100) using one or more components (such as the processor 1102, the memory 1104, the downlink scheduling and SPS control module 1108, the transceiver 1110, the modem 1112, one or more antennas 1116, and various combinations thereof). As shown, the method 1300 includes many enumerated steps, but the method 1300 may include additional steps before, after, and between the enumerated steps. For example, in some instances, one or more aspects of the scheduling / transmission configurations 500, 600, 700, 800, 900, 1000, and / or 1050 may be implemented as part of the method 1300. In some instances, one or more of the enumerated steps may be omitted or performed in a different order.

[0127] In step 1310, method 1300 includes the UE sending a capability report to the base station. The UE may convey one or more of its capabilities (e.g., one or more PDSCHs per time slot, processing parameters, etc.) to the base station in the capability report. The capability report may indicate that the user equipment is configured to receive a single physical downlink shared channel (PDSCH) communication per time slot. According to the present disclosure, the base station may utilize the UE's capabilities to schedule communication with the UE.

[0128] In step 1320, method 1300 includes the UE receiving a semi-persistent scheduling (SPS) grant from the base station. The SPS grant indicates a period associated with the resources of the SPS grant. The period of the SPS grant may range from 1 time slot (or sub-slot) to 1 second or longer, including any value therebetween. The base station may determine a particular period based on the type of data being transmitted and its associated communication interval requirements, as well as the UE's capabilities. In some instances, the period is one time slot.

[0129] In step 1330, method 1300 includes the UE monitoring for an SPS release and downlink data communication in a time slot scheduled for downlink data communication. In some instances, the UE monitors for the SPS release on the PDCCH and monitors for downlink data communication on the PDSCH (e.g., see Figures 6-9 ).

[0130] In step 1340, method 1300 includes the UE sending an acknowledgement (ACK) or negative acknowledgement (NACK) to the base station based on the monitoring of step 1330. In some instances, the ACK / NACK timing for the SPS release and the scheduled downlink data communication is aligned. For example, the ACK / NACK for the SPS release may be scheduled for the same time slot (or sub-slot) of the physical uplink control channel (PUCCH) as the ACK / NACK for the scheduled downlink data communication. The scheduled downlink data communication may be used for dynamic downlink data or SPS downlink data.

[0131] In some instances, the time slot is scheduled for dynamic downlink data communication. In this regard, with the dynamic downlink data communication scheduled in the time slot, the UE may detect an SPS release when monitoring in step 1330. In step 1340, the UE may send an ACK / NACK based on the decoding result of the SPS release detected during the time slot scheduled for dynamic downlink data communication.

[0132] In some instances, a time slot scheduled for downlink data communication is scheduled for SPS downlink data communication. The time slot scheduled for SPS downlink data communication may be associated with the SPS grant received at step 1320 or a different SPS grant of the UE. Monitoring for SPS release and downlink data communication using the time slot scheduled for SPS downlink data communication may result in receiving an SPS release that indicates to the UE to release one or more resources associated with the SPS grant received at step 1320, or one or more resources associated with a different SPS grant of the UE.

[0133] In some instances, monitoring for SPS release and downlink data communication at step 1330 includes detecting an SPS release on a physical downlink control channel (PDCCH), and sending an ACK or NACK at step 1340 includes sending an ACK based on successful decoding of the detected SPS release. In some instances, the SPS release is received before or at the same time as one or more symbols of the time slot scheduled for downlink data communication. In some instances, the SPS release is received at least n symbols (n≥0) before the start symbol of the scheduling of the downlink data communication.

[0134] In some instances, receiving an SPS grant at step 1320 includes receiving an indication of a first ACK / NACK feedback timing for SPS downlink data communication associated with the SPS grant, and receiving an SPS release includes receiving an indication of a second ACK / NACK feedback timing for the SPS release. The second ACK / NACK feedback timing may be aligned with the first ACK / NACK feedback timing. In this regard, the first ACK / NACK feedback timing may schedule an ACK / NACK for SPS downlink data communication received on a physical downlink shared channel (PDSCH) for a time slot (or sub-slot) of a physical uplink control channel (PUCCH), and the second ACK / NACK feedback timing may schedule an ACK / NACK for the SPS release received on the PDCCH for the same time slot (or sub-slot) of the PUCCH.

[0135] In some instances, monitoring for SPS release and downlink data communication at step 1330 includes unsuccessful decoding of the downlink data communication. For example, when the UE receives an SPS release, the UE may not detect and / or successfully decode the scheduled downlink data communication.

[0136] In some instances, monitoring for SPS release and downlink data communication at step 1330 includes detecting the downlink data communication and not detecting an SPS release, and sending an ACK / NACK at step 1340 includes sending an ACK or NACK based on the result of decoding the downlink data communication.

[0137] In some instances, monitoring for SPS release and downlink data communication in step 1330 includes not detecting an SPS release and not detecting downlink data communication; and transmitting an ACK / NACK in step 1340 includes transmitting a NACK.

[0138] Figure 14 is a flowchart of a communication method 1400 in accordance with some aspects of the present disclosure. Aspects of method 1400 may be performed by a wireless communication device (such as BS 108 and / or 1200) using one or more components (such as processor 1202, memory 1204, downlink scheduling and SPS control module 1208, transceiver 1210, modem 1212, one or more antennas 1216, and various combinations thereof). As shown, method 1400 includes a number of recited steps, but method 1400 may include additional steps before, after, and between the recited steps. For example, in some instances, one or more aspects of scheduling / transmission configurations 500, 600, 700, 800, 900, 1000, and / or 1050 may be implemented as part of method 1400. In some instances, one or more of the recited steps may be omitted or performed in a different order.

[0139] In step 1410, method 1400 includes a base station receiving a capability report from a user equipment. The UE may indicate to the base station one or more of its capabilities (e.g., one or more PDSCHs per time slot, processing parameters, etc.) in the capability report. In some instances, the capability report indicates that the user equipment is configured to receive a single physical downlink shared channel (PDSCH) communication per time slot. In accordance with the present disclosure, the base station may utilize the UE's capabilities to schedule communication with the UE.

[0140] In step 1420, method 1400 includes the base station sending a semi-persistent scheduling (SPS) grant to the user equipment, the SPS grant indicating a period associated with the resources of the SPS grant. The period of the SPS grant may range from 1 time slot (or sub-slot) to 1 second or longer, including any value therebetween. The base station may determine a particular period based on the type of data being transmitted and its associated communication interval requirements, as well as the capabilities of the UE. In some instances, the period is one time slot.

[0141] In step 1430, method 1400 includes the base station transmitting an SPS release in a time slot scheduled for downlink data communication for the user equipment. The SPS release may be transmitted on a physical downlink control channel (PDCCH). In some instances, the base station avoids transmitting physical downlink shared channel (PDSCH) communication - including any scheduled communication (e.g., seeFigures 6-9 )。

[0142] In step 1440, method 1400 includes the base station monitoring for an acknowledgement (ACK) or negative acknowledgement (NACK) from the user equipment in the time slot. In some instances, the ACK / NACK timing for SPS release and scheduled downlink data communication is aligned. For example, the ACK / NACK for SPS release can be scheduled for the same time slot (or sub - slot) of the physical uplink control channel (PUCCH) as the ACK / NACK for the scheduled downlink data communication. The scheduled downlink data communication can be for dynamic downlink data or SPS downlink data.

[0143] Figure 15 is a flow chart of a communication method 1500 according to some aspects of the present disclosure. Aspects of method 1500 can be performed by a wireless communication device (such as UE 106 and / or 1100) using one or more components (such as processor 1102, memory 1104, downlink scheduling and SPS control module 1108, transceiver 1110, modem 1112, one or more antennas 1116, and various combinations thereof). As shown, method 1500 includes a number of enumerated steps, but method 1500 can include additional steps before, after, and between the enumerated steps. For example, in some instances, one or more aspects of scheduling / transmission configurations 500, 600, 700, 800, 900, 1000, and / or 1050 can be implemented as part of method 1500. In some instances, one or more of the enumerated steps can be omitted or performed in a different order.

[0144] In step 1510, method 1500 includes the UE receiving a semi - persistent scheduling (SPS) grant from the base station. The SPS grant indicates a period associated with the resources of the SPS grant. The period of the SPS grant can range from 1 time slot (or sub - slot) to 1 second or longer, including any value therebetween. The base station can determine a particular period based on the type of data being transmitted, its associated communication interval requirements, and the capabilities of the UE. In some instances, the period is one time slot. Additionally, in some instances, the UE is configured to receive multiple physical downlink shared channel (PDSCH) communications per time slot. In some instances, the UE is configured to receive a single PDSCH communication per time slot.

[0145] In step 1520, method 1500 includes the UE monitoring for SPS downlink data communication and SPS release in the time slot scheduled for SPS downlink data communication. In some instances, the UE monitors for SPS release on the PDCCH and monitors for SPS downlink data communication on the PDSCH (e.g., see Figures 6-9)。In some instances, at least a threshold number of symbols before the start symbol of scheduling in a slot used for SPS downlink data communication on the PDSCH, an SPS release is received on the PDCCH in that slot. In some instances, the threshold number of symbols is at least partially based on the processing capabilities of the user equipment (PDSCH processing time, PUCCH processing time, available processing resources, etc.).

[0146] In step 1530, method 1500 includes the UE sending a single instance of an acknowledgement (ACK) or negative acknowledgement (NACK) to the base station based on monitoring of the SPS downlink data communication and the SPS release. In some instances, the ACK / NACK timing for the SPS release and the scheduled downlink data communication is aligned. For example, the ACK / NACK for the SPS release can be scheduled for the same slot (or sub-slot) of the physical uplink control channel (PUCCH) as the ACK / NACK for the scheduled SPS downlink data communication.

[0147] Some aspects of the present disclosure disclose a method of wireless communication performed by a base station, the method including: sending a semi-persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; in a slot scheduled for downlink data communication of the user equipment, sending an SPS release; and monitoring an acknowledgement (ACK) or negative acknowledgement (NACK) from the user equipment in that slot.

[0148] In some aspects, the period is one slot.

[0149] In some aspects, the slot scheduled for downlink data communication is scheduled for dynamic downlink data communication. In some instances, the downlink data communication is dynamic downlink data communication scheduled by dynamic authorized downlink control information (DCI).

[0150] In some aspects, the method further includes: sending dynamic downlink data communication to the user equipment in that slot; and wherein the ACK or NACK indicates whether the UE has received the sent SPS release.

[0151] In some aspects, the slot scheduled for downlink data communication is scheduled for SPS downlink data communication.

[0152] In some aspects, the slot scheduled for SPS downlink data communication is associated with the SPS grant. In some instances, the downlink data communication is SPS downlink data communication scheduled by the SPS grant.

[0153] In some aspects, the time slots scheduled for SPS downlink data communication are associated with different SPS authorizations. In some instances, the downlink data communication is SPS downlink data communication scheduled by different SPS authorizations.

[0154] In some aspects, the SPS release indicates to the user equipment the release of one or more resources associated with the SPS authorization.

[0155] In some aspects, the SPS release indicates to the user equipment the release of one or more resources associated with different SPS authorizations.

[0156] In some aspects, the monitoring of the ACK or NACK includes receiving an ACK that acknowledges the SPS release.

[0157] In some aspects, the method further includes: sending downlink data communication to the user equipment in the time slot; and determining, based on the ACK that acknowledges the SPS release, that the downlink data communication has not been successfully received by the user equipment.

[0158] In some aspects, sending the SPS release includes sending the SPS release before or at the same time as one or more symbols of the time slot scheduled for the downlink data communication. In some instances, the SPS release is received before the end of the last symbol of the downlink data communication.

[0159] In some aspects, sending the SPS release includes sending the SPS release at least n symbols before the start symbol of the scheduling of the downlink data communication.

[0160] In some aspects, sending the SPS authorization includes: sending an indication of the first ACK / NACK feedback timing for the SPS downlink data communication associated with the SPS authorization; and sending the SPS release includes sending an indication of the second ACK / NACK feedback timing for the SPS release, where the second ACK / NACK feedback timing is aligned with the first ACK / NACK feedback timing.

[0161] In some aspects, the first ACK / NACK feedback timing schedules the ACK / NACK for the SPS downlink data communication received on the physical downlink shared channel (PDSCH) in the first time slot of the physical uplink control channel (PUCCH); and the second ACK / NACK feedback timing schedules the ACK / NACK for the SPS release received on the PDCCH in the first time slot of the PUCCH.

[0162] In some aspects, the monitoring of the ACK or NACK includes receiving a NACK indicating that the SPS release has not been successfully decoded by the user equipment.

[0163] In some aspects, monitoring for an ACK or NACK includes: receiving a single-bit ACK / NACK from a user equipment.

[0164] In some aspects, the method further includes: avoiding transmitting further downlink data communication for the user equipment using resources associated with an SPS grant during a period of time after transmitting an SPS release.

[0165] Some aspects of the present disclosure disclose a method for wireless communication performed by a user equipment, the method including: receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; monitoring for an SPS downlink data communication and an SPS release in a time slot scheduled for SPS downlink data communication; and transmitting a single instance of an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring of the SPS downlink data communication and the SPS release.

[0166] In some aspects, the user equipment is configured to receive multiple physical downlink shared channel (PDSCH) communications per time slot.

[0167] In some aspects, monitoring for an SPS release and an SPS downlink data communication includes: receiving an SPS release that indicates to the user equipment the release of one or more resources associated with the SPS grant.

[0168] In some aspects, receiving the SPS grant includes receiving an indication of a first ACK / NACK feedback timing for the SPS downlink data communication associated with the SPS grant that includes the SPS downlink data communication; and receiving the SPS release includes receiving an indication of a second ACK / NACK feedback timing for the SPS release, wherein the second ACK / NACK feedback timing is aligned with the first ACK / NACK feedback timing.

[0169] In some aspects, the first ACK / NACK feedback timing schedules an ACK / NACK for the SPS downlink data communication received on a physical downlink shared channel (PDSCH) for a first time slot of a physical uplink control channel (PUCCH); and the second ACK / NACK feedback timing schedules an ACK / NACK for the SPS release received on a physical downlink control channel (PDCCH) for the first time slot of the PUCCH.

[0170] In some aspects, the SPS release is received on a physical downlink control channel (PDCCH) in the time slot at least a threshold number of symbols before a start symbol of a scheduling for the SPS downlink data communication on a physical downlink shared channel (PDSCH).

[0171] In some aspects, the threshold number of symbols is at least partially based on the PDSCH processing capability of the user equipment.

[0172] In some aspects, the downlink data communication is SPS downlink data communication scheduled by an SPS grant; monitoring the SPS release and the downlink data communication includes failing to successfully decode the downlink data communication; and transmitting an ACK or NACK includes failing to transmit an ACK or NACK as a result of failing to successfully decode the downlink data communication.

[0173] Some aspects of the present disclosure disclose a user equipment, including: components for receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; components for monitoring an SPS release and downlink data communication in a time slot scheduled for the downlink data communication; and components for transmitting an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

[0174] Some aspects of the present disclosure disclose a base station, including: components for transmitting a semi-persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; components for transmitting an SPS release in a time slot scheduled for the downlink data communication of the user equipment; and components for monitoring an acknowledgement (ACK) or a negative acknowledgement (NACK) from the user equipment in the time slot.

[0175] Some aspects of the present disclosure disclose a user equipment, including: components for receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; components for monitoring SPS downlink data communication and an SPS release in a time slot scheduled for the SPS downlink data communication; and components for transmitting a single instance of an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring of the SPS downlink data communication and the SPS release.

[0176] Some aspects of the present disclosure disclose a non-transitory computer-readable medium having recorded thereon program code for a user equipment to perform wireless communication, the program code including: code for causing the user equipment to receive a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; code for causing the user equipment to monitor an SPS release and downlink data communication in a time slot scheduled for the downlink data communication; and code for causing the user equipment to transmit an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring.

[0177] Some aspects of the present disclosure disclose a non-transitory computer-readable medium having program code for wireless communication by a base station recorded thereon, the program code including: code for causing the base station to send a semi-persistent scheduling (SPS) grant to a user equipment, the SPS grant indicating a period; code for causing the base station to send an SPS release in a time slot scheduled for downlink data communication of the user equipment; and code for causing the base station to monitor an acknowledgement (ACK) or a negative acknowledgement (NACK) from the user equipment in the time slot.

[0178] Some aspects of the present disclosure disclose a non-transitory computer-readable medium having program code for wireless communication by a user equipment recorded thereon, the program code including: code for causing the user equipment to receive a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; code for causing the user equipment to monitor SPS downlink data communication and an SPS release in a time slot scheduled for SPS downlink data communication; and code for causing the user equipment to send a single instance of an acknowledgement (ACK) or a negative acknowledgement (NACK) to the base station based on the monitoring of the SPS downlink data communication and the SPS release.

[0179] Several aspects of a wireless communication network have been introduced with reference to exemplary embodiments. As will be readily understood by those skilled in the art, the various aspects described throughout the present disclosure can be extended to other telecommunication systems, network architectures, and communication standards.

[0180] For example, the various aspects can be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). The various aspects can also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples can be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standards, network architectures, and / or communication standards employed will depend on the particular application and the overall design constraints imposed on the system.

[0181] In this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as more preferred or advantageous than other aspects of the disclosure. Similarly, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" as used herein refers to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered to be coupled to each other—even if they do not directly physically contact each other. For instance, a first object can be coupled to a second object even if the first object never makes direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors which, when connected and configured, perform the functions described in this disclosure, without limitation to the type of electronic circuit, and software implementations of information and instructions which, when executed by a processor, perform the functions described in this disclosure.

[0182] Figures 1-15 One or more of the components, steps, features, and / or functions shown therein can be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. Figures 1-15 The apparatus, device, and / or components shown therein can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0183] It should be understood that the particular order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. Based on design preferences, it should be understood that the particular order or hierarchy of steps in a method can be rearranged. The appended method claims present the elements of the various steps in an exemplary order and are not meant to be limited to the particular order or hierarchy presented, unless specifically recited therein.

[0184] The foregoing description is provided to enable a person of ordinary skill in the art to practice the various aspects described herein. Those of ordinary skill in the art will readily appreciate various modifications to these aspects, and the general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, wherein unless otherwise specifically stated, the singular forms of elements are not intended to mean "one and only one" but rather "one or more". The term "some", unless specifically stated otherwise, means one or more. A phrase referring to "at least one" of a series of items means any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. No claim element, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the phrase "step for", shall be construed under the provisions of 35 U.S.C. 112(f).

Claims

1. A method of wireless communication performed by a user equipment, the method comprising: Receiving a semi-persistent scheduling (SPS) grant from a base station, the SPS grant indicating a period; In a first time slot scheduled for downlink data communication, monitoring an SPS release and the downlink data communication, wherein the downlink data communication is scheduled in a first SPS resource of the first time slot, wherein a first physical uplink control channel (PUCCH) resource in a second time slot is scheduled to provide a first hybrid automatic repeat request acknowledgement (HARQ-ACK) for the downlink data communication, and wherein the monitoring includes receiving the SPS release before an end of a last symbol of the downlink data communication in the first time slot; Based on receiving the SPS release before an end of a last symbol of the downlink data communication in the first time slot, avoiding performing the following: Decoding the downlink data communication in the first time slot; And Transmitting, in the first PUCCH resource in the second time slot, the first HARQ-ACK for the downlink data communication; And In the first PUCCH resource scheduled to provide the first HARQ-ACK for the downlink data communication, transmitting a second HARQ-ACK for the SPS release to the base station without transmitting the first HARQ-ACK for the downlink data communication, wherein transmitting the second HARQ-ACK is based on receiving the SPS release before an end of a last symbol of the downlink data communication.

2. The method according to claim 1, wherein the period is one time slot.

3. The method according to claim 1, wherein the downlink data communication is dynamic downlink data communication scheduled by dynamic authorization downlink control information (DCI).

4. The method according to claim 3, wherein: Monitoring the SPS release and the downlink data communication includes detecting the SPS release; and Transmitting the second HARQ-ACK includes transmitting the second HARQ-ACK based on a decoding result of the SPS release.

5. The method according to claim 1, wherein the SPS release indicates to the user equipment to release one or more resources associated with the SPS grant.

6. The method according to claim 1, wherein the downlink data communication is SPS downlink data communication scheduled by the SPS grant.

7. The method according to claim 6, wherein: Monitoring the SPS release and the downlink data communication includes detecting the SPS release on a physical downlink control channel (PDCCH); and Transmitting the second HARQ-ACK includes transmitting the second HARQ-ACK based on successfully decoding the detected SPS release.

8. The method according to claim 6, wherein the SPS release is received at least n symbols before a start symbol of the scheduling of the downlink data communication.

9. The method according to claim 6, wherein: Receiving the SPS authorization includes receiving an indication of a first HARQ-ACK feedback timing for SPS downlink data communication associated with the SPS authorization; and Receiving the SPS release includes receiving an indication of a second HARQ-ACK feedback timing for the SPS release, wherein the second HARQ-ACK feedback timing is aligned with the first HARQ-ACK feedback timing.

10. The method according to claim 9, wherein: The first HARQ-ACK feedback timing schedules, in a second time slot, a first HARQ-ACK for SPS downlink data communication received on a physical downlink shared channel PDSCH; and The second HARQ-ACK feedback timing schedules, in the second time slot, a second HARQ-ACK for the SPS release received on a physical downlink control channel PDCCH.

11. The method according to claim 6, wherein monitoring the SPS release and the downlink data communication includes not successfully decoding the downlink data communication.

12. The method according to claim 1, wherein: Monitoring the SPS release and the downlink data communication includes detecting the downlink data communication and not detecting the SPS release; and Transmitting the second HARQ-ACK includes transmitting the second HARQ-ACK based on the result of decoding the downlink data communication.

13. The method according to claim 1, wherein: Monitoring the SPS release and the downlink data communication includes not detecting the SPS release and not detecting the downlink data communication; and The second HARQ-ACK includes a negative acknowledgment NACK indicating non-detection of the SPS release.

14. The method according to claim 1, wherein: Transmitting the second HARQ-ACK includes transmitting a one-bit HARQ-ACK in response to receiving the SPS release.

15. The method according to claim 1, wherein the downlink data communication is SPS downlink data communication scheduled by a different SPS authorization.

16. The method according to claim 15, wherein the SPS release indicates to the user equipment to release one or more resources associated with the different SPS authorization.

17. A wireless communication method performed by a base station, the method comprising: Sending a semi-persistent scheduling SPS authorization to a user equipment, the SPS authorization indicating a period and at least a first SPS resource, the first SPS resource being associated with a first physical uplink control channel PUCCH resource in a second time slot; Transmit an SPS release in a first time slot scheduled for downlink data communication of the user equipment and before the end of the last symbol of the downlink data communication in the first time slot, where the downlink data communication is scheduled in a first SPS resource in the first time slot, and where a first physical uplink control channel PUCCH resource in a second time slot is scheduled to receive a first hybrid automatic repeat request acknowledgement HARQ-ACK for the downlink data communication in the first time slot; And In the first PUCCH resource scheduled to receive the first HARQ-ACK for the downlink data communication, receive a second HARQ-ACK for the SPS release from the user equipment without receiving the first HARQ-ACK for the downlink data communication; Wherein, receiving the second HARQ-ACK for the SPS release is based on the following: the user equipment receives the SPS release before the end of the last symbol of the downlink data communication in the first time slot, and the user equipment avoids decoding the downlink data communication in the first time slot, and the user equipment avoids transmitting the first HARQ-ACK for the downlink data communication in the first PUCCH resource in the second time slot.

18. The method according to claim 17, wherein: The SPS grant indicates a first HARQ-ACK feedback timing for SPS downlink data communication associated with the SPS grant, where the first HARQ-ACK feedback timing schedules the first HARQ-ACK for SPS downlink data communication received on a physical downlink shared channel PDSCH in the second time slot; and The SPS release indicates an indication of a second HARQ-ACK feedback timing for the SPS release, where the second HARQ-ACK feedback timing is aligned with the first HARQ-ACK feedback timing and schedules the second HARQ-ACK for the SPS release received on a PDCCH in the second time slot.

19. The method according to claim 17, wherein receiving the second HARQ-ACK includes: In response to transmitting the SPS release, receive a 1-bit HARQ-ACK from the user equipment.

20. A user equipment, comprising: A transceiver configured to: Receive a semi-persistent scheduling SPS grant from a base station, the SPS grant indicating a period; And a processor in communication with the transceiver, the processor configured to: In a first time slot scheduled for downlink data communication, monitor the SPS release and the downlink data communication, where the downlink data communication is scheduled in a first SPS resource in the first time slot, where a first physical uplink control channel PUCCH resource in a second time slot is scheduled to provide a first hybrid automatic repeat request acknowledgement HARQ-ACK for the downlink data communication, and where the monitoring includes receiving the SPS release before the end of the last symbol of the downlink data communication in the first time slot; Wherein, the transceiver is further configured to: Avoid performing the following based on receiving an SPS release before the end of the last symbol of the downlink data communication in the first time slot: Decoding the downlink data communication in the first time slot; and Transmitting a first HARQ-ACK for the downlink data communication in a first PUCCH resource in the second time slot; and Transmitting a second HARQ-ACK for the SPS release to the base station without transmitting the first HARQ-ACK for the downlink data communication in the first PUCCH resource scheduled to provide the first HARQ-ACK for the downlink data communication, where the transmission of the second HARQ-ACK is based on receiving the SPS release before the end of the last symbol of the downlink data communication.

21. The user equipment according to claim 20, wherein: The downlink data communication is an SPS downlink data communication scheduled by the SPS grant.

22. The user equipment according to claim 20, wherein the transceiver is configured to send the second HARQ-ACK, including: The transceiver is configured to transmit a one-bit HARQ-ACK in response to receiving the SPS release.

23. A base station, comprising: A processor; And A transceiver communicating with the transceiver, the transceiver being configured to: Transmit a semi-persistent scheduling SPS grant to a user equipment, the SPS grant indicating a period and at least a first SPS resource, the first SPS resource being associated with a first physical uplink control channel PUCCH resource in a second time slot; Transmit an SPS release in a first time slot scheduled for the downlink data communication of the user equipment and before the end of the last symbol of the downlink data communication in the first time slot, where the downlink data communication is scheduled in the first SPS resource in the first time slot, and where the first physical uplink control channel PUCCH resource in the second time slot is scheduled to receive a first hybrid automatic repeat request acknowledgement HARQ-ACK for the downlink data communication in the first time slot; And Receive a second HARQ-ACK for the SPS release from the user equipment without receiving the first HARQ-ACK for the downlink data communication in the first PUCCH resource scheduled to receive the first HARQ-ACK for the downlink data communication; Wherein, receiving the second HARQ-ACK for the SPS release is based on: the user equipment receiving the SPS release before the end of the last symbol of the downlink data communication in the first time slot, and the user equipment avoiding decoding the downlink data communication in the first time slot, and the user equipment avoiding transmitting the first HARQ-ACK for the downlink data communication in the first PUCCH resource in the second time slot.

24. The base station according to claim 23, wherein the transceiver is further configured to: Send an indication of a first HARQ-ACK feedback timing for SPS downlink data communication associated with the SPS authorization, wherein the first HARQ-ACK feedback timing schedules the first HARQ-ACK / NACK for the SPS downlink data communication received on a physical downlink shared channel PDSCH in a second time slot of a physical uplink control channel PUCCH; and Send an indication of a second HARQ-ACK feedback timing for the SPS release, wherein the second HARQ-ACK feedback timing is aligned with the first HARQ-ACK feedback timing and schedules a second HARQ-ACK for the SPS release received on a PDCCH in the second time slot.

25. The base station according to claim 23, wherein the transceiver is configured to receive the second HARQ-ACK, including: The transceiver is configured to receive a one-bit HARQ-ACK in response to sending the SPS release.

26. A non-transitory computer-readable medium storing code for wireless communication by a user equipment, wherein the code is executable by one or more processors of the user equipment to cause the processors to perform the method according to any one of claims 1-16.

27. A non-transitory computer-readable medium storing code for wireless communication by a base station, wherein the code is executable by one or more processors of the base station to cause the processors to perform the method according to any one of claims 17-19.

Images