Methods and apparatus for channel state information report configuration and generation
The novel CSI reporting framework via MAC-CE on PUSCH addresses inefficiencies in existing frameworks by decoupling report timing from UL resources, enhancing flexibility and reducing arbitration complexity, leading to improved network efficiency and throughput.
Patent Information
- Application Number
- PCT/CN2025/102696
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-12-19
- Filing Date
- 2025-06-23
- Publication Date
- 2026-01-29
AI Technical Summary
Existing CSI reporting frameworks in mobile communications, particularly in LTE, 5G, and emerging 6G networks, face inefficiencies due to complex UL channel arbitration when CSI reports are transmitted via UCI on UL control or data channels, necessitating dedicated resources and fixed reporting times.
A novel CSI reporting framework that transmits CSI reports via MAC-CE on the PUSCH, decoupling report triggering timing from UL resource allocation, and indicating report availability based on conditions such as periodicity, starting time offsets, or event-based triggers, allowing flexible resource utilization and simplified arbitration.
This approach reduces power consumption, simplifies UL channel arbitration, and enhances flexibility in resource allocation, improving network efficiency and throughput by allowing CSI reports to be transmitted only when conditions are met, thus optimizing data and CSI transmission.
Smart Images

Figure CN2025102696_29012026_PF_FP_ABST
Abstract
Description
METHODS AND APPARATUS FOR CHANNEL STATE INFORMATION REPORT CONFIGURATION AND GENERATIONCROSS REFERENCE TO RELATED PATENT APPLICATION (S)
[0001] The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63 / 674,333, filed 23 July 2024, U.S. Patent Application No. 63 / 674,336, filed 23 July 2024, U.S. Patent Application No. 63 / 674,337, filed 23 July 2024, U.S. Patent Application No. 63 / 695,868, filed 18 September 2024, and U.S. Patent Application No. 63 / 736,024, filed 19 December 2024, the contents of which herein being incorporated by reference in their entirety.TECHNICAL FIELD
[0002] The present disclosure is generally related to mobile communications and, more particularly, to methods and apparatus for Channel State Information (CSI) report configuration and generation in mobile communications.BACKGROUND
[0003] Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.
[0004] In mobile communications, CSI reporting is an essential mechanism that allows mobile devices, such as User Equipment (UE) , to provide feedback to the Base Station (BS) about the current communication environment. This information includes signal quality, interference conditions, and channel availability, enabling the BS to adjust transmission power, modulation, and coding strategies accordingly. It further optimizes beamforming, ensuring stable and efficient data transmission. CSI reporting allows the communication systems to dynamically adapt to environmental changes, such as user mobility or external interference, enhancing overall network reliability and throughput.
[0005] CSI reporting facilitates more efficient spectrum utilization, ensuring that limited wireless resources are optimally distributed and used. By providing precise channel information, the system can minimize unnecessary interference and enhance resource allocation, allowing multiple users to share the spectrum without compromising communication quality. This technology is particularly crucial in Long-Term Evolution (LTE) and 5th Generation (5G) networks, as well as the emerging 6th Generation (6G) networks, where higher data transmission speeds and lower latency demands require networks to be more flexible and efficient.
[0006] Accordingly, how to improve the CSI reporting efficiency is an important issue for the newly developed wireless communication network.SUMMARY
[0007] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
[0008] An objective of the present disclosure is to propose solutions or schemes that address the aforementioned issues pertaining to CSI report configuration and generation in mobile communications.
[0009] In one aspect, a method may involve an apparatus receiving a report configuration from a network node. The report configuration may indicate a condition that a CSI report shall be available for transmission. The method may further involve the apparatus generating the CSI report according to the condition such that the CSI report is available for transmission when the condition is fulfilled. The method may further involve the apparatus transmitting the CSI report on an uplink resource allocated by the network node.
[0010] In one aspect, a method may involve a network node transmitting a report configuration to an apparatus. The report configuration may indicate a condition that a CSI report shall be available for transmission. The method may further involve the network node receiving the CSI report on an uplink resource allocated to the apparatus.
[0011] It is noteworthy that, although description provided herein may be in the context of certain Radio Access Technologies (RATs) , networks and network topologies such as LTE, LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR) , Internet-of-Things (IoT) and Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , and 6G, the proposed concepts, schemes and any variation (s) / derivative (s) thereof may be implemented in, for and by other types of RATs, networks and network topologies. Thus, the scope of the present disclosure is not limited to the examples described herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.
[0013] FIG. 1 is a diagram depicting an example scenario of periodic report generation in accordance with an implementation of the present disclosure.
[0014] FIG. 2 is a diagram depicting an example scenario of semi-persistent report generation in accordance with an implementation of the present disclosure.
[0015] FIG. 3 is a diagram depicting an example scenario of aperiodic report generation in accordance with an implementation of the present disclosure.
[0016] FIG. 4 is a diagram depicting an example scenario of event-based report generation in accordance with an implementation of the present disclosure.
[0017] FIG. 5 is a diagram depicting differences between the periodic reporting in NR and the proposed periodic report generation in accordance with an implementation of the present disclosure.
[0018] FIG. 6 is a diagram depicting differences between the aperiodic reporting in NR and the proposed aperiodic report generation in accordance with an implementation of the present disclosure.
[0019] FIG. 7 is a diagram depicting an example communication system having an example communication apparatus and an example network apparatus in accordance with an implementation of the present disclosure.
[0020] FIG. 8 is a diagram depicting an example process in accordance with an implementation of the present disclosure.
[0021] FIG. 9 is a diagram depicting another example process in accordance with an implementation of the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
[0022] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview
[0023] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and / or solutions pertaining to CSI report configuration and generation. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
[0024] The CSI reporting mechanism is an important interactive process between the BS and UE. The BS may first transmit specific Reference Signals (RS) in the downlink, allowing the UE to assess the channel conditions. Based on the received RS, the UE may measure the current wireless channel quality and generate the reporting metrics, including Channel Quality Indicator (CQI) , Precoding Matrix Indicator (PMI) , Rank Indicator (RI) , and other relevant metrics such as Signal-to-Noise Ratio (SNR) . The UE may then report the CSI measurement results to the BS via the uplink. The reporting may be done periodically or aperiodically.
[0025] Upon receiving the CSI feedback from the UE, the BS may adjust transmission strategies, including modulation and coding schemes, beamforming, transmission power control, and other transmission optimization techniques, based on the reported CSI. The BS may then transmit signal or data to the UE according to the optimized transmission parameters, so as to improve the throughput and reduce error rates.
[0026] In the existing CSI reporting framework, such as the CSI reporting framework in NR, the CSI report is conveyed via an Uplink (UL) Control Information (UCI) . The CSI reporting via UCI requires a dedicated reporting resource indicated or configured by the BS. Therefore, the CSI report configuration in NR indicates the associated reporting resource configuration, and the reporting resource may include the UL control channel and / or the UL data channel.
[0027] However, CSI reporting via UCI on UL control channel or data channel involves complicated UL channel arbitration when the UE encounters simultaneous or overlapped control channel requirements, or simultaneous or overlapped control and data channel requirements. To solve this problem, a novel CSI reporting framework, including the CSI report configuration and generation, is provided.
[0028] In the proposed CSI reporting framework, CSI reporting is performed via a Medium Access Control (MAC) Control Element (MAC-CE) on a data channel, such as the Physical Uplink Shared Channel (PUSCH) . In an event that the CSI report is transmitted via MAC-CE on PUSCH, UL channel arbitration can be avoided or simplified.
[0029] In addition, in the proposed CSI reporting framework, a CSI report configuration may indicate at least an associated measurement RS resource configuration, one or more associated report triggering timings, and a report quantity. Different from the NR CSI reporting framework in which a dedicated reporting resource is indicated or configured by the BS in the CSI report configuration, in the proposed CSI reporting framework, the report triggering timing is indicated in the CSI report configuration.
[0030] Because the MAC-CE can be transmitted on any PUSCH when available, no dedicated UL resources have to be provided for each CSI report configuration. Therefore, in the proposed CSI reporting framework, the report triggering timing instead of the associated reporting resource configuration is indicated in the CSI report configuration.
[0031] In addition, unlike the NR CSI report framework, the timing of CSI report (s) generation can be decoupled from UL resource allocation. In the proposed CSI reporting framework, the report configuration indicates when the CSI report shall be available for transmission (for example, indicated via the report triggering timing) , while when the UE sends the generated CSI report (s) is determined according to the scheduling of available PUSCH (s) .
[0032] Notably, in the implementations of the proposed CSI reporting framework, the report triggering timing may comprise time domain information, and may indicate when the CSI report shall be available for transmission, when to generate the associated CSI report, or may indicate when the associated CSI report shall be provided or generated. In some implementations, the report triggering timing may indicate how the UE shall generate or provide the CSI report (s) in the time domain.
[0033] Specifically, in some implementations, an apparatus (e.g., the UE) may receive a report configuration from a network node, and generate a CSI report according to the report configuration. The UE may transmit the CSI report on an UL resource allocated by the network node.
[0034] In some implementations, the report configuration may indicate a condition that the CSI report is available for transmission. The CSI report shall be available for transmission when the condition is fulfilled. In some alternative implementations, the report configuration may indicate a condition that the CSI report is provided or generated, or a condition that the CSI report is prepared. The CSI report shall be provided, generated, or prepared when the condition is fulfilled.
[0035] In yet some implementations, the report configuration may indicate a condition of when the UE should generate the CSI report or when the UE should start to generate the CSI report. The UE shall generate or start to generate the CSI report when the condition is fulfilled.
[0036] In some implementations, the UE may further transmit an indication after the condition is fulfilled, and the indication may be an uplink sequence-based signal.
[0037] In some implementations, when the physical layer entity of the UE has completed the CSI report generation or preparation (that is, when the CSI report is available for transmission) , the CSI report is provided to the MAC entity of the UE and the CSI report can be transmitted when there is an available UL resource (e.g., the PUSCH) .
[0038] Regarding operations associated with the network node (e.g., the BS) , the BS may transmit the report configuration to the UE and receive a CSI report on an UL resource allocated to the UE. The report configuration may indicate a condition, and the CSI report shall be available for transmission when the condition is fulfilled.
[0039] Information regarding the aforementioned condition may be comprised in the aforementioned one or more associated report triggering timings indicated in the report configuration.
[0040] In some implementations, the condition may comprise a periodicity and a starting time offset (e.g., reporting offset) . For example, in an event that the CSI report configuration indicates periodic report triggering (or the reporting configuration type is configured as periodic reporting) , the condition may comprise a periodicity and a starting time offset. The periodicity and the starting time offset may define the time-domain occasions associated with CSI report generation. The UE may periodically generate or provide CSI report (s) at a certain timing derived based on the periodicity and the starting time offset. In some implementations, the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset. The CSI report (s) shall be available for transmission when the condition is fulfilled.
[0041] In some implementations, the condition may comprise a periodicity and a starting time offset (e.g., reporting offset) , and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset if the reporting configuration is activated via a command, such as an activation command. The CSI report (s) shall be available for transmission when the condition is fulfilled. For example, in an event that the CSI report configuration indicates semi-persistent report triggering (or the reporting configuration type is configured as semi-persistent reporting) , the condition may comprise a periodicity and a starting time offset. The periodicity and the starting time offset may define the time-domain occasions associated with CSI report generation. In response to the CSI report configuration being activated by the BS via the command, the UE may periodically generate or provide CSI report (s) at a certain timing derived based on the periodicity and the starting time offset. In some implementations, the command may be transmitted via MAC-CE or Downlink Control Information (DCI) .
[0042] In some implementations, the condition may comprise a time offset (e.g., reporting offset) , and the condition may be considered as fulfilled at a time that is the time offset after a command (such as a triggering command) triggering the report configuration is received. The CSI report (s) shall be available for transmission when the condition is fulfilled. For example, in an event that the CSI report configuration indicates aperiodic report triggering (or the reporting configuration type is configured as aperiodic reporting) , the condition may comprise a time offset after a command triggering the report configuration is received. The time offset may be defined or configured between the command (e.g., the triggering command) and aperiodic report.
[0043] For aperiodic reporting, the triggering command may comprise a DCI. The triggering command may comprise an UL DCI which indicates the UL resource or a downlink (DL) DCI. In response to the CSI report configuration being triggered by the BS, the UE may generate or provide CSI report (s) at a certain timing derived based on the time offset.
[0044] In some implementations, the condition may comprise a time offset (e.g., reporting offset) and an event, and the condition may be considered as fulfilled at a time that is the time offset after the event is met. The CSI report (s) shall be available for transmission when the condition is fulfilled. For example, in an event that the CSI report configuration indicates event-based triggering (or the reporting configuration type is configured as event-triggered reporting) , the condition may comprise a time offset and an event. The UE may generate or provide CSI report (s) at a certain timing derived based on the time offset in response to the determination that the event associated with the CSI report configuration has occurred. For example, after confirming that the event associated with the CSI report configuration has occurred and following the time offset, the CSI report shall be available for transmission.
[0045] In some implementations, the condition may comprise a periodicity, a starting time offset and an event, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset after the event is met. The CSI report (s) shall be available for transmission when the condition is fulfilled. For example, after confirming that the event associated with the CSI report configuration has occurred, the UE may periodically generate or provide CSI report (s) at a certain timing derived based on the periodicity and the starting time offset.
[0046] To summarize, regarding CSI reporting operations associated with the UE based on the proposed CSI reporting framework, the UE may measure the RS resource, and prepare or generate the CSI report with designated report quantity at the associated report triggering timing (s) , where the RS resource, the report quantity and the one or more associated report triggering timings may be configured by the BS in the received report configuration.
[0047] The RS resource may be DL RS scheduled via the DCI. For example, the scheduled DL RS may comprise a CSI-RS or a Demodulation Reference Signal (DMRS) . The report quantity may comprise Reference Signal Received Power (RSRP) , Signal-to-Interference-plus-Noise Ratio (SINR) or SNR, CQI, PMI, RI, or other relevant metrics.
[0048] FIG. 1 illustrates an example scenario 100 of periodic report generation in accordance with an implementation of the present disclosure. The UE may determine the time-domain occasions associated with CSI report generation based on the periodicity and the starting time offset configured by the BS as the information indicated by the report triggering timings in the report configuration, and may periodically or repeatedly perform the CSI report generation, such as the first, second and third CSI report generations along the time axis as depict in FIG. 1. The report triggering timings may comprise information regarding the aforementioned condition.
[0049] Assuming that a Configured-Grant (CG) PUSCH (CG-PUSCH) (e.g., the CG-PUSCH 101) is available for transmission after the UE completes the first CSI report generation, the UE may transmit the CSI report via the MAC-CE on the CG-PUSCH 101. In addition, the BS may also transmit an UL DCI and schedule a Dynamic-Grant (DG) PUSCH (DG-PUSCH) . Assuming that the DG-PUSCH 102 is available for transmission after the UE completes the third CSI report generation, the UE may transmit the CSI report via the MAC-CE on the DG-PUSCH 102.
[0050] In some implementations, the UE may drop the generated CSI report when there is no available UL resource within a duration (or when there is Sounding Reference Signal (SRS) transmission for CSI acquisition) . For example, when there is no available PUSCH within a duration after the UE completes the second CSI report generation as depicted in FIG. 1, the UE may drop the generated CSI report. That is, in exemplary scenario 100, the UE does not transmit the CSI report associated with the second CSI report generation to the BS.
[0051] FIG. 2 illustrates an example scenario 200 of semi-persistent report generation in accordance with an implementation of the present disclosure. The report configuration may be activated in response to an activation command received from the BS. The UE may determine the time-domain occasions associated with CSI report generation based on the periodicity and the starting time offset configured by the BS as the information indicated by the report triggering timings in the report configuration, and may periodically or repeatedly perform the CSI report generation, such as the first, second and third CSI report generations along the time axis as depict in FIG. 2. The report triggering timings may comprise information regarding the aforementioned condition.
[0052] Assuming that a CG-PUSCH 201 is available for transmission after the UE completes the first CSI report generation, the UE may transmit the CSI report via the MAC-CE on the CG-PUSCH 201. Assuming that there is no available PUSCH within a duration after the UE completes the second CSI report generation as depicted in FIG. 2, which may mean that the BS doesn’ t need CSI feedback from the UE at that time, and the UE may drop the generated CSI report. Assuming that a DG-PUSCH 202 is available for transmission after the UE completes the third CSI report generation, the UE may transmit the CSI report via the MAC-CE on the DG-PUSCH 202.
[0053] FIG. 3 illustrates an example scenario 300 of aperiodic report generation in accordance with an implementation of the present disclosure. The BS may transmit a triggering command, such as an UL DCI, to trigger CSI report generation for aperiodic reporting. The UL DCI may schedule a DL RS, such as the CSI-RS, and may also schedule or allocate an UL resource, such as the DG-PUSCH 301, for carrying the CSI report. The UE may determine the time-domain occasions associated with CSI report generation based on the time offset configured by the BS, as the information indicated by the report triggering timings in the report configuration, and may perform the associated CSI report generation according to the scheduled DL RS. The UE may transmit the CSI report via the MAC-CE on the DG-PUSCH 301. The report triggering timings may comprise information regarding the aforementioned condition.
[0054] The BS may also transmit a DL DCI as a triggering command to trigger CSI report generation for aperiodic reporting. In one example, the DL DCI may schedule a DL RS, such as the DMRS, but does not allocate any UCI resource or does not provide UL resource allocation for carrying the CSI report. The UE may transmit the CSI report via the MAC-CE on the CG-PUSCH 302 when the CG-PUSCH 302 is available for transmission after the UE completes the CSI report generation.
[0055] FIG. 4 illustrates an example scenario 400 of event-based report generation in accordance with an implementation of the present disclosure, where the CSI report generation is triggered by an event (i.e., report triggering by event) . For example, the UE may perform the associated CSI report generation in response to a determination that a predefined event condition associated with the CSI report configuration has been satisfied. Assuming that a CG-PUSCH 401 is available for transmission after the UE completes the CSI report generation, the UE may transmit the CSI report via the MAC-CE on the CG-PUSCH 401.
[0056] Alternatively, in an event that there is no available UL resource after the UE completes the CSI report generation, the UE may transmit an UL indication to the BS to notify of report triggering by event. In response to the UL indication, the BS may transmit an UL DCI to schedule or allocate an UL resource, such as the DG-PUSCH 402, for carrying the CSI report. The UE may transmit the CSI report via the MAC-CE on the DG-PUSCH 402.
[0057] FIG. 5 illustrates an example scenario 500 for depicting differences between the periodic reporting in NR and the proposed periodic report generation in accordance with an implementation of the present disclosure. Regarding the periodic reporting in NR, the CSI report is periodically transmitted on the Physical Uplink Control Channel (PUCCH) . The CSI report timing will be fixed in the periodic reporting in NR. In addition, in NR, when the UE starts the CSI computation of the CSI report is up to UE implementation, and when the reporting resource will present is explicitly indicated or configured by the network (e.g., the BS) .
[0058] Regarding the periodic reporting under the proposed CSI reporting framework, the CSI report may be periodically generated, but the CSI report timing does not have to be fixed. In addition, in the proposed CSI reporting framework, the CSI report can be transmitted on the CG-PUSCH or DG-PUSCH. In addition, in the proposed CSI reporting framework, the CSI report can be dropped, skipped or cancelled if there is no available UL resource or there is no DL traffic, or if there is SRS transmission.
[0059] FIG. 6 illustrates an example scenario 600 for depicting differences between the aperiodic reporting in NR and the proposed aperiodic report generation in accordance with an implementation of the present disclosure. Similar to the aperiodic reporting in NR, in the proposed aperiodic reporting, the UE may receive an UL DCI from the BS. The UL DCI may schedule a DL RS, such as the CSI-RS, and schedule or allocate an UL resource, such as the DG-PUSCH, for carrying the CSI report. In the proposed aperiodic reporting, the UL DCI may trigger the CSI report generation. The UE may determine the time-domain occasions associated with CSI report generation based on the time offset configured by the BS in the report configuration, and may perform the associated CSI report generation according to the scheduled DL RS. The UE may transmit the CSI report via the MAC-CE on the DG-PUSCH.
[0060] Different from the aperiodic reporting in NR, in the proposed CSI reporting framework, the aperiodic reporting may be triggered by DL DCI. For example, the CSI report generation may be triggered by DL DCI for DMRS-based CSI acquisition. The DL DCI may schedule a PDSCH with DMRS, which is considered as the measurement resource for the CSI report. After completing the CSI report generation, the UE may transmit the CSI report via the MAC-CE on the CG-PUSCH when the CG-PDSCH is available for transmission, or may transmit the CSI report via the MAC-CE on the DG-PUSCH when the DG-PDSCH is available. Therefore, in the proposed aperiodic reporting, the triggering DCI (such as the UL DCI depicted in FIG. 6) may allocate UL resource for carrying the CSI report, and the triggering DCI (such as the DL DCI depicted in FIG. 6) may also not provide UL resource allocation for carrying the CSI report.
[0061] Based on the proposed CSI reporting framework, more flexibility for UL resource allocation is achieved. The BS doesn’ t need to consider UL resource allocation individually for data transmission and for CSI report transmission, and the aggregation of data and CSI report in one UL transmission becomes much easier. Both provide benefits to the BS operation.
[0062] In addition, UE’s power consumption can be reduced due to no individual UL transmissions for data and CSI report, and UL channel arbitration can be avoided or simplified. Therefore, the proposed CSI reporting framework also provides benefits to the UE. Illustrative Implementations
[0063] FIG. 7 illustrates an example communication system 700 having an example communication apparatus 710 and an example network apparatus 720 in accordance with an implementation of the present disclosure. Each of the communication apparatus 710 and the network apparatus 720 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to CSI report configuration and generation, including scenarios / schemes described above as well as the process 800 and the process 900 described below.
[0064] The communication apparatus 710 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, the communication apparatus 710 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. The communication apparatus 710 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, or IIoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, the communication apparatus 710 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. Alternatively, the communication apparatus 710 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. The communication apparatus 710 may include at least some of those components shown in FIG. 7 such as a processor 712, for example. The communication apparatus 710 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of the communication apparatus 710 are neither shown in FIG. 7 nor described below in the interest of simplicity and brevity.
[0065] The network apparatus 720 may be a part of an electronic apparatus, which may be a network node such as a satellite, a BS, a small cell, a router, or a gateway of a 4G / 5G / B5G / 6G, NR, IoT, NB-IoT or IIoT network. Alternatively, the network apparatus 720 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. The network apparatus 720 may include at least some of those components shown in FIG. 7 such as a processor 722, for example. The network apparatus 720 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of the network apparatus 720 are neither shown in FIG. 7 nor described below in the interest of simplicity and brevity.
[0066] In one aspect, each of the processor 712 and the processor 722 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “aprocessor” is used herein to refer to the processor 712 and the processor 722, each of the processor 712 and the processor 722 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of the processor 712 and the processor 722 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of the processor 712 and the processor 722 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks in accordance with various implementations of the present disclosure.
[0067] In some implementations, the communication apparatus 710 may also include a transceiver 716 coupled to the processor 712 and capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 716 may be capable of wirelessly communicating with different types of UEs and / or wireless networks of different RATs. In some implementations, the transceiver 716 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, the transceiver 716 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, the network apparatus 720 may also include a transceiver 726 coupled to the processor 722 and capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 726 may be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations, the transceiver 726 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 726 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.
[0068] In some implementations, the communication apparatus 710 may further include a memory 714 coupled to the processor 712 and capable of being accessed by the processor 712 and storing data therein. In some implementations, the network apparatus 720 may further include a memory 724 coupled to the processor 722 and capable of being accessed by the processor 722 and storing data therein. Each of the memory 714 and the memory 724 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of the memory 714 and the memory 724 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of the memory 714 and the memory 724 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and / or phase-change memory.
[0069] Each of the communication apparatus 710 and the network apparatus 720 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of the communication apparatus 710, as a UE, and the network apparatus 720, as a network node, is provided below with the processes 800 and 900. Illustrative Processes
[0070] FIG. 8 illustrates an example process 800 in accordance with an implementation of the present disclosure. The process 800 may be an example implementation of above scenarios / schemes, whether partially or completely, including those described above with respect to CSI report configuration and generation. The process 800 may represent an aspect of implementation of features of the communication apparatus 710. The process 800 may include one or more operations, actions, or functions as illustrated by one or more of blocks 810, 820 and 830. Although illustrated as discrete blocks, various blocks of the process 800 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of the process 800 may be executed in the order shown in FIG. 8 or, alternatively, in a different order. The process 800 may be implemented by or in the communication apparatus 710 or any suitable UE or machine type device. Solely for illustrative purposes and without limiting the scope, the process 800 is described below in the context of the communication apparatus 710, as a UE, and the network apparatus 720, as a network node (e.g., a BS such as gNB) . Process 800 may begin at block 810.
[0071] At block 810, the process 800 may involve the processor 712 of the communication apparatus 710 receiving a report configuration from the network apparatus 720. The report configuration may indicate a condition. A CSI report shall be available for transmission when the condition is fulfilled. The process 800 may proceed from block 810 to block 820.
[0072] At block 820, the process 800 may involve the processor 712 generating the CSI report according to the condition. The process 800 may proceed from block 820 to block 830.
[0073] At block 830, the process 800 may involve the processor 712 transmitting the CSI report on an UL resource allocated by the network apparatus 720.
[0074] In some implementations, the condition may comprise a periodicity and a starting time offset, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset.
[0075] In some implementations, the condition may comprise a periodicity and a starting time offset, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset if the reporting configuration is activated via a command.
[0076] In some implementations, the condition may comprise a time offset, and the condition may be considered as fulfilled at a time that is the time offset after a command triggering the report configuration is received.
[0077] In some implementations, the command triggering the report configuration may comprise a DCI.
[0078] In some implementations, the command triggering the report configuration may comprise a DCI which indicates the UL resource.
[0079] In some implementations, the condition may comprise a time offset and an event, and the condition may be considered as fulfilled at a time that is the time offset after the event is met.
[0080] In some implementations, the condition may comprise a periodicity, a starting time offset and an event, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset after the event is met.
[0081] In some implementations, the indication may be an uplink sequence-based signal.
[0082] In some implementations, the process 800 may involve the processor 712 transmitting an indication after the condition is fulfilled.
[0083] FIG. 9 depicting an example process 900 in accordance with an implementation of the present disclosure. The process 900 may be an example implementation of above scenarios / schemes, whether partially or completely, including those described above with respect to CSI report configuration and generation. The process 900 may represent an aspect of implementation of features of the network apparatus 720. The process 900 may include one or more operations, actions, or functions as illustrated by one or more of blocks 910 and 920. Although illustrated as discrete blocks, various blocks of the process 900 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of the process 900 may be executed in the order shown in FIG. 9 or, alternatively, in a different order. The process 900 may be implemented by or in the network apparatus 720 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 900 is described below in the context of the communication apparatus 710, as a UE, and the network apparatus 720, as a network node (e.g., a BS such as gNB) . Process 900 may begin at block 910.
[0084] At block 910, the process 900 may involve the processor 722 of the network apparatus 720 transmitting a report configuration to the communication apparatus 710. The report configuration may indicate a condition. A CSI report shall be available for transmission when the condition is fulfilled. The process 900 may proceed from block 910 to block 920.
[0085] At block 920, the process 900 may involve the processor 722 receiving the CSI report on an UL resource allocated to the communication apparatus 710.
[0086] In some implementations, the condition may comprise a periodicity and a starting time offset, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset.
[0087] In some implementations, the condition may comprise a periodicity and a starting time offset, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset if the reporting configuration is activated via a command.
[0088] In some implementations, the condition may comprise a time offset, and the condition may be considered as fulfilled at a time that is the time offset after a command triggering the report configuration is received by the communication apparatus 710.
[0089] In some implementations, the command triggering the report configuration may comprise a DCI.
[0090] In some implementations, the command triggering the report configuration may comprise a DCI which indicates the UL resource.
[0091] In some implementations, the condition may comprise a time offset and an event, and the condition may be considered as fulfilled at a time that is the time offset after the event is met.
[0092] In some implementations, the condition may comprise a periodicity, a starting time offset and an event, and the condition may be considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset after the event is met.
[0093] In some implementations, the process 900 may involve the processor 722 receiving an indication from the communication apparatus 710 after the condition is fulfilled.
[0094] In some implementations, the indication may be an uplink sequence-based signal. Additional Notes
[0095] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.
[0096] Further, with respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.
[0097] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”
[0098] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
1.A method, comprising:receiving, by a processor of an apparatus, a report configuration from a network node, wherein the report configuration indicates a condition, and wherein a channel state information (CSI) report shall be available for transmission when the condition is fulfilled;generating, by the processor, the CSI report according to the condition; andtransmitting, by the processor, the CSI report on an uplink (UL) resource allocated by the network node.2.The method of Claim 1, wherein the condition comprises a periodicity and a starting time offset, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset.3.The method of Claim 1, wherein the condition comprises a periodicity and a starting time offset, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset if the reporting configuration is activated via a command.4.The method of Claim 1, wherein the condition comprises a time offset, and the condition is considered as fulfilled at a time that is the time offset after a command triggering the report configuration is received.5.The method of Claim 1, wherein the condition comprises a time offset and an event, and the condition is considered as fulfilled at a time that is the time offset after the event is met.6.The method of Claim 1, wherein the condition comprises a periodicity, a starting time offset and an event, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset after the event is met.7.The method of Claim 1, further comprising:transmitting, by the processor, an indication after the condition is fulfilled.8.The method of Claim 4, wherein the command triggering the report configuration comprises a downlink control information (DCI) .9.The method of Claim 4, wherein the command triggering the report configuration comprises a downlink control information (DCI) which indicates the UL resource.10.The method of Claim 7, wherein the indication is an uplink sequence-based signal.11.A method, comprising:transmitting, by a processor of a network node, a report configuration to an apparatus, wherein the report configuration indicates a condition, and wherein a channel state information (CSI) report shall be available for transmission when the condition is fulfilled; andreceiving, by the processor, the CSI report on an uplink (UL) resource allocated to the apparatus.12.The method of Claim 11, wherein the condition comprises a periodicity and a starting time offset, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset.13.The method of Claim 11, wherein the condition comprises a periodicity and a starting time offset, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset if the reporting configuration is activated via a command.14.The method of Claim 11, wherein the condition comprises a time offset, and the condition is considered as fulfilled at a time that is the time offset after a command triggering the report configuration is received by the apparatus.15.The method of Claim 11, wherein the condition comprises a time offset and an event, and the condition is considered as fulfilled at a time that is the time offset after the event is met.16.The method of Claim 11, wherein the condition comprises a periodicity, a starting time offset and an event, and the condition is considered as fulfilled at a time that is equal to a sum of a multiple of the periodicity and the starting time offset after the event is met.17.The method of Claim 11, further comprising:receiving, by the processor, an indication from the apparatus after the condition is fulfilled.18.The method of Claim 14, wherein the command triggering the report configuration comprises a downlink control information (DCI) .19.The method of Claim 14, wherein the command triggering the report configuration comprises a downlink control information (DCI) which indicates the UL resource.20.The method of Claim 17, wherein the indication is an uplink sequence-based signal.
Citation Information
Patent Citations
Information reporting method and terminal
CN114501485A
Channel state information triggering for uplink dominated traffic
CN114651467A
Channel state information (CSI) reporting method and device and storage medium
CN114731532A
Channel state information reporting method, user equipment, base station and computer readable medium
CN117395782A
Method for transmitting and receiving uplink channel in wireless communication system and device therefor
US20200178220A1