Channel and interference measurement using semi-persistent scheduling resources in wireless communications

Abstract

A scheduling entity can configure semi-persistent scheduling (SPS) resources for downlink data and selectively receive channel and interference measurements from a user equipment. The scheduling entity can trigger channel and interference measurements using various methods including SPS configuration activation / re-activation / de-activation, DMRS-based triggers, and DCI-based triggers. The scheduling entity can benefit from more frequent and / or aperiodic interference and / or channel measurements when performing channel precoding, selecting a modulation and coding scheme (MCS), and estimating / predicting interference, noise, and channel quality at the UE. SPS configured channel and interference measurements also benefit the UE in decoding data, which can result in lower error rates and higher data rates.

Description

[0001] Priority requirements

[0002] This application claims priority and benefit to Patent Application No. 17 / 504,463, filed with the U.S. Patent and Trademark Office on October 18, 2021, as well as Provisional Patent Application No. 63 / 093,742 and Provisional Patent Application No. 63 / 093,760, filed with the U.S. Patent and Trademark Office on October 19, 2020, the entire contents of each of which are incorporated herein by reference as if their entire contents were fully set forth herein and for all applicable purposes. Technical Field

[0003] The techniques discussed below generally relate to wireless communication systems, and more specifically, to interference and channel measurements using semi-persistent scheduling (SPS) resources in wireless communication systems. Background Technology

[0004] In wireless communication systems, base stations can use dynamic scheduling or semi-persistent scheduling to schedule communication resources for user equipment (UE). Dynamic scheduling is a mechanism in which the base station uses, for example, downlink control information (DCI) to schedule downlink resources (e.g., Physical Downlink Shared Channel (PDSCH)) and / or uplink resources (e.g., Physical Uplink Shared Channel (PUSCH)) in each subframe or time slot. Dynamic scheduling provides the network with flexibility in assigning communication resources to UEs, at the cost of increased control signaling overhead for sending scheduling information for each uplink and / or downlink transmission.

[0005] To reduce communication overhead, base stations can allocate communication resources on a semi-persistent basis. Semi-persistent scheduling (SPS)-based resource allocation can semi-statically allocate periodic resources to the UE over a time interval (e.g., one or more time slots). In SPS, the base station can use semi-static control messages (e.g., Radio Resource Control (RRC) messages) to schedule uplink / downlink resources. Because the base station does not need to send scheduling information (e.g., permission) for each uplink or downlink communication, using SPS can significantly reduce control signaling overhead. In this disclosure, SPS and configured scheduling can be used interchangeably. Summary of the Invention

[0006] The following provides an overview of one or more aspects of this disclosure in order to provide a basic understanding of such aspects. This overview is not an exhaustive summary of all anticipated features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. Its sole purpose is to provide some concepts of one or more aspects of this disclosure in a formal manner as a prelude to the specific embodiments given below.

[0007] This disclosure provides a method, system, apparatus, and device for efficient interference and channel measurements using semi-persistent scheduling (SPS) resources. A scheduling entity can allocate uplink communication resources to a user equipment (UE) for channel and interference measurement results, and use SPS uplink resources to report measurement results. In some aspects, the scheduling entity can send reference signals or downlink control information to trigger the UE to measure channel and / or interference at one or more SPS times. The scheduling entity can benefit from the interference and channel measurement results when performing channel precoding, selecting modulation and coding schemes (MCS), and estimating / predicting interference, noise, and channel quality at the UE. Channel and interference measurement results also benefit the UE in data decoding, which can lead to lower error rates and higher data rates.

[0008] One aspect of this disclosure provides a scheduling entity for wireless communication. The scheduling entity includes a communication interface configured to communicate with a user equipment (UE); a memory; and a processor coupled to the communication interface and the memory. The processor and memory are configured to: transmit semi-persistent scheduling (SPS) information to the UE for radio resources that can be used to transmit downlink data; transmit to the UE a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration; and receive from the UE a report including channel measurement results, wherein the channel measurement results include at least one of channel state information, channel characteristics, or interference measurement results of the communication channel, according to at least one SPS configuration.

[0009] One aspect of this disclosure provides a method for wireless communication at a scheduling entity. The method includes: sending semi-persistent scheduling (SPS) information to a user equipment (UE) of radio resources capable of transmitting downlink data; sending to the UE a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration, based on the SPS information; and receiving from the UE a report including channel measurement results, wherein the channel measurement results include at least one of channel state information of the communication channel, channel characteristics, or interference measurement results.

[0010] One aspect of this disclosure provides a user equipment (UE) for wireless communication. The UE includes: a communication interface configured to communicate with a scheduling entity; a memory; and a processor coupled to the communication interface and the memory. The processor and memory are configured to: receive semi-persistent scheduling (SPS) information from the scheduling entity regarding radio resources available for receiving downlink data; receive from the scheduling entity a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration to the scheduling entity; and, according to at least one SPS configuration, send a report including channel measurement results to the scheduling entity, wherein the channel measurement results include at least one of channel state information, channel characteristics, or interference measurement results of the communication channel.

[0011] One aspect of this disclosure provides a method for wireless communication at a user equipment (UE). The method includes: receiving semi-persistent scheduling (SPS) information from a scheduling entity regarding radio resources available for receiving downlink data; receiving from the scheduling entity a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration, based on the SPS information; and sending a report including the channel measurement results to the scheduling entity based on at least one channel state information and the SPS configuration, wherein the channel measurement results include at least one of channel characteristics or interference measurement results of the communication channel.

[0012] These and other aspects of the invention will become more fully understood as you review the detailed description of the embodiments described below. Other aspects, features, and implementations will become apparent to those skilled in the art as you review the description of the specific, exemplary implementations below in conjunction with the accompanying drawings. While features may be discussed with respect to certain implementations and drawings below, all implementations may include one or more of the advantageous features discussed herein. In other words, while one or more implementations are discussed as having certain advantageous features, one or more such features may also be used according to the various implementations discussed herein. Similarly, while exemplary implementations are discussed below as devices, systems, or methods, it should be understood that such examples may be implemented in a wide variety of devices, systems, and methods. Attached Figure Description

[0013] Figure 1 It is a schematic diagram of a wireless communication system based on some aspects.

[0014] Figure 2 This is a schematic diagram illustrating an example of a radio access network based on some aspects.

[0015] Figure 3 It is a schematic diagram of the organization of radio resources in the air interface using orthogonal frequency division multiplexing (OFDM) based on some aspects.

[0016] Figure 4 This is a block diagram illustrating a transmitting and receiving device that supports multiple-input multiple-output (MIMO) communication, based on several aspects.

[0017] Figure 5 This is a schematic diagram illustrating an example semi-persistent scheduling (SPS) configuration for wireless communication, based on several aspects.

[0018] Figure 6 This is a schematic diagram illustrating some exemplary SPS timing configurations based on certain aspects.

[0019] Figure 7 This is a flowchart illustrating, based on some aspects, the process of triggering SPS configuration using indexes and tags included in the downlink control information (DCI).

[0020] Figure 8 This is a schematic diagram illustrating, based on some aspects, the use of bitmaps for triggering SPS configuration in DCI.

[0021] Figure 9 This is a schematic diagram illustrating, according to some aspects, an exemplary process for providing channel reports for blocks of SPS timing.

[0022] Figure 10This is a flowchart illustrating a method for selecting uplink control information resources for transmitting channel reports, based on several aspects.

[0023] Figure 11 This is a schematic diagram showing SPS configurations for downlink data and SPS configurations for channel / interference measurement results with different timings and periods, based on several aspects.

[0024] Figure 12 This is a schematic diagram illustrating an exemplary SPS configuration that provides both data SPS timing and channel measurement SPS timing, based on several aspects.

[0025] Figure 13 This is a schematic diagram illustrating an example of triggering a channel report by receiving a demodulation reference signal (DMRS) during an SPS timing, based on some aspects.

[0026] Figure 14 This is a schematic diagram illustrating another example of triggering a channel report by receiving a special DMRS during an SPS timing, based on some aspects.

[0027] Figure 15 This is a schematic diagram illustrating an example of triggering multiple channel reports by receiving a single special DMRS during an SPS timing, based on some aspects.

[0028] Figure 16 This is a schematic diagram illustrating an example of triggering multiple channel reports by receiving a single special DCI during an SPS timing, based on some aspects.

[0029] Figure 17 This is a block diagram illustrating examples of hardware implementations for a scheduling entity based on some aspects of this disclosure.

[0030] Figure 18 This is a flowchart illustrating an example process for using SPS resources at a scheduling entity for channel measurement results, based on several aspects.

[0031] Figure 19 This is a block diagram illustrating examples of hardware implementations for a scheduled entity, based on some aspects of this disclosure.

[0032] Figure 20 This is a flowchart illustrating an example process for using SPS resources at the scheduled entity for channel measurement results, based on several aspects.

[0033] Figure 21 and Figure 22 This is a schematic diagram illustrating some use cases of the SPS technology described above, based on certain aspects. Detailed Implementation

[0034] The specific embodiments described below with reference to the accompanying drawings are intended as a description of various configurations and are not intended to represent only the configurations in which the concepts described herein can be practiced. Specific details are included to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0035] While aspects and implementations have been described in this application through the illustration of some examples, those skilled in the art will understand that additional implementations and use cases can occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and / or uses can occur via integrated chips and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may be specific to a use case or application, or may not be specific to a use case or application, a wide variety of applicability to the described innovations is possible. Implementations 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 that incorporate one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily involve a number of 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 practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., with variable sizes, shapes, and configurations.

[0036] This disclosure provides methods, systems, apparatus, and devices for efficient interference and channel measurements on communication channels between a scheduling entity (e.g., a base station) and a user equipment (UE) using semi-persistent scheduling (SPS) resources. The scheduling entity can use SPS configuration to allocate periodic radio resources to the UE for channel and interference measurements that can be triggered by downlink reference signals or downlink control information (DCI). The scheduling entity and the UE can communicate via channels that may include, for example, control channels (e.g., physical downlink control channels (PDCCH) and physical uplink control channels (PUCCH)) and data channels (e.g., physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH)). The scheduling entity can benefit from more frequent interference and channel measurements when performing channel precoding, selecting modulation and coding schemes (MCS), and estimating / predicting interference, noise, and channel quality at the UE. Channel and interference measurements using SPS resources can also benefit the UE during data decoding, resulting in lower error rates and higher data rates. According to some aspects, in order to obtain channel condition information faster than that provided by scheduled channel reports via uplink data channels, the scheduling entity may send a DCI or reference signal to trigger the UE to send channel and / or interference reports using SPS resources.

[0037] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. See now for reference. Figure 1 As an example and not a limitation, various aspects of this disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the wireless communication system 100, the UE 106 can perform data communication with an external data network 110, such as (but not limited to) the Internet.

[0038] RAN 104 can implement any suitable wireless communication technology or multiple wireless communication technologies to provide radio access to UE106. As an example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate as 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 a Next Generation RAN or NG-RAN. Of course, many other examples can be used within the scope of this disclosure.

[0039] As shown, RAN 104 includes multiple base stations 108. Generally, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to by those skilled in the art as a base transceiver unit (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, evolved Node B), gNode B (gNB, g Node B), transmit and receive point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs, which may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands.

[0040] Radio access network 104 is further illustrated to support wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but those skilled in the art may also refer to it as a Mobile Station (MS), User Station, Mobile Unit, User Unit, Radio Unit, Remote Unit, Mobile Equipment, Radio Equipment, Wireless Communication Equipment, Remote Equipment, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handheld Device, Terminal, User Agent, Mobile Client, Client, or any other suitable term. The UE may be a device (e.g., a mobile device) that provides users with access to network services.

[0041] In this document, a “mobile” device does not necessarily need to be capable of movement and can be stationary. The term mobile device or mobile equipment generally refers to a wide variety of devices and technologies. A UE can include a number of hardware structural components of a size, shape, and arrangement designed to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, such as those corresponding to the “Internet of Things” (IoT). Mobile devices can additionally include automobiles or other transport vehicles, remote sensors or actuators, robots or robotic equipment, satellite radio units, Global Positioning System (GPS) devices, object tracking devices, unmanned aerial vehicles, multi-rotor helicopters, quadcopters, remote control devices, consumer devices 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. Mobile devices can additionally include digital home or smart home devices such as home audio, video and / or multimedia equipment, home appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can additionally include smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment for controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers, agricultural equipment, etc. Furthermore, mobile devices can be used to prepare for connected medical or telemedicine support (e.g., remote healthcare). Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority processing or access compared to other types of information, for example, priority access for the transmission of critical service data, and / or relevant QoS aspects for the transmission of critical service data.

[0042] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme can be using 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 a further aspect of this disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described 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 communications in some or all of its devices and equipment within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, UE 106 (which may be a scheduled entity) can utilize resources allocated by scheduling entity 108.

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

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

[0046] Typically, base station 108 may include a backhaul interface for communication with backhaul section 120 of a wireless communication system. Backhaul section 120 may provide a link between base station 108 and core network 102. Further, in some examples, the backhaul network may provide interconnection between the respective base stations 108. Various types of backhaul interfaces may be employed, such as direct physical connections using any suitable transport network, virtual networks, etc.

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

[0048] Figure 2 This is a diagram based on some aspects of the Radio Access Network (RAN) 200. In some examples, the RAN 200 can be integrated with the above-described and... Figure 1 The RAN 104 shown is the same. In some examples, RAN 200 may be the same as described above and in [the following text is incomplete and likely refers to another example]. Figure 1 The same as RAN 104 shown. The geographical area covered by RAN 200 can be divided into cellular areas (cells) that can be uniquely identified by a user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206, and small cell 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by groups of antennas, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0049] Various base stations can be used for deployment. For example, in Figure 2In the example shown, two base stations (base station 210 and base station 212) are illustrated in cells 202 and 204. A third base station (base station 214) is shown as a remote radio head (RRH) 216 controlling cell 206. That is, the base station can have an integrated antenna or can be connected to an antenna or RRH 216 via a feeder cable. In the example shown, cells 202, 204, and 206 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Further, base station 218 is shown in cell 208, which can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home node B, home eNode B, etc.) because base station 218 supports cells with relatively small sizes. Cell size determination can be based on system design and component constraints.

[0050] It should be understood that the radio access network 200 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be used in conjunction with those described above and in... Figure 1 The base station / scheduling entity 108 shown is the same.

[0051] Figure 2 It also includes an unmanned aerial vehicle (UAV) 220, which can be a quadcopter or an unmanned aircraft. The UAV 220 can be configured to act as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell can move depending on the location of a mobile base station such as the quadcopter 220.

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

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

[0054] In a further aspect of RAN 200, the sidelink signal can be used between UEs without necessarily relying on scheduling or control information from the base station. For example, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using peer-to-peer (P2P) or sidelink signal 237 without relaying the communication through the base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and transmit sidelink signal 237 between them without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also transmit sidelink signal 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 can allocate resources for sidelink communication to UEs 226 and 228. In either case, such sidelink signals 227 and 237 can be implemented in a P2P network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, a mesh network, or other suitable direct link network.

[0055] In RAN 200, the ability of a UE to communicate while on the move (independent of its location) is called mobility. The various physical channels between the UE and the radio access network are typically used by the Access and Mobility Management Functions (AMF, not shown). Figure 1 The access and mobility management functions, established, maintained, and released under the control of the core network (part of 102), may include Security Context Management (SCMF) and Security Anchoring Function (SEAF) for performing authentication. SCMF may manage the security context for control plane and user plane functions, in whole or in part.

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

[0057] In a network configured for UL-based mobility, the UL reference signal 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 uniform synchronization signals (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signal, derive carrier frequency and time slot timing from the synchronization signal, and transmit uplink pilot or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each cell in the network can measure the strength of the pilot signal, and the radio access network (e.g., one or more base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. As UE 224 moves through radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, radio access network 200 can, with or without notification to UE 224, hand over UE 224 from the serving cell to a neighboring cell.

[0058] While the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, they may not identify a specific cell but rather an area of ​​multiple cells operating on the same frequency and / or using the same timing. The use of areas in 5G networks or other next-generation communication networks enables uplink-based mobility frameworks and improves efficiency for both the UE and the network because it reduces the number of mobility messages that need to be exchanged between the UE and the network.

[0059] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically prepares for the dedicated use of a portion of the spectrum, usually by way of a license purchased by the mobile network operator from a government regulatory agency. Unlicensed spectrum prepares for the shared use of a portion of the spectrum without requiring a government-approved license. While some technical rules are usually still required to access unlicensed spectrum, access is generally available to any operator or device. Shared spectrum can fall between licensed and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee holding a license for a portion of licensed spectrum can provide Licensed Shared Access (LSA) to share the spectrum with other parties, for example, under conditions determined by the appropriate licensee.

[0060] The air interface in RAN 200 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at any given time. Half-duplex simulations are often implemented using Time Division Duplex (TDD) for radio links. In TDD, 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, for example, several times per time slot. In a radio link, a full-duplex channel typically relies on physical isolation between the transmitter and receiver and appropriate interference cancellation techniques. Full-duplex simulations are often implemented using Frequency Division Duplex (FDD) or Space Division Duplex (SDD) for radio links. In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as Subband Full-Duplex (SBFD), also known as Flexible Duplex.

[0061] Furthermore, the air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between various devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and to prepare for multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Furthermore, for UL transmission, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. Further, multiplexing of DL transmission from base station 210 to UEs 222 and 224 can be provided using 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.

[0062] All aspects of this disclosure will be referenced in Figure 3 The OFDM waveforms are illustrated herein. Those skilled in the art will understand that various aspects of this disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described herein. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms and other waveforms.

[0063] Within this disclosure, a frame refers to a 10 ms duration used for wireless transmission, where each frame comprises 10 subframes, each subframe being 1 ms long. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. See now. Figure 3 An extended view of an exemplary DL subframe 302 is shown, illustrating the OFDM resource grid 304. However, as those skilled in the art will readily understand, the PHY transport structure for any particular application can vary from the example described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers or tones.

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

[0065] UEs typically utilize only a subset of resource grid 304. RBs can be the smallest unit of resources allocated to a UE. Therefore, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE.

[0066] In this illustration, RB 308 is shown occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Further, in this illustration, RB 308 is shown occupying less than the entire duration of subframe 302, but this is only one possible example.

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

[0068] An extended view of one of the time slots in time slot 310 shows time slot 310 comprising a control region 312 and a data region 314. Typically, control region 312 may carry a control channel (e.g., a physical downlink control channel (PDCCH)), and data region 314 may carry a data channel (e.g., a 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 simple structure shown is merely exemplary in nature, and different time slot structures can be utilized, and may include one or more of each of the control area and data area.

[0069] Although Figure 3 Although not shown, each RE 306 within RB 308 can be scheduled to carry one or more physical channels (including control channels, shared channels, data channels, etc.). Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can prepare the receiving device for channel estimation of the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

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

[0071] Synchronization signals PSS and SSS (collectively referred to as SS), and in some examples PBCH, may be transmitted in an SS block comprising four consecutive OFDM symbols numbered in ascending order of time index from 0 to 3. In the frequency domain, the SS block may be extended over 240 consecutive subcarriers, where the subcarriers are numbered in ascending order of frequency from 0 to 239. Of course, this disclosure is not limited to this particular SS block configuration. Other non-limiting examples may utilize more or fewer than two synchronization signals; may include one or more supplementary channels in addition to PBCH; may omit PBCH; and / or may utilize non-consecutive symbols for the SS block, within the scope of this disclosure. PDCCH may carry downlink control information (DCI) for one or more UEs in the cell. This may include, but is not limited to, power control commands, scheduling information, permission and / or assignment for REs used in DL and UL transmissions.

[0072] In UL transmission, the transmitting device (e.g., the scheduled entity 106) may utilize one or more REs 306 to carry UL control information (UCI) 118. The UCI may originate from a higher layer and be transmitted to the scheduling entity 108 via one or more UL control channels such as the Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), etc. Furthermore, the UL RE may carry UL physical signals that typically do not carry information originating from higher layers, such as demodulation reference signals (DMRS), phase tracking reference signals (PT-RS), sounding reference signals (SRS), etc. In some examples, the uplink control information 118 may include a scheduling request (SR), i.e., a request for the scheduling entity 108 to schedule uplink transmissions. Here, in response to the SR transmitted on the uplink control information 118, the scheduling entity 108 may transmit downlink control information 114 that can schedule resources for uplink packet transmissions.

[0073] UL control information may also include Hybrid Automatic Repeat Request (HARQ) feedback (such as acknowledgment (ACK) or negative acknowledgment (NACK)), Channel State Information (CSI), or any other suitable UL control information. HARQ is a technique well-known to those skilled in the art, where the integrity of packet transmissions can be checked for accuracy at the receiving end, for example, using any appropriate integrity checking mechanism such as checksums or Cyclic Redundancy Check (CRC). If the integrity of the transmission is acknowledged, an ACK can be sent; otherwise, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which can enable appending, incremental redundancy, etc.

[0074] In addition to control information, one or more REs 306 (e.g., within data area 314) can be allocated for user data or service data. Such services can be carried on one or more service channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmission; or the Physical Uplink Shared Channel (PUSCH) for UL transmission.

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

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

[0077] The above description and in Figures 1-3 The channels or carriers shown are not necessarily all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and as those skilled in the art will recognize, other channels or carriers, such as other service, control and feedback channels, may be used in addition to those shown.

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

[0079] In some aspects of this disclosure, the scheduling entity and / or the scheduled entity can be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4An example of a MIMO-enabled wireless communication system 400 is shown. In the MIMO system, transmitter 402 includes a plurality of transmit antennas 404 (e.g., N transmit antennas), and receiver 406 includes a plurality of receive antennas 408 (e.g., M receive antennas). Therefore, there are N × M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of transmitter 402 and receiver 406 may be implemented, for example, within a scheduling entity 108, a scheduled entity 106, or any other suitable wireless communication device.

[0080] The use of such multi-antenna technology enables wireless communication systems to employ the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also known as layers) on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity, the latter being called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream with different weights and phase shifts), and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with distinct spatial signatures, allowing each UE to recover one or more data streams destined for it. On the uplink, each UE transmits a spatially precoded data stream, enabling the base station to identify the source of each spatially precoded data stream.

[0081] The number of data streams or layers corresponds to the transmission rank. Typically, the rank of a MIMO system 400 is limited by the number of transmit antennas 404 or receive antennas 408, whichever is lower. Furthermore, channel conditions at the UE and other considerations (such as available resources at the base station) can also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and therefore, the number of data streams) can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal-to-interference-plus-noise ratio (SINR) measured on each of the receive antennas. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI along with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0082] In a Time Division Duplex (TDD) system, UL and DL are reciprocal because they each use different time slots of the same frequency bandwidth. Therefore, in a TDD system, a scheduling entity (e.g., a base station) can assign a rank for DL ​​MIMO transmissions based on UL SINR measurements (e.g., based on sounding reference signals (SRS) or other pilot signals transmitted from the UE). Based on the assigned rank, the base station can then transmit DMRS and / or CSI-RS with separate RS sequences for each layer to prepare for multi-layer channel estimation. According to the CSI-RS, the UE can measure channel quality across layers and resource blocks, as well as feedback RIs and Channel Quality Indicators (CQIs) (which indicate to the base station the MCS for transmissions to the UE), used when updating rank and assigning REs for future downlink transmissions.

[0083] In the simplest case, such as Figure 4 As shown, in a 2x2 MIMO antenna configuration, rank-2 spatial multiplexing transmission sends a data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. The receiver 406 can then reconstruct the data stream using the signals received from each receive antenna 408.

[0084] Semi-persistent scheduling (SPS) of communication resources

[0085] Scheduling is the process of allocating communication or radio resources (e.g., time, frequency, and space resources) in a wireless communication system 100. A scheduling entity 108 (e.g., a gNB or eNB) can schedule communication resources using dynamic scheduling methods and / or semi-persistent scheduling (SPS) methods. In dynamic scheduling, the scheduling entity can use DCI and / or MAC CE to schedule and allocate resources for each communication (e.g., PDSCH / PUSCH and PUCCH) between the scheduling entity and the UE. To reduce communication overhead, the scheduling entity can use SPS techniques to schedule resources in a semi-static or semi-persistent manner. Using SPS, the scheduling entity can configure one or more SPS timings using one or more Radio Resource Control (RRC) messages (e.g., SPS-Config messages). For example, each SPS timing may include downlink (DL) resources and / or uplink (UL) resources. In some examples, the scheduling entity may send a single trigger signal (e.g., DCI) to activate one or more SPS timings configured in the SPS configuration. In some respects, scheduling entities can use SPS resources to send trigger signals (e.g., DCI, DMRS, or CSI-RS) to trigger channel and / or interference reports.

[0086] Figure 5This is a schematic diagram illustrating exemplary SPS configurations for wireless communication, based on several aspects. Scheduling entity 108 can send one or more SPS configurations to UE 106 using SPS signaling 502 (control information). In one example, SPS signaling 502 can be an RRC message that can configure one or more SPS configurations. In some examples, the RRC message can provide one or more SPS configurations or index values ​​for one or more SPS configurations. In some examples, each SPS configuration can be identifiable by a corresponding index value (e.g., index 0 for SPS configuration 0, index 1 for SPS configuration 1, etc.). In some aspects, the scheduling entity can use different indices for each SPS configuration.

[0087] In some respects, the same index can identify one or more SPS configurations, such as a data SPS configuration for downlink data and a measurement SPS configuration for channel / interference measurement results. The scheduling entity can configure both SPS configurations, for example, using RRC and / or MAC CE signaling. In addition to the SPS configuration index, the scheduling entity can also use fields in the DCI (e.g., tags) to indicate whether the same index is for signaling data SPS configuration or measurement SPS configuration. Therefore, the UE can determine whether the index activates a downlink data SPS configuration or a channel / interference measurement SPS configuration, and use the corresponding period P and feedback timing (e.g., K1 for PDSCH or Z for channel measurement results).

[0088] In some aspects, RRC messages can use different indexes to identify the SPS configuration for each configuration. SPS configurations can schedule and allocate periodic communication resources (e.g., time, frequency, and space resources) to multiple SPS opportunities with a predetermined period P or cyclic pattern. A scheduling entity can configure multiple SPS configurations for downlink data and / or channel measurement results. The scheduling entity can then send a DCI 520 to the UE to trigger or activate the desired SPS configuration. In one example, DCI 520 can include indexes (e.g., reporting timing parameter K1 for downlink data and reporting timing parameter Z for channel reporting) for identifying triggered or activated SPS configurations with corresponding periodicity and feedback timing. In some examples, timing parameters K1 and Z can indicate the time slot for the PUCCH opportunity to send feedback or channel measurement results after the associated SPS opportunity. In some aspects, SPS configurations can include both downlink data (e.g., PDSCH) and channel measurement resources spanning different SPS opportunities.

[0089] Three exemplary SPS timings (e.g., first to third SPS timings 504, 506, 508) and corresponding PUCCH timings (e.g., first to third PUCCH timings 510, 512, 514) are in Figure 5 The PUCCH timing is shown in the time domain. Each PUCCH timing can be used for HARQ feedback or channel / interference measurement results, depending on the SPS configuration that triggers it. In other aspects, the SPS configuration may have more or fewer than three SPS timings. The scheduling entity can configure the PUCCH timing to occur at a predetermined time after the associated SPS timing. In one example, the PUCCH timing for HARQ feedback may be at slot K1 after the associated SPS timing carrying downlink data (e.g., PDSCH), and the PUCCH timing for channel / interference measurement results may be at slot Z after the associated SPS timing that provides resources for channel / interference measurement results. In some aspects, the scheduling entity can configure the UL resources of the PUCCH timing by sending the PUCCH resource configuration to the UE or by including the PUCCH configuration as part of the SPS configuration. In some examples, the PUCCH resources may be pre-configured by the network.

[0090] In some respects, SPS timings (e.g., SPS timings 504, 506 and 508) can provide resources allocated for downlink data (e.g., PDSCH), reference signals for channel measurement results (e.g., DMRS and CSI-RS), and / or resources for interference measurement results (e.g., CSI-IM resources). Figure 6 This is a schematic diagram illustrating some exemplary SPS timing resource configurations that can be used for channel and / or interference measurement results, based on certain aspects. In a first exemplary SPS timing 602, some or all resources can be allocated to the DMRS. The UE can use the DMRS for channel measurement results (e.g., Reference Signal Received Power (RSRP)). Other resources in the first SPS timing 602 can be empty PDSCH resources, which may or may not carry DL data. When the PDSCH resource is not used to transmit DL data, the UE can use the empty PDSCH resource to perform interference measurements (e.g., interference from nearby radio devices). The PDSCH resource is considered an empty resource when the scheduling entity does not use the PDSCH resource to transmit downlink data or payloads. When the UE performs any channel / interference measurement results in the SPS timing, the UE can send a channel report that includes the channel / interference measurement results in the PUCCH timing associated with the SPS timing (e.g., Z slots after the SPS timing configured according to the SPS). Some examples of channel measurement results include CQI, RI, and channel characteristics. Some examples of channel characteristics include delay spread and Doppler spread.

[0091] In the second exemplary SPS timing 604, some or all resources may be allocated to the DMRS and the Interference Measurement Resource (CSI-IM). The CSI-IM may reside in the same bandwidth portion (BWP) used for user data (e.g., PDSCH). In some aspects, the scheduling entity may transmit a zero-power reference signal or symbol in the CSI-IM. When using the second SPS timing 604, the UE may assume that the scheduling entity has not allocated the CSI-IM to other devices, allowing the UE to use the CSI-IM to perform interference measurement results. In some aspects, the CSI-IM may include empty symbols to facilitate interference measurement results. Using the CSI-IM, the UE may measure interference from other transmitters to generate an interference report. The UE may then transmit the interference report in a PUCCH timing associated with the second SPS timing 604. In some aspects, the interference report may include one or more of the following: interference pattern in time and / or frequency, interference power, eigenvalues ​​of the interference covariance matrix, ratios between eigenvalues ​​of the interference covariance matrix, the interference covariance matrix, and the rank of the interference covariance matrix. In some respects, the report may include a broadband or single-band report.

[0092] In the third exemplary SPS timing 606, some or all of the resources can be allocated to the Channel State Information Reference Signal (CSI-RS). The UE can use the CSI-RS to perform channel measurements, such as CQI, Rank Indicator (RI), Precoding Matrix Indicator (PMI), and CSI-based RSRP. The UE can then transmit a report including the channel measurement results in the PUCCH timing associated with the third exemplary SPS timing 606.

[0093] In the fourth exemplary SPS timing 608, some or all of the resources can be allocated to CSI-RS and CSI-IM. The UE can use CSI-RS for channel measurement results and CSI-IM for interference measurement results as described above. The UE can then transmit a report including the channel and interference measurement results in the PUCCH timing associated with the fourth exemplary SPS timing 608. In other examples, besides Figure 6 In addition to the resources shown, SPS timings can have any combination of DMRS, CSI-RS, and / or CSI-IM resources.

[0094] In some aspects, the SPS configuration can schedule a specific configuration of empty PDSCH, DMRS, CSI-RS, and / or CSI-IM in each instance of the configured SPS timing. In some aspects, the SPS configuration can schedule a specific configuration of empty PDSCH, DMRS, CSI-RS, and / or CSI-IM in every X instances (X is 1 or greater) of the configured SPS timing. In some aspects, the scheduling entity can signal the value of X in an RRC message, MAC CE, or DCI. In some aspects, the SPS configuration can provide an initial or default value for X.

[0095] After one or more SPS configurations have been configured, the scheduling entity can send control signals (e.g., one or more DCI 520s in the PDCCH) to activate, reactivate, or deactivate the configured SPS configuration at the UE. In one aspect, the DCI can indicate the index of the activated, deactivated, or reactivated SPS configuration. In some examples, the DCI may include one or more indexes to trigger the corresponding SPS configuration.

[0096] Figure 7 This is a flowchart illustrating, based on some aspects, the process 700 for activating or triggering an SPS configuration using indexes and tags in a DCI. A scheduling entity may send a DCI (e.g., DCI 520) including SPS configuration indices corresponding to multiple SPS configurations. At block 702, the UE may receive a DCI including indices that can trigger multiple SPS configurations. At block 704, the UE may determine the SPS configuration corresponding to the same index (e.g., a downlink data SPS configuration and a channel measurement SPS configuration). The DCI also includes a field (e.g., an SPS tag) indicating whether the index triggers or activates a downlink data SPS configuration or a measurement SPS configuration. At block 706, the UE may determine whether to trigger a downlink data SPS configuration or a measurement SPS configuration based on the SPS tag.

[0097] In some aspects, DCI may include a bitmap that can trigger a combined SPS configuration that includes both data SPS timing and channel measurement SPS timing. Figure 8 This is a schematic diagram of a DCI 800 including a bitmap for triggering SPS configuration, based on some aspects. Each bit of the bitmap can correspond to an SPS timing. Three exemplary bits (B0, B1, and B2) of the bitmap are shown in... Figure 8As shown in the diagram. Based on the bit values ​​(0 or 1) and the position of each bit, the UE can determine whether the associated SPS timing is for downlink data (e.g., PDSCH) or for channel / interference measurements. For example, the first bit (B0) of the bitmap can indicate that the first SPS timing 802 is a data SPS timing. The second bit (B1) of the bitmap can indicate that the second SPS timing 804 is a measurement SPS timing. The third bit (B2) of the bitmap can indicate that the third SPS timing 806 is a data SPS timing. Based on the bitmap, the UE can use the correct period and reporting timing parameters (Z or K) to send feedback (e.g., ACK or CSI report) to the scheduling entity in the corresponding PUCCH timing 808.

[0098] In some aspects, the scheduling entity can configure a set of bitmaps (e.g., bitmap 812) to trigger a combination of SPS configurations with different combinations of data SPS timings and measurement SPS timings. Based on the bit values ​​of each bitmap, each bitmap can trigger a certain combination of data SPS timings and measurement SPS timings. The scheduling entity can then use DCI 810 to select a bitmap from the set to trigger the desired SPS timing corresponding to the selected bitmap. For example, DCI 810 has a field 812 indicating the selected bitmap (e.g., a bitmap index). In some aspects, the scheduling entity can use RRC or MAC CE to transmit the set of bitmaps to the UE to reduce the DCI payload. In some aspects, the bitmaps can be part of the SPS configuration. In this case, the scheduling entity can use the bitmap index in the DCI to signal the selected bitmap.

[0099] When an SPS configuration is activated or reactivated, the scheduling entity can use DCI to configure one or more transmission parameters, such as MCS, resource allocation, DMRS configuration, beamforming, precoding, etc. For each activated SPS configuration, the UE can use PUCCH timing (e.g., PUCCH timing 506) to transmit uplink control information (UCI) that may include HARQ feedback, scheduling requests (SR), and channel reports, which may include channel characteristic measurements and / or interference measurements.

[0100] The UE may use different PUCCH formats to transmit the UCI based on its content and / or size. Different PUCCH formats (e.g., formats 0-4) may have different durations (e.g., symbol lengths) and the number of UCI payload bits. For example, a PUCCH format may include one or more of the following: the number of PRBs, the start PRB, the start symbol, and the number of symbols.

[0101] The scheduling entity can use the SPS configurations described above, etc., to efficiently schedule frequent or periodic channel and interference measurements using SPS resources with low signaling overhead. Therefore, from the UE's perspective, the scheduling entity can have more up-to-date information about channel characteristics. UE measurements can help the scheduling entity with channel precoding, interference / noise / channel estimation and prediction, and MCS and transport configuration selection. The UE also benefits from having up-to-date information about channel characteristics that can enhance noise, interference, and / or channel estimation over time. Having up-to-date channel and interference information can enhance data decoding and can lead to lower error rates and higher data rates.

[0102] Reporting of channel and interference measurement results

[0103] In some aspects, SPS configuration can configure the UE to send a channel report for each configured SPS timing. The channel report may include channel characteristic measurements and / or interference measurements. In other aspects, SPS configuration can configure the UE to send a channel report for a block or a predetermined number of SPS timings. In this case, the UE does not send a channel report for every SPS timing. A block of SPS timings may include N SPS timings (N is an integer equal to 1 or greater). In one example, when N has a value of 3, the UE may send a channel report for every three SPS timings.

[0104] Figure 9 This is a schematic diagram illustrating an example of providing a channel report for a block of SPS timing, based on some aspects. The UE can send a single channel report in PUCCH timing 902 of block 904 of SPS timing. Figure 9 Block 904 illustrates an exemplary SPS timing including three SPS timings. In some aspects, the periodicity of the channel report may differ from the periodicity of the reference signal (e.g., DMRS and / or CSI-RS) used for channel measurement results and / or interference measurement resources (e.g., CSI-IM or empty PDSCH). Figure 9 In the example shown, the scheduling entity can send a reference signal 906 for every four SPS timings, and the UE can send a channel report for every three SPS timings. In some respects, the scheduling entity can, as needed, use DCI, RRC, and / or MAC CE, based on the channel report to change the transmission / retransmission parameters of one or more SPS configurations or timings (e.g., PDSCH timings).

[0105] In some respects, the size of a channel report (e.g., the number of bits or packets) can vary depending on the content of the channel report. For example, a UE may use S1 bits to report channel interference measurement results (e.g., CSI-IM based interference reports) and S2 bits to report channel measurement results (e.g., CSI reports). Therefore, the total number of bits in a particular channel report may include S1, S2, or S1+S2 bits, depending on the content of the channel report used for a particular SPS block or SPS timing.

[0106] In some respects, the scheduling entity and the UE can fix the size of the channel report. In this case, when the UE sends a report that includes channel measurement results and / or interference measurement results, the UE may need to reduce the report size to fit the fixed report size. In one example, the UE can use data compression techniques to reduce the data size. In another example, the channel report may include only a subset of the information from the channel / interference measurements. In other examples, the UE can use any appropriate technique or combination of techniques (e.g., compression or inclusion of only a subset of the information) to reduce the size of the channel report.

[0107] PUCCH Resource Allocation and Selection

[0108] In some aspects, the scheduling entity can configure multiple PUCCH resources (e.g., time, frequency, and spatial resources) for transmitting channel and / or interference measurement results based on the SPS configuration. For example, multiple PUCCH resources can be configured using the RRC message PUCCH-Config (e.g., SPS-PUCCH-LIST or multi-CSI-PUCCH-list). In some aspects, the scheduling entity can configure one or more common PUCCH resources for all configured SPS configurations. In some aspects, the scheduling entity can configure PUCCH resources for specific SPS configurations. In some aspects, the UE can use the configured PUCCH resources (e.g., defined in SPS-PUCCH-LIST or multi-CSI-PUCCH-list) to transmit blocks for SPS timing (e.g., ...). Figure 9 The cumulative HARQ feedback (in block 904) and the channel measurement report based on aperiodic, periodic and / or semi-persistent channel / interference measurement references (e.g., based on CSI-RS, DMRS or CSI-IM).

[0109] In one aspect, when the SPS configuration is configured for a single channel report per SPS timing, the scheduling entity can configure one or more PUCCH resources that can support the number of bits in the channel report, and assign specific PUCCH resources in the DCI that triggers the SPS configuration.

[0110] In one aspect, a UE may need to send one or more channel reports during the same PUCCH timing. In this case, the scheduling entity can configure one or more PUCCH resources that can be used to send multiple channel reports within the same PUCCH timing, and the UE can select a PUCCH resource based on the size of the channel report (number of bits or packets). The configured PUCCH resources may have different formats (e.g., format types 0-4) that can carry different payload sizes. For example, the scheduling entity can configure two PUCCH resources (PUCCH resource 0 and resource 1) with different PUCCH formats. For instance, PUCCH resource 0 can be used for channel reports with a size of 2 bits or less, and PUCCH resource 1 can be used for channel reports with a size greater than 2 bits. In some examples, the SPS configuration can indicate a specific PUCCH resource regardless of the size of the channel report payload.

[0111] Figure 10 This is a flowchart illustrating a method for selecting PUCCH resources for transmitting channel reports, based on several aspects. As described above, a scheduling entity can configure or pre-configure one or more common PUCCH resources for transmitting multiple configured channel reports in the same time slot, and configure specific PUCCH resources in an SPS configuration or timing to transmit a single channel report. For example, a UE can have a configured channel report for transmission in a certain SPS timing / PUCCH, similar to the above description. Figures 5-9 Those described. For this purpose, at box 1002, the UE determines the size of the channel report (e.g., the number of bits or packets). For example, the channel report may include channel measurement results and / or interference measurement results.

[0112] At decision box 1004, the UE determines whether the report size is less than or equal to a predetermined threshold. For example, the predetermined threshold could be a predetermined number of bits or packets. In one example, the predetermined threshold could be the number of bits corresponding to a data packet.

[0113] At box 1006, if the channel report size is equal to or less than a predetermined threshold, the UE can select the PUCCH resource indicated in the SPS configuration for configuring the SPS timing associated with the channel report. At box 1008, if the channel report size is greater than a predetermined threshold, the UE can select a PUCCH resource from pre-configured common PUCCH resources. In some aspects, the UE can select a PUCCH resource based on the size of the channel report (e.g., the number of bits or packets). For example, pre-configured common PUCCH resources may include a first PUCCH resource and a second PUCCH resource that differs from the first PUCCH resource in terms of time, frequency, and / or spatial resources. In one example, the UE can select the first PUCCH resource when the channel report has a number of bits less than or equal to the first size, and select the second PUCCH resource when the channel report has a number of bits greater than the first size. In other examples, pre-configured PUCCH resources may include more than two PUCCH resources that can be used for different channel report payload sizes.

[0114] In some aspects, the scheduling entity may not configure specific PUCCH resources for each SPS configuration. In this case, the scheduling entity can configure one or more common PUCCH resources for use by all SPS configurations. When the UE needs to send a channel report, the UE can select a common PUCCH resource, regardless of the payload report size. In some aspects, the scheduling entity can configure the same PUCCH resource for both HARQ feedback (e.g., ACK / NACK for PDSCH) and channel reporting. For example, the scheduling entity can configure one or more common PUCCH resources per SPS configuration for both HARQ feedback and CSI reporting.

[0115] In some respects, the scheduling entity (e.g., gNB or base station) can be configured with two SPS configurations with different start times and / or periodicity. Figure 11This is a schematic diagram illustrating downlink data (e.g., PDSCH) SPS configuration 1102 with different start times and periodicity, and channel and interference measurement results SPS configuration 1104. In one aspect, the scheduling entity / UE can use the same beamforming (e.g., the same DL beam and / or UL beam) for both SPS configurations 1102 and 1104. Therefore, the scheduling entity can use the same precoding for the reference signal (e.g., CSI-RS or DMRS) for SPS configuration 1104 and the PDSCH for SPS configuration 1102 to improve the accuracy of channel and interference measurement results. In one aspect, the channel reference signal (e.g., CSI-RS or DMRS) for the channel measurement results and interference measurement resources (e.g., CSI-IM) used for the channel and interference measurement SPS configurations can be in the same BWP and resources associated with the SPS PDSCH timing. In one aspect, the UE can be configured with one or more DMRSs (e.g., DMRS-based RSRP, channel delay spread, channel Doppler spread) for channel measurements. The UE can use each DMRS configuration individually to perform channel measurement results and send individual or combined reports. In one aspect, the UE can be configured to use one or more CSI-RS resources from a single resource set and / or multiple resource sets for channel measurement results.

[0116] In some respects, one or more DMRS configurations may be precoded using different precoding matrices, and the UE may send channel reports (e.g., DMRS-based RSRP, channel delay spread, channel Doppler spread) for each DMRS configuration or across all DMRS configurations. For each DMRS configuration, the report may include various channel measurements, such as CQI, RI, DMRS-based RSRP, channel delay spread, channel Doppler spread, etc. Based on the channel reports, the scheduling entity may determine the optimal DMRS configuration and channel parameters (e.g., channel precoding, MCS, etc.) for use in DL transmissions.

[0117] In some aspects, a single SPS configuration may include both DL data SPS timing and channel / interference measurement SPS timing, such that the two SPS timings can use the same beamforming for signal transmission. In some aspects, the reference signal used for channel measurement results (e.g., CSI-RS / DMRS) may use the same precoding as the associated DL data (e.g., PDSCH).

[0118] Figure 12This is a schematic diagram illustrating an SPS configuration 1200 that provides a combination of both DL data timing and channel / interference measurement timing, based on several aspects. The combined SPS configuration 1200 may include different types of SPS timing. In this example, a single SPS configuration 1200 provides both based on the respective periodicity, start symbol, and reporting timing of the DL data timing 1202 and the channel measurement timing 1204. As described above, a scheduling entity can use a bitmap to trigger (e.g., activate or reactivate) a single SPS configuration 1200 with a specific combination of data timing and measurement timing based on that bitmap. For example, bit "0" corresponds to the DL data SPS timing, and bit "1" corresponds to the channel / interference measurement SPS timing. In one example, the bitmap may be a representation of... Figure 12 The data SPS timing 1202 and measurement timing 1204 shown are represented by "1010101010". Therefore, different bitmaps result in different combinations of data timing 1202 and measurement timing 1204. In one example, the bitmap may have bit values ​​that provide more DL data timing 1202 or more channel measurement timing 1204. In other examples, the bitmap may have other bit values ​​for different combinations of SPS timings. SPS timings can be repeated cyclically or periodically according to the bitmap. In some aspects, the PUCCH resource allocation and selection process described above can be coupled with a single SPS bit. Figure 1 For example, PUCCH resources can be used for HARQ feedback on downlink data and channel reporting for channel / interference measurement results. In some respects, the SPS resource scheduling techniques described above can be applied to wireless networks using multiple component carriers (e.g., RAN 200) to provide HARQ feedback according to the SPS configuration.

[0119] Trigger channel measurement result reporting

[0120] In some aspects, when reporting is triggered via DMRS transmission, SPS configuration can configure the UE to send channel reports (e.g., channel and / or interference measurement reports) for configured SPS timings. Using DMRS triggering, the scheduling entity can make the UE send frequent and aperiodic reports. In some aspects, SPS configuration can configure the UE to measure and / or send interference measurement reports (e.g., CSI-IM reports) for one or more (e.g., a predetermined number) SPS timings or blocks of SPS timings when DMRS occurs. A block of SPS timings can include N SPS timings (N is an integer equal to 2 or greater).

[0121] Figure 13This is a schematic diagram illustrating, based on some aspects, an example of providing a channel report, such as one triggered by the reception of DMRS. The SPS configuration can be configured with multiple SPS times 1300, including DL times and PUCCH times. Initially, the UE can receive DCI 1302, which triggers an interference measurement based on measurement resources (e.g., CSI-IM 1304). The UE can then send a CSI-IM report 1306 (channel report) to a scheduling entity (e.g., a base station) within a PUCCH time. Subsequently, the reception of DMRS 1308 in an SPS time can trigger a measurement of CSI-IM 1310 and the transmission of a CSI-IM report 1312 during a PUCCH time 1314 associated with the SPS time. CSI-IM report 1312 is an example of a channel report. The process of measuring interference on CSI-IM and sending a CSI-IM report can continue either during an SPS time or upon receiving DMRS. In one example, unless the SPS PDSCH is empty (i.e., no data and no DMRS), the DMRS at each SPS time can trigger a non-periodic CSI-IM report that can be sent using resources configured with PUCCH (e.g., CSI-IM resources).

[0122] Figure 14 This is a schematic diagram illustrating an example of providing a channel report, such as one triggered by the reception of a specific DMRS. In this example, the scheduling entity can provide at least two types of DMRS in a certain SPS configuration 1400. Initially, the UE can receive DCI 1402, for example, during an SPS timing, and DCI 1402 can trigger an interference measurement result based on CSI-IM 1406. Then, the UE can send a CSI-IM report 1408 to the scheduling entity (e.g., a base station or gNB) during a PUCCH timing.

[0123] Subsequently, reception of Type 1 DMRS 1410 during the SPS timing does not trigger channel interference measurement or reporting. Instead, reception of Type 2 DMRS 1412 during the SPS timing, rather than Type 1 DMRS 1410, can trigger measurement of CSI-IM 1414 during the SPS timing and transmission of CSI-IM report 1416 during the PUCCH timing associated with the SPS timing. The process of measuring CSI-IM and sending CSI-IM reports can continue when Type 2 DMRS occurs or is received. For example, reception of another Type 2 DMRS 1420 can trigger measurement of CSI-IM 1422 and transmission of CSI-IM report 1424 during PUCCH timing 1426.

[0124] In one example, the second type of DMRS 1412 can use a different DMRS sequence than the first (nominal) DMRS type 1410, such as the sign of the reversed odd (or even) elements of the first type (nominal) DMRS sequence. For example, if the first type of DMRS (nominal) sequence is [a, b, c, d, e, f], then the second type of DMRS sequence could be [a, -b, c, -d, e, -f] (even elements reversed) or [-a, b, -c, d, -e, f] (odd elements reversed). Typically, two DMRSs (e.g., DMRS 1410, 1412, 1420) can differ in mode, number of symbols, DMRS configuration type, sequence, etc.

[0125] Figure 15 This is a schematic diagram illustrating an example of providing multiple channel reports across multiple PUCCH timings, triggered by the reception of a single specific DMRS in SPS configuration 1500. In this example, the scheduling entity can provide at least two DMRS types (e.g., nominal DMRS and specific DMRS). The reception of a single (specific or particular) DMRS can trigger multiple sequential interference measurement reports on CSI-IM. Initially, the UE can receive DCI 1502 during an SPS timing, triggering a measurement for CSI-IM 1504. Then, the UE can send CSI-IM measurement report 1506 to the scheduling entity (e.g., a base station or gNB) within a PUCCH timing.

[0126] Subsequently, reception of the first type DMRS 1510 during an SPS timing does not trigger channel interference measurements or reports. Instead, reception of the second type DMRS 1512 (e.g., a special DMRS) during an SPS timing triggers multiple CSI-IM measurements and the transmission of CSI-IM reports on multiple PUCCH timings. For example, the second type DMRS 1512 may trigger a first CSI-IM measurement 1514 and a first CSI-IM report 1516 during PUCCH timing 1518. The second type DMRS 1512 (special DMRS) may trigger CSI-IM reports on one or more subsequent PUCCH timings, even when the first type DMRS was received during an SPS timing associated with a PUCCH. For example, the second type DMRS 1512 may trigger a second CSI-IM measurement 1520 and a second CSI-IM report 1522 during PUCCH timing 1524 associated with an SPS timing having nominal DMRS. The number of CSI-IM measurements and reports triggered by a single Type II DMRS (Special DMRS) can be configurable. In some respects, Type II DMRS can use a different DMRS sequence than Type I (Nominal) DMRS 1510, such as the sign reversal of the odd (or even) elements of the nominal DMRS sequence as described above.

[0127] Figure 16 This is a schematic diagram illustrating an example of providing multiple channel reports across multiple PUCCH timings, triggered by the reception of a single specific DMRS in SPS configuration 1600. In this example, the scheduling entity can provide at least two DCI types (e.g., nominal DCI 1602 and specific DCI 1603). The reception of a single DCI 1603 (specific DCI) can trigger multiple sequential CSI-IM reports. Initially, the UE can receive a first type of DCI 1602, which triggers a measurement of CSI-IM 1606 during the SPS timing. Then, the UE can send CSI-IM report 1608 to the scheduling entity (e.g., the base station) within the PUCCH timing.

[0128] In this example, subsequent CSI-IM measurements and / or reports are not triggered by the reception of DMRS. Instead, channel interference measurements and reports are triggered by the reception of Type II DCI 1603. In some respects, Type II DCI 1603 can trigger multiple CSI-IM measurements and the transmission of CSI-IM reports at multiple PUCCH times. For example, Type II DCI 1603 can trigger a first CSI-IM measurement 1614 and a first CSI-IM report 1616 during PUCCH time 1618. Type II DCI 1603 is also used to trigger a second CSI-IM measurement 1620 and a second CSI-IM report 1622 during PUCCH time 1624. The number of CSI-IM measurements and reports triggered by a single Type II DCI can be configurable.

[0129] Figure 17 This is a block diagram illustrating an example hardware implementation of a scheduling entity 1700 employing a processing system 1714. For example, the scheduling entity 1700 could be as follows: Figure 1 , Figure 2 and / or Figure 4 Any one or more of the base stations or gNBs shown in the diagram.

[0130] The scheduling entity 1700 may be implemented using a processing system 1714 including one or more processors 1704. Examples of processors 1704 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, the scheduling entity 1700 may be configured to perform any one or more of the functions described herein. That is, the processor 1704 utilized in the scheduling entity 1700 may be used to implement the functions described herein and, for example... Figures 5-16 and Figure 18 Any one or more of the processes and steps shown herein.

[0131] Processor 1704 may be implemented via a baseband or modem chip in some cases, and in other implementations, processor 1704 may include a different number of devices than the baseband or modem chip (e.g., in scenarios where they can work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside the baseband modem processor may be used in implementations including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0132] In this example, processing system 1714 may be implemented using a bus architecture (typically represented by bus 1702). Depending on the specific application and overall design constraints of processing system 1714, bus 1702 may include any number of interconnected buses and bridges. Bus 1702 communicatively couples together various circuits including one or more processors (typically represented by processor 1704), memory 1705, and computer-readable media (typically represented by computer-readable media 1706). Bus 1702 may also link various other circuits such as clock sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will therefore not be described further. Bus interface 1708 provides an interface between bus 1702 and transceiver 1710. Transceiver 1710 and antenna array 1720 provide communication interfaces or units for communicating with various other devices via transmission media. Depending on the nature of the device, user interface 1712 (e.g., keyboard, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1712 is optional and can be omitted in some examples (such as base stations).

[0133] Processor 1704 is responsible for managing bus 1702 and general-purpose processing, including the execution of software stored on computer-readable medium 1706. When executed by processor 1704, the software causes processing system 1714 to perform the various functions described below for any particular device. Computer-readable medium 1706 and memory 1705 may also be used to store data manipulated by processor 1704 when executing the software.

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

[0135] In some aspects of this disclosure, processor 1704 may include circuitry configured for various functions, including, for example, performing channel measurement results and reporting using periodic SPS resources. For instance, the circuitry may be configured to implement... Figures 5-16 and Figure 18 One or more of the functions described.

[0136] In some aspects of this disclosure, processor 1704 may include communication and processing circuitry 1740 configured for various functions, including, for example, communicating with a network core (e.g., a 5G core network), a scheduled entity (e.g., a UE), or any other entity (such as, for example, local infrastructure or entity communicating with scheduling entity 1700 via the Internet (e.g., a network provider)). In some examples, communication and processing circuitry 1740 may include one or more hardware components providing a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuitry 1740 may include one or more transmit / receive chains. Furthermore, communication and processing circuitry 1740 may be configured to receive and process uplink traffic and uplink control messages (e.g., similar to...). Figure 1 The communication and processing circuitry 1740 can also transmit and process downlink service and downlink control messages (e.g., similar to downlink service 112 and downlink control information 114), including uplink service 116 and uplink control information 118. The communication and processing circuitry 1740 can also be configured to execute communication and processing software 1750 stored on a computer-readable medium 1706 to perform one or more of the functions described herein.

[0137] In some implementations of communication involving the reception of information, communication and processing circuitry 1740 may obtain information from components of a wireless communication device (e.g., transceiver 1710 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) that information, and output the processed information. For example, communication and processing circuitry 1740 may output information to another component of processor 1704, to memory 1705, or to bus interface 1708. In some examples, communication and processing circuitry 1740 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1740 may receive information via one or more channels. In some examples, communication and processing circuitry 1740 may include functionality for units used for receiving. In some examples, communication and processing circuitry 1740 may include functionality for units used for processing, including units for demodulation, units for decoding, etc.

[0138] In some implementations of communication involving the transmission (e.g., sending) of information, communication and processing circuitry 1740 may obtain information (e.g., from another component of processor 1704, memory 1705, or bus interface 1708), process that information (e.g., modulate, encode, etc.), and output the processed information. For example, communication and processing circuitry 1740 may output information to transceiver 1710 (e.g., transceiver 1710 transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1740 may transmit one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1740 may transmit information via one or more channels. In some examples, communication and processing circuitry 1740 may include functions for units for transmission (e.g., units for sending). In some examples, communication and processing circuitry 1740 may include functions for units for generation, including units for modulation, units for encoding, etc.

[0139] In one aspect, processor 1704 includes resource scheduling circuitry 1742, which can be configured to perform various functions used in allocating resources (e.g., time, frequency, and space resources) for wireless communication. For example, resource scheduling circuitry 1742 can allocate resources using dynamic scheduling and semi-persistent scheduling (SPS). In dynamic scheduling, each uplink / downlink data communication (e.g., PUSCH or PDSCH) can be scheduled and controlled via DCI. In SPS, one or more uplink / downlink SPS timings (e.g., PDSCH, PUSCH, and PUCCH timings) can be configured via semi-static messages (e.g., RRC messages) and activated / deactivated / reactivated, for example, using dynamic signaling (e.g., DCI). In one aspect, resource scheduling circuitry 1742 can allocate uplink / downlink data resources (e.g., PDSCH / PUSCH resources), channel / interference measurement resources (e.g., DMRS, CSI-RS, and CSI-IM resources), and PUCCH resources in an SPS configuration, as described above regarding... Figures 5-16 As described herein, the resource scheduling circuit 1742 can also be configured to execute resource scheduling software 1752 stored on a computer-readable medium 1706 to implement one or more of the functions described herein.

[0140] In one aspect, processor 1704 includes channel measurement circuitry 1744, which can be configured to use SPS resources to control various channel and interference measurement functions. Channel measurement circuitry 1744 can perform functions such as triggering UE measurements of the channel between the scheduling entity and the UE, and sending channel reports for that channel. For example, channel measurement circuitry 1744 can determine the DCI or DMRS to be sent to the UE for triggering channel and / or interference measurement results using SPS resources. Channel measurement circuitry 1744 can also be configured to execute channel measurement software 1754 stored on computer-readable medium 1706 to implement one or more of the functions described herein.

[0141] Figure 18 This is a flowchart illustrating an example procedure 1800 for obtaining channel measurement results using SPS and periodic resources, based on some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the features shown may not be required for all implementations. In some examples, procedure 1800 may be... Figure 17 The process is executed by the scheduling entity 1700 shown below. In some examples, the process 1800 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0142] At box 1802, the scheduling entity may send semi-persistent scheduling (SPS) information for radio resources to the UE. The radio resources can be used, for example, to transmit downlink data on SPS timings (e.g., PDSCH timings).

[0143] In one aspect, resource scheduling circuitry 1742 may provide elements for determining SPS information, which configures at least one SPS configuration to allocate downlink data resources (e.g., PDSCH), channel measurement resources (e.g., CSI-RS, DMRS), and / or interference measurement resources (e.g., CSI-IM, empty PDSCH symbols) according to at least one SPS configuration. Communication and processing circuitry 1740 may provide elements for transmitting SPS information to the UE using transceiver 1710 and antenna array 1720. In one example, the scheduling entity may use RRC messages or MAC CE to transmit SPS information.

[0144] At block 1804, the scheduling entity may send a channel measurement resource configuration to the UE for measuring the communication channel between the UE and the scheduling entity. The scheduling entity may also send a PUCCH resource configuration to the UE for reporting channel measurement results of the communication channel and PDSCH feedback associated with at least one SPS configuration, based on SPS information. In some aspects, the scheduling entity may send one or more channel measurement resource configurations to the UE. In one aspect, the scheduling entity may configure aperiodic, periodic, and semi-periodic radio resources (e.g., time, frequency, and spatial resources) for measuring the communication channel between the UE and the scheduling entity. In one aspect, the communication and processing circuitry 1740 may provide elements for sending the channel measurement resource configuration to the UE via transceiver 1710 and antenna array 1720. In one aspect, the resource scheduling circuitry 1742 may provide elements for determining and providing the channel measurement resource configuration.

[0145] In one aspect, the scheduling entity may send SPS information and / or channel measurement resource configuration, or send it in one or more DCIs. In one example, the DCI may activate, deactivate, or reactivate one or more SPS configurations that configure radio resources for transmitting data using downlink data resources (e.g., PDSCH) and / or reference signals (e.g., DMRS or CSI-RS) for channel measurement results, or provide CSI-IM / empty PDSCH to facilitate interference measurement results by the UE. Radio resources can be used by the UE at the configured SPS timing for at least one of the following operations: according to periodicity and reporting timing parameters defined in at least one SPS configuration (e.g., Figure 5 The parameters K1 or Z are used to receive downlink data and / or perform channel / interference measurements.

[0146] At block 1806, the scheduling entity can receive a report (e.g., a channel report) from the UE. The report includes channel measurement results configured according to at least one SPS. In one aspect, communication and processing circuitry 1740 can provide elements for receiving the report from the UE via transceiver 1710 and antenna array 1720. The report may include channel state information, channel measurement results / characteristics, and / or interference measurement results for the channel between the scheduling entity and the UE. In one example, the scheduling entity can receive the report at the UCI of a PUCCH timing scheduled via at least one SPS. In one example, the report may include channel measurement results, such as CQI, RI, DMRS-based RSRP, and channel characteristics (e.g., channel delay spread, channel Doppler spread, etc.). In one example, the report may include interference measurement results, such as interference patterns in time and / or frequency, interference power, eigenvalues ​​of the interference covariance matrix, ratios between eigenvalues ​​of the interference covariance matrix, the interference covariance matrix, and the rank of the interference covariance matrix. In some aspects, the report may include a wideband or single-band report.

[0147] In one aspect, the scheduling entity may transmit control information including a DCI, which includes an index for activating at least one SPS configuration among a plurality of SPS configurations. In one aspect, the at least one SPS configuration may include a first SPS configuration configuring resources for downlink data (e.g., PDSCH) and a second SPS configuration configuring resources for channel measurement results of the communication channel (e.g., DMRS, CSI-RS, and / or CSI-IM resources). In some examples, the DCI may also include flags for indicating, selecting, or activating the first or second SPS configuration as configured via control information (e.g., the DCI). In one aspect, the DCI may include a bitmap configured to indicate a cyclic pattern of a plurality of SPS timings, including at least one first SPS timing for downlink data and at least one second SPS timing for channel measurement results. In one aspect, the at least one SPS configuration may configure a plurality of SPS timings with a first periodicity, and the scheduling entity may receive reports with the first period or a second period different from the first period. In one aspect, the scheduling entity may transmit one or more reference signals during one or more of the plurality of SPS timings for measuring the communication channel. For example, one or more reference signals may include at least one of DMRS or CSI-RS.

[0148] In one aspect, the scheduling entity may send a DCI to trigger channel measurement results in at least one SPS timing defined in at least one SPS configuration. In another aspect, the scheduling entity may be configured to send a first DMRS in a first SPS timing defined in at least one SPS configuration, and a second DMRS in a second SPS timing defined in at least one SPS configuration. The first DMRS and the second DMRS are distinct from each other, and the second DMRS (a special DMRS) instead of the first DMRS triggers the UE to report channel measurement results. In one aspect, in response to a single instance of a DMRS, the scheduling entity may receive multiple reports separately in multiple PUCCH timings. In one aspect, the scheduling entity may send a special DCI that triggers the UE to report channel measurement results. In one aspect, in response to a single instance of a DCI, the scheduling entity may receive multiple reports separately in multiple PUCCH timings. In some aspects, the number of sequential timings in which the scheduling entity receives channel reports may be configured by sending an RRC signal or MAC CE defining the number of multiple channel reports.

[0149] In the example above, the circuitry included in processor 1704 is provided by way of example only, and other units for performing the described functions may be included in various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 1706, or Figure 1 , Figure 2 and / or Figure 4 Any other suitable device or unit described in any of the figures, and utilizing, for example, those described herein. Figures 5-16 and Figure 18 The described process and / or algorithm.

[0150] Figure 19 This is a conceptual diagram illustrating an example hardware implementation of an exemplary scheduled entity 1900 employing a processing system 1914. According to various aspects of this disclosure, elements, any portion of elements, or any combination of elements may be implemented using a processing system 1914 including one or more processors 1904. For example, the scheduled entity 1900 may be as follows: Figure 1 , Figure 2 and / or Figure 4 Any one or more of the user equipment (UE) shown in the figure.

[0151] Processing system 1914 can be with Figure 17 The processing system 1714 shown is substantially the same, including a bus interface 1908, a bus 1902, a memory 1905, a processor 1904, and a computer-readable medium 1906. Furthermore, the scheduled entity 1900 may include components substantially similar to those described above. Figure 17The user interface 1912, transceiver 1910, and antenna array 1920 described herein. That is, the processor 1904 (as utilized in the scheduled entity 1900) can be used to implement the features described herein and in [other applications]. Figures 5-16 and Figure 20 Any one or more processes shown in the diagram.

[0152] In some aspects of this disclosure, processor 1904 may include circuitry configured for various functions, including, for example, performing channel and interference measurements using periodic SPS resources. For instance, the circuitry may be configured to implement... Figures 5-16 and Figure 20 One or more of the functions described.

[0153] In some aspects of this disclosure, processor 1904 may include communication and processing circuitry 1940 configured for various functions, including, for example, communicating with scheduling entity 1700. In some examples, communication and processing circuitry 1940 may include one or more hardware components providing a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuitry 1940 may include one or more transmit / receive chains. Further, communication and processing circuitry 1940 may be configured to transmit and process uplink traffic and uplink control messages (e.g., similar to...). Figure 1 The communication and processing circuitry 1940 receives and processes downlink service and downlink control messages (e.g., similar to downlink service 112 and downlink control messages 114). The communication and processing circuitry 1940 can also be configured to execute communication and processing software 1950 stored on a computer-readable medium 1906 to perform one or more of the functions described herein.

[0154] In some implementations of communication involving the reception of information, communication and processing circuitry 1940 may obtain information from components of scheduled entity 1900 (e.g., from transceiver 1710 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process that information (e.g., decode it), and output the processed information. For example, communication and processing circuitry 1940 may output information to another component of processor 1904, to memory 1905, or to bus interface 1908. In some examples, communication and processing circuitry 1940 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1940 may receive information via one or more channels. In some examples, communication and processing circuitry 1940 may include functionality for units used for receiving. In some examples, communication and processing circuitry 1940 may include functionality for units used for processing, including units for demodulation, units for decoding, etc.

[0155] In some implementations of communication involving the transmission (e.g., sending) of information, communication and processing circuitry 1940 may obtain information (e.g., from another component of processor 1904, memory 1905, or bus interface 1908), process that information (e.g., modulate, encode, etc.), and output the processed information. For example, communication and processing circuitry 1940 may output information to transceiver 1910 (e.g., transceiver 1910 transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1940 may transmit one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1940 may transmit information via one or more channels. In some examples, communication and processing circuitry 1940 may include functions for units used for transmission (e.g., units used for sending). In some examples, communication and processing circuitry 1940 may include functions for units used for generation, including units for modulation, units for encoding, etc.

[0156] In one aspect, processor 1904 includes resource scheduling circuitry 1942, which can be configured to perform various functions used in selecting and choosing communication resources (e.g., time, frequency, and spatial resources) for wireless communication. For example, resource scheduling circuitry 1942 can determine resources based on dynamic signaling (e.g., DCI, MAC CE) and SPS information (RRC messages) received from a scheduling entity (e.g., a base station or gNB). In one aspect, resource scheduling circuitry 1942 can determine resource allocation for both uplink / downlink data during an SPS event (e.g., PUSCH / PDSCH resources, channel / interference measurements during an SPS event (e.g., DMRS, CSI-RS, CSI-IM resources), and PUCCH resources) based on SPS configuration received from a scheduling entity. Resource scheduling circuitry 1942 can also be configured to execute resource scheduling software 1952 stored on a computer-readable medium 1906 to implement one or more of the functions described herein.

[0157] In one aspect, processor 1904 includes channel measurement circuitry 1944, which can be configured to perform various channel and interference measurement functions used in wireless communication. For example, channel measurement circuitry 1944 can be configured to measure the CQI, RI, RSRP, channel delay spread, channel Doppler spread, etc., of a channel. Channel measurement circuitry 1944 can also be configured to measure interference patterns in time or frequency, eigenvalues ​​of the interference covariance matrix, the interference covariance matrix, ratios between eigenvalues, the rank of the interference covariance matrix, interference power, or the average number / average of interference signals. Channel measurement circuitry 1944 can also be configured to execute channel measurement software 1954 stored on computer-readable medium 1906 to implement one or more of the functions described herein.

[0158] Figure 20 This is a flowchart illustrating an example procedure 2000 for channel measurement using SPS and periodic resources, based on some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the features shown may not be required for all implementations. In some examples, procedure 2000 may be performed by... Figure 19 The process 2000 is executed by the UE implemented by the scheduled entity 1900 shown in the figure. In some examples, the process 2000 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0159] At box 2002, the UE can receive semi-persistent scheduling (SPS) information for periodic radio resources that can be used to receive downlink data. In one aspect, the communication and processing circuitry 1940 can provide elements for receiving SPS information via transceiver 1910 and antenna array 1920. In some aspects, the SPS information may include information similar to that described above. Figures 5-16 At least one SPS configuration described. In some aspects, based on the SPS configuration, the UE can determine one or more SPS timings that can be used to receive DL data (e.g., PDSCH) and / or perform channel / interference measurement results, and one or more PUCCH timings for transmitting channel reports, as described above regarding... Figures 5-16 As described. In one aspect, the resource scheduling circuit 1942 can provide a unit for determining the SPS timing and PUCCH timing based on SPS information.

[0160] At block 2004, the UE may receive channel measurement resource configurations for measuring the communication channel between the UE and the scheduling entity, and physical uplink control channel (PUCCH) resource configurations for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration based on SPS information. In some aspects, the UE may receive one or more channel measurement resource configurations. In one aspect, the communication and processing circuitry 1940 may provide elements for receiving channel measurement resource configurations via transceiver 1910 and antenna array 1920.

[0161] In one aspect, the channel resource configuration may be received in one or more DCIs received from the scheduling entity in the PDCCH. The DCI may include one or more fields or tags (e.g., bit fields or bitmaps) that can be activated, deactivated, or reactivated using, for example, one or more SPS configurations or timings. In one aspect, the resource scheduling circuit 1942 may provide a unit for determining the trigger state (activated, deactivated, or reactivated) of at least one SPS configuration based on the channel measurement resource configuration (e.g., DCI).

[0162] In some aspects, the UE can perform channel measurement results of the communication channel according to the periodicity and reporting timing parameters defined in at least one SPS configuration. For example, the SPS configuration can define multiple SPS timings with a period of P and a reporting timing parameter Z for sending reports on the channel measurement results. In one aspect, the channel measurement circuit 1944 can provide a unit for performing channel and interference measurement results of the communication channel. In some aspects, the UE can perform channel measurement results and send channel reports in response to receiving DMRS or DCI from the scheduling entity in one or more SPS timings, as described above regarding Figures 13-16 As described. Using DMRS / DCI to trigger channel reports enables the UE to provide frequent and aperiodic channel reports to the scheduling entity. In some aspects, channel measurement resource configuration can configure the UE to use periodic, aperiodic, and / or semi-persistent resources for channel measurement results, and to include channel measurement results for one or more SPS timings (e.g., Figure 9 In the PUCCH timing of block 904 of the SPS timing.

[0163] At block 2006, the UE may send a report to a scheduling entity (e.g., gNB). The report includes channel measurement results based on at least one SPS configuration. In some examples, the channel measurement results include at least one of channel state information, channel characteristics, or interference measurement results of the communication channel. In one aspect, the communication and processing circuitry 1940 may provide elements for transmitting the report via transceiver 1910 and antenna array 1920. In one example, the UE may transmit a UCI including the report during a PUCCH timing scheduled by at least one SPS configuration. In one aspect, the resource scheduling circuitry 1942 may provide elements for determining the PUCCH timing based on SPS configuration and / or control information (e.g., DCI). In one aspect, the report may include channel and / or interference measurement results of the communication channel. The channel and / or interference measurement results may include measurement results of channel characteristics (e.g., CQI, RI, PMI, and RSRP based on DMRS / CSI-RS) and interference measurement results of the communication channel. Examples of interference measurement results may include interference patterns in time and / or frequency, interference power, eigenvalues ​​of the interference covariance matrix, ratios between eigenvalues ​​of the interference covariance matrix, the interference covariance matrix, and the rank of the interference covariance matrix.

[0164] In one aspect, the control information may include a Data Interchange Context (DCI), which includes an index for activating at least one SPS configuration among a plurality of SPS configurations. In another aspect, the at least one SPS configuration may include a first SPS configuration configuring SPS resources for downlink data (e.g., PDSCH) and a second SPS configuration configuring SPS resources for channel measurement results of a communication channel (e.g., DMRS, CSI-RS, and / or CSI-IM resources). The DCI may also include a flag that can indicate, select, or activate the first or second SPS configuration configured via the control information. In one aspect, the DCI may include a bitmap configured to indicate a cyclic pattern of a plurality of SPS timings, including at least one first SPS timing for downlink data and at least one second SPS timing for channel measurement results. In one aspect, the at least one SPS configuration may configure a plurality of SPS timings with a first period, and the UE may transmit reports with the first period or a second period different from the first period. In one aspect, the UE may receive one or more reference signals during one or more of the plurality of SPS timings for measuring a communication channel. For example, one or more reference signals include at least one of DMRS or CSI-RS.

[0165] In one aspect, the UE may receive a DMRS at at least one SPS timing defined in at least one SPS configuration, and the DMRS may trigger channel measurement results. In another aspect, the UE may receive a DCI, which triggers channel measurement results at at least one SPS timing defined in at least one SPS configuration. In another aspect, the UE may further receive a first DMRS at a first SPS timing defined in at least one SPS configuration, and a second DMRS at a second SPS timing defined in at least one SPS configuration. The first DMRS and the second DMRS are distinct from each other, and only the second DMRS, not the first DMRS, triggers the UE to report channel measurement results. In one aspect, the UE may transmit multiple reports separately in multiple PUCCH timings in response to a single instance of a DMRS. In one aspect, the UE may receive a first DCI and a second DCI, wherein the first DCI and the second DCI are distinct from each other, and the second DCI, not the first DCI, triggers the UE to report channel measurement results. In another aspect, the UE may transmit multiple reports (e.g., channel and / or interference measurement results) separately in multiple PUCCH timings in response to a single instance of a DCI.

[0166] Of course, in the example above, the circuitry included in processor 1904 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 1906, or Figure 1 , Figure 2 and / or Figure 4 Any other suitable device or unit described in any of the figures, and utilizing, for example, those described herein. Figures 5-16 and Figure 20 The described process and / or algorithm.

[0167] Figure 21 and Figure 22 This is a diagram illustrating some use cases of the SPS technology described above, based on various aspects. (Reference) Figure 21 The scheduling entity can send DCI 2102 to activate one or more SPS configurations. The UE can use the first SPS timing 2104 for channel / interference measurements and report the measurement results in the first PUCCH timing 2106. Based on the measurement results, the scheduling entity can determine to change some transmission parameters, such as MCS, resource allocation, DMRS mode / configuration, beamforming, precoder, etc. For that purpose, the scheduling entity can send SPS reactivation DCI 2108 to change or update the transmission parameters for the upcoming SPS timing.

[0168] exist Figure 22 In this context, the scheduling entity can send DCI 2202 to trigger one or more SPS configurations. The UE can use the first SPS timing 2204 and the second SPS timing 2206 for channel / interference measurement results. Based on reports from these measurements, the scheduling entity can monitor the channel and predict and determine transmission parameters for future SPS timings. For example, the scheduling entity can send an SPS reactivation DCI 2208 to change or update transmission parameters for an upcoming SPS timing 2210. The scheduling entity can also use channel / interference measurement results to reconfigure retransmission parameters (e.g., resource allocation, MCS, DMRS mode, precoder, etc.) for failed PDSCH downlink data transmissions.

[0169] Several aspects of wireless communication networks have been given with reference to exemplary implementations. As will be readily understood by those skilled in the art, the various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0170] A first aspect of this disclosure provides a scheduling entity for wireless communication, the scheduling entity comprising: a communication interface configured to communicate with a user equipment (UE); a memory; and a processor coupled to the communication interface and the memory, wherein the processor and the memory are configured to: send semi-persistent scheduling (SPS) information to the UE of radio resources capable of transmitting downlink data; send to the UE a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results of the communication channel and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration; and receive from the UE a report including channel measurement results according to at least one SPS configuration, wherein the channel measurement results include at least one of channel state information of the communication channel, channel characteristics, or interference measurement results.

[0171] In the second aspect, either alone or in combination with the first aspect, the channel measurement results include channel measurement results based on at least one of the following: periodic, aperiodic, or semi-persistent downlink reference signals; or interference measurement resources of the channel.

[0172] In the third aspect, either alone or in combination with any of the first to second aspects, the PUCCH resource configuration includes resources for PDSCH feedback associated with at least one SPS configuration and resources for channel measurement results.

[0173] In the fourth aspect, either alone or in combination with any of the first to second aspects, the report includes: a first report comprising PDSCH feedback for one or more PDSCH timings for at least one SPS configuration; and a second report comprising channel measurement results for one or more channel measurement timings for at least one SPS configuration.

[0174] In the fifth aspect, either alone or in combination with the first aspect, the PDSCH feedback includes multiple Hybrid Automatic Repeat Request (HARQ) feedback bits associated with one or more PDSCH timings; and the channel measurement results include multiple Channel State Information (CSI) bits associated with one or more channel measurement timings.

[0175] In the sixth aspect, either alone or in combination with any of the first to second aspects, the processor and memory are further configured to: send downlink control information (DCI) to the UE including an index for activating at least one of the multiple SPS configurations.

[0176] In the seventh aspect, either alone or in combination with the first aspect, at least one SPS configuration includes a first SPS configuration configuring resources for downlink data and a second SPS configuration configuring resources for channel measurement results of the communication channel, and wherein the DCI further includes a flag configured to select either the first SPS configuration or the second SPS configuration activated by an index.

[0177] In the eighth aspect, either alone or in combination with any of the first to second aspects, the processor and memory are further configured to: transmit to the UE downlink control information (DCI) including a bitmap of a cyclic pattern configured to indicate multiple SPS timings, the multiple SPS timings including at least one first SPS timing configured for downlink data and at least one second SPS timing configured for channel measurement results.

[0178] In the ninth aspect, either alone or in combination with any of the first to second aspects, wherein at least one SPS configuration utilizes a first cycle to configure multiple SPS timings, and wherein the processor and memory are further configured to receive reports in the first cycle or a second cycle different from the first cycle.

[0179] In the tenth aspect, either alone or in combination with the ninth aspect, the processor and memory are further configured to transmit one or more reference signals during one or more SPS opportunities of a plurality of SPS opportunities for measuring the communication channel, wherein the one or more reference signals include at least one of the following: demodulation reference signal (DMRS); or channel state information reference signal (CSI-RS).

[0180] In the eleventh aspect, either alone or in combination with any of the first to second aspects, wherein the processor and memory are further configured to perform at least one of the following: transmitting a demodulation reference signal (DMRS) at at least one SPS timing defined in at least one SPS configuration, the DMRS being configured to trigger channel measurement results; or transmitting downlink control information (DCI) configured to trigger channel measurement results at at least one SPS timing defined in at least one SPS configuration.

[0181] In the twelfth aspect, either alone or in combination with the eleventh aspect, the processor and memory are further configured to transmit a DMRS comprising: a first DMRS in a first SPS timing defined in at least one SPS configuration; and a second DMRS in a second SPS timing defined in at least one SPS configuration, wherein the first DMRS and the second DMRS are distinct from each other, and the second DMRS, rather than the first DMRS, triggers the UE to report channel measurement results.

[0182] In the thirteenth aspect, either alone or in combination with the eleventh aspect, the processor and memory are further configured to receive reports, including: receiving multiple reports separately in multiple physical uplink control channel (PUCCH) moments in response to a single instance of DMRS or a single instance of DCI.

[0183] In the fourteenth aspect, alone or in combination with the eleventh aspect, the DCI includes a first DCI and a second DCI, wherein the first DCI and the second DCI are distinct from each other, and the second DCI, rather than the first DCI, triggers the UE to report channel measurement results.

[0184] The fifteenth aspect provides a method for wireless communication at a scheduling entity, the method comprising: sending semi-persistent scheduling (SPS) information to a user equipment (UE) of radio resources capable of transmitting downlink data; sending to the UE a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration, based on the SPS information; and receiving from the UE a report including channel measurement results based on at least one SPS configuration, wherein the channel measurement results include at least one of channel state information of the communication channel, channel characteristics, or interference measurement results.

[0185] A sixteenth aspect provides a user equipment (UE) for wireless communication, the UE comprising: a communication interface configured to communicate with a scheduling entity; a memory; and a processor coupled to the communication interface and the memory, wherein the processor and the memory are configured to: receive semi-persistent scheduling (SPS) information from the scheduling entity of radio resources capable of receiving downlink data; receive from the scheduling entity a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results of the communication channel and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration; and transmit a report including channel measurement results to the scheduling entity according to at least one SPS configuration, wherein the channel measurement results include at least one of channel state information of the communication channel, channel characteristics, or interference measurement results.

[0186] In the seventeenth aspect, alone or in combination with the sixteenth aspect, the channel measurement results include channel measurement results based on at least one of the following: periodic, aperiodic, or semi-persistent downlink reference signals; or interference measurement resources of the channel.

[0187] In the eighteenth aspect, alone or in combination with any of the sixteenth to seventeenth aspects, the PUCCH resource configuration includes resources for PDSCH feedback associated with at least one SPS configuration and resources for channel measurement results.

[0188] In the nineteenth aspect, alone or in combination with any of the sixteenth to seventeenth aspects, the report includes: a first report comprising PDSCH feedback for one or more PDSCH timings for at least one SPS configuration; and a second report comprising channel measurement results for one or more channel measurement timings for at least one SPS configuration.

[0189] In the twentieth aspect, alone or in combination with the nineteenth aspect, the PDSCH feedback includes multiple Hybrid Automatic Repeat Request (HARQ) feedback bits associated with one or more PDSCH timings; and the channel measurement results include multiple Channel State Information (CSI) bits associated with one or more channel measurement timings.

[0190] In the twenty-first aspect, either alone or in combination with any of the sixteenth to seventeenth aspects, the processor and memory are further configured to receive downlink control information (DCI) including an index for activating at least one of the plurality of SPS configurations.

[0191] In the twenty-second aspect, either alone or in combination with the twenty-first aspect, at least one SPS configuration includes a first SPS configuration configuring resources for downlink data and a second SPS configuration configuring resources for channel measurement results of the communication channel, and wherein the DCI further includes a flag configured to select either the first SPS configuration or the second SPS configuration activated by an index.

[0192] In the twentieth aspect, alone or in combination with any of the sixteenth to seventeenth aspects, the processor and memory are further configured to: receive downlink control information (DCI) including a bitmap of a cyclic pattern configured to indicate a plurality of SPS timings, the plurality of SPS timings including at least one first SPS timing configured for downlink data and at least one second SPS timing configured for channel measurement results.

[0193] In the 24th aspect, alone or in combination with any of the 16th to 17th aspects, wherein at least one SPS configuration utilizes a first cycle to configure multiple SPS timings, and wherein the processor and memory are further configured to send reports in the first cycle or a second cycle different from the first cycle.

[0194] In aspect 25, alone or in combination with aspect 24, the processor and memory are further configured to receive one or more reference signals during one or more SPS times of a plurality of SPS times for measuring the communication channel, wherein the one or more reference signals include at least one of the following: demodulation reference signal (DMRS); or channel state information reference signal (CSI-RS).

[0195] In the twenty-sixth aspect, alone or in combination with any of the sixteenth to seventeenth aspects, the processor and memory are further configured to perform at least one of the following: receiving a demodulation reference signal (DMRS) at at least one SPS timing defined in at least one SPS configuration, the DMRS being configured to trigger channel measurement results; or receiving downlink control information (DCI) configured to trigger channel measurement results at at least one SPS timing defined in at least one SPS configuration.

[0196] In the twentieth aspect, alone or in combination with the twentieth aspect, the processor and memory are further configured to receive DMRS, including: receiving a first DMRS at a first SPS timing defined in at least one SPS configuration; and receiving a second DMRS at a second SPS timing defined in at least one SPS configuration, wherein the first DMRS and the second DMRS are distinct from each other, and the second DMRS, rather than the first DMRS, triggers the UE to report channel measurement results.

[0197] In aspect 28, either alone or in combination with aspect 26, the processor and memory are further configured to transmit reports, including: in response to a single instance of DMRS or a single instance of DCI, transmitting multiple reports separately in multiple physical uplink control channel (PUCCH) moments.

[0198] In aspect 29, alone or in combination with aspect 26, the DCI includes a first DCI and a second DCI, wherein the first DCI and the second DCI are distinct from each other, and the second DCI, rather than the first DCI, triggers the UE to report channel measurement results.

[0199] A thirtieth aspect provides a method for wireless communication at a user equipment (UE), the method comprising: receiving semi-persistent scheduling (SPS) information from a scheduling entity of radio resources available for receiving downlink data; receiving from the scheduling entity a channel measurement resource configuration for measuring a communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting channel measurement results and physical downlink shared channel (PDSCH) feedback associated with at least one SPS configuration, based on the SPS information; and sending a report including channel measurement results to the scheduling entity based on at least one SPS configuration, wherein the channel measurement results include at least one of channel state information of the communication channel, channel characteristics, or interference measurement results.

[0200] For example, these aspects can be implemented within 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). They can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and all design constraints imposed on the system.

[0201] Within this disclosure, the term "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 being more preferred or advantageous than other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to 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 coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never physically contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors (which, when connected and configured, perform the functions described in this disclosure, without being a limitation on 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).

[0202] Can be Figures 1-22 The components, steps, features, and / or functions shown herein may 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 may also be added without departing from the novel features disclosed herein. Figures 1-22 The apparatus, devices, and / or components shown herein 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.

[0203] It should be understood that the specific order or hierarchy of steps in the disclosed method is an illustration of the exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the method may be rearranged. The appended method claims give the elements of various steps in a sample order, and do not imply that they are limited to the given specific order or hierarchy unless expressly stated therein.

[0204] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects shown herein, but conform to the full scope consistent with the language of the claims, wherein references to elements in the singular are not intended to mean “one and only one”, but rather “one or more”, unless expressly stated otherwise. The term “some” refers to one or more unless otherwise expressly stated. The phrase “at least one of” in the list of references refers to any combination of these items, including individual members. 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 and b and c. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and intended to be covered by the claims, and such structural and functional equivalents are known or will be known to those skilled in the art. Furthermore, nothing herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. No claim element is to be interpreted in accordance with 35 USC §112(f) unless the element is explicitly stated using the phrase “unit for…” or, in the case of a method claim, the element is stated using the phrase “step for…”.

Claims

1. A scheduling entity for wireless communication, comprising: Memory; as well as One or more processors coupled to the memory, the one or more processors being configured to: Semi-persistent scheduling (SPS) information of radio resources that can be used to transmit downlink data is sent to the user equipment (UE), the SPS information including: The first SPS configuration allocates Physical Downlink Shared Channel (PDSCH) resources; and The second SPS configuration allocates at least one of channel measurement resources or interference measurement resources. Sending to the UE a channel measurement resource configuration for measuring the communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting the channel measurement results and PDSCH feedback associated with the first SPS configuration; and The UE receives a report including the channel measurement results configured according to the second SPS, wherein the channel measurement results include at least one of the channel state information, channel characteristics, or interference measurement results of the communication channel.

2. The scheduling entity according to claim 1, wherein, The channel measurement results include channel measurement results based on at least one of the following: Periodic, aperiodic, or semi-persistent downlink reference signals; or Interference measurement resources for the channel.

3. The scheduling entity according to claim 2, wherein, The PUCCH resource configuration includes resources for the PDSCH feedback associated with the first SPS configuration based on the SPS information and resources for channel measurement results.

4. The scheduling entity according to claim 1, wherein, The report includes: The first report includes PDSCH feedback for one or more PDSCH timings in response to the first SPS configuration; and The second report includes the channel measurement results for one or more channel measurement occasions for the second SPS configuration.

5. The scheduling entity according to claim 4, wherein, The PDSCH feedback includes multiple Hybrid Automatic Repeat Request (HARQ) feedback bits associated with the one or more PDSCH timings; and the channel measurement results include multiple Channel State Information (CSI) bits associated with the one or more channel measurement timings.

6. The scheduling entity according to claim 1, wherein, The one or more processors are further configured to: Send downlink control information (DCI) to the UE, including an index for activating at least one of the first SPS configuration or the second SPS configuration.

7. The scheduling entity according to claim 6, in, The DCI also includes a flag configured to select either the first SPS configuration or the second SPS configuration activated by the index.

8. The scheduling entity according to claim 1, wherein, The one or more processors are further configured to: Downlink control information (DCI) is sent to the UE, including a bitmap of a cyclic pattern configured to indicate multiple SPS timings, the multiple SPS timings including at least one first SPS timing configured for the downlink data and at least one second SPS timing configured for the channel measurement results.

9. The scheduling entity according to claim 1, in, The first SPS configuration utilizes a first cycle to configure multiple first SPS timings, and The second SPS configuration utilizes a second period, which is different from the first period, to configure multiple second SPS timings.

10. The scheduling entity according to claim 9, wherein, The one or more processors are further configured to: One or more reference signals are transmitted during one or more of the plurality of second SPS timings used to measure the communication channel, wherein the one or more reference signals include at least one of the following: Demodulation Reference Signal (DMRS); or Channel State Information Reference Signal (CSI-RS).

11. The scheduling entity according to claim 1, wherein, The one or more processors are also configured to perform at least one of the following: A demodulation reference signal (DMRS) is transmitted at least one SPS timing defined in the second SPS configuration, the DMRS being configured to trigger the channel measurement results; or Send downlink control information (DCI), which is configured to trigger the channel measurement results in at least one SPS timing defined in the second SPS configuration.

12. The scheduling entity according to claim 11, wherein, The one or more processors are also configured to transmit the DMRS, including: The first DMRS in the first SPS timing defined in the second SPS configuration; and The second DMRS in the second SPS timing defined in the second SPS configuration. The first DMRS and the second DMRS are distinct from each other, and the second DMRS, rather than the first DMRS, triggers the UE to report the channel measurement results.

13. The scheduling entity according to claim 11, wherein, The one or more processors are also configured to receive the report, including: In response to a single instance of the DMRS or a single instance of the DCI, multiple reports are received separately during multiple Physical Uplink Control Channel (PUCCH) times.

14. The scheduling entity according to claim 11, wherein, The DCI includes a first DCI and a second DCI, wherein the first DCI and the second DCI are distinct from each other, and the second DCI, rather than the first DCI, triggers the UE to report the channel measurement results.

15. A method for wireless communication at a scheduling entity, comprising: Semi-persistent scheduling (SPS) information of radio resources that can be used to transmit downlink data is sent to the user equipment (UE), the SPS information including: The first SPS configuration allocates Physical Downlink Shared Channel (PDSCH) resources; and The second SPS configuration allocates at least one of channel measurement resources or interference measurement resources. Sending to the UE a channel measurement resource configuration for measuring the communication channel between the UE and the scheduling entity, and a physical uplink control channel (PUCCH) resource configuration for reporting the channel measurement results and PDSCH feedback associated with the first SPS configuration; and The UE receives a report including the channel measurement results configured according to the second SPS, wherein the channel measurement results include at least one of the channel state information, channel characteristics, or interference measurement results of the communication channel.

16. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors coupled to the memory, wherein the one or more processors are configured to: Receive semi-persistent scheduling (SPS) information from the scheduling entity regarding radio resources that can be used to receive downlink data, the SPS information including: The first SPS configuration allocates Physical Downlink Shared Channel (PDSCH) resources; and The second SPS configuration allocates at least one of channel measurement resources or interference measurement resources. Receive from the scheduling entity a channel measurement resource configuration for measuring the communication channel between the UE and the scheduling entity, and a PUCCH resource configuration for reporting the channel measurement results and PDSCH feedback associated with the first SPS configuration; and A report including the channel measurement results configured according to the second SPS is sent to the scheduling entity, wherein the channel measurement results include at least one of the channel state information, channel characteristics, or interference measurement results of the communication channel.

17. The UE according to claim 16, wherein, The channel measurement results include channel measurement results based on at least one of the following: Periodic, aperiodic, or semi-persistent downlink reference signals; or Interference measurement resources for the channel.

18. The UE according to claim 17, wherein, The PUCCH resource configuration includes resources for the PDSCH feedback associated with the first SPS configuration based on the SPS information and resources for channel measurement results.

19. The UE according to claim 16, wherein, The report includes: The first report includes PDSCH feedback for one or more PDSCH timings in response to the first SPS configuration; and The second report includes the channel measurement results for one or more channel measurement occasions for the second SPS configuration.

20. The UE according to claim 19, wherein, The PDSCH feedback includes multiple Hybrid Automatic Repeat Request (HARQ) feedback bits associated with the one or more PDSCH timings; and the channel measurement results include multiple Channel State Information (CSI) bits associated with the one or more channel measurement timings.

21. The UE according to claim 16, wherein, The one or more processors are further configured to: Receive downlink control information (DCI) including an index for activating at least one of the first SPS configuration or the second SPS configuration.

22. The UE according to claim 21, in, The DCI also includes a flag configured to select either the first SPS configuration or the second SPS configuration activated by the index.

23. The UE according to claim 16, wherein, The one or more processors are further configured to: Receive downlink control information (DCI) including a bitmap of a cyclic pattern configured to indicate multiple SPS timings, the multiple SPS timings including at least one first SPS timing configured for the downlink data and at least one second SPS timing configured for the channel measurement results.

24. The UE according to claim 16, in, The first SPS configuration utilizes a first cycle to configure multiple first SPS timings, and The second SPS configuration utilizes a second period, which is different from the first period, to configure multiple second SPS timings.

25. The UE according to claim 24, wherein, The one or more processors are further configured to: During one or more of the plurality of second SPS timings used to measure the communication channel, one or more reference signals are received, wherein the one or more reference signals include at least one of the following: Demodulation Reference Signal (DMRS); or Channel State Information Reference Signal (CSI-RS).

26. The UE according to claim 16, wherein, The one or more processors are also configured to perform at least one of the following: Receive a demodulation reference signal (DMRS) at at least one SPS timing defined in the second SPS configuration, the DMRS being configured to trigger the channel measurement results; or Receive downlink control information (DCI), the DCI being configured to trigger the channel measurement results in at least one SPS timing defined in the second SPS configuration.

27. The UE according to claim 26, wherein, The one or more processors are further configured to receive the DMRS, including: Receive the first DMRS during the first SPS timing defined in the second SPS configuration; and Receive the second DMRS during the second SPS timing defined in the second SPS configuration. The first DMRS and the second DMRS are distinct from each other, and the second DMRS, rather than the first DMRS, triggers the UE to report the channel measurement results.

28. The UE according to claim 26, wherein, The one or more processors are also configured to send the report, including: In response to a single instance of the DMRS or a single instance of the DCI, multiple reports are sent separately at multiple Physical Uplink Control Channel (PUCCH) times.

29. The UE according to claim 26, wherein, The DCI includes a first DCI and a second DCI, wherein the first DCI and the second DCI are distinct from each other, and the second DCI, rather than the first DCI, triggers the UE to report the channel measurement results.

30. A method for conducting wireless communication at a user equipment (UE), comprising: Receive semi-persistent scheduling (SPS) information from the scheduling entity regarding radio resources that can be used to receive downlink data, the SPS information including: The first SPS configuration allocates Physical Downlink Shared Channel (PDSCH) resources; and The second SPS configuration allocates at least one of channel measurement resources or interference measurement resources. Receive from the scheduling entity a channel measurement resource configuration for measuring the communication channel between the UE and the scheduling entity, and a PUCCH resource configuration for reporting the channel measurement results and PDSCH feedback associated with the first SPS configuration; and A report including the channel measurement results configured according to the second SPS is sent to the scheduling entity, wherein the channel measurement results include at least one of the channel state information, channel characteristics, or interference measurement results of the communication channel.

Images