Techniques for triggering csi reporting based on downlink grant signaling

Abstract

Various aspects of this disclosure provide techniques for triggering the generation and transmission of Channel State Information (CSI) reports by a User Equipment (UE) in response to a base station's announcement of at least one downlink permission. Furthermore, to address unique challenges that may arise regarding traffic conflicts and desynchronization related to downlink permission-triggered CSI reports (e.g., missed downlink control information (DCI)), various aspects of this disclosure can further restrict the transmission of aperiodic CSI (A-CSI) triggered by downlink permission on the Physical Uplink Control Channel (PUCCH) by the UE. Additionally, various aspects of this disclosure provide techniques for utilizing replicated CSI triggering indications (e.g., indicators in the downlink DCI) among multiple messages to signal to the UE that the transmission of A-CSI can be multiplexed or merged with another uplink message (e.g., an acknowledgment).

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 063,044, filed August 7, 2020, entitled “TECHNIQUES FOR TRIGGERING CSI REPORT BASED ON DOWNLINK GRANT SIGNALING”; and U.S. Patent Application No. 17 / 395,226, filed August 5, 2021, entitled “TECHNIQUES FOR TRIGGERING CSI REPORT BASED ON DOWNLINK GRANT SIGNALING”, which have been assigned to the assignee of this application and are hereby expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communication systems, and more specifically, to techniques for triggering the generation of Channel State Information (CSI) reports based on downlink permission signaling transmitted by a base station. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems.

[0005] These multiple access technologies have already been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. For example, fifth-generation (5G) wireless communication technology (which may be referred to as New Radio (NR)) is envisioned to expand and support a wide variety of use cases and applications related to the current generation of mobile networks. In one aspect, 5G communication technologies can include: enhanced mobile broadband addressing human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and massive machine-type communication that allows for a considerable number of connected devices and the transmission of relatively low amounts of non-latency-sensitive information. However, with the increasing demand for mobile broadband access, further improvements to NR communication technologies and other technologies may be expected. Summary of the Invention

[0006] Various aspects of this disclosure provide techniques for triggering the generation and transmission of Channel State Information (CSI) reports by a User Equipment (UE) in response to a base station's announcement of at least one downlink permission. Furthermore, to address unique challenges that may arise regarding traffic conflicts and desynchronization related to downlink permission-triggered CSI reports (e.g., missed downlink control information (DCI)), various aspects of this disclosure can further implement restrictions on the transmission of aperiodic CSIs (A-CSIs) triggered by downlink permission on the Physical Uplink Control Channel (PUCCH). For example, the UE can be configured to limit the transmission of at most one A-CSI on the PUCCH during a single time slot / sub-time slot (e.g., transmission opportunity). Additionally, various aspects of this disclosure provide techniques for utilizing replicated CSI triggering indications (e.g., indicators in the downlink DCI) across multiple messages to signal to the UE that the transmission of A-CSIs can be multiplexed or merged with another uplink message (e.g., acknowledgment).

[0007] In one example, a method for wireless communication implemented by a UE is disclosed. The method may include: receiving a first scheduling permission message from a base station during a first time period, wherein the first scheduling permission message is a downlink permission including a first Channel State Information (CSI) trigger indication for the UE. The method may further include: receiving a second scheduling permission message from the base station during a second time period, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling permission message. The method may further include: generating a CSI report based on receiving one or both of the first scheduling permission message or the second scheduling permission message. The method may further include: transmitting the CSI report from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to transmitting more than one CSI report in a single transmission opportunity.

[0008] In another example, an apparatus for wireless communication. The apparatus may include a memory having instructions; and a processor configured to execute the instructions to: receive a first scheduling permission message from a base station during a first time period for a UE, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. The processor may also be configured to execute the instructions to: receive a second scheduling permission message from the base station during a second time period for the UE, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling permission message. The processor may also be configured to execute the instructions to: generate a CSI report based on receiving one or both of the first scheduling permission message or the second scheduling permission message. The processor may also be configured to execute the instructions to: transmit the CSI report from the UE to the base station on a PUCCH, wherein the UE is restricted to transmitting more than one CSI report in a single transmission opportunity.

[0009] In some aspects, a non-transitory computer-readable medium includes instructions stored therein, which, when executed by a processor, cause the processor to perform the following steps: receiving a first scheduling grant message from a base station during a first time period when the UE is in the process of receiving the UE, wherein the first scheduling grant message is a downlink grant including a first CSI trigger indication for the UE. In some examples, the processor may further perform the following step: receiving a second scheduling grant message from the base station during a second time period when the UE is in the process of receiving the UE, wherein the second scheduling grant message includes a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling grant message. In some examples, the processor may further perform the following step: generating a CSI report based on receiving one or both of the first scheduling grant message or the second scheduling grant message. In some examples, the processor may further perform the following step: transmitting the CSI report from the UE to the base station on a PUCCH, wherein the UE is restricted to transmitting more than one CSI report in a single transmission opportunity.

[0010] In some aspects, another apparatus for wireless communication is disclosed. The apparatus may include: a unit for receiving a first scheduling permission message from a base station during a first time period for a UE, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. The apparatus may further include: a unit for receiving a second scheduling permission message from the base station during a second time period for the UE, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling permission message. The apparatus may further include: a unit for generating a CSI report based on receiving one or both of the first scheduling permission message or the second scheduling permission message. The apparatus may further include: a unit for transmitting the CSI report from the UE to the base station on a PUCCH, wherein the UE is restricted to transmitting more than one CSI report in a single transmission opportunity.

[0011] In another example, a different method implemented by a base station is disclosed. The method may include: sending a first scheduling permission message from the base station to a UE during a first time period, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. The method may further include: generating a second scheduling permission message, the second scheduling permission message including a second CSI trigger indication identical to the first CSI trigger indication sent in the first scheduling permission message, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message. The method may further include: sending the second scheduling permission message to the UE during a second time period. The method may further include: receiving a CSI report from the UE in response to the sending of the first scheduling permission message and the second scheduling permission message, wherein the base station receives no more than one CSI report from the UE during a single transmission opportunity.

[0012] In another example, an apparatus for wireless communication. The apparatus may include: a memory having instructions; and a processor configured to execute the instructions to: transmit a first scheduling permission message from a base station to a UE during a first time period, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. The processor may also be configured to execute the instructions to: generate a second scheduling permission message including a second CSI trigger indication identical to the first CSI trigger indication transmitted in the first scheduling permission message, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message. The processor may also be configured to execute the instructions to: transmit the second scheduling permission message to the UE during a second time period. The processor may also be configured to execute the instructions to: receive a CSI report from the UE in response to the transmission of the first scheduling permission message and the second scheduling permission message, wherein the base station receives no more than one CSI report from the UE during a single transmission opportunity.

[0013] In some aspects, a non-transitory computer-readable medium includes instructions stored therein, which, when executed by a processor, cause the processor to perform the following steps: transmitting a first scheduling grant message from a base station to a UE during a first time period, wherein the first scheduling grant message is a downlink grant including a first CSI trigger indication for the UE. In some examples, the processor may further perform the step of: generating a second scheduling grant message, the second scheduling grant message including a second CSI trigger indication identical to the first CSI trigger indication transmitted in the first scheduling grant message, wherein the second scheduling grant message is one of a second downlink grant message or an uplink grant message. In some examples, the processor may further perform the step of: transmitting the second scheduling grant message to the UE during a second time period. In some examples, the processor may further perform the step of: receiving a CSI report from the UE in response to the transmission of the first scheduling grant message and the second scheduling grant message, wherein the base station receives no more than a single CSI report from the UE during a single transmission opportunity.

[0014] In some aspects, another apparatus for wireless communication is disclosed. The apparatus may include: a unit for transmitting a first scheduling permission message from a base station to a UE during a first time period, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. The apparatus may further include: a unit for generating a second scheduling permission message, the second scheduling permission message including a second CSI trigger indication identical to the first CSI trigger indication transmitted in the first scheduling permission message, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message. The apparatus may further include: a unit for transmitting the second scheduling permission message to the UE during a second time period. The apparatus may further include: a unit for receiving a CSI report from the UE in response to the transmission of the first scheduling permission message and the second scheduling permission message, wherein the base station receives no more than one CSI report from the UE during a single transmission opportunity.

[0015] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0016] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided for illustration and not limitation of the disclosed aspects, wherein the same reference numerals denote the same elements, and in the drawings:

[0017] Figure 1 These are schematic diagrams illustrating examples of wireless communication systems based on various aspects of this disclosure;

[0018] Figure 2 This is a timing diagram of an example of downlink permission triggering based on the CSI report on the PUCCH in accordance with various aspects of this disclosure;

[0019] Figure 3 This is a timing diagram of an example of downlink permission triggering restrictions in the CSI report on the PUCCH according to various aspects of this disclosure;

[0020] Figure 4 This is a timing diagram of an example scenario where downlink permission is triggered to address a missed DCI based on various aspects of the CSI report on the PUCCH according to the present disclosure.

[0021] Figure 5This is a timing diagram of an example of downlink permission triggering for a CSI report on a PUCCH for carrier aggregation extension, based on various aspects of this disclosure;

[0022] Figure 6 This is a sequence diagram of an example scenario triggered by a CSI report based on downlink permission (followed by uplink permission release) according to various aspects of this disclosure;

[0023] Figure 7 This is a timing diagram of an example of CSI on a PUCCH that overlaps with a PUSCH, based on various aspects of this disclosure;

[0024] Figure 8 These are schematic diagrams illustrating example implementations of various components of a user device based on various aspects of this disclosure;

[0025] Figure 9 This is a flowchart illustrating an example of a method for wireless communication implemented by a UE in accordance with various aspects of this disclosure;

[0026] Figure 10 These are schematic diagrams illustrating example implementations of various components of a base station according to various aspects of this disclosure; and

[0027] Figure 11 This is a flowchart illustrating an example of a method for wireless communication implemented by a base station according to various aspects of this disclosure. Detailed Implementation

[0028] In wireless communication systems, base stations can use uplink permission to schedule UEs to send aperiodic Channel State Information (A-CSI) reports on the Physical Uplink Shared Channel (PUSCH). However, in recent years, with the widespread adoption of smartphones, user demand for mobile broadband has increased dramatically. Consequently, in emerging wireless systems such as those utilizing 5G communication technologies, the expected demand for downlink traffic (e.g., from base station to UE) far exceeds the volume of uplink traffic (e.g., from UE to base station). This is typically due to bandwidth-intensive applications (such as video streaming and multimedia file sharing) pushing current cellular systems to their limits.

[0029] In wireless communication, Channel State Information (CSI) refers to the channel properties of a communication link. This information describes how a signal propagates from the transmitter to the receiver and represents, for example, the combined effects of scattering, fading, and power attenuation with distance. This method can be called channel estimation. CSI enables transmissions to adapt to the current channel conditions, which can be crucial for achieving reliable communication with high data rates in wireless systems.

[0030] However, in scenarios where wireless services are disproportionately weighted towards downlink transmission, reliance on uplink permission triggering for A-CSI reports may not be ideal. In fact, restricting CSI report triggering to uplink permission may require additional bandwidth resources and adversely affect latency between the base station and the UE. Therefore, aspects of this disclosure provide techniques for triggering the generation and transmission of A-CSI reports by the UE in response to the base station's announcement of downlink permission. Utilizing downlink permission (as opposed to uplink permission) enables faster A-CSI reporting and provides the base station with more recent CSI information, which in turn helps improve downlink scheduling of data between the base station and the UE. Furthermore, downlink-triggered CSI-RS reporting can be supported to reduce latency and increase reliability.

[0031] Specifically, in some aspects, the downlink control information (DCI) may include a CSI trigger field (e.g., x bits, where x is an integer value greater than or equal to 1) to indicate the CSI trigger state for the UE. In some aspects, the CSI trigger state may identify CSI report settings (e.g., the type of CSI report that the UE may generate in response to receiving downlink permission with a CSI trigger indication) and / or CSI reference signal (CSI-RS) resource settings (e.g., resources for transmitting CSI-RS).

[0032] In other cases, downlink-permitted CSI report triggering can be based on a hybrid Automatic Repeat Request (HARQ) / Acknowledgement (ACK) that is self-decoding CSI and downlink-permitted, where the CSI and HARQ-ACK are sent from the UE to the base station in a separate PUCCH resource. Such an implementation allows for faster CSI feedback for Ultra-Reliable Low-Latency Communication (URLLC).

[0033] In some scenarios, a UE may receive multiple downlink grants (or a combination of downlink and / or uplink grants) from a base station. Each downlink grant independently triggers the generation of an A-CSI report and the transmission of the A-CSI report from the UE to the base station on the PUCCH, and / or the transmission of a HARQ-ACK. However, if the transmission of A-CSI on the PUCCH overlaps with another PUCCH transmission (including a second A-CSI or HARQ-ACK message) in a specific time slot or sub-time slot (collectively referred to as a "transmission opportunity"), or if the transmission of A-CSI overlaps with another PUSCH transmission, service conflicts may occur. Furthermore, to ensure correct decoding of A-CSI and overlapping PUCCH transmissions by the base station, the payload size of the transmission after multiplexing (e.g., multiplexing HARQ-ACK with A-CSI on the PUCCH) must be known to both the base station and the UE.

[0034] However, in some cases, the DCI for scheduling HARQ-ACK or A-CSI may be missed. For example, in some situations, due to poor channel conditions between the base station and the UE, the UE may not be able to receive the base station's transmission requesting downlink grant or Physical Downlink Shared Channel (PDSCH) for HARQ-ACK. In such cases, the base station may incorrectly expect to receive a message multiplexed from the UE during a transmission opportunity, including both A-CSI and HARQ-ACK, or a multiplexed payload of multiple A-CSIs (e.g., a first CSI report and a second CSI report). However, given that the UE may not receive at least one message (e.g., DCI) due to poor channel conditions, the UE may only send A-CSI or HARQ-ACK in response to the transmission made by the base station. Such an uplink payload may not be correctly decoded by the base station, as the base station may decode the payload as a multiplexed message, and the UE may only send one of A-CSI or HARQ-ACK. In such cases, desynchronization between the UE and the base station may adversely affect the base station's ability to receive and decode messages (including CSI reports) from the UE.

[0035] To address potential conflicts and desynchronization due to missed DCIs, aspects of this disclosure can restrict A-CSIs on PUCCHs triggered by downlink grants. For example, a UE can be configured to limit transmission to at most one A-CSI on PUCCHs that overlap in frequency and time resources during the same time slot / sub-slot (e.g., transmission opportunity). Thus, the phrase "overlapping" can refer to the UE transmitting multiple uplink payloads during the same time slot / sub-slot. In such cases, the UE can typically multiplex or combine multiple uplink payloads to form a single payload. In other cases, the UE can be restricted to receiving at most one downlink grant that triggers an A-CSI on the PUCCH in any given time slot / sub-slot to minimize potential conflicts from multiple uplink transmissions on a single transmission opportunity.

[0036] Specifically, since the A-CSI on the PUCCH may overlap with the ACK / NACK of a PDSCH that can be scheduled by another downlink DCI (e.g., a second DCI), aspects of this disclosure can address this missed admission problem (e.g., if the UE fails to receive a downlink admission that triggers the A-CSI report on the PUCCH) by implementing the following techniques: In this technique, the CSI trigger field (e.g., x bits) in the downlink admission A (e.g., a first scheduling admission message) may include a first CSI trigger indication for the UE, including the CSI trigger state (e.g., CSI report settings and / or CSI-RS resource settings). For subsequent downlink or uplink admissions that trigger the A-CSI, the CSI trigger indication for the first downlink admission can be copied. The copied CSI trigger indication in multiple scheduling admission messages can allow the base station to notify the UE that the ACK / NACK of a second scheduling admission message (e.g., a downlink or uplink admission) for PDSCH scheduling may need to be multiplexed or merged with the CSI report.

[0037] Therefore, even in scenarios where the UE fails to receive the first scheduling permission message (e.g., DL permission A), the UE can prepare a CSI report for the base station and appropriately multiplex the uplink payload (e.g., multiplex ACK / NACK with the CSI report) based on a copied CSI trigger indication that can be included in the second scheduling permission message from the base station. Furthermore, considering the implementation of restrictions on A-CSI on the PUCCH (e.g., the UE can be configured to limit the transmission of at most one A-CSI on PUCCHs overlapping in the time and frequency domains during the same time slot / sub-time slot), the UE can determine the exact number of CSI reports that need to be prepared to be fed back to the base station for both the first and second scheduling permission messages, even if the UE fails to receive one of the permission messages.

[0038] In the case of carrier aggregation, the CSI trigger field, including a CSI trigger indication, can be replicated for all subsequent downlink grant messages (e.g., second and third scheduling grant messages) that span multiple component carriers with associated ACK / NACKs on a PDSCH, which may overlap with a CSI report (e.g., triggered by a first scheduling grant message). Alternatively, in other examples, the CSI trigger field, including a CSI trigger indication, can be replicated for a portion of subsequent downlink grant messages (e.g., second or third scheduling grant messages) that span multiple component carriers with associated ACK / NACKs on a PDSCH, which may overlap with a CSI report.

[0039] In other cases, Radio Resource Control (RRC) can be configured with only a single trigger state to simplify operation. For example, in one scenario, a trigger (within a single downlink grant) can trigger A-CSI on the PUCCH carrier only for a single report containing CSIs only for downlink component carriers that can be received under downlink grant. This implementation has the advantage of lower resource overhead, but may not be configured to report CSIs for all component carriers. Alternatively, in another example, a trigger (within a single downlink grant) can trigger A-CSI on the PUCCH carrier only for a single report containing CSIs for all DL CCs. Such an implementation can provide a complete report of CSIs for all downlink component carriers, but has greater overlap due to over-reporting. Additional simplification techniques may include configuring the CSI trigger field to follow a single bit (e.g., x = 1 bit) of all downlink grants for the first scheduling grant message (e.g., downlink grant A) that triggers an A-CSI report on the PUCCH (if the associated ACK / NACK for a PDSCH scheduled by a later DL grant overlaps with an A-CSI report triggered by the first scheduling grant message).

[0040] In some examples, the second scheduling permission message may be an uplink permission message (e.g., where the first scheduling permission message is a downlink permission during a first time period, followed by an uplink permission during a second time period). In such a case, when an A-CSI report is triggered by the first scheduling permission message (e.g., DL permission A) and overlaps with a PUSCH scheduled by the second scheduling permission (e.g., UL permission D) (where UL permission (D) is received later than DL permission (A)), the base station can be configured to copy the A-CSI trigger from DL permission (A) to UL permission (D), or overwrite the A-CSI trigger from DL permission (A) with a new trigger in UL permission (D). Furthermore, the UE can be configured to ignore or discard the trigger in the first scheduling permission message (e.g., DL permission A) and follow the trigger in the second scheduling permission (e.g., UL permission D (later permission)).

[0041] Finally, in some examples, the downlink grant message may be a second scheduling grant message, which precedes the uplink grant (e.g., the first scheduling grant message). In a scenario where the UL grant (D) is received before the DL grant (A), the UE may: (1) treat this as an error condition; (2) follow the A-CSI trigger in the UL grant (earlier grant) and ignore the A-CSI trigger in the DL grant (later grant); (3) if the UL grant already has an A-CSI trigger, follow the A-CSI trigger in the UL grant and ignore the A-CSI trigger in the DL grant; otherwise, follow the A-CSI trigger in the DL grant to generate a CSI report, which is multiplexed onto the PUSCH by punching a specific set of PUSCH REs; or (4) follow the A-CSI trigger in the later grant (which is the DL grant A).

[0042] Now for reference Figure 1-11 The various aspects are described in more detail below. For purposes of explanation, numerous specific details are set forth in the following description to provide a comprehensive understanding of one or more aspects. However, it will be apparent that such aspects can be practiced without these specific details. Furthermore, as used herein, the term "component" can refer to a part of the structure that makes up the system, can be hardware, firmware, and / or software stored on a computer-readable medium, and can be categorized into other components.

[0043] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the examples. For example, the described methods may be performed in a different order than described, and steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0044] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include base station 102, UE 104, evolved packet core (EPC) 160, and / or 5G core (5GC) 190. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells may include base stations. Small cells may include femtocells, picocells, and microcells. In this example, base station 102 may also include gNB 180, as further described herein.

[0045] In one example, some UEs 104 in a wireless communication system may have a modem 814 and a CSI reporting component 850 (see [link to documentation]). Figure 8 The CSI reporting component 850 is used to respond to a CSI report triggering in response to a downlink grant issued by a base station, and is used to perform various aspects of this disclosure. Alternatively, one or more base stations 102 / 180 may include a CSI report triggering component 1150, which is used to issue one or more scheduling grant messages (e.g., downlink and / or uplink grants) to trigger a CSI report from the UE.

[0046] Base station 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., using the S1 interface). Base station 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) can interface with 5GC 190 via backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or 5GC 190) via backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 can be wired or wireless.

[0047] Base station 102 can wirelessly communicate with one or more UEs 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to restricted groups (which may be referred to as closed subscriber groups (CSG)). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) bandwidth allocated per carrier in carrier aggregation for transmissions in the DL and / or UL directions (e.g., for x component carriers). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetrical with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0048] In another example, some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0049] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0050] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage and / or increase the capacity of the access network.

[0051] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, gNodeB (gNB), or other types of base stations. Some base stations (such as gNB 180) can operate one or more frequency bands within the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, frequency bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating frequency bands have been identified as the frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming issues sometimes arise with FR2. Although it is different from the extremely high frequency (EHF) band (30GHz-300GHz) which is identified as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is usually (interchangeably) referred to as the “millimeter wave” (mmW) band in documents and articles.

[0052] Considering the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band. Communication using the mmW radio frequency band has extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 110 to compensate for path loss and short range.

[0053] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming service, and / or other IP services. The BM-SC 170 can provide functions for the provisioning and delivery of MBMS user services. The BM-SC 170 can act as an entry point for MBMS transmission by content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to areas of a Multicast-Broadcast Single Frequency Network (MBSFN) that broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0054] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 may be a control node handling signaling between UE 104 and 5GC 190. Typically, AMF 192 can provide QoS streaming and session management. (For example, user Internet Protocol (IP) packets from one or more UEs 104 may be transmitted via UPF 195. UPF 195 can provide UE IP address allocation for one or more UEs, as well as other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0055] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, base transceiver, wireless base station, wireless transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). IoT UEs may include Machine Type Communication (MTC) / Enhanced MTC (eMTC, also known as Category (CAT)-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT may refer to future technologies that can evolve from or are based on these technologies. For example, eMTC may include FeMTC (Further eMTC), eFeMTC (Further Enhanced eMTC), mMTC (Massive MTC), etc., and NB-IoT may include eNB-IoT (Enhanced NB-IoT), FeNB-IoT (Further Enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0056] Figure 2 This is a timing diagram 200 illustrating an example of downlink permission triggering 205 for a CSI report 210 on the PUCCH according to various aspects of this disclosure. Specifically, in some aspects, the DCI sent from the base station to the UE may include a CSI trigger field (e.g., x bits, where x is an integer value greater than or equal to 1) to indicate the CSI trigger state for the UE. In some aspects, the CSI trigger state may identify CSI report settings (e.g., the type of CSI report that the UE may generate in response to receiving a downlink permission with a CSI trigger indication) and / or CSI-RS resource settings (e.g., resources for transmitting CSI-RS).

[0057] In other cases, downlink-permitted CSI report triggering can be based on self-decoding CSI and downlink-permitted HARQ / ACK, where the CSI and HARQ-ACK are sent from the UE to the base station in a separate PUCCH resource. Such an implementation allows for faster CSI feedback for URLLC.

[0058] Therefore, as shown in timing diagram 200, base station 102 can send downlink grant message 205 to UE 104. Downlink grant message 205 may include CSI report information, which includes information related to CSI-RS. After sending downlink grant message 205, base station 102 can send a downlink packet (e.g., PDSCH 220) to the UE. In one example (e.g., option A), the UE can return CSI report 210 to the base station as part of a HARQ-ACK associated with the PDSCH 220 received at UE 104. In other words, the UE can combine the CSI report into the same message that sends the HARQ-ACK. In other examples (e.g., option B), the transmission of CSI report 210 to base station 104 can be separated from HARQ-ACK 225 in a separate transmission.

[0059] Figure 3This is a timing diagram 300 illustrating an example of downlink permission triggering restrictions for CSI reports on the PUCCH according to various aspects of this disclosure. As shown, in some scenarios, the UE may receive multiple downlink permissions 305 (or a combination of downlink and / or uplink permissions) from the base station, each downlink permission individually triggering the generation of an A-CSI report 310 and the transmission of the A-CSI report 310 from the UE to the base station on the PUCCH (and / or the transmission of a HARQ-ACK). However, if the transmission of A-CSI on the PUCCH (e.g., the first A-CSI 310-a on the PUCCH) overlaps with another PUCCH transmission (e.g., the second A-CSI 310-b or a HARQ-ACK message on the PUCCH) in any time slot or sub-time slot (collectively, "transmission opportunity"), there may be a traffic conflict between the transmissions of the first A-CSI 310-a and the second A-CSI 310-b on the PUCCH. Such service conflicts may render the transmission of one or both of the A-CSI reports 310 inoperable for the base station. In some cases, overlapping transmission attempts of A-CSI reports (e.g., the first A-CSI report 310-a in the first PUCCH and the second A-CSI report 310-b in the second PUCCH) during the same time slot or sub-time slot may also affect the base station's ability to accurately decode the transmitted A-CSI reports. For example, to ensure the base station correctly decodes A-CSI and overlapping PUCCH transmissions, the payload size of the transmission after multiplexing (e.g., multiplexing HARQ-ACK with A-CSI on the PUCCH) must be known to both the base station and the UE. However, due to overlapping (partial or complete) transmissions of multiple PUCCHs including CSI reports, the payload size of the overlapping PUCCHs received at the base station (e.g., the multiplexed first PUCCH 310-a and second PUCCH 310-b) may differ from the expected payload size. Thus, the base station may not be able to correctly decode the two PUCCH 310s, each containing the corresponding CSI report.

[0060] In some cases, DCIs that schedule HARQ-ACK or A-CSI may also be missed. For example, in some situations, due to poor channel conditions between the base station and the UE, the UE may be unable to receive the base station's transmissions requesting HARQ-ACK downlink grants or Physical Downlink Shared Channel (PDSCH). In such cases, the base station may incorrectly anticipate receiving messages multiplexed from the UE during a transmission opportunity, including both A-CSI and HARQ-ACK, or multiplexed payloads of multiple A-CSIs (e.g., first CSI report and second CSI report). However, given that the UE may not receive at least one message (e.g., DCI) due to poor channel conditions, the UE may only send A-CSI or HARQ-ACK in response to a transmission by the base station. Such uplink payloads may also not be correctly decoded by the base station, as the base station may decode the payload into multiplexed messages, while the UE may only send one of A-CSI or HARQ-ACK. In such cases, desynchronization between the UE and the base station may adversely affect the base station's ability to receive and decode messages (including CSI reports) from the UE.

[0061] To address potential conflicts and desynchronization due to missed DCIs, aspects of this disclosure can restrict A-CSIs on PUCCHs triggered by downlink grants. For example, a UE can be configured to limit the transmission of at most one A-CSI on PUCCHs that overlap in time and frequency resources during the same time slot / sub-slot (e.g., transmission opportunity). In other cases, a UE can be restricted to receiving at most one downlink grant that triggers an A-CSI on a PUCCH in any given time slot / sub-slot to minimize potential conflicts from multiple uplink transmissions on a single transmission opportunity.

[0062] Figure 4This is a timing diagram 400 illustrating an example of a scenario where a downlink grant triggered by a CSI report on the PUCCH addresses a missed DCI, according to various aspects of this disclosure. Specifically, as described above, since an A-CSI on the PUCCH may overlap with an ACK / NACK of a PDSCH that can be scheduled by another downlink DCI (e.g., a second DCI), various aspects of this disclosure can address this missed grant problem (e.g., if the UE fails to receive a downlink grant that triggers an A-CSI report on the PUCCH) by implementing the following technique: In this technique, the CSI trigger field (e.g., x bits) in the downlink grant A405 (e.g., a first scheduling grant message) may include a first CSI trigger indication for the UE, including a CSI trigger state (e.g., CSI report setting and / or CSI-RS resource setting). The CSI trigger indication for the first downlink grant 405 can be replicated for a subsequent downlink or uplink grant that triggers the A-CSI (e.g., downlink grant B 415). The replicated CSI trigger indication in the multiple scheduling grant message may allow the base station to notify the UE that the ACK / NACK 425 for the second scheduling grant message 415 for PDSCH scheduling (e.g., downlink or uplink grant) may need to be multiplexed or merged with the CSI report 430.

[0063] Therefore, even if the UE fails to receive the first scheduling permission message (e.g., DL permission A 405), the UE can still prepare a CSI report 430 for the base station and appropriately multiplex the uplink payload (e.g., multiplex ACK / NACK 425 / 435 with the CSI report 430) based on the replicated CSI trigger indication included in the second scheduling permission message 415 from the base station. Furthermore, considering the implementation of restrictions on A-CSI on the PUCCH (e.g., the UE can be configured to limit the transmission of at most one A-CSI on PUCCHs overlapping during time slots / sub-time slots), the UE can determine the exact number of CSI reports 430 that need to be prepared for feedback to the base station for both the first and second scheduling permission messages, even if the UE fails to receive one of the permission messages.

[0064] Figure 5This is a timing diagram illustrating an example of downlink permission triggering for CSI reports on a PUCCH used for carrier aggregation extension, according to various aspects of this disclosure. Specifically, in the case of carrier aggregation, multiple subsequent downlink permission messages (e.g., second scheduling permission message 515 and third scheduling permission message 520) spanning multiple component carriers (e.g., first PDSCH 510, second PDSCH 525, and third PDSCH 530) can replicate the CSI trigger field, including a CSI trigger indication, from the first scheduling permission message (e.g., first DL permission 505), which has associated ACK / NACK 535s (e.g., first ACK / NACK 535-a, second ACK / NACK 535-b, and third ACK / NACK 535-c) that may partially overlap with (e.g., CSI reports 540 triggered by the first scheduling permission message). Alternatively, in other examples, a CSI trigger field, including a CSI trigger indication, may be replicated for a portion of a subsequent downlink grant message (e.g., a second grant message 515 or a third grant message 520) that spans multiple component carriers of the scheduled PDSCH, where the PDSCH has associated ACK / NACK that may overlap with a CSI report.

[0065] In some cases, Radio Resource Control (RRC) can be configured with only a single trigger state to simplify operation. For example, in one scenario, a trigger (within a single downlink grant) might trigger A-CSI on the PUCCH carrier only for a single report containing CSIs only for downlink component carriers that are eligible for downlink grant. This implementation has the advantage of lower resource overhead, but may not be configured to report CSIs for all component carriers. Alternatively, in another example, a trigger (within a single downlink grant) might trigger A-CSI on the PUCCH carrier only for a single report containing CSIs for all DL CCs. Such an implementation can provide a complete report of CSIs for all downlink component carriers, but has greater overlap due to over-reporting. Additional simplification techniques may include configuring the CSI trigger field to follow a single bit (e.g., x = 1 bit) of all downlink grants for the first scheduling grant message (e.g., downlink grant A) that triggers an A-CSI report on the PUCCH (if the associated ACK / NACK for a PDSCH scheduled by a later DL grant overlaps with an A-CSI report triggered by the first scheduling grant message).

[0066] Figure 6This is a timing diagram 600 showing an example of a scenario triggered by a CSI report based on a downlink grant 605 (followed by an uplink grant 620) in accordance with various aspects of this disclosure. Specifically, in some examples, the second scheduling grant message 620 may be an uplink grant message (e.g., where the first scheduling grant message 605 is a downlink grant during a first time period, followed by an uplink grant during a second time period). In such a scenario, when A-CSI report 630 is triggered by a first scheduling permission message 605 (e.g., DL permission A) and overlaps with PUSCH 625 scheduled by a second scheduling permission 620 (e.g., UL permission D) (where UL permission (D) 620 is received later than DL permission (A) 605), the base station can be configured to copy the A-CSI trigger from DL permission (A) 605 to UL permission (D) 620, or overwrite the A-CSI trigger from DL permission (A) 605 with a new trigger in UL permission (D) 620. Furthermore, the UE can be configured to ignore or discard the trigger in the first scheduling permission message 605 (e.g., DL permission A) and follow the trigger in the second scheduling permission 620 (e.g., UL permission D (later permission)).

[0067] Figure 7 This is a timing diagram of an example of the overlap between CSI report 725 and PUSCH 720 on the PUCCH according to various aspects of this disclosure. In some examples, downlink grant message 710 may be a second scheduling grant message, which is preceded by uplink grant 705 (e.g., a first scheduling grant message). In a scenario where UL approval (D) is received earlier than DL approval (A), the UE may: (1) treat this as an error; (2) follow the A-CSI trigger in the UL approval (earlier approval) and ignore the A-CSI trigger in the DL approval (later approval); (3) if the UL approval already has an A-CSI trigger, follow the A-CSI trigger in the UL approval and ignore the A-CSI trigger in the DL approval; otherwise, follow the A-CSI trigger in the DL approval to generate a CSI report, and multiplex the CSI report on the PUSCH by punching a specific number of PUSCH REs, or (4) follow the A-CSI trigger in the later approval (which is DL approval A).

[0068] Figure 8Hardware components and sub-components of an apparatus according to various aspects of this disclosure are shown. This apparatus may be a UE 104 for implementing one or more methods described herein (e.g., method 900). For example, in addition to components including those such as: one or more processors 812, memory 816, and transceiver 802 communicating via one or more buses 844, which may operate in conjunction with a CSI reporting component 850 to perform the functions described herein related to one or more methods (e.g., 900) including this disclosure. In some examples, the CSI reporting component may include a scheduling permission receiving component 855 for receiving one or more scheduling permissions (e.g., DL or UL permissions) including A-CSI triggering from a base station. The scheduling permission receiving component 855 may decode one or more scheduling permission messages and identify whether the UE is configured to prepare and send a CSI report. The CSI reporting component 850 may also include a CSI report generation component 860 for generating a CSI report based on the receipt of one or more scheduling permissions.

[0069] One or more processors 812, modems 814, memory 816, transceivers 802, RF front-ends 888, and one or more antennas 865 may be configured to support voice and / or data calls (simultaneously or not simultaneously) in one or more wireless access technologies. In one aspect, one or more processors 812 may include modems 414 using one or more modem processors. Various functions associated with the CSI reporting component 850 may be included in modems 814 and / or processors 812, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 812 may include any one or any combination of the following: a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or a transceiver processor associated with transceiver 802. In other aspects, some features of one or more processors 812 and / or modems 814 associated with the CSI reporting component 850 may be performed by transceiver 802.

[0070] Memory 816 may be configured to store data used herein and / or a local version of application 875 executed by at least one processor 812, or one or more sub-components of CSI reporting component 850 and / or its sub-components. Memory 816 may include any type of computer-readable medium that can be used by a computer or at least one processor 812, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, memory 816 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes, wherein when UE 104 is operating at least one processor 812 to execute one or more sub-components of CSI reporting component 850 and / or its sub-components, the one or more computer-executable codes are used to define one or more sub-components of CSI reporting component 850 and / or its sub-components, and / or data associated therewith.

[0071] Transceiver 802 may include at least one receiver 806 and at least one transmitter 808. Receiver 806 may include hardware, firmware, and / or processor-executable software code for receiving data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Receiver 806 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 806 may receive signals transmitted by at least one UE 104. Additionally, receiver 806 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, SNR, RSRP, RSSI, etc. Transmitter 808 may include hardware, firmware, and / or processor-executable software code for transmitting data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 808 may include, but are not limited to, RF transmitters.

[0072] Furthermore, in one aspect, the transmitting device may include an RF front-end 888 that can operate communicatively with one or more antennas 865 and a transceiver 802 to receive and transmit radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by a UE 104. The RF front-end 888 may be connected to one or more antennas 865 and may include one or more low-noise amplifiers (LNAs) 890, one or more switches 892, one or more power amplifiers (PAs) 898, and one or more filters 896 for transmitting and receiving RF signals.

[0073] In one aspect, the LNA 890 can amplify a received signal at a desired output level. In one aspect, each LNA 890 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 888 can use one or more switches 892 to select a particular LNA 890 and its specified gain value based on the desired gain value for a particular application.

[0074] Furthermore, for example, the RF front-end 888 may use one or more PAs 898 to amplify the signal for RF output at a desired output power level. In one aspect, each PA898 may have a specified minimum gain value and a maximum gain value. In another aspect, the RF front-end 888 may use one or more switches 892 to select a particular PA898 and its specified gain value based on the desired gain value for a particular application.

[0075] Furthermore, for example, the RF front-end 888 may use one or more filters 896 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 896 may be used to filter the output from a corresponding PA 898 to produce an output signal for transmission. In one aspect, each filter 896 may be connected to a specific LNA 890 and / or PA 898. In one aspect, the RF front-end 888 may use one or more switches 892 to select the transmit or receive path using a specified filter 896, LNA 890, and / or PA 898 based on the configuration specified as given by the transceiver 802 and / or processor 812.

[0076] Therefore, transceiver 802 can be configured to transmit and receive wireless signals via RF front-end 888 and one or more antennas 865. In one aspect, transceiver 802 can be tuned to operate at a specified frequency, enabling the transmitting device to communicate with, for example, one or more base stations 102 or one or more cells or other UEs 104 associated with one or more base stations 102. In one aspect, for example, modem 814 can configure transceiver 802 to operate at a specified frequency and power level based on the configuration of the transmitting device and the communication protocol used by modem 814.

[0077] In one aspect, modem 814 may be a multi-band, multi-mode modem capable of processing digital signals and communicating with transceiver 802, enabling the transceiver 802 to transmit and receive digital data. In one aspect, modem 814 may be multi-band and can be configured to support multiple frequency bands for a specific communication protocol. In one aspect, modem 814 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 814 may control one or more components of a transmitting device (e.g., RF front-end 888, transceiver 802) based on a specified modem configuration to enable the transmission and / or reception of signals from the network. In one aspect, the modem configuration may be based on the mode and frequency band of modem 814 in use. In another aspect, the modem configuration may be based on UE configuration information associated with the transmitting device (such as information provided by the network during cell selection and / or cell reselection).

[0078] refer to Figure 9 Example methods 900 for wireless communication based on various aspects of this disclosure can be found by reference. Figure 1 and 8 One or more UEs 104 are discussed for execution. Although method 900 is described below with respect to the elements of UE 104, one or more of the steps described herein can be implemented using other components.

[0079] At block 905, method 900 may include: at the UE, receiving a first scheduling permission message from the base station during a first time period, wherein the first scheduling permission message is a downlink permission including a first CSI trigger indication for the UE. Aspects of block 905 may be derived from references to... Figure 8 The transceiver 802, CSI reporting component 850, and scheduling permission receiving component 855 described herein shall perform this function. Specifically, data packets received from the base station at one or more antennas 865 may be processed by the transceiver 802 and forwarded to the scheduling permission receiving component 855 via the UE's modem 814. Therefore, the CSI reporting component 850, the scheduling permission receiving component 855, the transceiver 802, one or more antennas 865, the modem 814, the processor 812, and / or one of the sub-components of the UE 104 or its sub-components may define a unit for receiving a first scheduling permission message from the base station at the UE during a first time period.

[0080] At block 910, the method may include: at the UE, receiving a second scheduling permission message from a base station during a second time period, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling permission message. In some examples, the second scheduling permission message may be one of a second downlink permission message or an uplink permission message. Furthermore, the first and second CSI trigger indications may include a CSI trigger state identifying one or both of the CSI reporting settings or CSI reference signal (CSI-RS) resource settings to be used by the UE.

[0081] In some aspects, the first scheduling grant message may be received from the base station on the first component carrier, and the second scheduling grant message may be received from the base station on the second component carrier. Therefore, in some cases, the first CSI trigger indication included in the first scheduling grant message may be replicated for all subsequent scheduling grant messages received across at least the first and second component carriers, wherein the scheduling transmission of the hybrid automatic repeat request (HARQ) / acknowledgment (ACK) for the scheduled physical downlink shared channel (PDSCH) overlaps with the transmission of the CSI report. In other cases, the first CSI trigger indication included in the first scheduling grant message may be replicated for at least a portion of subsequent scheduling grant messages received across at least the first and second component carriers, wherein the scheduling transmission of the HARQ / ACK for the scheduled PDSCH overlaps with the transmission of the CSI report.

[0082] Furthermore, the first CSI trigger indication included in the first scheduling grant message can trigger a CSI report on the PUCCH for the first component carrier on which the first scheduling grant message was received. Alternatively, the first CSI trigger indication included in the first scheduling grant message can trigger a CSI report on the PUCCH for at least the first component carrier and the second component carrier.

[0083] Furthermore, the second CSI trigger indication may be a single-bit trigger field included in a second scheduling grant message received from the base station. Therefore, in some aspects, the second scheduling grant message may be an uplink grant message, and the uplink grant message may include a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in a first scheduling grant message that serves as a downlink grant message. In other examples, the uplink grant message for the second scheduling grant message may include a second CSI trigger indication for the UE, the second CSI trigger indication overriding the first CSI trigger indication included in the first scheduling grant message that serves as a downlink grant message. In such a case, the method may include: discarding a first scheduling grant message from the base station during a first time period at the UE, wherein the first scheduling grant message is a downlink grant including a first CSI trigger indication for the UE. For this purpose, the UE may generate a CSI report based on the second CSI trigger indication included in the second scheduling grant message and transmit it from the UE to the base station on the PUCCH.

[0084] The various aspects of frame 910 can also be referenced as follows Figure 8 The transceiver 802, CSI reporting component 850, and scheduling permission receiving component 855 described herein shall perform this function. Specifically, as described above, data packets received from the base station at one or more antennas 865 may be processed by the transceiver 802 and forwarded to the scheduling permission receiving component 855 via the UE's modem 814. Therefore, the CSI reporting component 850, the scheduling permission receiving component 855, the transceiver 802, one or more antennas 865, the modem 814, the processor 812, and / or one of the UE 104 or its sub-components may define a unit for receiving a second scheduling permission message from the base station during a second time period, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, the second CSI trigger indication being the same as the first CSI trigger indication included in the first scheduling permission message.

[0085] At block 915, method 900 may include generating a CSI report based on receiving one or both of a first scheduling permission message or a second scheduling permission message. Aspects of block 915 may also be derived from, as referenced... Figure 8 The CSI reporting component 850 described herein performs this function. Therefore, one of the following sub-components, CSI reporting component 850, modem 814, processor 812, and / or UE 104 or their sub-components, may define a unit for generating a CSI report based on receiving one or both of a first scheduling permission message or a second scheduling permission message.

[0086] At block 920, method 900 may include: sending a CSI report from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity. Aspects of block 920 may also be derived from, as referenced... Figure 8 The CSI reporting component 850 is described to perform this action. Therefore, one of the following sub-components, CSI reporting component 850, modem 814, processor 812, and / or UE 104 or its sub-components, may define a unit for sending a CSI report from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity.

[0087] Figure 10 Hardware components and sub-components of an apparatus according to various aspects of this disclosure are shown. This apparatus may be a base station 102 for implementing one or more methods described herein (e.g., method 1000). For example, in addition to components including those such as: one or more processors 1012, memory 1016, and transceiver 1002 communicating via one or more buses 1044, which may operate in conjunction with a CSI report triggering component 1050 to perform the functions described herein related to one or more methods (e.g., 1000) including this disclosure. For example, the CSI report triggering component 1050 may include a CSI trigger generation component 1055 for generating one or more scheduling permission messages (e.g., DL / UL permission) from the base station to the UE during multiple time periods. The CSI report triggering component 1050 may also include a CSI report receiving component 1060 for receiving a CSI report from the UE in response to the transmission of a scheduling permission message.

[0088] One or more processors 1012, modems 1014, memory 1016, transceivers 1002, RF front-ends 1088, and one or more antennas 1065 may be configured to support voice and / or data calls (simultaneously or not simultaneously) in one or more wireless access technologies. In one aspect, one or more processors 1012 may include modems 1014 using one or more modem processors. Various functions associated with the CSI report triggering component 1050 may be included in modems 1014 and / or processors 1012, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 1012 may include any one or any combination of the following: a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or a transceiver processor associated with transceiver 1002. In other respects, some features of one or more processors 1012 and / or modems 1014 associated with the CSI report triggering component 1050 may be performed by transceiver 1002.

[0089] Memory 1016 may be configured to store data used herein and / or a local version of application 1075 executed by at least one processor 1012, or one or more sub-components of CSI report triggering component 1050 and / or its sub-components. Memory 1016 may include any type of computer-readable medium that can be used by a computer or at least one processor 1012, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, memory 1016 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes, wherein when base station 102 is operating at least one processor 1012 to execute one or more sub-components of CSI report triggering component 1050 and / or its sub-components, the one or more computer-executable codes are used to define one or more sub-components of CSI report triggering component 1050 and / or its sub-components, and / or data associated therewith.

[0090] Transceiver 1002 may include at least one receiver 1006 and at least one transmitter 1008. Receiver 1006 may include hardware, firmware, and / or processor-executable software code for receiving data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Receiver 1006 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 1006 may receive signals transmitted by at least one UE 104. Additionally, receiver 1006 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, SNR, RSRP, RSSI, etc. Transmitter 1008 may include hardware, firmware, and / or processor-executable software code for transmitting data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 1008 may include, but are not limited to, RF transmitters.

[0091] Furthermore, in one aspect, the transmitting device may include an RF front-end 1088 that can operate communicatively with one or more antennas 1065 and a transceiver 1002 to receive and transmit radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by a UE 104. The RF front-end 1088 may be connected to one or more antennas 1065 and may include one or more low-noise amplifiers (LNAs) 1090, one or more switches 1092, one or more power amplifiers (PAs) 1098, and one or more filters 1096 for transmitting and receiving RF signals.

[0092] In one aspect, the LNA 1090 can amplify a received signal at a desired output level. In one aspect, each LNA 1090 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 1088 can use one or more switches 1092 to select a particular LNA 1090 and its specified gain value based on the desired gain value for a particular application.

[0093] Furthermore, for example, the RF front end 1088 may use one or more PAs 1098 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 1098 may have a specified minimum gain value and a maximum gain value. In another aspect, the RF front end 1088 may use one or more switches 1092 to select a particular PA 1098 and its specified gain value based on the desired gain value for a particular application.

[0094] Furthermore, for example, the RF front-end 1088 may use one or more filters 1096 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 1096 may be used to filter the output from a corresponding PA 1098 to produce an output signal for transmission. In one aspect, each filter 1096 may be connected to a specific LNA 1090 and / or PA 1098. In one aspect, the RF front-end 1088 may use one or more switches 1092 to select the transmit or receive path using a specified filter 1096, LNA 1090, and / or PA 1098 based on a configuration specified as given by the transceiver 1002 and / or processor 1012.

[0095] Therefore, transceiver 1002 can be configured to transmit and receive wireless signals via RF front end 1088 and one or more antennas 1065. In one aspect, transceiver 1002 can be tuned to operate at a specified frequency, enabling the transmitting device to communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102 or other UEs 104. In one aspect, for example, modem 1014 can configure transceiver 1002 to operate at a specified frequency and power level based on the configuration of the transmitting device and the communication protocol used by modem 1014.

[0096] In one aspect, modem 1014 may be a multi-band, multi-mode modem capable of processing digital signals and communicating with transceiver 1002, enabling the use of transceiver 1002 to transmit and receive digital data. In one aspect, modem 1014 may be multi-band and can be configured to support multiple frequency bands for a specific communication protocol. In one aspect, modem 1014 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 1014 may control one or more components of a transmitting device (e.g., RF front-end 1088, transceiver 1002) based on a specified modem configuration to enable the transmission and / or reception of signals from the network. In one aspect, the modem configuration may be based on the mode and frequency band of modem 1014 in use. In another aspect, the modem configuration may be based on base station configuration information associated with the transmitting device (such as information provided by the network during cell selection and / or cell reselection).

[0097] refer to Figure 11 Example methods 1100 for wireless communication based on various aspects of this disclosure can be found by reference. Figure 1 and 10One or more base stations 102 are discussed to perform the procedure. Although method 1100 is described below with respect to the elements of base station 102, one or more of the steps described herein can be implemented using other components.

[0098] At block 1105, method 1100 may include: sending a first scheduling permission message from a base station to a user equipment (UE) during a first time period, wherein the first scheduling permission message is a downlink permission including a first channel state information (CSI) trigger indication for the UE. Aspects of block 1105 may be derived from, as referenced... Figure 10 The transceiver 1002, CSI report triggering component 1050, and CSI triggering component 1055 described herein are used to perform this action. In some examples, CSI triggering component 1055 may generate one or more scheduling grants and route the scheduling grant message to transceiver 1002 via modem 1014, which then transmits the converted radio signal to the UE via one or more antennas 1065. Therefore, one of the following components may be defined: CSI report triggering component 1050, CSI triggering component 1055, transceiver 1002, one or more antennas 1065, modem 1014, processor 1012, and / or base station 102 or a subcomponent thereof. This may define an element for transmitting a first scheduling grant message from the base station to the UE during a first time period.

[0099] At block 1110, the method may include: generating a second scheduling grant message, the second scheduling grant message including a second CSI trigger indication identical to the first CSI trigger indication sent in the first scheduling grant message, wherein the second scheduling grant message is one of a second downlink grant message or an uplink grant message. In some examples, the first CSI trigger indication and the second CSI trigger indication may include a CSI trigger state identifying one or both of the CSI reporting settings or CSI reference signal (CSI-RS) resource settings to be used by the UE. Aspects of block 1110 may also be derived from, for example, reference... Figure 10 The transceiver 1002 and CSI report triggering component 1050 described herein are used to perform this action. Therefore, the CSI report triggering component 1050, CSI triggering component 1055, transceiver 1002, one or more antennas 1065, modem 1014, processor 1012, and / or a base station or one of its sub-components may define a unit for generating a second scheduling permission message, the second scheduling permission message including a second CSI triggering indication identical to the first CSI triggering indication sent in the first scheduling permission message.

[0100] At block 1115, the method may include: sending a second scheduling permission message to the UE during a second time period. In some aspects, the first scheduling permission message may be sent by the base station on a first component carrier, and the second scheduling permission message may be sent by the base station on a second component carrier. Therefore, in some cases, the first CSI trigger indication included in the first scheduling permission message may be replicated for all subsequent scheduling permission messages received across at least the first and second component carriers, wherein scheduling transmissions of the PUCCH may overlap with transmissions of CSI reports. In other cases, the first CSI trigger indication included in the first scheduling permission message may be replicated for at least a portion of subsequent scheduling permission messages received across at least the first and second component carriers, wherein scheduling transmissions of the PDSCH overlap with transmissions of CSI reports.

[0101] Furthermore, the first CSI trigger indication included in the first scheduling grant message can trigger a CSI report on the PUCCH for the first component carrier in which the first scheduling grant message is received. Alternatively, the first CSI trigger indication included in the first scheduling grant message can trigger a CSI report on the PUCCH for at least the first component carrier and the second component carrier.

[0102] Furthermore, the second CSI trigger indication may be a single-bit trigger field included in the second scheduling grant message received from the base station. Therefore, in some aspects, the second scheduling grant message may be an uplink grant message, and the uplink grant message may include a second CSI trigger indication for the UE, the second CSI trigger indication being identical to the first CSI trigger indication included in the first scheduling grant message which is a downlink grant message. In other examples, the uplink grant message used for the second scheduling grant message may include a second CSI trigger indication for the UE, the second CSI trigger indication overriding the first CSI trigger indication included in the first scheduling grant message which is a downlink grant message.

[0103] The various aspects of frame 1115 can also be referenced as follows Figure 10 The transceiver 1002 and CSI report triggering component 1050 described herein shall be used to perform this action. Therefore, the CSI report triggering component 1050, transceiver 1002, one or more antennas 1065, modem 1014, processor 1012, and / or a base station or a sub-component thereof may define a unit for sending a second scheduling permission message to the UE during the second time period.

[0104] At block 1120, the method may include: receiving a CSI report from the UE in response to the transmission of a first scheduling grant message and a second scheduling grant message, wherein the base station receives no more than a single CSI report from the UE during a single transmission opportunity. Aspects of block 1120 may also be provided by reference to [reference needed]. Figure 10 The CSI report triggering component 1050 and CSI report receiving component 1060 described herein shall perform this action. Therefore, the CSI report triggering component 1050, the CSI report receiving component 1060, one or more antennas 1065, modem 1014, processor 1012, and / or a base station or a sub-component thereof may define a unit for receiving a CSI report from the UE in response to the transmission of a first scheduling permission message and a second scheduling permission message.

[0105] Some further example terms

[0106] Implementation examples are described in the following numbered clauses:

[0107] 1. A method for wireless communication, comprising:

[0108] During a first time period, the user equipment (UE) receives a first scheduling permission message from the base station, wherein the first scheduling permission message is a downlink permission including a first channel state information (CSI) trigger indication for the UE;

[0109] The UE receives a second scheduling permission message from the base station during a second time period, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, and the second CSI trigger indication is the same as the first CSI trigger indication included in the first scheduling permission message;

[0110] A CSI report is generated based on receiving one or both of the first scheduling permission message and the second scheduling permission message; and

[0111] The CSI report is sent from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity.

[0112] 2. The method according to Clause 1, wherein the second scheduling permission message is either a second downlink permission message or an uplink permission message.

[0113] 3. The method according to any one of Clauses 1-2, wherein the first CSI trigger indication and the second CSI trigger indication include a CSI trigger state, the CSI trigger state being identified by one or both of the CSI reporting settings or CSI reference signal (CSI-RS) resource settings used by the UE.

[0114] 4. The method according to any one of clauses 1-3, wherein the first scheduling permission message is received from the base station on the first component carrier, and

[0115] The second scheduling permission message is received from the base station on the second component carrier.

[0116] 5. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is replicated for all subsequent scheduling grant messages received across at least the first component carrier and the second component carrier, wherein the scheduling transmission of the hybrid automatic repeat request (HARQ) / acknowledgment (ACK) of the scheduled physical downlink shared channel (PDSCH) overlaps with the transmission of the CSI report.

[0117] 6. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is copied for at least a portion of a subsequent scheduling grant message received across at least the first component carrier and the second component carrier, wherein the scheduling transmission of the hybrid automatic repeat request (HARQ) / acknowledgment (ACK) of the scheduled physical downlink shared channel (PDSCH) overlaps with the transmission of the CSI report.

[0118] 7. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

[0119] 8. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling permission message triggers the CSI report on the PUCCH for at least the first component carrier and the second component carrier.

[0120] 9. The method according to any of the foregoing provisions, wherein the second CSI trigger indication is a single-bit trigger field included in the second scheduling permission message received from the base station.

[0121] 10. The method according to any of the foregoing provisions, wherein the second scheduling permission message is an uplink permission message.

[0122] 11. The method described under any of the foregoing provisions further includes:

[0123] The first scheduling permission message from the base station during the first time period is discarded at the UE, wherein the first scheduling permission message is the downlink permission including the first CSI trigger indication for the UE; and

[0124] The CSI report is sent from the UE to the base station on the PUCCH based on the second CSI trigger indication included in the second scheduling permission message.

[0125] 12. The method according to any of the foregoing clauses, wherein the single transmission opportunity is a transmission slot or a sub-slot.

[0126] 13. An apparatus for wireless communication, comprising:

[0127] At least one processor;

[0128] and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations:

[0129] During a first time period, the user equipment (UE) receives a first scheduling permission message from the base station, wherein the first scheduling permission message is a downlink permission including a first channel state information (CSI) trigger indication for the UE;

[0130] The UE receives a second scheduling permission message from the base station during a second time period, wherein the second scheduling permission message includes a second CSI trigger indication for the UE, and the second CSI trigger indication is the same as the first CSI trigger indication included in the first scheduling permission message;

[0131] A CSI report is generated based on receiving one or both of the first scheduling permission message and the second scheduling permission message; and

[0132] The CSI report is sent from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity.

[0133] 14. The apparatus according to any of the foregoing provisions, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message.

[0134] 15. The apparatus according to any of the foregoing provisions, wherein the first CSI trigger indication and the second CSI trigger indication include a CSI trigger state, the CSI trigger state identifying one or both of the CSI reporting settings or CSI reference signal (CSI-RS) resource settings to be used by the UE.

[0135] 16. The apparatus according to any of the foregoing provisions, wherein the first scheduling permission message is received from the base station on the first component carrier, and

[0136] The second scheduling permission message is received from the base station on the second component carrier.

[0137] 17. The apparatus according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is replicated for all subsequent scheduling grant messages received across at least the first component carrier and the second component carrier, wherein the scheduled transmission of the hybrid automatic repeat request (HARQ) / acknowledgment (ACK) of the scheduled physical downlink shared channel (PDSCH) overlaps with the transmission of the CSI report.

[0138] 18. The apparatus according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is copied for at least a portion of a subsequent scheduling grant message received across at least the first component carrier and the second component carrier, wherein the scheduling transmission of the hybrid automatic repeat request (HARQ) / acknowledgment (ACK) of the scheduled physical downlink shared channel (PDSCH) overlaps with the transmission of the CSI report.

[0139] 19. An apparatus according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

[0140] 20. A method for wireless communication, comprising:

[0141] During a first time period, a first scheduling permission message is sent from the base station to the user equipment (UE), wherein the first scheduling permission message is a downlink permission including a first channel state information (CSI) trigger indication for the UE;

[0142] A second scheduling permission message is generated, the second scheduling permission message including a second CSI trigger indication that is the same as the first CSI trigger indication sent in the first scheduling permission message, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message;

[0143] During the second time period, the second scheduling permission message is sent to the UE; and

[0144] In response to the transmission of the first scheduling permission message and the second scheduling permission message, the base station receives a CSI report from the UE, wherein the base station receives no more than a single CSI report from the UE during a single transmission opportunity.

[0145] 21. The method according to any of the foregoing provisions, wherein the first CSI trigger indication and the second CSI trigger indication include a CSI trigger state, the CSI trigger state identifying one or both of the CSI reporting settings or CSI reference signal (CSI-RS) resource settings to be used by the UE.

[0146] 22. The method according to any of the foregoing provisions, wherein the first scheduling permission message is transmitted from the base station on the first component carrier, and

[0147] The second scheduling permission message is sent from the base station on the second component carrier.

[0148] 23. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is replicated for all subsequent scheduling grant messages received across at least the first component carrier and the second component carrier, wherein the scheduling transmission of the PUCCH overlaps with the transmission of the CSI report.

[0149] 24. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message is copied for at least a portion of a subsequent scheduling grant message received across at least the first component carrier and the second component carrier, wherein the scheduling transmission of the PUCCH overlaps with the transmission of the CSI report.

[0150] 25. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

[0151] 26. The method according to any of the foregoing provisions, wherein the first CSI trigger indication included in the first scheduling permission message triggers the CSI report on the PUCCH for at least the first component carrier and the second component carrier.

[0152] 27. The method according to any of the foregoing provisions, wherein the second CSI trigger indication is a single-bit trigger field included in the second scheduling permission message received from the base station.

[0153] 28. The method according to any of the foregoing provisions, wherein the second scheduling permission message is the uplink permission message.

[0154] 29. The method according to any of the foregoing clauses, wherein the single transmission opportunity is a transmission slot or a sub-slot.

[0155] 30. An apparatus for wireless communication, comprising:

[0156] At least one processor;

[0157] and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations:

[0158] During a first time period, a first scheduling permission message is sent from the base station to the user equipment (UE), wherein the first scheduling permission message is a downlink permission including a first channel state information (CSI) trigger indication for the UE;

[0159] A second scheduling permission message is generated, the second scheduling permission message including a second CSI trigger indication that is the same as the first CSI trigger indication sent in the first scheduling permission message, wherein the second scheduling permission message is one of a second downlink permission message or an uplink permission message;

[0160] During the second time period, the second scheduling permission message is sent to the UE; and

[0161] In response to the transmission of the first scheduling permission message and the second scheduling permission message, the base station receives a CSI report from the UE, wherein the base station receives a single CSI report during a single transmission opportunity.

[0162] The above detailed description, illustrated in conjunction with the accompanying drawings, describes examples, but does not represent the only examples that can be implemented or are within the scope of the claims. The term "example," as used in this description, means "serving as an example, instance, or illustration" and is not "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concept of the described examples.

[0163] Information and signals can be represented using any of a wide variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned above can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0164] The various illustrative boxes and components described in connection with this disclosure can be implemented or executed using specially programmed devices designed to perform the functions described herein, such as, but not limited to, processors, digital signal processors (DSPs), ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A specially programmed processor can be a microprocessor, but alternatively, it can be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0165] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted through a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a specially programmed processor, hardware, firmware, hardwired, or any combination of these items. Features used to implement the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations. Furthermore, as used herein (including in the claims), the word "or" in a list of items ending with "at least one of" indicates a disjoint list, such that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0166] Computer-readable media includes both computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired units of program code in the form of instructions or data structures, and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (e.g., infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (e.g., infrared, radio, and microwave) is included in the definition of media. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

[0167] The detailed description above, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a comprehensive 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 cases, well-known structures and components are shown in the form of block diagrams in order to avoid obscuring such concepts.

[0168] Several aspects of the telecommunications system are also described with reference to various apparatuses and methods. These apparatuses and methods are described in detail and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0169] By way of example, an element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0170] It should be noted that the techniques described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and others. The terms "system" and "network" are often used interchangeably. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High-Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as the Global System for Mobile Communications (GSM). OFDMA systems can implement technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 902.11 (Wi-Fi), IEEE 902.16 (WiMAX), IEEE 902.20, and Flash OFDM. TMRadio technologies such as UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Improved LTE (LTE-A) are newer versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the systems and radio technologies mentioned above, as well as other systems and radio technologies, including cellular (e.g., LTE) communications sharing radio frequency spectrum bands. However, for illustrative purposes, the following description focuses on LTE / LTE-A and / or 5G New Radio (NR) systems, and the terms LTE or 5G NR are used in much of the following description, but the technologies described are applicable to applications beyond LTE / LTE-A and 5G NR applications (e.g., other next-generation communication systems).

[0171] The prior description of this disclosure is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Furthermore, while elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural form is contemplated unless expressly stated to be limited to the singular. Moreover, unless otherwise stated, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment. Therefore, this disclosure is not limited to the examples and designs described herein, but is given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, comprising: During a first time period, the user equipment (UE) receives a first scheduling permission message from the base station while on a first component carrier, wherein the first scheduling permission message is a first downlink permission including a first channel state information (CSI) trigger indication for the UE; At the UE, one or more subsequent scheduling permission messages are received, wherein the transmission of Hybrid Automatic Repeat Request (HARQ) / Acknowledgement (ACK) for the Physical Downlink Shared Channel (PDSCH) scheduled by at least some of the subsequent scheduling permission messages overlaps with the transmission of CSI reports, and wherein the at least some of the subsequent scheduling permission messages include a copy of the first CSI trigger indication included in the first scheduling permission message; The CSI report is generated based on receiving the first scheduling permission message or one or more subsequent scheduling permission messages; and The CSI report is sent from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity.

2. The method according to claim 1, wherein, The one or more subsequent scheduling permission messages are either a second downlink permission message or an uplink permission message.

3. The method according to claim 1, wherein, The first CSI trigger indication and the copy of the first CSI trigger indication each include a CSI trigger state, the CSI trigger state being identified by one or both of the CSI report settings or CSI reference signal (CSI-RS) resource settings used by the UE.

4. The method according to claim 1, wherein, At least some of the scheduling permission messages in the one or more subsequent scheduling permission messages are received from the base station on the second component carrier.

5. The method according to claim 4, wherein, The at least some of the subsequent scheduling permission messages in the one or more subsequent scheduling permission messages include all subsequent scheduling permission messages.

6. The method according to claim 4, wherein, The first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

7. The method according to claim 4, wherein, The first CSI trigger indication included in the first scheduling permission message triggers the CSI report on the PUCCH for at least the first component carrier and the second component carrier.

8. The method according to claim 1, wherein, The replication of the first CSI trigger indication is a single-bit trigger field included in one or more subsequent scheduling permission messages received from the base station.

9. The method according to claim 1, wherein, The one or more subsequent scheduling permission messages are uplink permission messages.

10. The method according to claim 1, further comprising: The first scheduling permission message from the base station during the first time period is discarded at the UE; as well as The CSI report is sent from the UE to the base station on the PUCCH based on the copy of the first CSI trigger indication included in one or more subsequent scheduling permission messages.

11. The method according to claim 1, wherein, The individual transmission opportunity is a transmission time slot or sub-time slot.

12. An apparatus for wireless communication, comprising: At least one processor; as well as A memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations: During a first time period, the user equipment (UE) receives a first scheduling permission message from the base station while on a first component carrier, wherein the first scheduling permission message is a first downlink permission including a first channel state information (CSI) trigger indication for the UE; At the UE, one or more subsequent scheduling permission messages are received, wherein the transmission of Hybrid Automatic Repeat Request (HARQ) / Acknowledgement (ACK) for the Physical Downlink Shared Channel (PDSCH) scheduled by at least some of the subsequent scheduling permission messages overlaps with the transmission of CSI reports, and wherein the at least some of the subsequent scheduling permission messages include a copy of the first CSI trigger indication included in the first scheduling permission message; The CSI report is generated based on receiving the first scheduling permission message or one or more subsequent scheduling permission messages; and The CSI report is sent from the UE to the base station on the Physical Uplink Control Channel (PUCCH), wherein the UE is restricted to sending more than one CSI report in a single transmission opportunity.

13. The apparatus according to claim 12, wherein, The one or more subsequent scheduling permission messages are either a second downlink permission message or an uplink permission message.

14. The apparatus according to claim 12, wherein, The first CSI trigger indication and the copy of the first CSI trigger indication each include a CSI trigger state, the CSI trigger state being identified by one or both of the CSI report settings or CSI reference signal (CSI-RS) resource settings used by the UE.

15. The apparatus according to claim 12, wherein, At least some of the scheduling permission messages in the one or more subsequent scheduling permission messages are received from the base station on the second component carrier.

16. The apparatus according to claim 15, wherein, The at least some of the subsequent scheduling permission messages in the one or more subsequent scheduling permission messages include all subsequent scheduling permission messages.

17. The apparatus according to claim 15, wherein, The first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

18. A method for wireless communication, comprising: During a first time period, a first scheduling permission message is sent from the base station to the user equipment (UE) on the first component carrier, wherein the first scheduling permission message is a first downlink permission including a first channel state information (CSI) trigger indication for the UE; One or more subsequent scheduling permission messages are generated at the base station, wherein the transmission of the Physical Uplink Control Channel (PUCCH) associated with at least some of the scheduling permission messages overlaps with the transmission of CSI reports, and wherein the at least some of the scheduling permission messages include a CSI trigger indication, the CSI trigger indication being a copy of a first CSI trigger indication sent in the first scheduling permission message, wherein the one or more subsequent scheduling permission messages are one of a second downlink permission message or an uplink permission message; Sending one or more subsequent scheduling permission messages from the base station to the UE; and The base station receives the CSI report from the UE in response to the transmission of the first scheduling grant message and the one or more subsequent scheduling grant messages, wherein the base station receives no more than one CSI report from the UE during a single transmission opportunity.

19. The method according to claim 18, wherein, The first CSI trigger indication and the copy of the first CSI trigger indication each include a CSI trigger state, the CSI trigger state being identified by one or both of the CSI report settings or CSI reference signal (CSI-RS) resource settings used by the UE.

20. The method according to claim 18, wherein, At least some of the scheduling permission messages in the one or more subsequent scheduling permission messages are transmitted from the base station on the second component carrier.

21. The method according to claim 20, wherein, The at least some of the subsequent scheduling permission messages in the one or more subsequent scheduling permission messages include all subsequent scheduling permission messages.

22. The method according to claim 20, wherein, The first CSI trigger indication included in the first scheduling grant message triggers the CSI report on the PUCCH for the first component carrier on which the first scheduling grant message is received.

23. The method of claim 20, wherein, The first CSI trigger indication included in the first scheduling permission message triggers the CSI report on the PUCCH for at least the first component carrier and the second component carrier.

24. The method according to claim 18, wherein, The replication of the first CSI trigger indication is a single-bit trigger field included in one or more subsequent scheduling permission messages received from the base station.

25. The method according to claim 18, wherein, The one or more subsequent scheduling permission messages are the uplink permission messages.

26. The method according to claim 18, wherein, The individual transmission opportunity is a transmission time slot or sub-time slot.

27. An apparatus for wireless communication, comprising: At least one processor; as well as A memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations: During a first time period, a first scheduling permission message is sent from the base station to the user equipment (UE) on the first component carrier, wherein the first scheduling permission message is a first downlink permission including a first channel state information (CSI) trigger indication for the UE; One or more subsequent scheduling permission messages are generated at the base station, wherein the transmission of the Physical Uplink Control Channel (PUCCH) associated with at least some of the scheduling permission messages overlaps with the transmission of CSI reports, and wherein the at least some of the scheduling permission messages include a CSI trigger indication, the CSI trigger indication being a copy of a first CSI trigger indication sent in the first scheduling permission message, wherein the one or more subsequent scheduling permission messages are one of a second downlink permission message or an uplink permission message; Sending one or more subsequent scheduling permission messages from the base station to the UE; and The base station receives the CSI report from the UE in response to the transmission of the first scheduling grant message and the one or more subsequent scheduling grant messages, wherein the base station receives a single CSI report during a single transmission opportunity.

Images