Channel state information indication method and apparatus

By using channel status information to report configuration and indication information in 5G networks, and activate or deactivate CSI reports of multiple sub-configurations, the problem of inaccurate reporting of channel status information caused by dynamic adjustment of antenna configuration is solved, and efficient and accurate CSI indications and Energy-saving effect.

WO2024234246A1PCT designated stage expired Publication Date: 2024-11-211FINITY INC +2
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/094276
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In 5G networks, when dynamically adjusting the antenna configuration to save energy, it may lead to inaccurate or untimely reporting of channel status information, affecting transmission performance, and it is difficult for the prior art to effectively instruct the terminal device to send multiple channel status information reports.

Method used

By transmitting channel status information between the terminal device and the network device to report configuration and indication information, and using RRC signaling and DCI control, CSI reports of multiple sub-configurations are activated or deactivated, ensuring that the terminal device sends CSI reports efficiently and accurately.

Benefits of technology

It realizes efficient and accurate CSI indications and reports in energy-saving mode, saves CSI reporting overhead, saves uplink resources, and improves the accuracy and efficiency of CSI by network equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023094276_21112024_PF_FP_ABST
    Figure CN2023094276_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a channel state information indication method and apparatus. The method comprises: a terminal device receiving a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration being related to L pieces of CSI, the channel state information (CSI) reporting configuration comprising S sub-configurations, wherein 1 ≤ S ≤ L, and one of the S sub-configurations corresponds to at least one piece of channel state information (CSI); and the terminal device receiving indication information, the indication information being used for triggering (indicating / activating) at least one of the S sub-configurations.
Need to check novelty before this filing date? Find Prior Art

Description

Channel state information indication method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] As a crucial component of new global infrastructure, fifth-generation (5G) communication networks have experienced rapid global development in recent years. With the widespread adoption of 5G across various industries and its application in more geographical areas, the need for higher data rates and denser networks, coupled with the use of more antennas, greater bandwidth, and more frequency bands, is driving increasing energy consumption in 5G devices.

[0003] According to operator statistics, the average energy consumption of a 5G base station is more than three times that of an LTE base station. Nearly 50% of the cost of deploying a 5G network for operators comes from electricity costs. Furthermore, 5G base stations consume significant energy even during periods of inactivity. Therefore, network energy conservation is crucial for improving environmental sustainability, reducing environmental impact (such as greenhouse gas emissions), and saving operating costs. Energy conservation in 5G networks is an urgent issue that needs to be addressed.

[0004] To achieve network energy conservation, Rel-18 launched a project to research various energy-saving technologies related to network energy conservation. During the discussion, network energy-saving technologies can be categorized into time-domain, frequency-domain, spatial-domain, and energy-domain energy conservation. Examples of spatial-domain energy conservation include dynamically adjusting the number of antennas, dynamically adjusting data transmission power, and introducing cell-based DTX / DRX technology. Using these various energy-saving technologies can significantly save network equipment energy.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] However, the inventors have discovered that some wireless communication application scenarios (such as energy-saving mode) may have negative impacts. For example, when network devices dynamically adjust the number of antennas or transmission power, this may cause changes in the corresponding channels, resulting in inaccurate or untimely reporting of Channel State Information (CSI) from terminal devices, ultimately affecting transmission performance.

[0008] When the network device adjusts the antenna configuration (for example, for energy saving purposes), the network device triggers / indicates / activates the terminal device to report N CSIs out of L CSIs, where N < L. How the network device performs CSI indication to enable the terminal device to send a CSI report of multiple CSIs is a key issue that needs to be solved currently.

[0009] Regarding at least one of the above problems, an embodiment of the present application provides a method and apparatus for indicating channel state information.

[0010] According to one aspect of the embodiments of the present application, a method for indicating channel state information (CSI) is provided, including:

[0011] The terminal device receives a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration is related to L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1 ≤ S ≤ L, and one sub-configuration in the S sub-configurations corresponds to at least one channel state information (CSI);

[0012] The terminal device receives indication information, and the indication information is used to trigger (indicate / activate) at least one sub-configuration in the S sub-configurations.

[0013] According to another aspect of the embodiments of the present application, an apparatus for indicating channel state information is provided, and the apparatus includes:

[0014] A first receiving unit that receives a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration is related to L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1 ≤ S ≤ L, and one sub-configuration in the S sub-configurations corresponds to at least one channel state information (CSI);

[0015] A second receiving unit that receives indication information, and the indication information is used to trigger (indicate / activate) at least one sub-configuration in the S sub-configurations.

[0016] According to another aspect of the embodiments of the present application, a method for indicating channel state information (CSI) is provided, including:

[0017] The network device sends a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration is related to L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1 ≤ S ≤ L, and one sub-configuration in the S sub-configurations corresponds to at least one channel state information (CSI);

[0018] The network device sends indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0019] According to another aspect of an embodiment of the present application, a device for indicating channel state information is provided, the device including:

[0020] a first sending unit configured to send a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is associated with L CSIs, the channel state information (CSI) reporting configuration including S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0021] The second sending unit sends indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0022] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0023] A network device that sends channel state information (CSI) reporting configuration and indication information; and

[0024] A terminal device, which receives the channel state information (CSI) reporting configuration and the indication information;

[0025] The channel state information (CSI) reporting configuration is related to L CSIs, and the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI); the indication information is used to trigger (indicate / activate) at least one sub-configuration of the S sub-configurations.

[0026] One of the beneficial effects of the embodiments of the present application is that: even in some scenarios of wireless communication applications (such as energy-saving mode), the network equipment can efficiently and accurately instruct the terminal device to report CSI, so that the terminal device can efficiently and accurately send CSI reports, and can save CSI reporting overhead and save uplink resources.

[0027] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0028] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0029] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0031] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0032] FIG2 is a schematic diagram of activating / deactivating MAC CE for PUCCH SP-CSI reporting according to an embodiment of the present application;

[0033] FIG3 is a schematic diagram of a method for indicating channel state information according to an embodiment of the present application;

[0034] FIG4 is another schematic diagram of a method for indicating channel state information according to an embodiment of the present application;

[0035] FIG5 is another schematic diagram of a method for indicating channel state information according to an embodiment of the present application;

[0036] FIG6 is a schematic diagram of a device for indicating channel state information according to an embodiment of the present application;

[0037] FIG7 is a schematic diagram of a device for indicating channel state information according to an embodiment of the present application;

[0038] FIG8 is a schematic diagram of a network device according to an embodiment of the present application;

[0039] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0041] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0042] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0043] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0044] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0045] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0046] Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), IAB host, etc., and may also include remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0047] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0048] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0049] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0050] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0051] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0052] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0053] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0054] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0055] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0056] In mobile communication systems, terminal devices typically measure channel state information (CSI) based on instructions and configuration from network devices and then report the measured CSI to the network devices. When scheduling a terminal device, the network device can refer to this CSI to schedule the terminal device for transmission using the appropriate resources and transmission method. Different terminal devices may experience different physical channel conditions. Using a CSI feedback mechanism can effectively utilize resources, thereby improving overall network transmission efficiency.

[0057] In the NR CSI feedback mechanism, the terminal device measures and reports the reference signal based on the CSI configuration. CSI may include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Channel Measurement Reference Signal Resource Indicator (CSI-RS Resource Indicator, CRI), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block Resource Indicator (SSBRI), Layer Indicator (LI), and Rank Indication (RI).

[0058] In the NR CSI reporting framework, CSI reporting is performed by associating CSI reports with CSI resources. CSI reports can be configured into the following three types: periodic CSI reporting (P-CSI): transmitted only on the Physical Uplink Control Channel (PUCCH); semi-persistent CSI reporting (SP-CSI): transmitted on the PUCCH or Physical Uplink Shared Channel (PUSCH); and aperiodic CSI reporting (AP-CSI): transmitted only on the PUSCH.

[0059] The following first describes the PUSCH-based semi-persistent CSI (or the semi-persistent CSI carried by the PUSCH, hereinafter referred to as PUSCH semi-persistent CSI).

[0060] In the CSI feedback framework, the network device configures a set of trigger states for the terminal device through the RRC high-level parameter CSI-SemiPersistentOnPUSCH-TriggerStateList, and each trigger state corresponds to a CSI reporting setting. The network device activates or deactivates a trigger state through the CSI request field in the DCI, and there can be multiple PUSCH-based SP-CSIs in active state at the same time. A terminal device (UE) does not want to receive a DCI encrypted by SP-CSI-RNTI, which activates a semi-persistent CSI report with the same CSI-reportconfigid that has been activated by a previous DCI.

[0061] According to the position order of the trigger states configured in CSI-SemiPersistentOnPUSCH-TriggerStateList, the codepoint of the CSI request field in the DCI is mapped to the SP-CSI trigger state, and codepoint "0" is mapped to the trigger state in the first position. For the activation or deactivation of semi-persistent CSI, the terminal device will verify the PDCCH of the DCI only when the following conditions are met:

[0062] -The CRC parity bits of the DCI format are scrambled with the SP-CSI-RNTI provided by the higher-layer parameter sp-CSI-RNTI;

[0063] -The settings of the special fields of the DCI format are shown in Table 1 or Table 2 below:

[0064] Table 1: Specific fields for PDCCH validation for semi-persistent CSI activation

[0065] Table 2: Specific fields for PDCCH verification for semi-persistent CSI deactivation

[0066] If the verification is achieved, the terminal device regards the information in the DCI format as a valid activation or valid deactivation of semi-persistent CSI transmission based on PUSCH, and the terminal device activates or deactivates the CSI reporting setting indicated by the CSI request field in the DCI. If the verification is not successful, the terminal device considers that a mismatched CRC has been detected in the DCI format.

[0067] For example, the terminal device receives the trigger state list CSI-SemiPersistentOnPUSCH-TriggerStateList configured by RRC. The terminal device receives DCI format 0_1 / 0_2. If the DCI format is SP-CSI-RNTI scrambled and the special fields in DCI Format 0_1 ​​are corresponding to the activation of semi-persistent CSI, the terminal device obtains the CSI report config ID based on the CSI trigger state corresponding to the codepoint in the CSI request field; the terminal device determines the CSI report to be activated.

[0068] For another example, the terminal device receives DCI format 0_1 / 0_2. If the DCI format is SP-CSI-RNTI scrambled and the special fields in DCI Format 0_1 ​​correspond to the deactivation of semi-persistent CSI, the terminal device obtains the CSI report config ID according to the CSI trigger state corresponding to the codepoint in the CSI request field; the terminal device determines the CSI report that needs to be deactivated.

[0069] The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the trigger state list for semi-persistent CSI reporting to the terminal device. For example, it can be shown in Table 3 below.

[0070] Table 3 CSI-SemiPersistentOnPUSCH-TriggerStateList IE

[0071] The following further describes the PUSCH-based aperiodic CSI (or the aperiodic CSI carried by the PUSCH, hereinafter referred to as PUSCH aperiodic CSI).

[0072] In the CSI feedback framework, the network device configures a set of trigger states for the terminal device through the RRC high-level parameter CSI-AperiodicTriggerStateList, and each trigger state can correspond to multiple CSI reporting settings. The network device activates a trigger state through the CSI request field in the DCI.

[0073] The CSI-AperiodicTriggerStateList IE is used to configure an aperiodic trigger state list for the terminal device. Each code point in the DCI field "CSI request" is associated with a trigger state. When a value associated with a trigger state is received, the terminal device will perform CSI-RS, CSI-IM and / or SSB (reference signal) measurements and perform aperiodic reporting on L1 based on all entries in the associatedReportConfigInfoList of the trigger state.

[0074] Table 4 CSI-AperiodicTriggerStateList IE

[0075] The following further describes the PUCCH-based semi-persistent CSI (or the semi-persistent CSI carried by the PUCCH, hereinafter referred to as PUCCH semi-persistent CSI).

[0076] For PUCCH semi-persistent CSI, the PUCCH resource used to transmit the CSI report is configured by reportConfigType. PUCCH semi-persistent CSI is activated by an activation command, which selects a semi-persistent reporting setting of PUCCH for the terminal device to use. When the terminal device sends PUCCH with HARQ-ACK information on the PDSCH corresponding to slot n carrying the activation command, it shall select slot n from the PDSCH. The first slot after that starts to apply the specified semi-persistent reporting setting, where μ is the SCS configuration of PUCCH.

[0077] FIG2 is a PUCCH SP-CSI reporting activation / deactivation MAC CE according to an embodiment of the present application, which is identified by a MAC subheader with an LCID. As shown in FIG2 , the MAC CE includes a fixed 16-bit size and includes the following fields:

[0078] -Serving cell ID: This field indicates the identifier of the serving cell used by the MAC CE; the field length is 5 bits;

[0079] -BWP ID: This field indicates the UL BWP applied by the MAC CE, which is the code point of the DCI bandwidth part indication field. The BWP ID field length is 2 bits;

[0080] -S i :Indicates the activation / deactivation status of the semi-persistent CSI reporting configuration in CSI-reportconfigtoaddmodlist. S0 indicates the reporting configuration, including the PUCCH resources for SP CSI reporting in the specified BWP, and has the lowest CSI-reportconfigid in the list with type set to semiPersistentOnPUCCH; S1 indicates the reporting configuration, including the PUCCH resources for SP CSI reporting in the specified BWP, and has the second lowest CSI-reportconfigid, and so on. If the number of reporting configurations in the list with type set to semiPersistentOnPUCCH in the specified BWP is less than i+1, the MAC entity will ignore S i Field. S i Setting this field to 1 indicates that the corresponding semi-persistent CSI reporting configuration will be activated. i If the field is set to 0, it indicates that the corresponding semi-persistent CSI reporting configuration will be deactivated;

[0081] -R: Reserved bit, set to 0.

[0082] The above examples illustrate PUSCH-based semi-persistent CSI, PUCCH-based aperiodic CSI, and PUCCH-based semi-persistent CSI, but the embodiments of the present application are not limited thereto.

[0083] The inventors discovered that in order to achieve network energy saving, network equipment needs to adjust the antenna configuration used to serve terminal equipment according to the real-time needs of network services, such as the number of antenna elements, antenna ports, etc. In order to ensure that network equipment obtains CSI in a timely and accurate manner, a feasible solution is that the terminal equipment simultaneously reports multiple CSIs corresponding to different antenna configuration schemes at the reporting time. However, how the network equipment indicates CSI to the terminal equipment so that the terminal equipment can perform CSI reporting of multiple CSIs has become an urgent problem to be solved. The following is an example of energy-saving scenarios, but the present application is not limited to this and can be applied to any scenario involving channel state information reporting.

[0084] Embodiments of the first aspect

[0085] The present invention provides a method for indicating channel state information, which is described from the perspective of a terminal device. FIG3 is a schematic diagram of the method for indicating channel state information according to an embodiment of the present invention. As shown in FIG3 , the method includes:

[0086] 301. A terminal device receives a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is related to L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0087] 302. The terminal device receives indication information, where the indication information is used to trigger / indicate / activate at least one sub-configuration among the S sub-configurations.

[0088] It is worth noting that FIG3 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG3 above.

[0089] In some embodiments, the number of PUSCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is H, and / or the number of PUSCH-based non-periodic CSI reporting configurations including at least one sub-configuration is Q, and / or the number of PUCCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is R, where H, Q and R are positive integers.

[0090] For example, the number H of PUSCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is 1, and / or the number Q of PUSCH-based non-periodic CSI reporting configurations including at least one sub-configuration is 1, and / or the number R of PUCCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is 1.

[0091] In some embodiments, a CSI reporting configuration includes P CSI sub-configurations, where each CSI sub-configuration corresponds to one CSI, for example, corresponding to one spatial / energy domain adjustment mode. A terminal device may report N CSIs at a CSI reporting moment, where the N CSIs are associated with the N CSI sub-configurations in the P sub-configurations.

[0092] The terminal device reports a CSI report at the CSI reporting moment. The CSI report includes the first CSI, the second CSI...the Nth CSI, which correspond to CSI subconfiguration 1, subconfiguration 2...subconfiguration N, respectively. Different subconfigurations correspond to different spatial / energy domain adjustment modes.

[0093] Taking N=4 as an example, the CSI report contains 4 CSIs. The first CSI (CSI of sub-configuration 1) corresponds to the spatial adjustment mode of CSI-RS32 ports, the second CSI (CSI of sub-configuration 2) corresponds to the spatial adjustment mode of 16 ports, the third CSI (CSI of sub-configuration 3) corresponds to the spatial adjustment mode of 8 ports, and the fourth CSI corresponds (CSI of sub-configuration 4) to the spatial adjustment mode of 4 ports.

[0094] In some embodiments, the first CSI is a baseline CSI. For example, in a CSI-RS resource set containing multiple resources, each resource being associated with at least one spatial adjustment mode, each resource is associated with four spatial adjustment modes, and the four spatial adjustment modes correspond to 32 ports, 16 ports, 8 ports, and 4 ports, respectively. The 16 ports, 8 ports, and 4 ports are subsets of the 32 ports. That is, the resources associated with the second CSI, the third CSI, and the fourth CSI are subsets of the resources associated with the first CSI. Partial information of the second CSI, the third CSI, and the fourth CSI can be obtained from the first CSI. Therefore, the first CSI is the baseline CSI.

[0095] In the embodiments of the present application, for ease of description, the first CSI, the second CSI, ..., the Nth CSI may be replaced by the CSI of subconfiguration 1, subconfiguration 2, ..., subconfiguration N. The subconfiguration may be replaced by group, configuration, mode, pattern, sub-group, sub-mode, sub-pattern, and the like.

[0096] In some embodiments, the sub-configuration includes at least one of the following information: parameter N1; parameter N2; parameter Ng; codebook subset restriction; port information, wherein the port information is used to indicate part of the ports of the channel state information reference signal (CSI-RS) resources associated with the channel state information (CSI) reporting configuration.

[0097] For example, the port information indicates some ports or a subset of ports in the form of a bitmap, wherein each bit in the bitmap represents a port, a code division multiplexing (CDM) group, or a predefined port group.

[0098] In some embodiments, the maximum number of sub-configurations included in the CSI reporting configuration may be configured via an RRC parameter, such as maxNrOfSubConfig, which is included in Multiplicity and type constraint definitions or CSI-ReportConfig.

[0099] In some embodiments, the sub-configuration is included in the sub-configuration information (e.g., sub-config) of the channel state information (CSI) reporting configuration, or included in the codebook configuration information (e.g., codebook config) of the channel state information (CSI) reporting configuration, or included in the parameter configuration information (e.g., N1-N2config) of the channel state information (CSI) reporting configuration.

[0100] For example, the CSI reporting configuration includes a sub-config list, where one sub-config in the list includes codebook configuration information (codebook config or codebook type or codebook subset restriction, N1, N2, and Ng) and / or port information; or the CSI reporting configuration includes P sub-configurations, i.e., sub-config1 to sub-config P, where each sub-config includes codebook configuration information (codebook config or codebook type or codebook subset restriction) and / or port information;

[0101] For another example, the codebook configuration (codebook config) in the CSI reporting configuration includes codebook configuration 1 to codebook configuration P, which correspond to P sub-configurations respectively. One of the codebook configurations 1 to P includes information such as codebook subset restriction, N1, N2, and Ng; the port information indicated by the port subset does not need to be obtained through explicit indication information, and can be obtained through other predefined methods or implicit methods;

[0102] For another example, the codebook configuration (codebook config) in the CSI reporting configuration includes N1-N2 1 to N1-N2P, which correspond to P sub-configurations respectively. One of the codebook configurations 1 to P includes information such as N1, N2, and Ng. The port information indicated by the port subset does not need to be obtained through explicit indication information, but can be obtained through other predefined methods or implicit methods. Only one common codebook subset restriction parameter is configured in the CSI reporting configuration, and the codebook subset restriction information of each sub-configuration is obtained from the common codebook subset restriction parameter based on the N1, N2, and Ng parameters.

[0103] The CSI reporting configuration includes P sub-configurations, which may be P-1 sub-configurations / codebook configuration indexes / identifiers / information included in the CSI report, or P-1 sub-configurations included in the sub-configuration list, or P-1 codebook configurations included in the codebook configuration list. The above-mentioned P-1 sub-configurations / codebook configuration indexes / identifiers / information or P-1 sub-configurations or P-1 codebook configurations correspond to P-1 sub-configurations respectively. The resource configuration and codebook configuration included in the CSI reporting configuration are one sub-configuration. Therefore, the CSI reporting configuration includes P sub-configurations;

[0104] Alternatively, the CSI reporting configuration includes P sub-configurations, and the CSI reporting may include P sub-configurations / codebook configuration indexes / identifiers / information, or the sub-configuration list includes P sub-configurations, or the codebook configuration list includes P codebook configurations, and one of the P sub-configurations / codebook configuration indexes / identifiers / information or the P sub-configurations or the P codebook configurations is a resource configuration and a codebook configuration included in the CSI reporting configuration. Therefore, the CSI reporting configuration includes P sub-configurations.

[0105] In the embodiments of the present application, the terms "index", "identification" and "information" can be used interchangeably, but the present application is not limited thereto.

[0106] In some embodiments, the channel state information (CSI) reporting configuration may be configured via radio resource control (RRC) signaling, and the indication information may be a DCI or a MAC CE. The indication information is used to instruct the terminal device to report a CSI report at the CSI reporting moment, where the CSI report includes N CSIs, namely, a first CSI, a second CSI, ... an Nth CSI, that is, the CSI of sub-configuration 1, the CSI of sub-configuration 2, ... the CSI of sub-configuration N.

[0107] FIG4 is another schematic diagram of a method for indicating channel state information according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0108] 401. A terminal device receives a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is associated with L CSIs, the channel state information (CSI) reporting configuration including S sub-configurations, where 1≤S≤L, and one of the S sub-configurations corresponds to at least one channel state information (CSI);

[0109] 402. The terminal device receives indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0110] As shown in FIG4 , the method may further include:

[0111] 403. The terminal device performs channel measurements according to M sub-configurations among the triggered / indicated / activated S sub-configurations; and

[0112] 404. The terminal device transmits a Channel State Information (CSI) report, and the Channel State Information (CSI) report includes N pieces of Channel State Information (CSI); wherein, the M sub-configurations correspond to N pieces of Channel State Information (CSI), and 1 ≤ M ≤ N.

[0113] It should be noted that the above Figure 4 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted. In addition, some other operations can be added or some of the operations can be reduced. Those skilled in the art can make appropriate modifications according to the above content, not limited to the description in the above Figure 4 only.

[0114] In some embodiments, the CSI reporting configuration is for Physical Uplink Shared Channel (PUSCH) semi-persistent CSI reporting. A first trigger / indication / activation status list can be configured through RRC, and the first trigger / indication / activation status list includes a set of X1 trigger (indication / activation) statuses.

[0115] In some embodiments, the first trigger / indication / activation status list for PUSCH semi-persistent CSI reporting is S sub-configurations in the CSI reporting configuration, and one trigger / indication / activation status in the list is a sub-configuration. Or one trigger (indication / activation) status in the list is associated with a CSI reporting configuration, that is, one trigger (indication / activation) status in the list is associated with an associated reporting configuration information, and the associated reporting configuration information can be associated with at least one sub-configuration, that is, a list of associated sub-configurations is included below the associated reporting configuration information.

[0116] For example, sub-config1~sub-config S or codebook config 1~codebook config S in the CSI reporting configuration are S sub-configurations, and each trigger / indication / activation is a sub-configuration. If one sub-configuration corresponds to one CSI, then X = S = L; if one sub-configuration corresponds to multiple CSIs, then X = S < L. Thus, RRC signaling overhead can be saved, and there is no need to separately configure the trigger / indication / activation (status) list.

[0117] In some embodiments, the first trigger / indication / activation state list for PUSCH semi-persistent CSI reporting is an existing IE or a newly defined IE, and one trigger (indication / activation) state in the list is associated with at least one CSI reporting configuration index and / or at least one sub-configuration. Alternatively, one trigger (indication / activation) state in the list is associated with one CSI reporting configuration, that is, one trigger (indication / activation) state in the list is associated with one associated reporting configuration information, and the associated reporting configuration information may be associated with at least one sub-configuration, that is, the associated reporting configuration information contains an associated sub-configuration list.

[0118] For example, the first trigger / indication / activation state list for PUSCH semi-persistent CSI reporting can reuse an existing IE (e.g., CSI-SemiPersistentOnPUSCH-TriggerStateList), and add a new parameter in each trigger state in the list, where the parameter is used to associate a sub-configuration or CSI-RS resource, such as associatedsubConfigInfo or associatedResourceConfigInfo. The parameter type or value can be a sub-configuration index or a CSI-ResourcConfig index, where the sub-configuration index is the index of one of the S sub-configurations in the CSI reporting configuration, and the sub-configuration index can be a positive integer.

[0119] The newly added parameter (associatedSubConfigInfo or associatedResourceConfigInfo) is an optional parameter. For example, when the trigger state is only used for CSI report activation / deactivation, the newly added parameter (associatedSubConfigInfo or associatedResourceConfigInfo) is not configured; and / or, when the trigger state is used for CSI report activation / deactivation and triggering / indication / activation of sub-configuration, the newly added parameter (associatedSubConfigInfo or associatedResourceConfigInfo) is configured, and the trigger state is associated with CSI-ReportConfigId and is also associated with sub-configuration or CSI-ResourceConfig. Therefore, the first trigger / indication / activation state list for PUSCH semi-persistent CSI reporting is used for both activation / deactivation of CSI reporting and triggering / indication / activation of sub-configuration.

[0120] Table 5 shows an example of a trigger / indication / activation status list for PUSCH semi-persistent CSI reporting.

[0121] Table 5

[0122] Table 6 shows another example of a triggering / indication / activation state list for PUSCH semi-persistent CSI reporting.

[0123] Table 6

[0124] For another example, the first trigger / indication / activation state list for PUSCH semi-persistent CSI reporting may also be a newly defined list, for example, it may be named CSI-SemiPersistentOnPUSCH-TriggerStateList-r18, or CSI-SemiPersistentOnPUSCH-subConfig-TriggerStateList, or NES-sub-CSI-SemiPersistent OnPUSCH-TriggerStateList; a trigger / indication / activation state in the list may be associated with a CSI reporting configuration and / or at least one CSI-RS resource configuration index and / or at least one sub-configuration, and the first trigger / indication / activation state list may be used for both activation / deactivation of CSI reporting and triggering / indication / activation of sub-configuration.

[0125] Table 7 shows another example of a triggering / indication / activation state list for PUSCH semi-persistent CSI reporting.

[0126] Table 7

[0127] In the above example of reusing IEs and newly defined IEs, a portion of the trigger / indication / activation state-associated CSI reporting configuration indexes in the first trigger state list for PUSCH semi-persistent CSI reporting are used for activation / deactivation of CSI reporting; another portion of the trigger / indication / activation state-associated CSI reporting configuration indexes and / or sub-configurations in the list can be used for both activation of the CSI reporting configuration associated with the trigger / indication / activation state and triggering / indication / activation of the sub-configuration in the activated CSI reporting configuration, or can be used only for triggering / indication / activation of the sub-configuration. As a result, CSI activation / deactivation and triggering / indication / activation of the sub-configuration share the same first trigger / indication / activation state list, saving RRC overhead.

[0128] For another example, the first trigger / indication / activation state list for PUSCH semi-persistent CSI reporting is a newly defined IE. Each trigger / indication / activation state in the list is associated with a CSI reporting configuration index and at least one sub-configuration, and is used for triggering / indicating / activating the sub-configuration in the CSI reporting configuration. Thus, CSI-SemiPersistentOn PUSCH-TriggerStateList is used for activating / deactivating CSI reporting, and the first trigger / indication / activation state list is used for triggering / indicating / activating the sub-configuration.

[0129] For another example, the first trigger / indication / activation state list of PUSCH semi-persistent CSI reporting is a newly defined IE, and one trigger / indication / activation state in the list is associated with at least one sub-configuration, which is used for triggering / indicating / activating the at least one sub-configuration. In this method, there is no need to indicate the CSI reporting configuration index, there is only one CSI reporting configuration, the network device and the terminal device know the CSI reporting index by default, or the CSI reporting configuration index has been indicated through other RRC lists and DCI domains, so there is no need to indicate the CSI reporting configuration index here. Therefore, CSI-SemiPersistentOnPUSCH-TriggerStateList is used for activation / deactivation of CSI reporting, and the first trigger / indication / activation state list is used for triggering / indicating / activating sub-configurations.

[0130] In the above embodiment, a trigger / indication / activation state in the first trigger / indication / activation state list can be associated with a CSI reporting configuration index and / or at least one sub-configuration, where the sub-configuration can be a sub-configuration (index) in the CSI reporting configuration, a codebook configuration (index), a port subset indication information (index), an n1-n2 configuration (index), a CSI-RS resource index, etc. Each sub-configuration-related parameter is associated with a spatial domain / energy domain adjustment element pattern.

[0131] For example, a trigger / indication / activation state in the first trigger / indication / activation state list is associated with a CSI reporting configuration index and at least one sub-configuration. When the trigger / indication / activation state is activated, it indicates that the at least one sub-configuration in the CSI reporting configuration is triggered / indicated / activated, or it indicates that the CSI reporting configuration index is activated and the at least one sub-configuration in the CSI reporting configuration is triggered / indicated / activated.

[0132] For another example, a trigger / indication / activation state in the first trigger / indication / activation state list is associated with at least one sub-configuration information, indicating that the at least one sub-configuration is triggered / indicated / activated.

[0133] For another example, a trigger / indication / activation state in the first trigger / indication / activation state list is associated with at least one CSI-RS resource index. For example, a CSI-RS Resource set includes multiple resources, each resource corresponds to a sub-configuration, that is, a spatial / energy domain element adjustment mode, and a trigger / indication / activation state is associated with at least one CSI-RS resource index. When the trigger / indication / activation state is activated, it indicates that at least the corresponding sub-configuration is triggered / indicated / activated;

[0134] The above schematically illustrates the CSI reporting configuration, and the following schematically illustrates the indication information.

[0135] In some embodiments, the indication information is downlink control information (DCI). The downlink control information (DCI) is user-specific (UE-specific) and is scrambled by a first RNTI. The first RNTI may be an RNTI related to network energy saving that is different from the SP-CSI-RNTI or the C-RNTI, or the first RNTI may be the SP-CSI-RNTI or the C-RNTI.

[0136] For example, a new RNTI dedicated to network energy saving can be defined, such as NES-RNTI, NES-SP-CSI-RNTI, etc. For details on how to generate these RNTIs, please refer to related technologies. These newly defined RNTIs can also be used for other functions. For another example, the first RNTI can also use the existing SP-CSI-RNTI or C-RNTI.

[0137] In some embodiments, the downlink control information (DCI) is DCI format 0_1 ​​or DCI format 0_2; the CSI request field (CSI request field) and / or the first trigger / indication / activation field (which may be referred to as the first indication field, such as the sub-CSI indication field) in the downlink control information (DCI) are used to activate a CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0138] For example, the DCI format can reuse the existing DCI format (0_1, 0_2), the DCI domain can also reuse the existing CSI request domain, or can reuse other idle domains in the DCI format, and the first trigger / indication / activation domain of the DCI is the CSI request domain or other existing domains. The maximum bit width of the CSI request domain has been determined to be 6, and the bit width of the DCI domain determines the number of activation states in the first trigger / indication / activation state list. Or the first trigger / indication / activation domain is a partial CSI request domain, and the first trigger / indication / activation domain is used for both activation / deactivation of the CSI and triggering / indication / activation of the sub-configuration.

[0139] The first trigger / indication / activation state list configured by RRC is an existing IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList) or a newly defined IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList-r18), wherein one of the trigger / indication / activation states in a part of the list is associated with a CSI reporting configuration, and one of the trigger / indication / activation state associations in a part of the trigger / indication / activation state associations is associated with a CSI reporting configuration and / or at least one sub-configuration.

[0140] If the trigger state indicated by the CSI request field is associated with only one CSI reporting configuration index, the activation / deactivation of the CSI report is performed, and the triggering / indication / activation of the sub-configuration is not performed;

[0141] If the trigger status indicated by the CSI request field is associated with a CSI reporting configuration and a subconfiguration, and if the CSI report is not activated, activate the CSI report and trigger / indicate / activate the subconfiguration in the CSI reporting configuration; if the CSI reporting configuration is activated, adjust / update / re-indicate the subconfiguration of the CSI reporting configuration, with the updated subconfiguration overwriting the previously indicated subconfiguration;

[0142] If the trigger status indicated by the CSI request field is only associated with the sub-configuration, it means that there is only one CSI reporting configuration for configuring multiple sub-configurations. Based on the CSI reporting configuration information of RRC, the terminal device and the network device are already aware of the CSI reporting configuration index containing multiple sub-configurations. Therefore, the terminal device executes the triggering / indication / activation of the sub-configuration.

[0143] For another example, the first trigger / indication / activation field of the DCI is a newly defined field, such as CSI-request-r18. This newly defined field is used for both activation / deactivation of CSI reporting and triggering / indication / activation of sub-configurations. The field bit width can be larger and used for both activation / deactivation of CSI and triggering / indication / activation of sub-configurations, allowing for flexible and unrestricted sub-configuration triggering / indication / activation.

[0144] The first trigger / indication / activation state list configured by RRC is an existing IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList) or a newly defined IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList-r18), wherein one of the trigger / indication / activation states in a part of the list is associated with a CSI reporting configuration, and one of the trigger / indication / activation states in a part of the trigger / indication / activation states is associated with a CSI reporting configuration and at least one sub-configuration.

[0145] If the trigger status indicated by CSI request-r18 is only associated with the CSI reporting configuration index: the CSI report is activated / deactivated, but the sub-configuration is not triggered / indicated / activated;

[0146] If the trigger status indicated by CSI request-r18 is associated with a CSI reporting configuration and a sub-configuration: if the CSI report is not activated, activate the CSI report and trigger / indicate / activate the sub-configuration in the CSI reporting configuration; if the CSI reporting configuration is activated, adjust / update / re-indicate the sub-configuration of the CSI reporting configuration, with the updated sub-configuration overwriting the previously indicated sub-configuration;

[0147] If the trigger status indicated by CSI request-r18 is only associated with the sub-configuration: it means that there is only one CSI reporting configuration that configures multiple sub-configurations. Based on the CSI reporting configuration information of RRC, the terminal device and the network device are already aware of the CSI reporting configuration index containing multiple sub-configurations. Therefore, the terminal device executes the triggering / indication / activation of the sub-configuration in the CSI reporting configuration.

[0148] In the above example, one list configured by RRC + one field in DCI is used for activation / deactivation of CSI and triggering / indication / activation of sub-configuration.

[0149] For another example, the first trigger / indication / activation field of the DCI is a newly defined field. The existing CSI request field and the newly defined field jointly trigger / indicate / activate N1 subconfigurations out of the S subconfigurations in the CSI reporting configuration. The CSI request field is used to activate / deactivate CSI reporting, and the newly defined field is used to trigger / indicate / activate the subconfiguration in the CSI reporting configuration index S activated by the CSI request.

[0150] For example, CSI request field + newly defined DCI field, the newly defined DCI field is all zero or invalid value: the activation / deactivation of the CSI is performed, and the triggering / indication / activation of the sub-configuration is not performed;

[0151] For another example, CSI request domain + newly defined DCI domain, the newly defined DCI domain is a non-zero value or a valid value: if the CSI report is not activated, the activation / deactivation of the CSI report is performed, and the triggering / indication / activation of the sub-configuration is performed; if the CSI report is activated, the adjustment / update / re-indication of the sub-configuration of the CSI reporting configuration is performed, and the updated sub-configuration overwrites the previously indicated sub-configuration.

[0152] In the above example, two lists can be configured through RRC, one is the original CSI-SemiPersistent OnPUSCH-TriggerStateList, and the other is a newly defined list; two domains in DCI, one is the original CSI request, and the other is a newly defined DCI domain. The CSI request domain is used for CSI activation / deactivation, and the newly defined DCI domain is used for sub-configuration triggering / indication / activation.

[0153] In some embodiments, for PUSCH-based semi-persistent CSI reporting, according to a special field in the downlink control information (DCI), the CSI request field (CSI request field) and / or the first trigger / indication / activation field (e.g., sub-CSI indication field) in the downlink control information (DCI) are used to activate / deactivate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0154] In some embodiments, the special field in the downlink control information (DCI) is one or more existing fields in the DCI (such as HARQ process number and / or Redundancy Version, etc.), including a semi-persistent CSI activation / deactivation PDCCH verification field.

[0155] In some embodiments, the special field in the downlink control information (DCI) is a field related to network energy saving that is different from the semi-persistent CSI activation / deactivation PDCCH verification field.

[0156] For example, the first specific field of the valid trigger / indication / activation PDCCH verification is used to verify the trigger / indication / activation of the PUSCH semi-persistent CSI subconfiguration. If the verification is achieved, the terminal equipment (UE) regards the information in the DCI format as a valid trigger / indication / activation of the PUSCH semi-persistent CSI subconfiguration. If the verification is not achieved, the UE considers that the DCI format has detected a mismatched CRC.

[0157] The first specific field may be a field for semi-persistent CSI activation PDCCH verification (e.g., HARQ process number and / or Redundancy version), which uses the existing CSI activation specific field, as shown in Table 1. The first specific field may be a newly defined field used to verify the triggering / indication / activation of the PUSCH semi-persistent CSI sub-configuration.

[0158] For another example, the first specific field of the valid release / deactivation PDDCH verification is used to verify the release / deactivation of the PUSCH semi-persistent CSI sub-configuration trigger / indication / activation command. If the verification is achieved, the terminal equipment (UE) regards the information in the DCI format as the valid release / deactivation of the valid trigger / indication / activation command of the PUSCH semi-persistent CSI sub-configuration. If the verification is not achieved, the UE believes that the DCI format has detected a mismatched CRC.

[0159] The first specific field may be a field for semi-persistent CSI deactivation PDCCH verification (e.g., HARQ process number and / or Modulation and coding scheme and / or Resource block assignment and / or Redundancy version), and the specific field for existing CSI deactivation may be used, as shown in Table 2. The first specific field may be a newly defined field used to verify the release / deactivation of the trigger / indication / activation command of the PUSCH semi-persistent CSI sub-configuration.

[0160] The valid triggering / indication / activation and valid release of the sub-configuration of PUSCH semi-persistent CSI may both have specific fields, and the valid triggering / indication / activation specific field and the valid release / deactivation specific field may be the same configuration value or different configuration values.

[0161] Alternatively, the effective triggering / indication / activation of the PUSCH semi-persistent CSI sub-configuration has a specific domain, but the effective release / deactivation does not have a specific domain, that is, there is no need to configure a specific domain for the effective release / deactivation. For example, CSI deactivation represents the effective release / deactivation of the triggering / indication / activation sub-configuration.

[0162] Alternatively, the effective triggering / indication / activation and effective release of the PUSCH semi-persistent CSI sub-configuration do not have a specific domain, that is, no specific domain needs to be configured for them. At least in the following cases, the effective triggering / indication / activation and effective release do not require a specific domain:

[0163] In one DCI, the semi-persistent CSI reporting configuration index can be activated and S sub-configurations in the activated CSI reporting configuration can be triggered / indicated / activated. In this case, the SP-CSI-RNTI is used to scramble the DCI, and the specific field of the DCI is the specific field for semi-persistent CSI activation PDCCH verification in the existing protocol; when CSI is deactivated, the specific field of the DCI is the specific field for semi-persistent CSI deactivation PDCCH verification in the existing protocol, indicating the effective release / deactivation of the sub-configuration.

[0164] In some embodiments, the size / number of bits of the first trigger / indication / activation field (eg, sub-CSI indication field) in the downlink control information (DCI) is predefined or configured through RRC signaling.

[0165] For example, when the first trigger / indication / activation field of the DCI is a newly defined DCI field, the first trigger / indication / activation size (size) is used to determine the bit width of the first trigger / indication / activation field of the DCI. The method for determining the first trigger / indication / activation size (size) may be as follows:

[0166] For example, the first trigger / indication / activation size (size) is determined in a predefined manner, where X is a positive integer greater than 0. For example, the first trigger / indication / activation size (size) is 8, that is, the first trigger / indication / activation field of the DCI is 8 bits.

[0167] For another example, the first trigger / indication / activation size (size) is configured through RRC and / or the maximum value of the first trigger / indication / activation size (size) is configured through RRC, for example, the first trigger / indication / activation size (size) is determined by the higher-layer parameter nes-ReportTriggerSize, and the maximum value of the first trigger / indication / activation size (size) is determined by the higher-layer parameter max-nes-ReportTriggerSize;

[0168] For another example, the first trigger / indication / activation size (size) is configured through RRC and / or the maximum value of the first trigger / indication / activation size (size) is determined through a predefined method. For example, the maximum value of the first trigger / indication / activation size (size) is predefined as 6, and the first trigger / indication / activation size (size) is determined by the higher-layer parameter nes-ReportTriggerSize, which can be configured as a positive integer greater than or equal to 0 and less than or equal to 6.

[0169] In some embodiments, the number of bits in the first trigger / indication / activation field is log2X, where X is the number of trigger (indication / activation) states, wherein the bit values ​​correspond to the trigger (indication / activation) states in the order of the trigger state positions.

[0170] For example, the codepoints of the first trigger / indication / activation field in the downlink control information are mapped to the trigger (indication / activation) state in the order of the position of the trigger state; wherein, codepoint "0" or codepoint "1" is mapped to the trigger / indication / activation state of the first position.

[0171] For another example, the first trigger / indication / activation state list has X rows, each row corresponding to a trigger / indication / activation state. The bit width of the DCI's first trigger / indication / activation field is log2X. Based on the order of the trigger states configured in the trigger / indication / activation state list, the codepoints of the DCI's first trigger / indication / activation field are mapped to the trigger / indication / activation states in the list, with codepoint "0" or codepoint "1" mapped to the first trigger / indication / activation state.

[0172] In some embodiments, the first trigger / indication / activation field (sub-CSI indication field) in the downlink control information (DCI) is a bitmap. The number of bits of the first trigger / indication / activation field is X; X is the number of trigger / indication / activation states, or the number of sub-configurations in the CSI reporting configuration; wherein the bit position corresponds to the trigger / indication / activation state or the sub-configuration in sequence. The bits from MSB to LSB of the bitmap correspond to the first to last trigger / indication / activation state in the first trigger / indication / activation state list, or the first to last sub-configuration in the CSI reporting configuration; wherein 1 represents the trigger / indication / activation of the sub-configuration, and 0 represents the release / deactivation / deactivation of the sub-configuration.

[0173] The above schematically illustrates the DCI domain and mapping, which will be further illustrated below with examples.

[0174] In some embodiments, for example, the first trigger / indication / activation state list configured by RRC is an existing IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList) or a newly defined IE (e.g., CSI-Semi PersistentOnPUSCH-TriggerStateList-r18), and one trigger / indication / activation state in the list is associated with a CSI reporting configuration and / or at least one sub-configuration, that is, a part of the trigger / indication / activation states in the list are associated with the CSI reporting configuration index, and another part of the trigger / indication / activation states are associated with the CSI reporting configuration index and / or at least one sub-configuration; the DCI format reuses the existing DCI format (0_1, 0_2), the first trigger / indication / activation field of the DCI is the CSI request field or a newly defined field (e.g., CSI request field-r18), and the existing DCI field is reused, and codepoint "0" or "1" is mapped to the trigger / indication / activation state at the first position.

[0175] For the case of SP-CSI activation, for example, the terminal device receives DCI 0_1 / 0_2, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 / 0_2 correspond to the semi-persistent CSI activation PDCCH verification specific field, the CSI request field or the newly defined field (for example, CSI request field-r18) activates a trigger / indication / activation state, and the trigger / indication / activation state is associated with a CSI reporting configuration index, then the terminal device activates the CSI reporting configuration.

[0176] For the case of SP-CSI deactivation, for example, the terminal device receives DCI 0_1 / 0_2, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 / 0_2 correspond to the semi-persistent CSI deactivation PDCCH verification specific field, the CSI request field or the newly defined field (for example, CSI request field-r18) corresponds to a trigger / indication / activation state, and the trigger / indication / activation state is associated with a CSI reporting configuration index, then the terminal device deactivates the CSI reporting configuration.

[0177] For the case of CSI activation + sub-configuration triggering / indication / activation, for example, the terminal device receives DCI 0_1 / 0_2, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 ​​correspond to the semi-persistent CSI activation PDCCH verification specific domain, the CSI request domain or the newly defined domain (such as CSI request field-r18) corresponds to a triggering / indication / activation state, and the triggering / indication / activation state is associated with a CSI reporting configuration index and at least one sub-configuration, then the terminal device activates the CSI reporting configuration and triggers / indicates / activates the at least one sub-configuration in the CSI reporting configuration. CSI deactivation or the triggering / indication / activation of the next sub-configuration represents the effective release / deactivation of the current sub-configuration triggering / indication / activation information.

[0178] For the triggering / indication / activation of the sub-configuration after CSI activation, for example, the terminal device receives DCI format 0_1, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 ​​are semi-persistent CSI activation PDCCH verification specific fields, the CSI request field corresponds to a trigger / indication / activation state, and the trigger / indication / activation state is associated with a CSI reporting configuration index and at least one sub-configuration. If the CSI reporting configuration is activated by DCI scrambled by SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI is activated, the terminal device triggers / indicates / activates the sub-configuration in the CSI reporting configuration at the current moment, and this sub-configuration trigger / indication / activation information overwrites the previous sub-configuration trigger / indication / activation information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration trigger / indication / activation information.

[0179] For example, at time T1, the terminal device receives the SP-CSI-RNTI scrambled DCI format 0_1, the special field is the CSI semi-persistent CSI activation PDCCH verification specific field, and the trigger / indication / activation status association corresponding to the CSI request field is {CSI report config1, 32port CSI-RS subconfiguration, 16port CSI-RS subconfiguration}, then the terminal device activates CSI report config1 and indicates the 32port CSI-RS and 16port subconfiguration;

[0180] At time T2, the terminal device receives the SP-CSI-RNTI-scrambled DCI format 0_1, the special field is the CSI semi-persistent CSI activation PDCCH verification specific field, and the trigger / indication / activation status association corresponding to the CSI request field is {CSI report config1, 8-port CSI-RS sub-configuration, 4-port CSI-RS sub-configuration}. The terminal device determines that CSI report config1 has been activated, then the terminal device re-indicates the sub-configuration of CSI report config1, and updates / adjusts the sub-configuration 32-port CSI-RS and 16-port sub-configuration to 8-port CSI-RS and 4-port CSI-RS sub-configuration.

[0181] For the case of re-triggering / indicating / activating the sub-configuration after CSI activation, for example, the terminal device receives DCI format 0_1, if the DCI format is SP-CSI-RNTI encrypted, and the special fields in DCI Format 0_1 ​​are different from the special fields for semi-continuous CSI activation / deactivation PDCCH verification specific fields for sub-configuration triggering / indicating / activating fields, the CSI request field or the newly defined field (for example, CSI request field-r18) corresponds to a triggering / indicating / activating state, and the triggering / indicating / activating state is associated with a CSI reporting configuration index and at least one sub-configuration. If the CSI reporting configuration is activated by DCI encrypted with SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI is activated, the terminal device triggers / indicates / activates the sub-configuration in the CSI reporting configuration at the current moment, and the sub-configuration triggering / indicating / activating information this time overwrites the previous sub-configuration triggering / indicating / activating information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration triggering / indication / activation information.

[0182] For the triggering / indication / activation of the sub-configuration after CSI activation, for example, the terminal device receives DCI format 0_1, if the DCI format is encrypted with the newly defined network energy-saving related RNTI, such as NES-RNTI, the CSI request field or the newly defined field (such as CSI request field-r18) corresponds to a trigger / indication / activation state, and the trigger / indication / activation state is associated with a CSI reporting configuration index and at least one sub-configuration. If the CSI reporting configuration is activated by the DCI encrypted with SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI report is activated, the terminal device triggers / indicates / activates the sub-configuration in the CSI reporting configuration at the current moment, and the sub-configuration trigger / indication / activation information of this time overwrites the previous sub-configuration trigger / indication / activation information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration trigger / indication / activation information.

[0183] As a result, CSI activation / deactivation and sub-configuration triggering / indication / activation share the same RRC configuration list and DCI domain, which can indicate multiple sub-configurations and multiple CSIs in the DCI domain triggering / indication / activation mechanism, with high indication flexibility; and save DCI and RRC overhead.

[0184] In some embodiments, for example, RRC configures a first trigger / indication / activation state list, the list is a newly defined IE, such as CSI-SemiPersistentOnPUSCH-subConfig-TriggerStateList or NES-sub-CSI-Semi PersistentOnPUSCH-TriggerStateList, a trigger / indication / activation state in the list is associated with a CSI reporting configuration index and / or at least one sub-configuration, and RRC configures CSI-SemiPersistentOn PUSCH-TriggerStateList; the DCI Format reuses the existing DCI format (0_1, 0_2), and the first trigger / indication / activation domain of the DCI is a newly defined DCI domain; the existing CSI-Semi PersistentOnPUSCH-TriggerStateList and CSI request field are used for activation / deactivation of the CSI report, and the first trigger / indication / activation state list and the first trigger / indication / activation domain are used for triggering / indication / activation of the sub-configuration.

[0185] The first trigger / indication / activation field may be a codepoint with a bit width of log2X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and codepoint "0" or "1" is mapped to the trigger / indication / activation state at the first position, and is mapped sequentially in ascending order of the trigger / indication / activation state indices in the first trigger / indication / activation state list; or, the first trigger / indication / activation field (NES sub-CSI indication field) may also be a bitmap with a bit width of X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and is arranged in ascending order of the trigger / indication / activation state indices in the first trigger / indication / activation state list, and the MSB to LSB of the bitmap correspond to the first to the last trigger / indication / activation state.

[0186] For the case of SP-CSI activation, for example, the terminal device receives DCI 0_1, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 ​​correspond to the activation of semi-persistent CSI, the newly defined first trigger / indication / activation field (NES sub-CSI indication field) is all zero or an invalid value or other reference value, then the terminal device performs the CSI activation operation and determines the CSI report to be activated according to the CSI request field.

[0187] For the case of SP-CSI deactivation, for example, the terminal device receives DCI 0_1, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 ​​correspond to the deactivation of semi-persistent CSI, the newly defined DCI field (NES sub-CSI indication field) is all zero or an invalid value or other reference value, then the terminal device performs the CSI deactivation operation and determines the CSI report to be deactivated according to the CSI request field.

[0188] For the case of SP-CSI activation + sub-configuration triggering / indication / activation, for example, the terminal device receives DCI 0_1, if the DCI format is SP-CSI-RNTI scrambled, and the special fields in DCI Format 0_1 ​​correspond to the activation of semi-persistent CSI, the newly defined first trigger / indication / activation field (NES sub-CSI indication field) is a non-zero valid value, and the terminal device activates the semi-persistent CSI report according to the CSI reporting configuration index corresponding to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined first trigger / indication / activation field (NES sub-CSI indication field), that is, triggers / indicates / activates the sub-configuration in the CSI reporting configuration activated by the CSI request field.

[0189] For the triggering / indication / activation of the sub-configuration after SP-CSI activation, for example, the terminal device receives DCI0_1, if the DCI format is SP-CSI-RNTI encrypted, and the special fields in DCI Format 0_1 ​​correspond to the activation of semi-persistent CSI, the newly defined first trigger / indication / activation field (NES sub-CSI indication field) is a non-zero valid value. The terminal device obtains the CSI reporting configuration index according to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined first trigger / indication / activation field (NES sub-CSI indication field). If the CSI reporting configuration is activated by the DCI encrypted by SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI report is activated, the sub-configuration trigger / indication / activation information this time overwrites the previous sub-configuration trigger / indication / activation information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration trigger / indication / activation information.

[0190] For example, at time T1, the terminal device receives the SP-CSI-RNTI encrypted DCI 0_1 signaling, the CSI request field corresponds to CSI report config 1, and the newly defined first trigger / indication / activation field (NES sub-CSI indication field) indicates the 32 / 16port sub-configuration among the four sub-configurations of 32 / 16 / 8 / 4port. The specific field is the CSI activation PDCCH verification specific field. The terminal device activates CSI report config 1 based on the above signaling, and triggers / indicates / activates two of the four sub-configurations (32port and 16port sub-configurations).

[0191] At time T2, CSI report config 1 is still in the activation period. The terminal device receives the SP-CSI-RNTI encrypted DCI 0_1 signaling. The CSI request field corresponds to CSI report config 1. The newly defined first trigger / indication / activation field (NES sub-CSI indication field) indicates the 8port sub-configuration among the four sub-configurations of 32 / 16 / 8 / 4port. The specific field is the CSI activation PDCCH verification specific field. The terminal device determines that one of the four sub-configurations (8port sub-configuration) is triggered / indicated / activated based on the above signaling, and no processing is required for CSI activation.

[0192] For the case of triggering / indicating / activating the sub-configuration after SP-CSI activation, for example, the terminal device receives DCI0_1. If the DCI format is SP-CSI-RNTI encrypted, and the special fields in DCI Format 0_1 ​​are different from the special fields for semi-persistent CSI activation / deactivation PDCCH verification for sub-configuration triggering / indicating / activating, the newly defined first triggering / indicating / activating field (NES sub-CSI indication field) is a non-zero valid value. The terminal device obtains the CSI reporting configuration index according to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined first triggering / indicating / activating field (NES sub-CSI indication field). If the CSI reporting configuration is activated by the DCI encrypted by SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI report is activated, the sub-configuration triggering / indicating / activating information this time overwrites the previous sub-configuration triggering / indicating / activating information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration triggering / indication / activation information.

[0193] For the triggering / indication / activation of the sub-configuration after SP-CSI activation, for example, the terminal device receives DCI0_1. If the DCI format is encrypted with the newly defined network energy-saving related RNTI, such as NES-RNTI, the newly defined first trigger / indication / activation field (NES sub-CSI indication field) is a non-zero valid value. The terminal device obtains the CSI reporting configuration index according to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined first trigger / indication / activation field (NES sub-CSI indication field). If the CSI reporting configuration is activated by the DCI encrypted with the SP-CSI-RNTI at a previous moment, and the sub-configuration is triggered / indicated / activated at the same time as the CSI report is activated, the sub-configuration trigger / indication / activation information of this time overwrites the previous sub-configuration trigger / indication / activation information. CSI deactivation or the next sub-configuration triggering / indication / activation represents the effective release / deactivation of the current sub-configuration trigger / indication / activation information.

[0194] In some embodiments, the terminal device receives a first DCI encrypted by SP-CSI-RNTI, the CSI request field of the first DCI is associated with a semi-persistent CSI report with the same identifier as the CSI reporting configuration, and the semi-persistent CSI report is activated by a second DCI encrypted by SP-CSI-RNTI received previously, then the first DCI is used to retrigger / indicate / activate the sub-configuration during the activation period of the semi-persistent CSI report.

[0195] In some embodiments, the triggering / indicating / activating information of the latter sub-configuration overrides the triggering / indicating / activating information of the previous sub-configuration; after the semi-persistent CSI report is deactivated, the triggering / indicating / activating information of the sub-configuration is released / deactivated / deactivated.

[0196] According to existing protocols, a UE does not expect to receive a DCI scrambled with SP-CSI-RNTI activating one semi-persistent CSI report with the same CSI-ReportConfigId as in a semi-persistent CSI report which is activated by a previously received DCI scrambled with SP-CSI-RNTI.

[0197] In the above embodiment, a UE may receive a DCI scrambled by SP-CSI-RNTI, the CSI request field of which is associated with a semi-persistent CSI report with the same CSI-ReportConfigId, and the semi-persistent CSI report is activated by the previously received DCI scrambled by SP-CSI-RNTI. The transmission behavior is not used for the activation of the semi-persistent CSI report, but for the re-triggering / indication / activation of the sub-configuration during the activation of the CSI report. As a result, in the DCI field triggering / indication / activation mechanism, multiple sub-configurations and multiple CSIs can be indicated each time, with higher indication flexibility; and the DCI field has fewer bits and lower overhead.

[0198] In some embodiments, the CSI reporting configuration is associated with L CSIs, and the CSI report includes S sub-configurations, such as sub-config1 to sub-config L or codebook config 1 to codebook config L, one sub-configuration corresponds to one CSI, S=L; the first trigger / indication / activation state list is the S sub-configurations of the CSI reporting configuration, X=S=L; the DCI format reuses the existing DCI format (0_1, 0_2), the first trigger / indication / activation field of the DCI is a newly defined DCI field, the existing CSI-Semi PersistentOnPUSCH-TriggerStateList and CSI request field are used for activation / deactivation of the CSI report, and the list of S sub-configurations in the CSI reporting configuration and the first trigger / indication / activation field are used for triggering / indicating / activating the sub-configuration.

[0199] The first trigger / indication / activation field may be a codepoint with a bit width of log2X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and codepoint "0" or "1" is mapped to the trigger / indication / activation state at the first position, and is mapped sequentially in ascending order of the trigger / indication / activation state indices in the first trigger / indication / activation state list; or, the first trigger / indication / activation field (NES sub-CSI indication field) may also be a bitmap with a bit width of X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and is arranged in ascending order of the trigger / indication / activation state indices in the first trigger / indication / activation state list, and the MSB to LSB of the bitmap correspond to the first to the last trigger / indication / activation state.

[0200] The above schematically illustrates the situation of semi-persistent CSI reporting of PUSCH. For example, a set of trigger / indication / activation states is configured by a first trigger / indication / activation state list configured by a higher layer, wherein the first trigger / indication / activation field in the DCI is combined with the first RNTI to trigger / indicate / activate at least one of the trigger states. According to the first mapping method, the first trigger / indication / activation field of the DCI is mapped to the trigger / indication / activation state in the first trigger / indication / activation state list configured by the higher layer.

[0201] For example, the first trigger / indication / activation status list is used to configure / indicate the CSI reporting configuration and / or sub-configuration of the terminal device. Each row of the first trigger / indication / activation status list is a trigger / indication / activation status, and there are X rows in total, i.e., X trigger / indication / activation states. Each trigger state is or is associated with at least one CSI reporting configuration and / or at least one sub-configuration.

[0202] The first trigger / indication / activation field in the DCI is combined with the first RNTI to trigger / indicate / activate at least one of the trigger states, that is, trigger / indicate / activate the CSI reporting configuration and / or N1 sub-configurations of the S sub-configurations. The bit width of the first trigger / indication / activation field is determined by the first trigger / indication / activation size.

[0203] For the triggering / indication / activation of the PUSCH semi-persistent CSI sub-configuration, the UE shall verify the PDCCH on the DCI only if the following conditions are met: the CRC parity bits of the DCI format are scrambled by the first RNTI provided by the upper layer, and / or the DCI format special field is configured as the first special field.

[0204] If the verification is achieved, the UE considers the information in the DCI format as a valid trigger / indication / activation and / or a valid release / deactivation of the PUSCH semi-persistent CSI subconfiguration, and the UE triggers / indication / activates or deactivates / releases the subconfiguration setting indicated by the first trigger / indication / activation field in the DCI. If the verification is not achieved, the UE considers that a mismatched CRC has been detected for the DCI format.

[0205] The following is a schematic description of the non-periodic CSI reporting of PUSCH, and the same content as above is omitted. The following second trigger / indication / activation state list, second trigger / indication / activation domain, second mapping method, etc. can refer to the aforementioned first trigger / indication / activation state list, first trigger / indication / activation domain, and first mapping method.

[0206] For example, a group of trigger / indication / activation states is configured by a second trigger / indication / activation state list configured by a higher layer, wherein a second trigger / indication / activation field in the DCI triggers / indicates / activates at least one of the trigger states. According to the second mapping manner, the second trigger / indication / activation field of the DCI is mapped to the trigger / indication / activation state in the second trigger / indication / activation state list configured by the higher layer.

[0207] In some embodiments, the second trigger / indication / activation state list for PUSCH aperiodic CSI reporting is an existing IE or a newly defined IE, and one trigger (indication / activation) state in the list is associated with at least one CSI reporting configuration index and / or at least one sub-configuration. That is, one trigger (indication / activation) state in the list contains an associated reporting configuration list (associatedReportConfigInfoList) and an associated sub-configuration list (associated ReportConfigInfoList); or one trigger (indication / activation) state in the list is associated with at least one CSI reporting configuration, that is, one trigger (indication / activation) state in the list contains an associated reporting configuration list (associatedReportConfigInfoList), the reporting configuration list is at least one associated reporting configuration (associatedReportConfigInfo), and one associated reporting configuration in the at least one associated reporting configuration is associated with at least one sub-configuration, that is, one associated reporting configuration in the at least one associated reporting configuration contains an associated sub-configuration list, such as associatedSubConfigInfoList.

[0208] The second trigger / indication / activation state list for PUSCH aperiodic CSI reporting is used to configure a group of trigger / indication / activation states, where one trigger / indication / activation state in the list is associated with at least one CSI reporting configuration index and / or at least one sub-configuration. Alternatively, one trigger (indication / activation) state in the list is associated with at least one CSI reporting configuration, that is, one trigger (indication / activation) state in the list is associated with at least one associated reporting configuration information, and the associated reporting configuration information can be associated with at least one sub-configuration, that is, the associated reporting configuration information contains an associated sub-configuration list.

[0209] In some embodiments, the second trigger / indication / activation state list for PUSCH aperiodic CSI reporting is S sub-configurations in the CSI reporting configuration, and each trigger / indication / activation state in the list is a sub-configuration, where X=S; for example, sub-config1 to sub-config S or codebook config 1 to codebook config S in the CSI reporting configuration are S sub-configurations.

[0210] In some embodiments, the second trigger / indication / activation state list for PUSCH aperiodic CSI reporting may reuse an existing IE, such as CSI-AperiodicTriggerStateList, or may be a newly defined IE, such as CSI-AperiodicTriggerStateList-r18, where each trigger state may be associated with at least one CSI reporting configuration and / or at least one sub-configuration. Alternatively, a trigger (indication / activation) state may be associated with at least one CSI reporting configuration, i.e., a trigger (indication / activation) state in the list may be associated with at least one associated reporting configuration information, and the associated reporting configuration information may be associated with at least one sub-configuration, i.e., an associated sub-configuration list may be included below the associated reporting configuration information.

[0211] The sub-configuration information may be a sub-configuration (index), a codebook configuration (index), a port subset indication information (index), an n1-n2 configuration (index), etc. Each sub-configuration related parameter is associated with a spatial / energy domain adjustment element mode.

[0212] Table 8 shows an example of a trigger / indication / activation status list for PUSCH aperiodic CSI reporting.

[0213] Table 8

[0214] For example, the first trigger / indication / activation status list based on PUSCH semi-persistent CSI reporting and the second trigger / indication / activation status list based on PUSCH aperiodic CSI reporting can be the same list, that is, one list contains both semi-persistent CSI reporting information and aperiodic CSI reporting information.

[0215] In some embodiments, the second trigger / indication / activation field of the DCI is used to indicate at least one trigger / activation / at least state of the second trigger / indication / activation state list configured by RRC, for activation / deactivation of CSI reporting and / or triggering / indication / activation of sub-configuration.

[0216] For example, the existing DCI format (0_1, 0_2) may be reused to reproduce the existing DCI field (CSI request); the second triggering / indication / activation field of the DCI is the CSI request field.

[0217] For another example, the second trigger / indication / activation field of the DCI is a newly defined DCI field. The existing CSI request field is used for activation / deactivation of CSI reporting, and the newly defined DCI field is used for triggering / indication / activation of sub-configuration.

[0218] For another example, the first trigger / indication / activation domain of the DCI based on PUSCH semi-persistent CSI reporting and the second trigger / indication / activation domain of the DCI based on PUSCH non-periodic CSI reporting can be the same DCI domain, that is, they are distinguished by different RNTI scrambling, which is non-periodic CSI reporting when C-RNTI scrambled and semi-persistent CSI reporting when SP-CSI-RNTI scrambled; or, the first trigger / indication / activation domain of the DCI based on PUSCH semi-persistent CSI reporting and the second trigger / indication / activation domain of the DCI based on PUSCH non-periodic CSI reporting can also be different DCI domains. In some embodiments, the second trigger / indication / activation state list configured by RRC is an existing IE (e.g., CSI-AperiodicTriggerStateList) or a newly defined IE (e.g., CSI-AperiodicTriggerStateList-r18), and one trigger / indication / activation state in the list is associated with at least one CSI reporting configuration and / or at least one sub-configuration, that is, a part of the trigger / indication / activation states in the list are associated only with the CSI reporting configuration index, and the other part of the trigger / indication / activation states are associated with the CSI reporting configuration index and / or sub-configuration; the existing DCI format (0_1, 0_2) can be reused, and the second trigger / indication / activation field of the DCI is the CSI request field or a newly defined DCI field (e.g., CSI request field-r18), and the second trigger / state / indication state list and the second trigger / indication / indication field are used for activation of the CSI report and triggering / indication / activation of the sub-configuration. The newly defined second trigger / indication / activation field has a bit width of log2X, and codepoint "0" or "1" is mapped to the trigger / indication / activation state in the first position, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list.

[0219] For the case of AP-CSI activation, for example, the terminal device receives DCI 0_1, the newly defined DCI field (NES sub-CSI indication field) is all zero or invalid value, and the terminal device determines the CSI report to be activated based on the CSI request field.

[0220] For the case of AP-CSI activation + sub-configuration triggering / indication / activation, for example, the terminal device receives DCI 0_1, the newly defined DCI field (NES sub-CSI indication field) is a non-zero valid value, and the terminal device activates semi-continuous CSI reporting according to the CSI reporting configuration index corresponding to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined DCI field (NES sub-CSI indication field).

[0221] In some embodiments, for example, RRC configures a second trigger / indication / activation state list, the list is a newly defined IE, such as CSI-Aperiodic-subConfig-TriggerStateList or NES-sub-CSI-Aperiodic OnPUSCH-TriggerStateList, the two trigger / indication / activation states in the list are associated with the CSI reporting configuration index and / or at least one sub-configuration, and RRC configures CSI-AperiodicOnPUSCH-TriggerStateList; the DCI Format reuses the existing DCI format (0_1, 0_2), and the second trigger / indication / activation domain of the DCI is a newly defined DCI domain; the existing CSI-AperiodicOnPUSCH-TriggerStateList and CSI request field are used for activation of the CSI report, and the second trigger / indication / activation state list and the second trigger / indication / activation domain are used for triggering / indicating / activating the sub-configuration. The second trigger / indication / activation field may be a codepoint with a bit width of log2X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and codepoint "0" or "1" is mapped to the trigger / indication / activation state at the first position, and is mapped sequentially in ascending order of the trigger / indication / activation state indices in the second trigger / indication / activation state list; or, the second trigger / indication / activation field (NES sub-CSI indication field) may also be a bitmap with a bit width of X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and is arranged in ascending order of the trigger / indication / activation state indices in the second trigger / indication / activation state list, and the MSB to LSB of the bitmap correspond to the first to the last trigger / indication / activation state.

[0222] For the case of AP-CSI activation, for example, the terminal device receives DCI 0_1, the newly defined DCI field (NES sub-CSI indication field) is all zero or invalid value, and the terminal device determines the CSI report to be activated based on the CSI request field.

[0223] For the case of AP-CSI activation + sub-configuration triggering / indication / activation, for example, the terminal device receives DCI 0_1, the newly defined DCI field (NES sub-CSI indication field) is a non-zero valid value, and the terminal device activates semi-continuous CSI reporting according to the CSI reporting configuration index corresponding to the CSI request field, and triggers / indicates / activates the sub-configuration according to the newly defined DCI field (NES sub-CSI indication field).

[0224] In some embodiments, the CSI reporting configuration is associated with L CSIs, and the CSI report includes S sub-configurations, such as sub-config1 to sub-config L or codebook config 1 to codebook config L, one sub-configuration corresponds to one CSI, S=L; the second trigger / indication / activation state list is the S sub-configurations of the CSI reporting configuration, X=S=L; the DCI format reuses the existing DCI format (0_1, 0_2), the second trigger / indication / activation field of the DCI is a newly defined DCI field, the existing CSI-AperiodicOnPUSCH-TriggerStateList and CSI request field are used for activation of the CSI report, and the list of S sub-configurations in the CSI reporting configuration and the second trigger / indication / activation field are used for triggering / indicating / activating the sub-configurations. The second trigger / indication / activation field may be a codepoint with a bit width of log2X, where X is the number of trigger / indication / activation states in the first trigger / indication / activation state list or the number of rows in the list, and codepoint "0" or "1" is mapped to the trigger / indication / activation state at the first position, and is mapped sequentially in ascending order of the trigger / indication / activation state indices in the first trigger / indication / activation state list; or, the second trigger / indication / activation field (NES sub-CSI indication field) may also be a bitmap with a bit width of X, where X is the number of trigger / indication / activation states in the second trigger / indication / activation state list or the number of rows in the list, and is arranged in ascending order of the trigger / indication / activation state indices in the second trigger / indication / activation state list, and the MSB to LSB of the bitmap correspond to the first to the last trigger / indication / activation state.

[0225] For the case of AP-CSI activation, for example, when the terminal device receives DCI 0_1, a newly defined DCI field (NES sub-CSI indication field) is all zeros or an invalid value, and the terminal device determines the CSI report to be activated according to the CSI request field.

[0226] For the case of AP-CSI activation + sub-configuration triggering / indicating / activation, for example, when the terminal device receives DCI 0_1, a newly defined DCI field (NES sub-CSI indication field) is a non-zero valid value, the terminal device activates semi-persistent CSI reporting according to the CSI reporting configuration index corresponding to the CSI request field, and also triggers / indicates / activates the sub-configuration according to the newly defined DCI field (NES sub-CSI indication field).

[0227] The following further schematically illustrates the case of group common signaling.

[0228] In some embodiments, the downlink control information (DCI) is group common signaling, and the downlink control information is scrambled by a second RNTI. The group common signaling includes multiple blocks, and each block corresponds to a terminal device. The group common signaling is used for triggering / indicating / activating the sub-configuration of at least one terminal device.

[0229] In some embodiments, the block is used to indicate the CSI reporting configuration index of the terminal device and / or at least one sub-configuration. In the block, a codepoint or a bitmap (bitmap) is used to indicate the sub-configuration, and the bit value / position corresponds to the triggering (indicating / activating) state in sequence. The bit width of the block is related to the number of sub-configurations of the terminal device and / or the bit width of the CSI reporting configuration index.

[0230] For example, DCI Format 2_X is used to notify one or more terminal devices of the information of N sub-configurations out of L sub-configurations in the CSI reporting configuration, where N < L, and each sub-configuration is associated with a CSI. The terminal device reports N CSIs based on DCI Format 2_X.

[0231] For example, the following information uses DCI Format 2_X, and the CRC is scrambled and transmitted by a second RNTI (such as nes-RNTI): Block 1, Block 2,..., Block N.

[0232] In some embodiments, the second RNTI is determined according to a first parameter, and the payload size of the downlink control information is determined according to a fourth parameter; the starting position of the corresponding block information of the terminal device in the downlink control information (DCI) is determined according to the second parameter; the bit width of the corresponding block of the terminal device in the downlink control information (DCI) is determined according to a third parameter; and the CSI reporting configuration index bit width of the terminal device is determined according to a fifth parameter.

[0233] For example, the starting position of the block is determined by the second parameter (e.g., nes-PositionDCI-2-6) configured by the higher layer for the terminal device. If the terminal device is configured with the second RNTI (e.g., nes-RNTI) and dci-Format2-X through the higher layer parameters, the higher layer configures a block for the terminal device, and the block field content includes at least one of the following:

[0234] - CSI reporting configuration index—Y bit, where Y is determined by pre-definition, for example, Y=2; or the size of Y is determined by the fifth parameter of the higher layer;

[0235] - Subconfiguration trigger / indication / activation indication—The bitmap width is determined based on the third parameter of the higher layer. Each bit corresponds to a subconfiguration. The subconfiguration indexes in the CSI reporting configuration are sorted in ascending order. The MSB to LSB bits in the bitmap correspond to the first to last subconfiguration. 1 indicates activation and 0 indicates deactivation.

[0236] The size of DCI Format 2_X is indicated by a higher-layer fourth parameter (e.g., sizeDCI-2-X). DCI Format 2_X is used by a terminal device to monitor DCI Format 2_X, for example, DCI Format 2_X related to network energy conservation and / or a CSI reporting configuration containing L sub-configurations; where X can be a positive integer greater than 6.

[0237] In some embodiments, the first parameter is used for the RNTI value of the scrambled CRC of the DCI format 2-X for network energy saving; the second parameter is the starting position of the CSI reporting configuration index and / or sub-configuration trigger / indication / activation indication in the DCI format 2-X; the third parameter is used to indicate the bit width of the sub-configuration trigger / indication / activation indication information, that is, the number of sub-configurations, each bit corresponds to one sub-configuration; the fourth parameter is used to indicate the size of the DCI Format 2_X; the fifth parameter is used to determine the size of the above-mentioned Y.

[0238] In some embodiments, a terminal device configured with a network energy-saving function can detect DCI format 2_X during PDCCH reception. For example, the terminal device determines the RNTI of DCI format 2_X based on a first parameter; monitors PDCCH via DCI format 2-X to monitor DCI format 2_X on the active DL BWP of a PCell or SpCell; determines the payload size of DCI format 2_X based on a fourth parameter; determines the position of the terminal device's information in DCI format 2_X based on a second parameter; determines the size of Y based on a fifth parameter or a predefined rule, with the first Y bits used to determine the CSI reporting configuration index. When the fifth parameter determines that the value of Y is equal to 0, it indicates that there is no CSI reporting configuration index information in the current DCI format; determines the bit width of the bitmap based on the third parameter, that is, determines the number of sub-configurations in the CSI reporting configuration. The position of the bitmap is after the CSI reporting configuration index information (if the CSI reporting configuration index information is configured), and the size of the bitmap is equal to the number of sub-configurations, with each bit corresponding to one sub-configuration; a 1 in the bitmap indicates that the sub-configuration is activated, and a 0 indicates deactivation.

[0239] The following further describes the case of PUCCH semi-persistent CSI reporting, and the same contents as above are omitted. The following third trigger / indication / activation state list can refer to the above first trigger / indication / activation state list.

[0240] In some embodiments, the channel state information (CSI) reporting configuration is for physical uplink control channel (PUCCH) semi-persistent CSI reporting. The indication information is a medium access control (MAC) control element (CE), and the MAC CE activates or deactivates at least one of the multiple sub-configurations.

[0241] For example, the trigger / indication / activation MAC CE of the sub-configuration of the PUCCH semi-persistent CSI reporting configuration can be identified by a MAC sub-header with an LCID. For example, there is a fixed bit width, the bit width size is the first bit width parameter, and contains the following fields:

[0242] -Serving cell ID: This field indicates the identifier of the serving cell used by the MAC CE. The field length is 5 bits;

[0243] -BWP ID: This field indicates the UL BWP applied by the MAC CE, which is the code point of the DCI bandwidth part indication field. The BWP ID field length is 2 bits;

[0244] -Si: Indicates the triggering / indication / activation and release / deactivation / deactivation status of the sub-configuration in the third trigger / indication / activation list of the semi-persistent CSI reporting carried by PUCCH. S0 indicates the sub-configuration with the lowest CSI-ReportConfigId in the third trigger / indication / activation list; S1 indicates the sub-configuration with the second lowest CSI-ReportConfigId in the type set to the third trigger / indication / activation list, and so on. If the number of sub-configurations in the third trigger / indication / activation list is less than i+1, the MAC entity will ignore the Si field. The Si field is set to 1, indicating that the sub-configuration of the corresponding semi-persistent CSI reporting configuration will be triggered / indicated / activated. The Si field is set to 0, indicating that the sub-configuration of the corresponding semi-persistent CSI reporting configuration will be released / deactivated / deactivated;

[0245] -R: Reserved bit, set to 0.

[0246] The first bit width parameter may be determined in a predefined manner, for example, the first bit width parameter=X, X=16; or the first bit width parameter may be determined by an RRC high-layer parameter.

[0247] In some embodiments, a third trigger / indication / activation list is configured through RRC, and a row in the third trigger / indication / activation list corresponds to a CSI reporting configuration index and / or at least one CSI-RS resource index or at least one sub-configuration.

[0248] For example, the third trigger / indication / activation state list of PUCCH semi-persistent CSI reporting is S sub-configurations in the CSI reporting configuration, each row in the list is a sub-configuration, where X=S; for example, sub-config1 to sub-config S or codebook config 1 to codebook config S in the CSI reporting configuration are S sub-configurations.

[0249] For another example, the third trigger / indication / activation status list of PUCCH semi-persistent CSI reporting reuses the existing IE, such as CSI-reportconfigtoaddmodlist or part of CSI-reportconfigtoaddmodlist, and each row of the list contains at least one sub-configuration, X=S.

[0250] For another example, the trigger / indication / activation (state) list of PUCCH semi-persistent CSI reporting is a newly defined IE, such as NES-sub-CSI-SemipersistentOnPUCCHList, where each row may be a sub-configuration, X=S.

[0251] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0252] It can be seen from the above embodiments that even in some scenarios of wireless communication applications (such as energy-saving mode), the network equipment can efficiently and accurately indicate CSI to the terminal device, so that the terminal device can efficiently and accurately send CSI reports, and can save CSI reporting overhead and save uplink resources.

[0253] Embodiments of the second aspect

[0254] The embodiment of the present application provides a method for indicating channel state information, which is described from the perspective of a network device. The embodiment of the second aspect can be combined with the embodiment of the first aspect, and the same contents as the embodiment of the first aspect will not be repeated.

[0255] FIG5 is a schematic diagram of a method for indicating channel state information according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0256] 501. A network device sends a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is related to L CSIs, and the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0257] 502. The network device sends indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0258] It is worth noting that FIG5 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG5 above.

[0259] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0260] It can be seen from the above embodiments that even in some scenarios of wireless communication applications (such as energy-saving mode), the network equipment can efficiently and accurately indicate CSI to the terminal device, so that the terminal device can efficiently and accurately send CSI reports, and can save CSI reporting overhead and save uplink resources.

[0261] Embodiments of the third aspect

[0262] The embodiment of the present application provides a device for indicating channel state information. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. The contents that are the same as those in the embodiment of the first aspect are not repeated here.

[0263] FIG6 is a schematic diagram of a device for indicating channel state information according to an embodiment of the present application. As shown in FIG6 , the device for indicating channel state information 600 includes:

[0264] a first receiving unit 601 configured to receive a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is associated with L CSIs, the channel state information (CSI) reporting configuration including S sub-configurations, where 1≤S≤L, and one of the S sub-configurations corresponds to at least one channel state information (CSI);

[0265] The second receiving unit 602 receives indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0266] In some embodiments, the number of PUSCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is P, and / or the number of PUSCH-based non-periodic CSI reporting configurations including at least one sub-configuration is Q, and / or the number of PUCCH-based semi-persistent CSI reporting configurations including at least one sub-configuration is R, where P, Q and R are positive integers.

[0267] In some embodiments, as shown in FIG6 , the apparatus may further include:

[0268] a processing unit 603, which performs channel measurement according to M sub-configurations among the triggered (indicated / activated) S sub-configurations; and

[0269] The sending unit 604 sends a channel state information (CSI) report, where the channel state information (CSI) report includes N channel state information (CSI); wherein the M sub-configurations correspond to N channel state information (CSI), and 1≤M≤N.

[0270] In some embodiments, the one sub-configuration includes at least one of the following information: parameter N1; parameter N2; parameter Ng; codebook subset restriction; port information, the port information being used to indicate part of the ports of the channel state information reference signal (CSI-RS) resource associated with the channel state information (CSI) reporting configuration;

[0271] The sub-configuration is included in the sub-configuration information (sub-config) of the channel state information (CSI) reporting configuration, or included in the codebook configuration information (codebook config) of the channel state information (CSI) reporting configuration, or included in the parameter configuration information (N1-N2config) of the channel state information (CSI) reporting configuration.

[0272] In some embodiments, the channel state information (CSI) reporting configuration is for semi-persistent CSI reporting of a physical uplink shared channel (PUSCH); a first trigger / indication / activation state list is configured through RRC, the first trigger / indication / activation state list including a set of X1 trigger (indication / activation) states;

[0273] Alternatively, the channel state information (CSI) reporting configuration is for aperiodic CSI reporting of a physical uplink shared channel (PUSCH); a second trigger / indication / activation state list is configured through RRC, where the second trigger / indication / activation state list includes a group of X2 trigger (indication / activation) states;

[0274] Among them, one trigger (indication / activation) state is associated with at least one CSI reporting configuration index and / or at least one CSI-RS resource index and / or at least one sub-configuration.

[0275] In some embodiments, the indication information is downlink control information (DCI);

[0276] The downlink control information (DCI) is user-specific (UE-specific), and the downlink control information is encrypted by a first RNTI; wherein the first RNTI is an RNTI related to network energy saving that is different from SP-CSI-RNTI or C-RNTI, or the first RNTI is SP-CSI-RNTI or C-RNTI.

[0277] In some embodiments, the downlink control information (DCI) is DCI format 0_1 ​​or DCI format 0_2; the CSI request field (CSI request field) and / or the first indication field (sub-CSI indication field) in the downlink control information (DCI) are used to activate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0278] In some embodiments, for PUSCH-based semi-persistent CSI reporting, according to a special field in the downlink control information (DCI), the CSI request field (CSI request field) and / or the first indication field (sub-CSI indication field) in the downlink control information (DCI) are used to activate / deactivate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0279] In some embodiments, the special field in the downlink control information (DCI) is one or more existing fields in the DCI, including a semi-persistent CSI activation / deactivation PDCCH verification field;

[0280] Alternatively, the special field in the downlink control information (DCI) is a field related to network energy saving that is different from the semi-persistent CSI activation / deactivation PDCCH verification field.

[0281] In some embodiments, the second receiving unit 602 also receives a first DCI encrypted by SP-CSI-RNTI, the CSI request field of the first DCI is associated with a semi-persistent CSI report with the same identifier as the CSI reporting configuration, and the semi-persistent CSI report is activated by the previously received second DCI encrypted by SP-CSI-RNTI, then the first DCI is used to retrigger / indicate / activate the sub-configuration during the activation period of the semi-persistent CSI report.

[0282] In some embodiments, the sub-configuration re-triggering / indication / activation information overrides the triggering / indication / activation of the previous sub-configuration; after the semi-persistent CSI report is deactivated, the sub-configuration re-triggering / indication / activation information is released / deactivated / deactivated.

[0283] In some embodiments, the size / number of bits of the first indication field in the downlink control information (DCI) is predefined or configured through RRC signaling; the number of bits of the first indication field is log2X; X is the number of trigger (indication / activation) states; wherein the bit value corresponds to the trigger (indication / activation) state in the order of the trigger state position;

[0284] The codepoints of the first indication field in the downlink control information are mapped to the trigger (indication / activation) state in the order of the trigger state positions; wherein, codepoint "0" or codepoint "1" is mapped to the trigger / indication / activation state of the first position.

[0285] In some embodiments, the first indication field in the downlink control information (DCI) is a bitmap; wherein the number of bits in the first indication field is X; X is the number of trigger (indication / activation) states; wherein the bit position corresponds to the trigger (indication / activation) state in sequence;

[0286] The bits from MSB to LSB of the bitmap correspond to the first to last trigger / indication / activation status, respectively; wherein 1 indicates triggering / indication / activation of the subconfiguration, and 0 indicates release / deactivation / deactivation of the subconfiguration.

[0287] In some embodiments, the indication information is downlink control information (DCI), the downlink control information (DCI) is group common signaling, and the downlink control information is scrambled by the second RNTI;

[0288] The group common signaling includes multiple blocks, each block corresponds to a terminal device, and the group common signaling is used to trigger / indicate / activate a sub-configuration of at least one terminal device.

[0289] In some embodiments, the block is used to indicate the CSI reporting configuration index and / or at least one sub-configuration of the terminal device, and a codepoint or bitmap is used in the block to indicate the sub-configuration, and the bit value / position corresponds to the trigger (indication / activation) state in sequence; the bit width of the block is related to the number of sub-configurations of the terminal device and / or the bit width of the CSI reporting configuration index.

[0290] In some embodiments, the second RNTI is determined according to a first parameter, and the payload size of the downlink control information is determined according to a fourth parameter; the starting position of the corresponding block information of the terminal device in the downlink control information (DCI) is determined according to the second parameter; the bit width of the corresponding block of the terminal device in the downlink control information (DCI) is determined according to a third parameter; and the CSI reporting configuration index bit width of the terminal device is determined according to a fifth parameter.

[0291] In some embodiments, the channel state information (CSI) reporting configuration is for physical uplink control channel (PUCCH) semi-persistent CSI reporting;

[0292] The indication information is a medium access control (MAC) control element (CE), and the MAC CE activates or deactivates at least one sub-configuration of the multiple sub-configurations.

[0293] In some embodiments, a third trigger / indication / activation list is configured through RRC, and a row in the third trigger / indication / activation list corresponds to a CSI reporting configuration index and / or at least one CSI-RS resource index or at least one sub-configuration.

[0294] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The channel state information indication device 600 may also include other components or modules. For details of these components or modules, please refer to the relevant art.

[0295] In addition, for the sake of simplicity, FIG6 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0296] Through the embodiments of the present application, even in some scenarios of wireless communication applications (such as energy-saving mode), the network device can efficiently and accurately indicate CSI to the terminal device, so that the terminal device can efficiently and accurately send CSI reports, and can save CSI reporting overhead and save uplink resources.

[0297] Embodiments of the fourth aspect

[0298] The embodiment of the present application provides a device for indicating channel state information. The device may be, for example, a network device, or one or more components or assemblies configured in the network device. The contents that are the same as those in the first and second aspects of the embodiment are not repeated here.

[0299] FIG7 is a schematic diagram of a device for indicating channel state information according to an embodiment of the present application. As shown in FIG7 , a device 700 for indicating channel state information includes:

[0300] A first sending unit 701 is configured to send a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is associated with L CSIs, and the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0301] The second sending unit 702 is configured to send indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0302] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The channel state information report receiving device 500 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0303] In addition, for simplicity, FIG5 only illustrates the connection relationship or signal path between various components or modules. However, those skilled in the art should be aware that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0304] Through the embodiments of the present application, even in some scenarios of wireless communication applications (such as energy-saving mode), the network device can efficiently and accurately indicate CSI to the terminal device, so that the terminal device can efficiently and accurately send CSI reports, and can save CSI reporting overhead and save uplink resources.

[0305] Embodiments of the fifth aspect

[0306] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents that are the same as those in the first to fourth aspects of the embodiments will not be repeated.

[0307] In some embodiments, the communication system 100 may include at least:

[0308] A network device that sends channel state information (CSI) reporting configuration and indication information; and

[0309] A terminal device, which receives the channel state information (CSI) reporting configuration and the indication information;

[0310] The channel state information (CSI) reporting configuration is related to L CSIs, and the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI); the indication information is used to trigger (indicate / activate) at least one sub-configuration of the S sub-configurations.

[0311] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0312] Figure 8 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 8 , network device 800 may include a processor 810 (e.g., a central processing unit (CPU)) and a memory 820 ; the memory 820 is coupled to the processor 810 . The memory 820 may store various data and may also store an information processing program 830 , which is executed under the control of the processor 810 .

[0313] For example, the processor 810 may be configured to execute a program to implement the channel state information indication method as described in the embodiment of the second aspect. For example, the processor 810 may be configured to perform the following control: sending a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration being related to L CSIs, the channel state information (CSI) reporting configuration including S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponding to at least one channel state information (CSI); sending indication information, the indication information being used to trigger (indicate / activate) at least one sub-configuration of the S sub-configurations.

[0314] In addition, as shown in FIG8 , network device 800 may further include: a transceiver 840 and an antenna 850, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 800 does not necessarily include all the components shown in FIG8 ; in addition, network device 800 may also include components not shown in FIG8 , and reference may be made to the prior art for details.

[0315] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0316] Figure 9 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 9 , terminal device 900 may include a processor 910 and a memory 920. Memory 920 stores data and programs and is coupled to processor 910. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0317] For example, the processor 910 may be configured to execute a program to implement the channel state information indication method as described in the embodiment of the first aspect. For example, the processor 910 may be configured to perform the following control: receiving a channel state information (CSI) reporting configuration, the channel state information (CSI) reporting configuration being related to L CSIs, the channel state information (CSI) reporting configuration including S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponding to at least one channel state information (CSI); and receiving indication information, the indication information being used to trigger (indicate / activate) at least one sub-configuration of the S sub-configurations.

[0318] As shown in Figure 9 , the terminal device 900 may further include: a communication module 930, an input unit 940, a display 950, and a power supply 960. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 900 does not necessarily include all of the components shown in Figure 9 , and these components are not essential. Furthermore, the terminal device 900 may also include components not shown in Figure 9 , for which reference may be made to the prior art.

[0319] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the channel state information indication method described in the embodiment of the first aspect.

[0320] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method for indicating channel state information described in the embodiment of the first aspect.

[0321] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program enables the network device to execute the channel state information indication method described in the embodiment of the second aspect.

[0322] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method for indicating channel state information described in the embodiment of the second aspect.

[0323] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0324] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0325] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0326] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0327] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0328] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0329] 1. A method for indicating channel state information (CSI), comprising:

[0330] The terminal device receives a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is associated with L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0331] The terminal device receives indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0332] 2. The method according to Note 1, wherein the number of PUSCH-based semi-continuous CSI reporting configurations including at least one sub-configuration is H, and / or the number of PUSCH-based non-periodic CSI reporting configurations including at least one sub-configuration is Q, and / or the number of PUCCH-based semi-continuous CSI reporting configurations including at least one sub-configuration is R, wherein H, Q and R are positive integers.

[0333] 3. The method according to Supplementary Note 2, wherein the method further comprises:

[0334] The terminal device performs channel measurement according to M sub-configurations among the triggered (indicated / activated) S sub-configurations; and

[0335] Send a channel state information (CSI) report, where the channel state information (CSI) report includes N channel state information (CSI); wherein the M sub-configurations correspond to the N channel state information (CSI), and 1≤M≤N.

[0336] 4. The method according to any one of Notes 1 to 3, wherein the sub-configuration includes at least one of the following information:

[0337] Parameter N1;

[0338] Parameter N2;

[0339] Parameter Ng;

[0340] codebook subset restriction;

[0341] Port information, where the port information is used to indicate some ports of a channel state information reference signal (CSI-RS) resource associated with the channel state information (CSI) reporting configuration.

[0342] 5. The method according to any one of Notes 1 to 4, wherein the sub-configuration is included in the sub-configuration information (sub-config) of the channel state information (CSI) reporting configuration, or included in the codebook configuration information (codebook config) of the channel state information (CSI) reporting configuration, or included in the parameter configuration information (N1-N2config) of the channel state information (CSI) reporting configuration.

[0343] 6. The method according to any one of Notes 1 to 5, wherein the channel state information (CSI) reporting configuration is for semi-persistent CSI reporting of the physical uplink shared channel (PUSCH).

[0344] 7. The method according to Note 6, wherein the first trigger / indication / activation state list is configured through RRC, and the first trigger / indication / activation state list includes a group of X1 trigger (indication / activation) states.

[0345] 8. The method according to any one of Notes 1 to 5, wherein the channel state information (CSI) reporting configuration is for non-periodic CSI reporting of the physical uplink shared channel (PUSCH).

[0346] 9. The method according to Note 8, wherein a second trigger / indication / activation state list is configured through RRC, and the second trigger / indication / activation state list includes a group of X2 trigger (indication / activation) states.

[0347] 10. A method according to any one of Notes 6 to 9, wherein a trigger (indication / activation) state is associated with at least one CSI reporting configuration index and / or at least one CSI-RS resource index and / or at least one sub-configuration.

[0348] 11. The method according to any one of Notes 1 to 10, wherein the indication information is downlink control information (DCI).

[0349] 12. The method according to Note 11, wherein the downlink control information (DCI) is user-specific (UE-specific) and the downlink control information is scrambled by the first RNTI.

[0350] 13. The method according to Note 12, wherein the first RNTI is an RNTI related to network energy saving that is different from SP-CSI-RNTI or C-RNTI.

[0351] 14. The method according to Note 12, wherein the first RNTI is SP-CSI-RNTI or C-RNTI.

[0352] 15. The method according to Note 12, wherein the downlink control information (DCI) is DCI format 0_1 ​​or DCI format 0_2; the CSI request field (CSI request field) and / or the first indication field (sub-CSI indication field) in the downlink control information (DCI) are used to activate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0353] 16. The method according to Note 15, wherein, for semi-continuous CSI reporting based on PUSCH, according to a special field in the downlink control information (DCI), the CSI request field and / or the first indication field in the downlink control information (DCI) are used to activate / deactivate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

[0354] 17. The method according to Note 16, wherein the special field in the downlink control information (DCI) is one or more existing fields in the DCI, including a semi-persistent CSI activation / deactivation PDCCH verification field.

[0355] 18. The method according to Note 16, wherein the special field in the downlink control information (DCI) is a field related to network energy saving that is different from the semi-persistent CSI activation / deactivation PDCCH verification field.

[0356] 19. The method according to any one of Notes 1 to 18, wherein the method further comprises:

[0357] The terminal device receives a first DCI encrypted by SP-CSI-RNTI, the CSI request field of the first DCI is associated with a semi-persistent CSI report with the same identifier as the CSI reporting configuration, and the semi-persistent CSI report is activated by a second DCI encrypted by SP-CSI-RNTI received previously, then the first DCI is used to retrigger / indicate / activate the sub-configuration during the activation period of the semi-persistent CSI report.

[0358] 20. The method according to supplementary note 19, wherein the information of the sub-configuration re-triggering / indication / activation overrides the triggering / indication / activation of the previous sub-configuration;

[0359] After the semi-persistent CSI reporting is deactivated, the sub-configuration re-triggering / indication / activation information is released / deactivated / deactivated.

[0360] 21. A method according to any one of Notes 12 to 20, wherein the size / number of bits of the first indication field (e.g., sub-CSI indication field) in the downlink control information (DCI) is predefined or configured through RRC signaling.

[0361] 22. The method according to Note 21, wherein the number of bits of the first indication field is log2X; X is the number of trigger (indication / activation) states.

[0362] The bit values ​​correspond to the trigger (indication / activation) states in the order of the trigger state positions.

[0363] 23. The method according to note 21, wherein the codepoints of the first indication field in the downlink control information are mapped to trigger (indication / activation) states in the order of the positions of the trigger states;

[0364] Among them, codepoint "0" or codepoint "1" is mapped to the trigger / indication / activation state of the first position.

[0365] 24. The method according to any one of Notes 12 to 20, wherein the first indication field (sub-CSI indication field) in the downlink control information (DCI) is a bitmap.

[0366] 25. The method according to note 24, wherein the number of bits in the first indication field is X; X is the number of trigger (indication / activation) states;

[0367] The bit positions correspond to the trigger (indication / activation) states in sequence.

[0368] 26. The method according to note 24, wherein the bits from the most significant bit (MSB) to the least significant bit (LSB) of the bitmap correspond to the first to the last trigger / indication / activation state, respectively;

[0369] Among them, 1 represents the triggering / indication / activation of the sub-configuration, and 0 represents the release / deactivation / deactivation of the sub-configuration.

[0370] 27. The method according to Note 11, wherein the downlink control information (DCI) is group common signaling, and the downlink control information is scrambled by a second RNTI.

[0371] 28. The method according to Note 27, wherein the group common signaling includes multiple blocks, each block corresponds to a terminal device, and the group common signaling is used to trigger / indicate / activate a sub-configuration of at least one terminal device.

[0372] 29. The method according to Note 28, wherein the block is used to indicate the CSI reporting configuration index and / or at least one sub-configuration of the terminal device, and a codepoint or bitmap is used in the block to indicate the sub-configuration, and the bit value / position corresponds to the trigger (indication / activation) status in sequence.

[0373] 30. The method according to Note 28, wherein the bit width of the block is related to the number of sub-configurations of the terminal device and / or the bit width of the CSI reporting configuration index.

[0374] 31. A method according to any one of Notes 28 to 30, wherein the second RNTI is determined according to the first parameter, the payload size of the downlink control information is determined according to the fourth parameter; the starting position of the corresponding block information of the terminal device in the downlink control information (DCI) is determined according to the second parameter; the bit width of the corresponding block of the terminal device in the downlink control information (DCI) is determined according to the third parameter; and the CSI reporting configuration index bit width of the terminal device is determined according to the fifth parameter.

[0375] 32. A method according to any one of Notes 1 to 5, wherein the channel state information (CSI) reporting configuration is for semi-persistent CSI reporting of the physical uplink control channel (PUCCH).

[0376] 33. The method according to Note 32, wherein the indication information is a medium access control (MAC) control element (CE), and the MAC CE activates or deactivates at least one sub-configuration of the multiple sub-configurations.

[0377] 34. According to the method described in Note 32, a third trigger / indication / activation list is configured through RRC, and a row in the third trigger / indication / activation list corresponds to a CSI reporting configuration index and / or at least one CSI-RS resource index or at least one sub-configuration.

[0378] 35. A method for indicating channel state information (CSI), comprising:

[0379] The network device sends a channel state information (CSI) reporting configuration, where the channel state information (CSI) reporting configuration is related to L CSIs, the channel state information (CSI) reporting configuration includes S sub-configurations, where 1≤S≤L, and one sub-configuration of the S sub-configurations corresponds to at least one channel state information (CSI);

[0380] The network device sends indication information, where the indication information is used to trigger (indicate / activate) at least one sub-configuration among the S sub-configurations.

[0381] 36. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the channel state information indication method as described in any one of Notes 1 to 34.

[0382] 37. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the channel state information indication method as described in Note 35.

Claims

1. A device for indicating channel state information, the device comprising: a first receiving unit configured to receive a channel state information reporting configuration, where the channel state information reporting configuration is related to L CSIs, the channel state information reporting configuration including S sub-configurations, where S is greater than or equal to 1 and less than or equal to L, and one of the S sub-configurations corresponds to at least one channel state information; A second receiving unit is configured to receive indication information, where the indication information is used to trigger / indicate / activate at least one sub-configuration among the S sub-configurations.

2. The device according to claim 1, wherein The number of PUSCH-based semi-persistent CSI reporting configurations containing at least one sub-configuration is H, and / or the number of PUSCH-based non-periodic CSI reporting configurations containing at least one sub-configuration is Q, and / or the number of PUCCH-based semi-persistent CSI reporting configurations containing at least one sub-configuration is R, where H, Q and R are positive integers.

3. The device according to claim 1, wherein The device further comprises: a processing unit configured to perform channel measurement according to M sub-configurations among the triggered / indicated / activated S sub-configurations; and A sending unit sends a channel state information report, where the channel state information report includes N channel state information; wherein the M sub-configurations correspond to the N channel state information, and M is greater than or equal to 1 and less than or equal to N.

4. The device according to claim 1, wherein The one sub-configuration includes at least one of the following information: parameter N1; parameter N2; parameter Ng; codebook subset restriction; port information, the port information is used to indicate part of the ports of the channel state information reference signal resource associated with the channel state information reporting configuration; The sub-configuration is included in the sub-configuration information of the channel state information reporting configuration, or included in the codebook configuration information of the channel state information reporting configuration, or included in the parameter configuration information of the channel state information reporting configuration.

5. The device according to claim 1, wherein The channel state information reporting configuration is for semi-persistent CSI reporting of a physical uplink shared channel; a first trigger / indication / activation state list is configured through radio resource control, wherein the first trigger / indication / activation state list includes a group of X1 trigger / indication / activation states; Alternatively, the channel state information reporting configuration is for aperiodic channel state information reporting of a physical uplink shared channel; a second trigger / indication / activation state list is configured through radio resource control, wherein the second trigger / indication / activation state list includes a group of X2 trigger / indication / activation states; Among them, one trigger / indication / activation state is associated with at least one channel state information reporting configuration index / identifier / information, and / or, at least one channel state information reference signal resource index / identifier / information, and / or, at least one sub-configuration.

6. The device according to claim 1, wherein The indication information is downlink control information; The downlink control information is user-specific and is encrypted by a first RNTI; wherein the first RNTI is an RNTI related to network energy saving that is different from SP-CSI-RNTI or C-RNTI, or the first RNTI is SP-CSI-RNTI or C-RNTI.

7. The device according to claim 6, wherein The downlink control information is DCI format 0_1 ​​or DCI format 0_2; the CSI request field and / or the first indication field in the downlink control information is used to activate at least one CSI report and / or indicate at least one sub-configuration of multiple sub-configurations.

8. The device according to claim 7, wherein For PUSCH-based semi-persistent CSI reporting, according to a specific field in the downlink control information, the CSI request field and / or the first indication field in the downlink control information are used to activate / deactivate at least one CSI report and / or indicate at least one sub-configuration of the multiple sub-configurations.

9. The device according to claim 8, wherein The specific fields in the downlink control information are one or more existing fields in the DCI, including a semi-persistent CSI activation / deactivation PDCCH verification field; Alternatively, the specific field in the downlink control information is a field related to network energy saving that is different from the semi-persistent CSI activation / deactivation PDCCH verification field.

10. The device according to claim 1, wherein The second receiving unit also receives a first DCI encrypted by SP-CSI-RNTI, the CSI request field of the first DCI is associated with a semi-persistent CSI report with the same identifier as the CSI reporting configuration, and the semi-persistent CSI report is activated by a second DCI encrypted by SP-CSI-RNTI received previously, then the first DCI is used to retrigger / indicate / activate the sub-configuration during the activation period of the semi-persistent CSI report.

11. The device according to claim 10, wherein The information of the sub-configuration re-triggering / indication / activation covers the triggering / indication / activation of the previous sub-configuration; after the semi-persistent CSI report is deactivated, the information of the sub-configuration re-triggering / indication / activation is released / deactivated / deactivated.

12. The device according to claim 7, wherein The size / number of bits of the first indication field in the downlink control information is predefined or configured through RRC signaling; the number of bits of the first indication field is log2X; X is the number of trigger / indication / activation states; wherein the bit value corresponds to the trigger / indication / activation state in the order of the trigger state position; The code points of the first indication field in the downlink control information are mapped to the trigger / indication / activation state in the order of the trigger state position; wherein, codepoint "0" or codepoint "1" is mapped to the trigger / indication / activation state at the first position.

13. The device according to claim 7, wherein The first indication field in the downlink control information is a bitmap; wherein the number of bits in the first indication field is X; X is the number of trigger / indication / activation states; wherein the bit positions correspond to the trigger / indication / activation states in sequence; The bits from the most significant bit to the least significant bit of the bitmap correspond to the first to the last trigger / indication / activation status respectively; wherein 1 represents the triggering / indication / activation of the subconfiguration, and 0 represents the release / deactivation / deactivation of the subconfiguration.

14. The device according to claim 1, wherein The indication information is downlink control information, the downlink control information is group common signaling, and the downlink control information is scrambled by the second RNTI; The group common signaling includes multiple blocks, each block corresponds to a terminal device, and the group common signaling is used to trigger / indicate / activate a sub-configuration of at least one terminal device.

15. The device according to claim 14, wherein The block is used to indicate the channel state information reporting configuration index and / or at least one sub-configuration of the terminal device, and a code point or bitmap is used in the block to indicate the sub-configuration, and the bit value / position corresponds to the trigger / indication / activation state in sequence; the bit width of the block is related to the number of sub-configurations of the terminal device and / or the channel state information reporting configuration index bit width.

16. The device according to claim 14, wherein The second RNTI is determined according to the first parameter, and the payload size of the downlink control information is determined according to the fourth parameter; the starting position of the corresponding block information of the terminal device in the downlink control information is determined according to the second parameter; the bit width of the corresponding block of the terminal device in the downlink control information is determined according to the third parameter; the CSI reporting configuration index bit width of the terminal device is determined according to the fifth parameter.

17. The device according to claim 1, wherein The channel state information reporting configuration is for semi-persistent CSI reporting of the physical uplink control channel; The indication information is a medium access control element, and the medium access control element activates or deactivates at least one sub-configuration among the multiple sub-configurations.

18. The device according to claim 17, wherein A third trigger / indication / activation list is configured through RRC, where a row in the third trigger / indication / activation list corresponds to a CSI reporting configuration index and / or at least one CSI-RS resource index or at least one sub-configuration.

19. A device for indicating channel state information, the device comprising: a first sending unit configured to send a channel state information reporting configuration, where the channel state information reporting configuration is related to L CSIs, the channel state information reporting configuration including S sub-configurations, where S is greater than or equal to 1 and less than or equal to L, and one of the S sub-configurations corresponds to at least one channel state information; The second sending unit sends indication information, which is used to trigger / indicate / activate the S sub-configurations. At least one sub-configuration in the configuration.

20. A communication system comprising: A network device that sends channel state information reporting configuration and indication information; as well as A terminal device receiving the channel state information reporting configuration and the indication information; The channel state information reporting configuration is related to L CSIs, and the channel state information reporting configuration includes S sub-configurations, where S is greater than or equal to 1 and less than or equal to L, and one sub-configuration in the S sub-configurations corresponds to at least one channel state information; the indication information is used to trigger / indicate / activate at least one sub-configuration in the S sub-configurations.

Citation Information

Patent Citations

  • User terminal and wireless communication method

    CN111512665A

  • User terminal and wireless communication method

    CN112514480A

  • Method and device for aperiodic channel state information reporting, and related equipment

    CN114765515A

  • Method and apparatus in node used for wireless communication

    CN115378558A

  • Method and device for transmitting channel state information

    WO2021082013A1