Channel information sending method, channel information receiving method and related equipment

Abstract

The present application discloses a channel information transmission method, a channel information reception method, and related devices, belonging to the field of communications technology. The channel information transmission method includes: a terminal receiving a first downlink authorization, the first downlink authorization being used to indicate the reporting of channel state information (CSI); and the terminal transmitting a CSI report on a target physical uplink shared channel (PUSCH) resource. The present application can trigger the terminal to report a CSI report via a downlink authorization, thereby reducing downlink signaling overhead while timely updating channel information and improving data transmission reliability.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a channel information sending method, a channel information receiving method and related equipment. Background Art

[0002] Network-side devices schedule downlink data transmission based on the Channel State Information (CSI) reported by terminals. In the prior art, terminals typically report CSI periodically. However, when reporting CSI periodically, the CSI used by network-side devices to schedule downlink data transmission may be outdated if the reporting period is long, resulting in low data transmission reliability. Summary of the Invention

[0003] The embodiments of the present application provide a channel information sending method, a channel information receiving method, and related devices, which can solve the problem of low data transmission reliability caused by the terminal periodically reporting CSI.

[0004] In a first aspect, a method for sending channel information is provided, the method comprising:

[0005] The terminal receives a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI;

[0006] The terminal sends a CSI report on a target physical uplink shared channel PUSCH resource.

[0007] In a second aspect, a method for receiving channel information is provided, the method comprising:

[0008] The network side device sends a first downlink grant, where the first downlink grant is used to instruct CSI reporting;

[0009] The network side device receives the CSI report on the target PUSCH resource.

[0010] According to a third aspect, a channel information sending device is provided, including:

[0011] A first receiving module, configured for a terminal to receive a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI;

[0012] The first sending module is configured to send a CSI report by the terminal on a target physical uplink shared channel PUSCH resource.

[0013] In a fourth aspect, a channel information receiving device is provided, comprising:

[0014] A second sending module, configured for a network-side device to send a first downlink authorization, where the first downlink authorization is used to indicate a report of the CSI;

[0015] The second receiving module is used for the network side device to receive the CSI report on the target PUSCH resource.

[0016] In a fifth aspect, a terminal is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0017] In the sixth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and runnable on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0018] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0019] In the eighth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run network-side device programs or instructions to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0020] In this embodiment of the present application, the network device can send a downlink grant to instruct CSI reporting; the terminal can respond to the downlink grant by sending a CSI report on the target PUSCH resource. In this way, when scheduling downlink data transmission, the network device can trigger the terminal to report CSI through the downlink grant, thereby saving downlink signaling overhead while timely updating channel information and improving data transmission reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0022] Figure 2 This is a flow chart of a method for sending channel information provided by an embodiment of the present application;

[0023] Figure 3 This is a schematic diagram of information transmission provided by an embodiment of the present application;

[0024] Figure 4 is a flow chart of a channel information receiving method provided in an embodiment of the present application;

[0025] Figure 5 is a structural diagram of a channel information sending device provided in an embodiment of the present application;

[0026] Figure 6 is a structural diagram of a channel information receiving device provided in an embodiment of the present application;

[0027] Figure 7 is a structural diagram of a communication device provided in an embodiment of the present application;

[0028] Figure 8 is a structural diagram of a terminal provided in an embodiment of the present application;

[0029] Figure 9 This is a structural diagram of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects. For example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0032] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions. These technologies can also be applied to applications other than NR system applications, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0033] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (UE). The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal-side devices. Wearable devices include: bracelets, headphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, where the base station can be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other appropriate term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary.

[0034] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0035] 1. Service scenarios in New Radio (NR)

[0036] During the NR technology standardization process, three main use cases were considered: enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). These three use cases have significantly different performance requirements in terms of data rate, latency, reliability, number of connections, traffic density, and mobility. eMBB scenarios focus on data rate and traffic density, mMTC scenarios on number of connections, and URLLC scenarios on latency and reliability. Because these scenarios are closely related to service attributes and bearer requirements, they will be referred to as service scenarios.

[0037] 2. Triggering and feedback of aperiodic CSI in NR.

[0038] The NR communication system supports a downlink aperiodic CSI reporting mechanism. For example, the base station can use the uplink scheduling downlink control information (DCI) to trigger the transmission of downlink CSI on the scheduled physical uplink shared channel (PUSCH) as needed.

[0039] The base station can pre-configure an aperiodic trigger state list (Aperiodic Trigger State List) for the UE through Radio Resource Control (RRC) signaling. Each state corresponds to an associated reporting configuration information list. Each reporting configuration information specifies how to report and which CSI-RS resource sets to use.

[0040] Uplink scheduling DCI, DCI format (Format) 0_1, can specifically indicate which pre-configured aperiodic triggering state is actually triggered through the "CSI request" field, and the corresponding CSI reporting information is carried on the scheduled PUSCH.

[0041] The offset K2 (in time slots) between the time slot where the scheduled PUSCH is located and the time slot where the uplink scheduled DCI is located is determined as follows:

[0042] When the PUSCH carries a transport block (TB) and does not carry / carries downlink aperiodic CSI reporting information, the "Time domain resource assignment" field is used as an index to determine the effective row in the pre-configured or specified table, and the time slot offset in the effective row is taken as the applied K2 value.

[0043] When PUSCH does not carry transport blocks and only carries downlink aperiodic CSI reporting information, the "Time domain resource assignment" field is first used as an index to determine the effective reporting time slot offset in the reporting time slot offset list of each reporting configuration information in the reporting configuration information list corresponding to the actually triggered aperiodic trigger state, and then the maximum value of these one or more reporting time slot offsets (number of reporting time slot offsets = number of reporting configuration information items in the list) is taken as the applied K2 value.

[0044] Considering the high computational overhead of CSI, the time position requirement for the first uplink symbol of the PUSCH carrying the CSI report must not be earlier than any of the following symbol positions:

[0045] T proc,CSI =(Z)(2048+144)·κ2 -μ ·T C The first uplink symbol after that, Z is the end time relative to the triggering DCI;

[0046] T' proc,CSI =(Z')(2048+144)·κ2 -μ ·T C For the first uplink symbol after the measurement, Z' is the end time of the last symbol occupied by the latest resource in the non-periodic measurement resources used.

[0047] The values ​​of Z and Z' mentioned above may refer to the corresponding values ​​in Table 1 or Table 2 in different situations.

[0048] Table 1: CSI computation delay requirement1

[0049]

[0050] Table 2: CSI computation delay requirement2

[0051]

[0052] When the scheduled PUSCH does not meet the above time position requirements, the UE may ignore the corresponding aperiodic CSI reporting (when not multiplexed with HARQ-ACK or TB), or not update the corresponding CSI information.

[0053] See also Figure 2 , Figure 2 1 is a flow chart of a method for sending channel information provided by an embodiment of the present application. The method for sending channel information according to an embodiment of the present application can be executed by a terminal.

[0054] like Figure 2 As shown, the channel information sending method may include the following steps:

[0055] Step 201: The terminal receives a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information (CSI).

[0056] In the embodiment of the present application, a downlink grant (DL grant) may be used to indicate the reporting of CSI, that is, the downlink grant may trigger the reporting of CSI.

[0057] In a specific implementation, the downlink authorization for indicating the reporting of the CSI may be: downlink control information (DCI) or a media access control (MAC) control element (CE), but is not limited thereto.

[0058] like Figure 3 As shown, the DL grant can be used to schedule the Physical Downlink Shared Channel (PDSCH) and trigger the reporting of CSI.

[0059] In addition, Figure 3 In the DL grant, the CSI report (CSI report) triggered by the DL grant can be transmitted through the Physical Uplink Shared Channel (PUSCH). The Hybrid Automatic Repeat Request (HARQ) feedback information corresponding to the PDSCH scheduled by the DL grant can be transmitted through the Physical Uplink Control Channel (PUCCH). The network-side device can also send a Reference Signal (RS), such as CSI-RS, for channel or interference measurement to obtain the CSI report.

[0060] It should be noted that Figure 3 The DL grant in the example is only an example. In other embodiments, the DL grant may be a DL grant that does not schedule a PDSCH. For example, the DL grant may be a DCI for triggering a one-shot HARQ-ACK codebook, or a DCI for triggering a dormancy indication for a secondary cell (SCell).

[0061] Step 202: The terminal sends a CSI report on a target physical uplink shared channel (PUSCH) resource.

[0062] In actual applications, after receiving a downlink grant, the terminal can detect whether the received downlink grant is used to indicate CSI reporting. If the received downlink grant is used to indicate CSI reporting, the CSI report can be sent on the target PUSCH resource; otherwise, the process can be terminated.

[0063] In this embodiment of the present application, in addition to sending a CSI report on the target PUSCH resource, the terminal may also send at least one of the following on the target PUSCH resource: HARQ feedback information corresponding to the PDSCH scheduled by the first uplink grant; and other uplink data. This improves the utilization of the target PUSCH resource and reduces uplink signaling overhead.

[0064] In the channel information transmission method of the embodiment of the present application, a terminal can transmit a CSI report on a target PUSCH resource in response to a received first downlink grant indicating CSI reporting. In this way, when scheduling downlink data transmission, the network-side device can trigger the terminal to report a CSI report through the downlink grant, thereby saving downlink signaling overhead while timely updating channel information and improving data transmission reliability.

[0065] In an embodiment of the present application, a physical uplink shared channel (PUSCH) resource may include at least one transmission parameter. Optionally, the PUSCH resource may include at least one of the following transmission parameters:

[0066] Time domain resources; frequency domain resources; frequency domain hopping parameters; Demodulation Reference Signal (DMRS) configuration / parameters; Precoder and number of layers; Sounding Reference Signal (SRS) resource indicator; Antenna port number; Modulation and Coding Scheme (MCS); Uplink transmission waveform; Beta offset value (Beta-offset) for uplink control information (UCI) multiplexing; Open-loop power control parameters; Closed-loop power control parameters; HARQ process number; Number of HARQ processes; Redundant Version (RV); Number of repetitions.

[0067] Furthermore, frequency domain resources may include the size of a resource block group (RBG); frequency domain frequency hopping parameters may include a frequency hopping mode and a frequency hopping offset; DMRS configuration / parameters may include DMRS sequence initialization parameters; and open-loop power control parameters may include P0 and / or α.

[0068] In the embodiment of the present application, the transmission parameters of the PUSCH resources may be configured by a network-side device and / or predefined by a protocol.

[0069] In the embodiment of the present application, the network side device can configure the transmission parameters of the PUSCH resource through the downlink grant. It can be seen that in the embodiment of the present application, the downlink grant can also be used to indicate the transmission parameters of the PUSCH resource.

[0070] Of course, in the embodiment of the present application, the network side device can also configure the transmission parameters of the PUSCH resource through other downlink information, such as at least one of RRC signaling, MACCE, etc. The specific configuration can be determined according to actual conditions, and the embodiment of the present application does not limit this.

[0071] Based on the above, it can be understood that, optionally, the transmission parameters of the target PUSCH resource can be determined by at least one of the following: the first downlink grant indication, a radio resource control (RRC) signaling configuration, or a protocol pre-defined parameter. This can improve the flexibility and richness of determining the transmission parameters of the target PUSCH resource.

[0072] In the above optional implementation manner, the downlink authorization used to trigger CSI reporting and the downlink authorization used to indicate the transmission parameters of PUSCH resources are the same downlink authorization. It should be noted that in other implementation manners, the downlink authorization used to trigger CSI reporting and the downlink authorization used to indicate the transmission parameters of PUSCH resources may be different downlink authorizations, which may be determined according to actual circumstances and are not limited in this embodiment of the present application.

[0073] Optionally, the time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers;

[0074] The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

[0075] In this optional implementation manner, the time domain resource of the target PUSCH resource is determined based on the first time domain resource. The relationship between the time domain resource of the target PUSCH resource and the first time domain resource is described as follows:

[0076] In a first implementation manner, the time domain resource of the target PUSCH resource may be the first time domain resource.

[0077] In a second implementation manner, the time domain resource of the target PUSCH resource may be the first available uplink time domain resource after the first time domain resource.

[0078] In the above-mentioned second implementation method, the first available uplink time domain resource after the first time domain resource can be determined according to at least one of the following: semi-static time division duplex (TDD) configuration; dynamic TDD configuration; RRC configuration, which can be determined according to actual conditions, and the embodiment of the present application does not limit this.

[0079] In this optional implementation, the first time domain resource is determined based on P reference time points and Q time domain offsets.

[0080] In a specific implementation, the first time domain resource can be determined based on some or all of the P reference moments and / or some or all of the Q time domain offsets. The determination of the first time domain resource is described below:

[0081] Optionally, the determination of the first time domain resource satisfies at least one of the following:

[0082] 1) The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in chronological order; the first time domain offset is: the maximum time domain offset among S time domain offsets, or the sum of the S time domain offsets;

[0083] 2) The first time domain resource is the last time domain resource of L time domain resources arranged in chronological order, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different;

[0084] Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

[0085] In 1), the following implementations may be included:

[0086] Implementation method 1: The first reference moment is the last reference moment after T reference moments are arranged in order from earliest to latest; the first time domain offset is the maximum time domain offset among the S time domain offsets.

[0087] Implementation method 2: The first reference moment is the last reference moment after T reference moments are arranged in order from earliest to latest; the first time domain offset is the sum of the S time domain offsets.

[0088] For easier understanding, the following examples are provided:

[0089] Assume that the T reference moments include 3 reference moments, and the 3 reference moments are arranged in order from earliest to thickest time: reference moment 1, reference moment 2, and reference moment 3; the S time domain offsets include 2 time domain offsets, namely time domain offset 1 and time domain offset 2, and time domain offset 1 is greater than time domain offset 2.

[0090] Then, for the above implementation method 1, the first time domain resource is located after the reference time 3 and is separated from the reference time 3 by a time domain offset 1. For the above implementation method 2, the first time domain resource is located after the reference time 3 and is separated from the reference time 3 by a time domain offset 1 and a time domain offset 2.

[0091] In 2), the following implementations may be included:

[0092] Implementation method a: When S is equal to T, optionally, each of the L time domain resources can be determined based on one reference moment among the T reference moments and one time domain offset among the S time domain offsets, and the reference moments and time domain offsets of different time domain resources are determined to be different. In this implementation, L, S and T are all equal.

[0093] For example, it is assumed that the T reference moments include two reference moments, namely reference moment 1 and reference moment 2; and the S time domain offsets include two time domain offsets, namely time domain offset 1 and time domain offset 2.

[0094] Then, the L time domain resources may include time domain resource 1 and time domain resource 2. Optionally, time domain resource 1 = reference time 1 + time domain offset 1, that is, time domain resource 1 may be located after reference time 1 and be separated from reference time 1 by time domain offset 1; time domain resource 2 = reference time 2 + time domain offset 2, that is, time domain resource 2 may be located after reference time 2 and be separated from reference time 2 by time domain offset 2.

[0095] Implementation method b: When S is greater than T, optionally, the method for determining T-1 time domain resources among the L time domain resources can be the same as the method for determining the time domain resources in implementation method a; the remaining time domain resources can be determined based on unused reference time and time domain offset.

[0096] For example, it is assumed that the T reference moments include two reference moments, namely reference moment 1 and reference moment 2; and the S time domain offsets include three time domain offsets, namely time domain offset 1, time domain offset 2, and time domain offset 3.

[0097] Then, the L time domain resources may include time domain resource 1 and time domain resource 2. Optionally, time domain resource 1 = reference time 1 + time domain offset 1; time domain resource 2 = reference time 2 + time domain offset 2 + time domain offset 3, that is, time domain resource 2 may be located after reference time 2, and be separated from reference time 2 by time domain offset 2 and time domain offset 3.

[0098] Implementation method c: When S is less than T, optionally, the method for determining S time domain resources among the L time domain resources can be the same as the method for determining the time domain resources in implementation method a; the remaining time domain resources can be determined based on unused reference moments.

[0099] For example, it is assumed that the T reference moments include three reference moments, namely reference moment 1, reference moment 2, and reference moment 3; and the S time domain offsets include two time domain offsets, namely time domain offset 1 and time domain offset.

[0100] Then, the L time domain resources may include time domain resource 1, time domain resource 2 and time domain resource 3. Optionally, time domain resource 1 = reference time 1 + time domain offset 1; time domain resource 2 = reference time 2 + time domain offset 2; time domain resource 3 = reference time 3 + time domain offset 1 + time domain offset 2, or, time domain resource 3 = reference time 3 + time domain offset 1, or, time domain resource 3 = reference time 3 + time domain offset 2.

[0101] It should be noted that the implementation in 2) is only an example and does not limit the protection scope of 2). The unit of time domain resources can be a time slot, a sub-time slot, or a symbol, etc., which can be determined according to actual conditions and is not limited in this embodiment of the application.

[0102] The following describes the Q time domain offsets and P reference moments:

[0103] 1. For Q time domain offsets.

[0104] The Q time domain offsets may be configured by the network side and / or predefined by a protocol. Optionally, the Q time domain offsets are determined by at least one of the following: the first downlink grant indication; RRC signaling configuration; or protocol predefined.

[0105] In the above optional implementation manner, the downlink authorization used to trigger CSI reporting and the downlink authorization used to indicate the time domain offset are the same downlink authorization. It should be noted that in other implementation manners, the downlink authorization used to trigger CSI reporting and the downlink authorization used to indicate the time domain offset may be different downlink authorizations, which may be determined based on actual circumstances and are not limited in this embodiment of the present application.

[0106] Optionally, the Q time domain offsets may be determined according to processing time;

[0107] The processing time is: CSI calculation time; or PDSCH processing time. PDSCH processing time can be understood as the time defined by the protocol for receiving PDSCH.

[0108] In specific implementation, in one implementation, the processing time can be directly determined as the time domain offset; in another implementation, the time domain offset can be determined based on the processing time and timing advance (TA). Optionally, time domain offset = processing time + TA, but is not limited to this.

[0109] 2. For P reference moments.

[0110] Optionally, the P reference moments may include at least one of the following:

[0111] a time at which the first downlink authorization is received;

[0112] a transmission time of hybrid automatic repeat request HARQ feedback information, where the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant;

[0113] A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

[0114] In a specific implementation, the first reference signal may be a reference signal used for channel measurement, such as CSI-RS; or a reference signal used for interference measurement, such as CSI Interference Measurement (CSI-IM).

[0115] In the embodiment of the present application, there may be one or more PUSCH resources used to transmit the CSI report. If there is only one PUSCH resource used to transmit the CSI report, the target PUSCH resource is that PUSCH resource; if there are multiple PUSCH resources used to transmit the CSI report, the target PUSCH resource is one of the multiple PUSCH resources.

[0116] Optionally, the target PUSCH resource is any one of the following:

[0117] a) PUSCH resources corresponding to the identification information of the first downlink grant indication;

[0118] b) PUSCH resources associated with the CSI report;

[0119] c) The terminal determines a PUSCH resource according to the payload size reported by the CSI.

[0120] In the embodiment of the present application, the downlink grant may also be used to indicate the PUSCH resource for transmitting the CSI report. Therefore, in a), the target PUSCH resource is indicated by the downlink grant.

[0121] During specific implementation, the first downlink grant indicates the PUSCH resource used for transmitting the CSI report by indicating identification information corresponding to the PUSCH resource.

[0122] For example, assuming that the PUSCH resources used to transmit the CSI report include PUSCH resource 1 and PUSCH resource 2, the identification information corresponding to PUSCH resource 1 is identification information 1, and the identification information corresponding to PUSCH resource 2 is identification information 2. Then, if the first downlink grant indicates identification information 1, the terminal can send the CSI report on PUSCH resource 1.

[0123] In a), the first downlink grant can be used not only to trigger CSI reporting, but also to indicate the PUSCH resources used to transmit the CSI report. That is, the downlink grant used to trigger CSI reporting and the downlink grant used to indicate the PUSCH resources used to transmit the CSI report are the same downlink grant. However, it is understandable that in other implementations, the downlink grant used to trigger CSI reporting and the downlink grant used to indicate the PUSCH resources used to transmit the CSI report can be different downlink grants, which can be determined based on actual circumstances and are not limited in this embodiment of the present application.

[0124] In b), the target PUSCH resource is determined by the CSI report triggered by the downlink grant. In specific implementation, one downlink grant can trigger the reporting of multiple CSI reports, and the multiple CSI reports are associated with the PUSCH resource. In this association, one PUSCH resource can be associated with one or more CSI reports.

[0125] For example, assuming that downlink grant 1 is used to trigger the reporting of CSI report 1 and CSI report 2, CSI report 1 is associated with PUSCH resource 1, and CSI report 2 is associated with PUSCH resource 2.

[0126] Then, after receiving downlink grant 1, the terminal sends CSI report 1 in PUSCH resource 1 and sends CSI report 2 in PUSCH resource 2.

[0127] In c), the target PUSCH resource is determined by the terminal based on the payload size of the reported CSI report. For example, assuming that the payload size of CSI report 1 is in the first interval and the PUSCH resource corresponding to the first interval is PUSCH resource 1, then the terminal sends CSI report 1 on PUSCH resource 1.

[0128] In an embodiment of the present application, the CSI report sent by the terminal may include at least one of the following: channel quality indicator (COI); precoding matrix indicator (PMI); rank indicator (RI); CSI-RS resource indicator (CSI-RS Resource Indicator, CRI).

[0129] Optionally, the channel quality indicator (CQI) included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among R CQIs; the variance of the R CQIs; and M CQIs with the smallest values ​​among the R CQIs. The CQI is a subband CQI, where R equals the number of subbands, and N and M are both positive integers less than or equal to R. Of course, the CQI included in the CSI report may be the average of the R CQIs. This shows that the embodiments of the present application improve the flexibility and richness of the CQI included in the CSI report.

[0130] See also Figure 4 , Figure 4 1 is a flow chart of a channel information receiving method provided in an embodiment of the present application. The channel information receiving method in an embodiment of the present application is executed by a network side device.

[0131] like Figure 4 As shown, the channel information receiving method may include the following steps:

[0132] Step 401: The network-side device sends a first downlink authorization, where the first downlink authorization is used to indicate CSI reporting.

[0133] Step 402: The network-side device receives a CSI report on a target PUSCH resource.

[0134] In the channel information receiving method of the embodiment of the present application, the network-side device can send a first downlink grant to instruct CSI reporting and receive the CSI report on the target PUSCH resource. In this way, when scheduling downlink data transmission, the network-side device can trigger the terminal to report the CSI report through the first downlink grant, thereby saving downlink signaling overhead while timely updating channel information and improving data transmission reliability.

[0135] Optionally, the transmission parameters of the target PUSCH resource are determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol predefinition.

[0136] Optionally, the time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers;

[0137] The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

[0138] Optionally, the Q time domain offsets are determined according to processing time;

[0139] The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

[0140] Optionally, the P reference moments include at least one of the following:

[0141] a time at which the first downlink authorization is received;

[0142] a transmission time of hybrid automatic repeat request HARQ feedback information, where the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant;

[0143] A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

[0144] Optionally, the determination of the first time domain resource satisfies at least one of the following:

[0145] The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets;

[0146] The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different;

[0147] Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

[0148] Optionally, the time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

[0149] Optionally, the target PUSCH resource is any one of the following:

[0150] A PUSCH resource corresponding to the identification information of the first downlink grant indication;

[0151] PUSCH resources associated with the CSI report;

[0152] The terminal determines the PUSCH resources according to the payload size reported by the CSI.

[0153] Optionally, the CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs;

[0154] The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

[0155] It should be noted that this embodiment is Figure 2 The embodiments of the network side device corresponding to the method embodiments can therefore be referred to Figure 2 The relevant descriptions in the method embodiment can achieve the same beneficial effects. In order to avoid repeated descriptions, they will not be repeated here.

[0156] The various optional implementation methods introduced in the embodiments of the present application can be implemented in combination with each other or can be implemented separately, and the embodiments of the present application do not limit this.

[0157] For easier understanding, the following examples are provided:

[0158] The network is configured with a PUSCH resource for CSI reporting. This PUSCH is a semi-statically configured PUSCH resource. When a terminal receives a DL grant, it triggers CSI reporting according to the DL grant instructions. After receiving the DL grant that triggers CSI reporting, the UE triggers a CSI report transmission on the corresponding PUSCH resource.

[0159] 1) The PUSCH resource includes one or more of the following transmission parameters:

[0160] Time domain resource allocation; frequency domain resource allocation (including RBG size); frequency domain hopping parameters, including hopping mode and hopping offset; DMRS configuration / parameters (including DMRS sequence initialization parameters); Precoder and layer number; SRS resource indicator; antenna port number; MCS; uplink transmission waveform; Beta-offset; open-loop power control parameters, P0 and / or alpha; closed-loop power control parameters; HARQ process number and / or number of HARQ processes; RV; number of repetitions; etc.

[0161] 2) The transmission parameters included in the PUSCH resource are determined by one or more of the following:

[0162] The DL grant indication; RRC configuration; predefined.

[0163] 3) The PUSCH resource may be one or more PUSCH resources.

[0164] If there are multiple PUSCH resources, the UE selects the target PUSCH resource in the following way:

[0165] 1. The target PUSCH resource is explicitly indicated by the DL grant.

[0166] For example, each PUSCH resource is configured with an index number (index), and the DL grant explicitly indicates the index of the PUSCH resource;

[0167] 2. The target PUSCH resource is determined by the PUSCH associated with the CSI report triggered by the DL grant.

[0168] For example, each CSI report i is associated with a PUSCH resource k, and the association is configured or predefined by the network. For a CSI report i triggered by a DL grant indication, the PUSCH resource is determined based on the PUSCH resource corresponding to the CSI report i.

[0169] 3. The target PUSCH resource is determined by the UE based on the CSI payload size.

[0170] If CSI part 2 is included, the rank is assumed to be 1.

[0171] 4) For the PUSCH time domain resource in 1), at least one of the following is included: starting position, time domain resource length, number of time domain transmission opportunities, end position, etc. The time domain resource can be determined based on the first time (i.e., the aforementioned reference time) and the time domain offset.

[0172] The time domain offset includes at least one of the following:

[0173] Offset 1 indicated by the DL grant; offset 2 configured by RRC; offset 3 predefined by the protocol.

[0174] Optionally, offset3 may be determined according to processing time, such as offset3_1 determined according to CSI calculation time Z, or offset3_2 determined according to PDSCH processing time N1.

[0175] It should be noted that the time domain offset can be 0.

[0176] The first moment may include at least one of the following:

[0177] The reception time of DL grant is t1; the HARQ-ACK transmission time scheduled by DL grant is t2; the reception time of CSI-RS is t3.

[0178] The time domain offset can be one or more items, and the first moment can be one or more items.

[0179] When the time domain offset and the first moment are both one item, the time domain resource can be determined according to the first moment + the time domain offset.

[0180] When the time domain offset is multinomial and the first moment is a single term:

[0181] Option 1: The time domain resources are determined by the first time point + max (time domain offset 1, time domain offset 2, ...);

[0182] Option 2: The time domain resource is determined by the first time + (time domain offset 1 + time domain offset 2, ...);

[0183] When the time domain offset is one item and the first moment is multiple items, the time domain resource is determined according to the latest time domain position among {first moment 1+time domain offset, first moment 2+time domain offset, ...}.

[0184] When the time domain offset is multiple and the first moment is multiple, the time domain resource is determined according to the latest time domain position among {first moment 1+time domain offset 1, first moment 2+time domain offset 2, ...}.

[0185] Optionally, the PUSCH time domain resource is the first available uplink resource (time slot / sub-time slot / symbol) after the time domain position (including the position) determined in the above manner. The uplink resource is an available uplink resource determined according to a semi-static TDD configuration or an RRC configuration.

[0186] For example:

[0187] The PUSCH time domain resource is the time domain position determined by t1+offset1;

[0188] The PUSCH time domain resource is the time domain position determined by t1+offset1+offset2;

[0189] The PUSCH time domain resource is the later time domain position of the two time domain positions determined according to {t1+offset1, t3+offset3};

[0190] The PUSCH time domain resource is the time domain position determined by t1+offset1+d;

[0191] Here, d is the interval between the time domain position determined according to t1+offset1 and the first available uplink resource.

[0192] Optionally, after receiving a DL grant triggering CSI reporting, the UE triggers a CSI reporting transmission on the corresponding PUSCH resource. The CSI reporting includes one or more of the following: CQI; PMI; RI; CRI.

[0193] The CQI may be any of the following: the best N CQIs; the average CQI; the variance CQI; or the worst M CQIs.

[0194] Optionally, the UE may further include at least one of the following items on the corresponding PUSCH resource: HARQ-ACK; uplink data.

[0195] Example 1

[0196] The network configures PUSCH resources for CSI transmission. The configuration information includes one or more of the following transmission parameters (the PUSCH resources are similar to the semi-statically configured PUSCH resources):

[0197] Time domain resource allocation; frequency domain resource allocation; frequency domain hopping parameters, including hopping mode and hopping offset; DMRS configuration / parameters; number of precoders and layers; SRS resource indicator; antenna port number; MCS; uplink transmission waveform; Beta-offset; open-loop power control parameters, P0 and / or alpha; closed-loop power control parameters; HARQ process number and / or number of HARQ processes; RV; number of repetitions; etc.

[0198] When the terminal receives a DL grant, it triggers CSI reporting according to the instruction of the DL grant and instructs the UE to send the CSI report on the PUSCH resources configured by the network.

[0199] In this example, the DL grant is only used to trigger CSI reporting and does not indicate PUSCH resource parameters. PUSCH resource parameters can be configured by RRC.

[0200] Example 2

[0201] The network configures PUSCH resources for CSI transmission. The configuration information includes one or more of the following transmission parameters (the PUSCH resources are similar to the semi-statically configured PUSCH resources):

[0202] Frequency domain resource allocation; frequency domain hopping parameters, including hopping mode and hopping offset; DMRS configuration / parameters; number of precoders and layers; SRS resource indicator; antenna port number; MCS; uplink transmission waveform; Beta-offset; open-loop power control parameters, P0 and / or alpha; closed-loop power control parameters; HARQ process number and / or number of HARQ processes; RV; number of repetitions; etc.

[0203] When the terminal receives a DL grant, it triggers CSI reporting according to the instruction of the DL grant and instructs the UE to send the CSI report on the PUSCH resources configured by the network.

[0204] In this example, the DL grant is used to trigger CSI reporting and also indicates the time domain resource parameters of the PUSCH resources. For example, the DL grant indicates the time domain offset relative to the HARQ-ACK transmission time scheduled by the DL grant, and the time domain resource location of the PUSCH carrying the CSI reporting is determined based on this time domain offset. Other PUSCH resource parameters can be configured by RRC.

[0205] Example 3

[0206] The network configures multiple PUSCH resources for CSI transmission. Each PUSCH configuration information includes one or more of the following transmission parameters (the PUSCH resource is similar to the semi-statically configured PUSCH resource):

[0207] Frequency domain resource allocation; frequency domain hopping parameters, including hopping mode and hopping offset; DMRS configuration / parameters; number of precoders and layers; SRS resource indicator; antenna port number; MCS; uplink transmission waveform; Beta-offset; open-loop power control parameters, P0 and / or alpha; closed-loop power control parameters; HARQ process number and / or number of HARQ processes; RV; number of repetitions; etc.

[0208] When the terminal receives a DL grant, it triggers CSI reporting according to the instruction of the DL grant and instructs the UE to send the CSI report on one of the PUSCH resources configured by the network.

[0209] In this example, the DL grant is used to trigger CSI reporting and also indicates the target PUSCH resources.

[0210] The target PUSCH resource can be determined by the PUSCH associated with the CSI report triggered by the DL grant. For example, each CSI report i is associated with a PUSCH resource k, and this association is configured by the network. For CSI report i triggered by the DL grant indication, the PUSCH resource is determined based on the PUSCH resource corresponding to CSI report i.

[0211] The transmission parameters of the target PUSCH resources may be configured by RRC.

[0212] The embodiments of the present application are applicable to single carrier and multi-carrier, as well as authorized frequency bands or unlicensed frequency bands.

[0213] The embodiments of the present application can trigger aperiodic CSI reporting when scheduling downlink transmission, update channel information in a timely manner, and avoid increasing the overhead of downlink signaling.

[0214] It should be noted that the channel information sending method provided in the embodiments of the present application can be executed by a channel information sending device, or a control module in the channel information sending device for executing the channel information sending method. In the embodiments of the present application, the channel information sending device provided in the embodiments of the present application is described by taking the channel information sending device executing the channel information sending method as an example.

[0215] See also Figure 5 , Figure 5 It is a structural diagram of the channel information sending device provided in an embodiment of the present application.

[0216] like Figure 5 As shown, the channel information sending device 500 includes:

[0217] A first receiving module 501 is configured for a terminal to receive a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI;

[0218] The first sending module 502 is configured for the terminal to send a CSI report on a target physical uplink shared channel PUSCH resource.

[0219] Optionally, the transmission parameters of the target PUSCH resource are determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol predefinition.

[0220] Optionally, the time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers;

[0221] The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

[0222] Optionally, the Q time domain offsets are determined according to processing time;

[0223] The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

[0224] Optionally, the P reference moments include at least one of the following:

[0225] a time at which the first downlink authorization is received;

[0226] a transmission time of hybrid automatic repeat request HARQ feedback information, where the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant;

[0227] A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

[0228] Optionally, the determination of the first time domain resource satisfies at least one of the following:

[0229] The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets;

[0230] The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different;

[0231] Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

[0232] Optionally, the time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

[0233] Optionally, the target PUSCH resource is any one of the following:

[0234] A PUSCH resource corresponding to the identification information of the first downlink grant indication;

[0235] PUSCH resources associated with the CSI report;

[0236] The terminal determines a PUSCH resource according to the payload size of the CSI report.

[0237] Optionally, the channel quality indicator CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs;

[0238] The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

[0239] The channel information receiving device in the embodiments of the present application may be a device, or a component, integrated circuit, or chip in a terminal. The device may be a mobile terminal or a non-mobile terminal. For example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may include servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc., and the embodiments of the present application do not specifically limit this.

[0240] The channel information receiving device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0241] The channel information receiving 500 provided in the embodiment of the present application can achieve Figure 2 The various processes implemented in the method embodiment achieve the same technical effects, and to avoid repetition, they will not be described here.

[0242] It should be noted that the channel information receiving method provided in the embodiments of the present application can be executed by a channel information receiving device, or by a control module in the channel information receiving device for executing the channel information receiving method. In the embodiments of the present application, the channel information receiving device provided in the embodiments of the present application is described by taking the channel information receiving device executing the channel information receiving method as an example.

[0243] See also Figure 6 , Figure 6 It is a structural diagram of the channel information receiving device provided in an embodiment of the present application.

[0244] like Figure 6 As shown, the channel information receiving device 600 includes:

[0245] The second sending module 601 is configured for the network side device to send a first downlink authorization, where the first downlink authorization is used to indicate a CSI report;

[0246] The second receiving module 602 is configured for the network side device to receive a CSI report on a target PUSCH resource.

[0247] Optionally, the transmission parameters of the target PUSCH resource are determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol predefinition.

[0248] Optionally, the time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers;

[0249] The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

[0250] Optionally, the Q time domain offsets are determined according to processing time;

[0251] The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

[0252] Optionally, the P reference moments include at least one of the following:

[0253] a time at which the first downlink authorization is received;

[0254] a transmission time of hybrid automatic repeat request HARQ feedback information, where the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant;

[0255] A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

[0256] Optionally, the determination of the first time domain resource satisfies at least one of the following:

[0257] The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets;

[0258] The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different;

[0259] Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

[0260] Optionally, the time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

[0261] Optionally, the target PUSCH resource is any one of the following:

[0262] A PUSCH resource corresponding to the identification information of the first downlink grant indication;

[0263] PUSCH resources associated with the CSI report;

[0264] The terminal determines the PUSCH resources according to the payload size reported by the CSI.

[0265] Optionally, the CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs;

[0266] The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

[0267] The channel information receiving device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a network side device. The network side device can include but is not limited to the types of network side devices 12 listed above, and the embodiment of the present application does not specifically limit it.

[0268] The channel information receiving device 600 provided in the embodiment of the present application can realize Figure 4 The various processes implemented in the method embodiment achieve the same technical effects, and to avoid repetition, they will not be described here.

[0269] Optional, such as Figure 7As shown, the embodiment of the present application further provides a communication device 700, including a processor 701, a memory 702, and a program or instruction stored in the memory 702 and executable on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction is executed by the processor 701 to implement the above Figure 2 When the communication device 700 is a network side device, the program or instruction is executed by the processor 701 to implement the above Figure 4 The various processes of the method embodiments can achieve the same technical effects, and to avoid repetition, they will not be described here.

[0270] Figure 8 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0271] The terminal 800 includes but is not limited to components such as a radio frequency unit 801 , a network module 802 , an audio output unit 803 , an input unit 804 , a sensor 805 , a display unit 806 , a user input unit 807 , an interface unit 808 , a memory 809 , and a processor 810 .

[0272] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 810 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0273] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processing unit 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 808 includes a touch panel 8081 and other input devices 8082. The touch panel 8081 is also called a touch screen. The touch panel 8081 may include two parts: a touch detection device and a touch controller. Other input devices 8082 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0274] In this embodiment of the present application, the radio frequency unit 801 receives downlink data from the network-side device and transmits it to the processor 810 for processing. Furthermore, the radio frequency unit 801 transmits uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0275] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, at least one application program or instruction required for a function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include a high-speed random access memory and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0276] Processor 810 may include one or more processing units. Optionally, processor 810 may be integrated into an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs or instructions, while the modem processor primarily processes wireless communications, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0277] The radio frequency unit 801 is used to:

[0278] The terminal receives a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI;

[0279] The terminal sends a CSI report on a target physical uplink shared channel PUSCH resource.

[0280] Optionally, the transmission parameters of the target PUSCH resource are determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol predefinition.

[0281] Optionally, the time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers;

[0282] The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

[0283] Optionally, the Q time domain offsets are determined according to processing time;

[0284] The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

[0285] Optionally, the P reference moments include at least one of the following:

[0286] a time at which the first downlink authorization is received;

[0287] a transmission time of hybrid automatic repeat request HARQ feedback information, where the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant;

[0288] A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

[0289] Optionally, the determination of the first time domain resource satisfies at least one of the following:

[0290] The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets;

[0291] The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different;

[0292] Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

[0293] Optionally, the time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

[0294] Optionally, the target PUSCH resource is any one of the following:

[0295] A PUSCH resource corresponding to the identification information of the first downlink grant indication;

[0296] PUSCH resources associated with the CSI report;

[0297] The terminal determines a PUSCH resource according to the payload size of the CSI report.

[0298] Optionally, the channel quality indicator CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs;

[0299] The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

[0300] It should be noted that the terminal 800 in this embodiment can implement the embodiment of this application. Figure 2 The various processes in the method embodiments achieve the same beneficial effects and will not be described again here to avoid repetition.

[0301] Specifically, the embodiment of the present application also provides a network side device. Figure 9 As shown, network device 900 includes an antenna 91, a radio frequency device 92, and a baseband device 93. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0302] The frequency band processing device may be located in the baseband device 93 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 . The baseband device 93 includes a processor 94 and a memory 95 .

[0303] The baseband device 93 may include, for example, at least one baseband board on which a plurality of chips are arranged, such as Figure 9 As shown, one of the chips is, for example, a processor 94, which is connected to a memory 95 to call a program in the memory 95 and execute the network device operations shown in the above method embodiment.

[0304] The baseband device 93 may further include a network interface 96 for exchanging information with the radio frequency device 92 . The interface may be, for example, a common public radio interface (CPRI).

[0305] Specifically, the network side device of the embodiment of the present application further includes: instructions or programs stored in the memory 95 and executable on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute Figure 4 The various processes in the method embodiments achieve the same technical effects and are not described here in detail to avoid repetition.

[0306] The present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, Figure 2 or Figure 4 The various processes of the method embodiments can achieve the same technical effects and are not described here in detail to avoid repetition. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0307] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by the processor, the above Figure 2 or Figure 4 The various processes of the method embodiments can achieve the same technical effects, and to avoid repetition, they will not be described here.

[0308] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0309] The embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a network side device program or instruction to implement the above Figure 2 or Figure 4 The various processes of the method embodiments can achieve the same technical effects, and to avoid repetition, they will not be described here.

[0310] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0311] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0312] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0313] The above-mentioned drawings are used to describe the embodiments of the present application, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, which are all within the protection of the present application.

Claims

1. A method for sending channel information, characterized in that: The method comprises: The terminal receives a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI; The terminal sends a CSI report on a target physical uplink shared channel PUSCH resource; The time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers; The P reference time points include a transmission time point of hybrid automatic repeat request HARQ feedback information, and the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant.

2. The method according to claim 1, characterized in that The transmission parameter of the target PUSCH resource is determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol pre-definition.

3. The method according to claim 1, characterized in that The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

4. The method according to claim 3, characterized in that The Q time domain offsets are determined according to the processing time; The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

5. The method according to claim 3, characterized in that The P reference moments also include at least one of the following: a time at which the first downlink authorization is received; A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

6. The method according to claim 3, characterized in that The determination of the first time domain resource satisfies at least one of the following: The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets; The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different; Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

7. The method according to claim 3, characterized in that The time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

8. The method according to claim 1, characterized in that The target PUSCH resource is any one of the following: A PUSCH resource corresponding to the identification information of the first downlink grant indication; PUSCH resources associated with the CSI report; The terminal determines a PUSCH resource according to the payload size of the CSI report.

9. The method according to claim 1, characterized in that The channel quality indicator CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs; The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

10. A method for receiving channel information, characterized in that: The method comprises: The network side device sends a first downlink grant, where the first downlink grant is used to instruct CSI reporting; The network side device receives the CSI report on the target PUSCH resource; The time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers; The P reference time points include a transmission time point of hybrid automatic repeat request HARQ feedback information, and the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant.

11. The method according to claim 10, characterized in that The transmission parameter of the target PUSCH resource is determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol pre-definition.

12. The method according to claim 10, characterized in that The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

13. The method according to claim 12, characterized in that The Q time domain offsets are determined according to the processing time; The processing time is: CSI calculation time; or physical downlink shared channel PDSCH processing time.

14. The method according to claim 12, characterized in that The P reference moments also include at least one of the following: a time at which the first downlink authorization is received; A reception time of a first reference signal, where the first reference signal is a reference signal corresponding to the CSI report.

15. The method according to claim 12, characterized in that The determination of the first time domain resource satisfies at least one of the following: The first time domain resource is located after a first reference time and is separated from the first reference time by a first time domain offset, where the first reference time is the last reference time after T reference times are arranged in order from earliest to latest; the first time domain offset is: a maximum time domain offset among the S time domain offsets, or a sum of the S time domain offsets; The first time domain resource is the last time domain resource of L time domain resources arranged in order from earliest to latest in time, each time domain resource in the L time domain resources is determined based on at least one reference time of the T reference times and at least one time domain offset of the S time domain offsets, and at least one of the reference time and the time domain offset corresponding to different time domain resources is different; Among them, the T reference moments are T reference moments among the P reference moments, and T is a positive integer less than or equal to P; the S time domain offsets are S time domain offsets among the Q time domain offsets, and S is a positive integer less than or equal to Q; and L is an integer greater than or equal to S or T.

16. The method according to claim 12, characterized in that The time domain resource of the target PUSCH resource is the first available uplink time domain resource after the first time domain resource.

17. The method according to claim 10, characterized in that The target PUSCH resource is any one of the following: A PUSCH resource corresponding to the identification information of the first downlink grant indication; PUSCH resources associated with the CSI report; The terminal determines the PUSCH resources according to the payload size reported by the CSI.

18. The method according to claim 10, wherein: The CQI included in the CSI report includes at least one of the following: N CQIs with the largest values ​​among the R CQIs; variances of the R CQIs; M CQIs with the smallest values ​​among the R CQIs; The CQI is the CQI of the subband, R is equal to the number of subbands, and N and M are both positive integers less than or equal to R.

19. A channel information sending device, characterized in that: include: A first receiving module, configured for a terminal to receive a first downlink grant, where the first downlink grant is used to indicate reporting of channel state information CSI; A first sending module, configured for the terminal to send a CSI report on a target physical uplink shared channel (PUSCH) resource; The time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers; The P reference time points include a transmission time point of hybrid automatic repeat request HARQ feedback information, and the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant.

20. The channel information transmitting device according to claim 19, wherein: The transmission parameter of the target PUSCH resource is determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol pre-definition.

21. The channel information transmitting device according to claim 19, wherein: The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

22. The channel information transmitting device according to claim 19, wherein: The target PUSCH resource is any one of the following: A PUSCH resource corresponding to the identification information of the first downlink grant indication; PUSCH resources associated with the CSI report; The terminal determines a PUSCH resource according to the payload size of the CSI report.

23. A channel information receiving device, characterized in that: include: A second sending module, configured for a network-side device to send a first downlink authorization, where the first downlink authorization is used to indicate a report of the CSI; A second receiving module is configured for the network side device to receive a CSI report on a target PUSCH resource; The time domain resource of the target PUSCH resource is determined based on a first time domain resource, where the first time domain resource is determined based on P reference times and Q time domain offsets, where P and Q are positive integers; The P reference time points include a transmission time point of hybrid automatic repeat request HARQ feedback information, and the HARQ feedback information is HARQ feedback information corresponding to the PDSCH scheduled by the first downlink grant.

24. The channel information receiving device according to claim 23, wherein: The transmission parameter of the target PUSCH resource is determined by at least one of the following: the first downlink authorization indication; radio resource control RRC signaling configuration; protocol pre-definition.

25. The channel information receiving device according to claim 23, wherein: The Q time domain offsets are determined by at least one of the following: the first downlink authorization indication; RRC signaling configuration; protocol pre-definition.

26. The channel information receiving device according to claim 23, wherein: The target PUSCH resource is any one of the following: A PUSCH resource corresponding to the identification information of the first downlink grant indication; PUSCH resources associated with the CSI report; The terminal determines the PUSCH resources according to the payload size reported by the CSI.

27. A terminal, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the channel information sending method according to any one of claims 1 to 9.

28. A network side device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the channel information receiving method according to any one of claims 10 to 18.

29. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the channel information sending method according to any one of claims 1 to 9 are implemented, or the steps of the channel information receiving method according to any one of claims 10 to 18 are implemented.

Images