Method and apparatus for csi reporting configuration and generation

Abstract

Methods and apparatuses related to channel state information (CSI) reporting configuration and generation in mobile communications are described. An apparatus can receive a reporting configuration from a network node. The reporting configuration can indicate a condition that, when satisfied, a CSI report should be ready for transmission. The apparatus can generate a CSI report in accordance with the condition and transmit the CSI report on uplink (UL) resources allocated by the network node.

Description

[0001] Cross-referencing

[0002] This disclosure is a non-provisional application and claims priority to U.S. Patent Application No. 63 / 674,333 (filed July 23, 2024), U.S. Patent Application No. 63 / 674,336 (filed July 23, 2024), U.S. Patent Application No. 63 / 674,337 (filed July 23, 2024), U.S. Patent Application No. 63 / 695,868 (filed September 18, 2024), and U.S. Patent Application No. 63 / 736,024 (filed December 19, 2024), the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to a method and apparatus for configuring and generating Channel State Information (CSI) reports in mobile communications. Background Technology

[0004] Unless otherwise indicated herein, the methods described in this section are not prior art to the following claims and are not acknowledged as prior art by virtue of being included in this section.

[0005] In mobile communications, Channel State Information (CSI) reporting is a crucial mechanism that allows mobile devices, such as User Equipment (UE), to report the current communication environment to the Base Station (BS). 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 to ensure stable and efficient data transmission. CSI reporting allows communication systems to dynamically adapt to environmental changes, such as user mobility or external interference, thereby improving overall network reliability and throughput.

[0006] CSI reports facilitate more efficient spectrum utilization, ensuring that limited radio resources are optimally allocated and used. By providing accurate channel information, systems can minimize unnecessary interference and improve resource allocation, enabling multiple users to share spectrum without compromising communication quality. This technology is particularly important in Long Term Evolution (LTE) and 5G networks, as well as emerging 6G networks, where higher data transmission rates and lower latency requirements necessitate greater network flexibility and efficiency.

[0007] Therefore, improving CSI reporting efficiency is an important issue in newly developed wireless communication networks. Summary of the Invention

[0008] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the summary aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] One objective of this disclosure is to propose a solution or approach to address the aforementioned problems related to the configuration and generation of Channel State Information (CSI) reports in mobile communications.

[0010] In one aspect, a method may include means receiving a report configuration from a network node. The report configuration may indicate a condition that a Channel State Information (CSI) report should be ready for transmission. The method may further include means generating a CSI report based on the condition, such that when the condition is met, the CSI report is ready for transmission. The method may also involve means transmitting the CSI report on uplink resources allocated by the network node.

[0011] In one aspect, a method may involve a network node sending a report configuration to a device. This report configuration may indicate a condition that a Channel State Information (CSI) report should be ready for transmission. The method may also include the network node receiving the CSI report on uplink resources allocated to the device.

[0012] It is worth noting that although the content described herein may be set 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), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), and 6G, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of RATs, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0013] The accompanying drawings are included in this specification to further understand this disclosure and form part of this disclosure. The drawings illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of this disclosure.

[0014] Figure 1 This is a schematic diagram illustrating an example scenario of periodic report generation according to an implementation of this disclosure.

[0015] Figure 2 This is a schematic diagram illustrating an example scenario for generating semi-persistent reports according to an implementation of this disclosure.

[0016] Figure 3 This is a schematic diagram illustrating an example scenario of non-periodic report generation according to an implementation of this disclosure.

[0017] Figure 4 This is a schematic diagram illustrating an example scenario of event-based report generation according to an implementation of this disclosure.

[0018] Figure 5 This is a schematic diagram illustrating the difference between periodic reports in NR and the proposed periodic report generation, according to an implementation of this disclosure.

[0019] Figure 6 This is a schematic diagram illustrating the difference between aperiodic reporting in NR and the proposed aperiodic reporting generation, according to an implementation of this disclosure.

[0020] Figure 7 This is a schematic diagram of an example communication system having an example communication device and an example network device, described in accordance with embodiments of the present disclosure.

[0021] Figure 8 A schematic diagram illustrating an example process is provided to illustrate an implementation of this disclosure.

[0022] Figure 9 This is a schematic diagram illustrating another example process for implementing the present disclosure. Detailed Implementation

[0023] Detailed embodiments and implementations of the subject matter of the claims are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the subject matter of the claims and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure exhaustive and complete, and to adequately convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0024] Overview

[0025] Implementations of this disclosure relate to various techniques, methods, schemes, and / or solutions related to the configuration and generation of Channel State Information (CSI) reports. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more solutions can be implemented in some combination.

[0026] The CSI reporting mechanism is a crucial interaction process between the base station (BS) and the user equipment (UE). The base station first transmits a specific reference signal (RS) in the downlink, allowing the UE to assess channel conditions. Based on the received reference signal, the UE measures the current radio channel quality and generates report metrics, including the Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and other relevant metrics such as Signal-to-Noise Ratio (SNR). The UE then reports the CSI measurement results to the base station via the uplink. This reporting can be periodic or non-periodic.

[0027] After receiving CSI feedback from user equipment, the base station can adjust its transmission strategy based on the reported CSI, including modulation and coding schemes, beamforming, transmission power control, and other transmission optimization techniques. The base station can then send signals or data to the user equipment according to the optimized transmission parameters to improve throughput and reduce bit error rate.

[0028] In existing CSI reporting frameworks, such as the CSI reporting framework in NR, CSI reports are transmitted via uplink (UL) control information (UCI). Reporting CSI via UCI requires the base station to indicate or configure dedicated reporting resources. Therefore, the CSI reporting configuration in NR indicates the relevant reporting resource configuration, which may include uplink control channels and / or uplink data channels.

[0029] However, when user equipment encounters simultaneous or overlapping control channel requirements, or simultaneous or overlapping control and data channel requirements, CSI reporting via UCI on the uplink control or data channel involves complex uplink channel arbitration. To address this issue, a novel CSI reporting framework is proposed, encompassing CSI report configuration and generation.

[0030] In the proposed CSI reporting framework, CSI reports are made on the data channel via a Media Access Control (MAC) element (MAC-CE), such as the Physical Uplink Shared Channel (PUSCH). When CSI reports are transmitted on the PUSCH via the MAC-CE, uplink channel arbitration can be avoided or simplified.

[0031] Furthermore, in the proposed CSI reporting framework, the CSI reporting configuration can indicate at least one associated measurement reference signal resource configuration, one or more associated report triggering times, and the number of reports. Unlike the NR CSI reporting framework where the base station indicates or configures dedicated reporting resources in the CSI reporting configuration, in the proposed CSI reporting framework, the report triggering time is indicated in the CSI reporting configuration.

[0032] Since MAC-CE can be transmitted on any available PUSCH, there is no need to provide dedicated uplink resources for each CSI report configuration. Therefore, in the proposed CSI reporting framework, the CSI report configuration indicates the timing of the report triggering, rather than the associated report resource configuration.

[0033] Furthermore, unlike the NR CSI reporting framework, the timing of CSI report generation can be decoupled from uplink resource allocation. In the proposed CSI reporting framework, the report configuration indicates when the CSI report should be available for transmission (e.g., through a report trigger timing indication), while when the user equipment sends the generated CSI report is determined based on the scheduling of available PUSCH.

[0034] It is worth noting that, in the implementation of the proposed CSI reporting framework, the report triggering timing may include time-domain information and may indicate when a CSI report should be available for transmission, when a relevant CSI report should be generated, or when a relevant CSI report should be provided or generated. In some implementations, the report triggering timing may indicate how the user equipment should generate or provide a CSI report in the time domain.

[0035] Specifically, in some implementations, an apparatus (e.g., a user equipment) may receive a report configuration from a network node and generate a CSI report based on the report configuration. The user equipment may then transmit the CSI report on uplink resources allocated by the network node.

[0036] In some implementations, the report configuration may indicate the conditions under which a CSI report is available for transmission. When these conditions are met, the CSI report should be available for transmission. In some alternative implementations, the report configuration may indicate the conditions under which a CSI report is provided or generated, or the conditions under which a CSI report is prepared. When these conditions are met, the CSI report should be provided, generated, or prepared.

[0037] In other implementations, the reporting configuration may indicate when the user equipment should generate a CSI report or the conditions under which CSI report generation should begin. When these conditions are met, the user equipment should generate or begin generating a CSI report.

[0038] In some implementations, the user equipment may also send an indication message, which is a signal based on the uplink sequence, after the condition is met.

[0039] In some implementations, when the physical layer entity of the user equipment completes the generation or preparation of the CSI report (i.e., when the CSI report is available for transmission), the CSI report is provided to the MAC entity of the user equipment and can be transmitted when there are available uplink resources (e.g., PUSCH).

[0040] Regarding operations related to network nodes (e.g., base stations), base stations may send report configurations to user equipment and receive CSI reports on uplink resources allocated to user equipment. The report configuration may indicate a condition, and when that condition is met, the CSI report should be available for transmission.

[0041] Information regarding the above conditions may be included in one or more relevant report triggering times indicated in the report configuration.

[0042] In some implementations, the condition may include a period value and a start time offset (e.g., a report offset). For example, the condition may include a period value and a start time offset when the CSI report configuration indicates that periodic reporting is triggered (or the report configuration type is configured for periodic reporting). The period value and start time offset define the time-domain timing associated with CSI report generation. The user equipment may periodically generate or provide CSI reports at specific times derived from the period value and start time offset. In some implementations, the condition may be considered satisfied when the time equals the sum of a multiple of the period value and the start time offset. When this condition is satisfied, the CSI report should be available for transmission.

[0043] In some implementations, the condition may include a period value and a start time offset (e.g., a report offset), and if the reporting configuration is activated by a command (such as an activation command), the condition is considered satisfied when the time equals a multiple of the period value plus the start time offset. Channel State Information (CSI) reports should be ready for transmission when the condition is satisfied. For example, the condition may include a period value and a start time offset if the CSI report configuration indicates semi-persistent report triggering (or the report configuration type is configured as semi-persistent reporting). The period value and start time offset can define the time-domain timing associated with CSI report generation. In response to the base station (BS) activating the CSI report configuration by a command, the user equipment (UE) can periodically generate or provide CSI reports at certain times based on the period value and start time offset. In some implementations, this command may be transmitted via a MAC control element (MAC-CE) or downlink control information (DCI).

[0044] In some implementations, the condition may include a time offset (e.g., a reporting offset), and the condition is considered satisfied after a time offset has elapsed since receiving a command to trigger the reporting configuration (e.g., a trigger command). Channel State Information (CSI) reports should be ready for transmission when the condition is satisfied. For example, in cases where the CSI reporting configuration indicates aperiodic reporting triggering (or the reporting configuration type is configured for aperiodic reporting), the condition may include a time offset elapsed since receiving the command to trigger the reporting configuration. This time offset may be defined or configured between the command (e.g., the trigger command) and the aperiodic report.

[0045] For non-periodic reporting, the triggering command may include downlink control information (DCI). The triggering command may include a UL DCI indicating uplink (UL) resources or a downlink (DL) DCI. In response to a base station (BS) triggering CSI reporting configuration, a user equipment (UE) may generate or provide a CSI report at a specific time based on a time offset.

[0046] In some implementations, the condition may include a time offset (e.g., a reporting offset) and an event, and the condition is considered satisfied after a time offset has elapsed following the satisfaction of the event. A Channel State Information (CSI) report should be ready for transmission when the condition is satisfied. For example, if the CSI report configuration indicates event-triggered reporting (or the report configuration type is configured for event-triggered reporting), the condition may include a time offset and an event. The User Equipment (UE) may generate or provide a CSI report at a specific time based on the time offset after determining that an event related to the CSI report configuration has occurred. For example, the CSI report should be ready for transmission after the time offset has elapsed following confirmation that an event related to the CSI report configuration has occurred.

[0047] In some implementations, the condition may include a period value, a start time offset, and an event, and the condition is considered satisfied when the event is met, and the time is equal to the sum of a multiple of the period value and the start time offset. Channel State Information (CSI) reports should be ready for transmission when the condition is met. For example, after confirming the occurrence of an event related to CSI report configuration, the User Equipment (UE) may periodically generate or provide CSI reports at certain times based on the period value and the start time offset.

[0048] In summary, regarding CSI reporting operations related to user equipment (UE) based on the proposed CSI reporting framework, the user equipment (UE) can measure reference signal (RS) resources and prepare or generate a specified number of CSI reports at relevant report triggering times, wherein the reference signal (RS) resources, the number of reports, and one or more relevant report triggering times can be configured by the base station (BS) in the received report configuration.

[0049] Reference signal (RS) resources can be downlink reference signals (DL RS) scheduled via downlink control information (DCI). For example, the scheduled downlink reference signals may include CSI reference signals (CSI-RS) or demodulation reference signals (DMRS). Reported quantities may include reference signal received power (RSRP), signal-to-interference-plus-noise ratio (SINR) or signal-to-noise ratio (SNR), channel quality indicator (CQI), precoding matrix indicator (PMI), ranking indicator (RI), or other relevant metrics.

[0050] Figure 1An example scenario 100 of periodic report generation according to an embodiment of this disclosure is illustrated. A user equipment (UE) can determine the time-domain timing associated with CSI report generation based on the period value and start time offset configured by the base station (BS), as information indicated by the report triggering timing in the report configuration, and can perform CSI report generation periodically or repeatedly, such as... Figure 1 The first, second, and third CSI reports are generated along the timeline, as shown. The timing of the report triggering may include information about the conditions mentioned above.

[0051] Assuming that after the User Equipment (UE) completes the generation of the first CSI report, the Configured-Grant (CG) Physical Uplink Shared Channel (PUSCH) (e.g., CG-PUSCH 101) is available for transmission, the UE can transmit the CSI report on CG-PUSCH 101 via the MAC Control Element (MAC-CE). Furthermore, the Base Station (BS) can also send Uplink Control Information (UL DCI) and schedule Dynamic-Grant (DG) PUSCH (DG-PUSCH). Assuming that after the UE completes the generation of the third CSI report, DG-PUSCH 102 is available for transmission, the UE can transmit the CSI report on DG-PUSCH 102 via the MAC Control Element (MAC-CE).

[0052] In some implementations, a user equipment (UE) may discard a generated CSI report when no uplink (UL) resources are available for a given period of time (or when a sounding reference signal (SRS) transmission for CSI acquisition is present). For example, such as Figure 1 As shown, after the User Equipment (UE) completes the generation of the second CSI report, if no PUSCH is available for a certain period of time, the UE may discard the generated CSI report. That is, in example scenario 100, the UE will not transmit the CSI report related to the generation of the second CSI report to the base station (BS).

[0053] Figure 2 An example scenario 200 of semi-persistent report generation according to an embodiment of this disclosure is illustrated. The report configuration can be activated upon receiving an activation command from the base station (BS). The user equipment (UE) can determine the time-domain timing associated with CSI report generation based on the period value and start time offset configured by the base station (BS), as information indicated by the report triggering timing in the report configuration, and can perform CSI report generation periodically or repeatedly, such as... Figure 2The first, second, and third CSI reports are generated along the timeline, as shown. The timing of the report triggering may include information about the conditions mentioned above.

[0054] Assuming that CG-PUSCH 201 is available for transmission after the User Equipment (UE) completes the generation of the first CSI report, the UE can transmit the CSI report on CG-PUSCH 201 via the MAC Control Element (MAC-CE). Assuming that after the UE completes the generation of the second CSI report, no PUSCH is available for a specified period, such as... Figure 2 As shown, this may mean that the base station (BS) does not need CSI feedback from the user equipment (UE) at this moment, and the user equipment (UE) can discard the generated CSI report. Assuming that DG-PUSCH 202 can be used for transmission after the user equipment (UE) completes the generation of the third CSI report, the user equipment (UE) can transmit the CSI report on DG-PUSCH 202 through the MAC control element (MAC-CE).

[0055] Figure 3 An example scenario 300 of non-periodic report generation according to an embodiment of this disclosure is illustrated. A base station (BS) can send a trigger command, such as uplink control information (UL DCI), to trigger the generation of a channel state information (CSI) report for non-periodic reporting. The UL DCI can schedule downlink reference signals (DL RS), such as CSI reference signals (CSI-RS), and can also schedule or allocate uplink resources, such as group scheduling of the physical uplink shared channel (DG-PUSCH) 301 for carrying CSI reports. A user equipment (UE) can determine the time-domain timing associated with CSI report generation based on the time offset configured by the base station, as indicated by the report trigger timing in the report configuration, and can perform the associated CSI report generation according to the scheduled DLRS. The UE can send the CSI report on DG-PUSCH 301 via a MAC control element (MAC-CE). The report trigger timing may include information about the above conditions.

[0056] The base station can also send downlink control information (DL DCI) as a trigger command to trigger CSI report generation for non-periodic reporting. In one example, the DL DCI may schedule downlink reference signals (DL RS), such as demodulation reference signals (DMRS), but not allocate any uplink control information (UCI) resources or provide uplink resource allocation for carrying CSI reports. The UE can send CSI reports on CG-PUSCH 302 via MAC-CE after CSI report generation is complete, provided that CG-PUSCH 302 is available for transmission.

[0057] Figure 4 An example scenario 400 of event-based report generation according to an embodiment of this disclosure is illustrated, where CSI report generation is triggered by an event (i.e., event-triggered reporting). For example, the UE can perform relevant CSI report generation when it determines that predefined event conditions related to CSI report configuration have been met. Assuming that CG-PUSCH 401 is available for transmission after the UE completes CSI report generation, the UE can send the CSI report on CG-PUSCH 401 via MAC-CE.

[0058] Alternatively, if no uplink resources are available after the UE completes CSI report generation, the UE can send an uplink indication message to the base station to notify the event-triggered report. In response to this uplink indication message, the base station can send a UL DCI to schedule or allocate uplink resources, such as DG-PUSCH 402, for carrying the CSI report. The UE can send the CSI report on DG-PUSCH 402 via MAC-CE.

[0059] Figure 5 An example scenario 500 is illustrated to describe the difference between periodic reporting in NR and the periodic reporting generation proposed according to embodiments of this disclosure. Regarding periodic reporting in NR, CSI reports are periodically transmitted on the Physical Uplink Control Channel (PUCCH). The timing of CSI reports is fixed in NR periodic reporting. Furthermore, in NR, when the UE initiates CSI calculations for CSI reporting depends on the UE's implementation, and when reporting resources become available is explicitly indicated or configured by the network (e.g., a base station).

[0060] Regarding periodic reporting under the proposed CSI reporting framework, CSI reports can be generated periodically, but the timing of CSI reporting does not need to be fixed. Furthermore, in the proposed CSI reporting framework, CSI reports can be transmitted on either CG-PUSCH or DG-PUSCH. Additionally, in the proposed CSI reporting framework, if there are no available uplink resources or downlink traffic, or if SRS transmission is present, CSI reports can be discarded, skipped, or canceled.

[0061] Figure 6An example scenario 600 is illustrated to describe the difference between aperiodic reporting in NR and aperiodic reporting generation proposed according to embodiments of this disclosure. Similar to aperiodic reporting in NR, in a proposed aperiodic report, the UE can receive a UL DCI from the base station. The UL DCI can schedule downlink reference signals (DL RS), such as CSI-RS, and schedule or allocate uplink resources, such as DG-PUSCH, to carry CSI reports. In a proposed aperiodic report, the ULDCI can trigger CSI report generation. The UE can determine the time-domain timing associated with CSI report generation based on the time offset configured by the base station in the report configuration, and can perform the associated CSI report generation based on the scheduled DL RS. The UE can transmit the CSI report on the DG-PUSCH via MAC-CE.

[0062] Unlike aperiodic reporting in NR, aperiodic reporting in the proposed CSI reporting framework can be triggered by DLDCI. For example, CSI report generation can be triggered by DL DCI for DMRS-based CSI acquisition. DL DCI can schedule the Physical Downlink Shared Channel (PDSCH) with DMRS, which is considered the measurement resource for CSI reporting. After CSI report generation is complete, the UE can transmit the CSI report on the CG-PUSCH via MAC-CE when the CG-PDSCH is available, or on the DG-PUSCH via MAC-CE when the DG-PDSCH is available. Therefore, in the proposed aperiodic reporting, triggering DCI (such as...) Figure 6 The UL DCI shown can allocate uplink resources for carrying CSI reports, while triggering the DCI (such as...) Figure 6 The DL DCI shown may also not provide uplink resource allocation for carrying CSI reports.

[0063] Based on the proposed CSI reporting framework, more flexible uplink resource allocation is achieved. Base stations no longer need to separately consider uplink resource allocation for data transmission and CSI report transmission, making the aggregation of data and CSI reports within a single uplink transmission easier. Both bring benefits to base station operation.

[0064] Furthermore, since data and CSI reports do not need to be transmitted separately via the uplink, UE power consumption can be reduced, and uplink channel arbitration can be avoided or simplified. Therefore, the proposed CSI reporting framework also benefits the UE.

[0065] Example Implementation

[0066] Figure 7An example communication system 700 according to an embodiment of this disclosure is shown, including an example communication device 710 and an example network device 720. Both the communication device 710 and the network device 720 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to CSI report configuration and generation, including the scenarios / schemes described above and processes 800 and 900 described below.

[0067] The communication device 710 may be part of an electronic device, which may be a user equipment (UE), such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 710 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device (such as a tablet, laptop, or mobile phone). The communication device 710 may also be part of a machine-type device, which may be an Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) device, such as a non-movable or fixed device, a home device, a wired communication device, or a computing device. For example, the communication device 710 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 710 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, 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 device 710 may include... Figure 7 The communication device 710 may include at least some of the components shown, such as processor 712. It may also include one or more other components unrelated to this disclosure (e.g., internal power supply, display device, and / or user interface device). Therefore, for the sake of brevity, these components of the communication device 710 are not listed in the [disclosure details]. Figure 7 This is shown in the text and is not described in the following text.

[0068] Network device 720 may be part of an electronic device, which may be a network node, such as a satellite, base station (BS), cell, router, or gateway for a 4G / 5G / B5G / 6G, NR, IoT, NB-IoT, or IIoT network. Alternatively, network device 720 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 720 may include Figure 7The network device 720 may include at least some of the components shown, such as processor 722. It may also include one or more other components unrelated to this disclosure (e.g., internal power supply, display device, and / or user interface device). Therefore, for the sake of brevity, these components of the network device 720 are not listed in the [disclosure details]. Figure 7 This is shown in the text and is not described in the following text.

[0069] In one aspect, each of processors 712 and 722 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 712 and 722, each of processors 712 and 722 may include multiple processors in some implementations and a single processor in others, depending on the different implementations of this disclosure. In another aspect, each of processors 712 and 722 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, 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 transformers, these electronic components being configured and arranged to achieve the specific purposes of this disclosure. In other words, in at least some implementations, each of processors 712 and 722 is a dedicated machine specifically designed, arranged, and configured to perform a specific task according to various implementations of this disclosure.

[0070] In some implementations, the communication device 710 may further 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 wireless communication with wireless networks of different types of UEs and / or different Radio Access Technologies (RATs). In some implementations, the transceiver 716 may be equipped with multiple antenna ports (not shown), such as 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 communication. In some implementations, the network device 720 may further 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 wireless communication with different types of UEs of different RATs. In some implementations, the transceiver 726 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, the transceiver 726 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0071] In some implementations, the communication device 710 may further include a memory 714 coupled to and accessible by the processor 712 for storing data. In some implementations, the network device 720 may further include a memory 724 coupled to and accessible by the processor 722 for storing data. Each of the memories 714 and 724 may include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, each of the memories 714 and 724 may include a read-only memory (ROM), such as a mask ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Alternatively, each of the memories 714 and 724 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0072] Each of the communication device 710 and the network device 720 can be a communication entity capable of communicating with each other according to various schemes of this disclosure. For illustrative purposes and without limitation, the capabilities of the communication device 710 as a UE and the network device 720 as a network node are described below in conjunction with procedures 800 and 900.

[0073] Explanatory process

[0074] Figure 8An example flow 800 according to an embodiment of this disclosure is illustrated. Flow 800 may be an example implementation of the above-described scenario / solution, whether in part or in whole, including the content regarding the configuration and generation of Channel State Information (CSI) reports described above. Flow 800 may represent one aspect of the functional implementation of communication device 710. Flow 800 may include one or more operations, actions, or functions, as shown in one or more steps 810, 820, and 830. Although shown as independent steps, the individual steps of flow 800 may be divided into more steps, combined into fewer steps, or omitted depending on the desired implementation. Furthermore, the steps of flow 800 may be arranged according to... Figure 8 The process can be executed in the order shown, or in a different order. Process 800 can be implemented by communication device 710 or any suitable user equipment (UE) or machine type device. For illustrative purposes only and without limitation, process 800 is described below with communication device 710 as the UE and network device 720 as a network node (e.g., a base station such as a gNB). Process 800 can begin at step 810.

[0075] In step 810, process 800 may involve the processor 712 of communication device 710 receiving a report configuration from network device 720. This report configuration may indicate a condition. When this condition is met, a CSI report should be ready for transmission. Process 800 can then proceed from step 810 to step 820.

[0076] In step 820, process 800 may involve processor 712 generating a CSI report based on the condition. Process 800 may continue from step 820 to step 830.

[0077] In step 830, process 800 may involve processor 712 sending a CSI report on uplink (UL) resources allocated by network device 720.

[0078] In some implementations, the condition may include a period value and a start time offset, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset.

[0079] In some implementations, the condition may include a period value and a start time offset, and if the reporting configuration is activated by a command, the condition is considered to be met when the time is equal to a multiple of the period value plus the start time offset.

[0080] In some implementations, the condition may include a time offset, and the condition is considered to be met after the time offset has elapsed since the command that triggered the report configuration was received.

[0081] In some implementations, the command that triggers the report configuration may include downlink control information (DCI).

[0082] In some implementations, the command that triggers the report configuration may include downlink control information (DCI) indicating the UL resource.

[0083] In some implementations, the condition may include a time offset and an event, and the condition is considered satisfied after a time offset has elapsed following the satisfaction of the event.

[0084] In some implementations, the condition may include a period value, a start time offset, and an event, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset after the event is satisfied.

[0085] In some implementations, the indication information may be a signal based on the uplink sequence.

[0086] In some implementations, process 800 may involve processor 712 sending an instruction message after the condition is met.

[0087] Figure 9 An example flow 900 according to an embodiment of this disclosure is illustrated. Flow 900 may be an example implementation of the scenario / solution described above, whether in part or in whole, including the content regarding CSI report configuration and generation. Flow 900 may represent one aspect of the functionality of network device 720. Flow 900 may include one or more operations, actions, or functions, as shown in one or more steps 910 and 920. Although shown as independent steps, the individual steps of flow 900 may be divided into more steps, combined into fewer steps, or omitted depending on the desired implementation. Furthermore, the steps of flow 900 may be arranged according to... Figure 9 The process can be executed in the order shown, or in a different order. Process 900 can be implemented by network device 720 and any variant thereof. For illustrative purposes only and without limitation, process 900 is described below with communication device 710 as the UE and network device 720 as a network node (e.g., a base station such as a gNB). Process 900 may begin at step 910.

[0088] In step 910, process 900 may involve the processor 722 of network device 720 sending a report configuration to communication device 710. This report configuration may indicate a condition. When this condition is met, a CSI report should be ready for transmission. Process 900 can then proceed from step 910 to step 920.

[0089] In step 920, process 900 may involve processor 722 receiving a CSI report on UL resources allocated to communication device 710.

[0090] In some implementations, the condition may include a period value and a start time offset, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset.

[0091] In some implementations, the condition may include a period value and a start time offset, and if the reporting configuration is activated by a command, the condition is considered to be met when the time is equal to a multiple of the period value plus the start time offset.

[0092] In some implementations, the condition may include a time offset, and the condition is considered to be satisfied after the time offset has elapsed since the communication device 710 received the command that triggered the report configuration.

[0093] In some implementations, the command that triggers the report configuration may include downlink control information (DCI).

[0094] In some implementations, the command that triggers the report configuration may include downlink control information (DCI) indicating the UL resource.

[0095] In some implementations, the condition may include a time offset and an event, and the condition is considered satisfied after a time offset has elapsed following the satisfaction of the event.

[0096] In some implementations, the condition may include a period value, a start time offset, and an event, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset after the event is satisfied.

[0097] In some implementations, process 900 may involve processor 722 receiving instruction information from communication device 710 after the condition is met.

[0098] In some implementations, the indication information may be a signal based on the uplink sequence.

[0099] Additional notes

[0100] The topics described herein sometimes demonstrate different components contained within or connected to other different components. It should be understood that such architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieves the same function is considered "associated" in order to achieve the desired functionality. Therefore, any two components combined in this document to achieve a specific function can be considered "associated" with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered "operably connected" or "operably coupled" to achieve the desired functionality, and any two components that can be suchly associated can also be considered "operably coupled" to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0101] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0102] Furthermore, those skilled in the art will understand that the terms used herein, particularly in appended claims, such as the body portion of appended claims, are generally considered "open" terms. For example, the word "comprising" should be interpreted as "including but not limited to," the word "having" should be interpreted as "having at least," and the word "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also understand that if a specific quantity introduced in a claim has an explicit intent, that intent will be explicitly stated in the claim; if no such statement is made, then such intent does not exist. For example, for ease of understanding, the following appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce the content of the claim. However, the use of such phrases should not be interpreted as limiting any particular claim containing that content to containing only one such content, even if the same claim contains the introductory phrases "one or more" or "at least one" and indefinite articles such as "one" or "a," for example, "one" and / or "a" should be interpreted as "at least one" or "one or more"; the same applies to definite articles used to introduce the content of the claim. Furthermore, even if a specific quantity is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated quantity. For example, stating only "two items" without other modifiers implies at least two items, or two or more items. Additionally, when using conventions such as "at least one A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C coexist. Similarly, when using conventions such as "at least one A, B, or C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C coexist. Those skilled in the art will also understand that almost all extractive terms and / or phrases presenting two or more alternative terms in the specification, claims, or drawings should be understood to include one term, either term, or both terms. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B" or "A and B".

[0103] As can be seen from the foregoing, this document describes various embodiments of the present disclosure for illustrative purposes, and various modifications can be made without departing from the scope and spirit of the present disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are defined by the following claims.

Claims

1. A method comprising: The device's processor receives a report configuration from a network node, wherein the report configuration indicates a condition, and wherein when the condition is met, a channel state information report should be ready for transmission; The processor generates the channel state information report based on this condition; as well as The processor sends the channel status information report on the uplink resources allocated by the network node.

2. The method as described in claim 1, wherein, The condition includes a period value and a start time offset, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset.

3. The method of claim 1, wherein, The condition includes a period value and a start time offset, and if the report configuration is activated via command, the condition is considered met when the time is equal to a multiple of the period value plus the start time offset.

4. The method of claim 1, wherein, The condition includes a time offset, and the condition is considered satisfied after the time offset has elapsed since the command that triggered the report configuration was received.

5. The method of claim 1, wherein, The condition includes a time offset and an event, and the condition is considered satisfied after the time offset has elapsed since the event was satisfied.

6. The method of claim 1, wherein, The condition includes a period value, a start time offset, and an event, and the condition is considered satisfied when the time is equal to a multiple of the period value plus the start time offset after the event is satisfied.

7. The method of claim 1, wherein, Also includes: Once the condition is met, the processor sends an instruction message.

8. The method of claim 4, wherein, The command that triggers this report configuration includes downlink control information.

9. The method of claim 4, wherein, The command that triggers this report configuration includes downlink control information indicating the uplink resource.

10. The method of claim 7, wherein, This indication is based on the uplink sequence.

11. A method comprising: The processor of the network node sends a report configuration to the device, wherein the report configuration indicates a condition, and wherein when the condition is met, the channel state information report should be ready for transmission; as well as The processor receives the channel status information report on the uplink resources allocated to the device.

12. The method of claim 11, wherein, The condition includes a period value and a start time offset, and the condition is considered satisfied when the time is equal to the sum of a multiple of the period value and the start time offset.

13. The method of claim 11, wherein, The condition includes a period value and a start time offset, and if the report configuration is activated via command, the condition is considered met when the time is equal to a multiple of the period value plus the start time offset.

14. The method of claim 11, wherein, The condition includes a time offset, and the condition is considered to be satisfied after the time offset has elapsed since the device received the command that triggered the report configuration.

15. The method of claim 11, wherein, The condition includes a time offset and an event, and the condition is considered satisfied after the time offset has elapsed since the event was satisfied.

16. The method of claim 11, wherein, The condition includes a period value, a start time offset, and an event, and the condition is considered satisfied when the time is equal to a multiple of the period value plus the start time offset after the event is satisfied.

17. The method of claim 11, wherein, Also includes: Once the condition is met, the processor receives the instruction information from the device.

18. The method of claim 14, wherein, The command that triggers this report configuration includes downlink control information.

19. The method of claim 14, wherein, The command that triggers this report configuration includes downlink control information indicating the uplink resource.

20. The method of claim 17, wherein, This indication is based on the uplink sequence.

Images