Report sending method, report receiving method, and apparatus

By determining the PUCCH and PUSCH paths within the cell group in the terminal device, the transmission path problem of event-driven CSI reporting under multi-carrier or cell group conditions is solved, achieving reporting flexibility and optimized resource utilization.

WO2026065470A1PCT designated stage Publication Date: 2026-04-021FINITY INC +9
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-30
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

When a terminal device is configured with multiple carriers or cell groups, how to effectively send event-driven CSI reports, especially determining the transmission paths for report configuration information, PUCCH, DCI, and PUSCH in multiple carriers or cell groups, remains unresolved.

Method used

A report sending apparatus is provided for a terminal device configured with two cell groups, including a method for sending a PUCCH on a first cell and receiving a DCI and sending a PUSCH on a second cell when a trigger condition is met, and a method for sending a PUCCH on a first cell and sending a PUSCH on a fourth cell when a trigger condition is met.

Benefits of technology

It achieves a good trade-off between the flexibility of reporting across multiple carriers or cell groups and the reporting overhead, ensuring timely delivery of reports and efficient use of resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024122935_02042026_PF_FP_ABST
    Figure CN2024122935_02042026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application are a report sending method, a report receiving method, and an apparatus. The report sending method is applied to a terminal device configured with two cell groups, and comprises: when a report meets a trigger condition, sending a PUCCH on a first cell, wherein the first cell is a cell, which is configured with the PUCCH, in a cell group; and receiving downlink control information (DCI) on a second cell, and sending the report on a physical uplink shared channel (PUSCH) indicated by the DCI, wherein the second cell and the first cell belong to the same cell group.
Need to check novelty before this filing date? Find Prior Art

Description

Report sending and receiving method and apparatus TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology. BACKGROUND

[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report can include at least one of a CSI-RS Resource Indicator (CRI), a SSB Resource Indicator (SSBRI), a Layer 1 Reference Signal Received Power (L1-RSRP), a Layer 1 Signal to Interference plus Noise Ratio (L1-SINR), i.e., a beam-related report. A terminal device sends a beam report to a network device, and the network device can perform beam management based on the beam report, e.g., indicate a better beam to the terminal device.

[0003] When the terminal device sends a CSI report is determined by the network device, i.e., the report is a network device-scheduled report. The network device can configure a periodic CSI report, so that the terminal device sends a CSI report periodically; the network device can configure a semi-persistent CSI report, so that the terminal device sends a CSI report periodically after the semi-persistent CSI report is activated by the network device; the network device can configure an aperiodic CSI report, so that the terminal device sends a CSI report once after the aperiodic CSI report is triggered by the network device. The CSI report includes measurement results for a serving cell.

[0004] In Rel-19, event-driven reporting (also referred to as event-triggered reporting or terminal device-initiated reporting) will be introduced. More specifically, further enhancements to CSI reporting will be introduced, i.e., event-driven CSI reporting will be supported. Event-driven CSI reporting corresponds to the traditional CSI reporting.

[0005] Unlike the traditional reporting described above, for event-driven reporting, when the terminal device sends a report is determined by the terminal device, i.e., triggered by an event. In other words, the terminal device only sends a report when necessary, so that the report can be sent more timely, and in addition, the reporting overhead can also be reduced due to the avoidance of unnecessary reporting.

[0006] It should be noted that the above introduction to the technical background is only to facilitate a clear and complete description of the technical solutions of the present application, and to facilitate the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application.

[0007] SUMMARY

[0008] The inventors find that a terminal device receives report configuration information (CSI-ReportConfig), where the report configuration information configures event-driven reporting. The terminal device measures a measurement reference signal and transmits a PUCCH when one report meets a triggering condition. In mode A, the terminal device receives DCI and transmits the report on a PUSCH scheduled by the DCI; in mode B, the terminal device transmits the report on a PUSCH associated with the PUCCH. However, in a case where the terminal device is configured with multiple carriers, each carrier can generate a report meeting the triggering condition, and only a part of the carriers can be used to transmit the PUCCH, how to transmit the event-driven report in this case is a problem to be solved. For example, in a case where the terminal device is configured with multiple carriers in carrier aggregation, and / or in a case where the terminal device is configured with two cell groups, which carrier is configured or transmitted with the report configuration information, the PUCCH, the DCI and the PUSCH respectively is a problem to be solved.

[0009] To solve at least one of the above problems, embodiments of the present application provide a method for transmitting event-driven reporting in a carrier aggregation scenario.

[0010] According to an aspect of embodiments of the present application, a reporting transmitting apparatus is provided, applied to a terminal device configured with two cell groups, where the apparatus comprises:

[0011] a transmitter, configured to transmit a PUCCH on a first cell when one report meets a triggering condition, the first cell being a cell configured with the PUCCH in one cell group;

[0012] a receiver, configured to receive a DCI on a second cell, and the transmitter is configured to transmit the report on a PUSCH indicated by the DCI;

[0013] wherein the second cell and the first cell belong to the one cell group.

[0014] According to an aspect of embodiments of the present application, a reporting transmitting apparatus is provided, applied to a terminal device configured with two cell groups, where the apparatus comprises:

[0015] a transmitter, configured to transmit a PUCCH on a first cell when one report meets a triggering condition, the first cell being a cell configured with the PUCCH in one cell group; and transmit the report on a PUSCH associated with the PUCCH, where the transmitter is configured to transmit the PUSCH on a fourth cell;

[0016] The fourth cell and the first cell belong to the one cell group.

[0017] According to an aspect of an embodiment of the present application, a report sending device is provided, which is applied to a terminal device configured with two cell groups, and the device comprises:

[0018] a transmitter which sends a PUCCH on a first cell when a report meets a trigger condition, the first cell being a cell configured with the PUCCH in one cell group;

[0019] a receiver which receives a DCI on a fifth cell, and the transmitter further sends the report on a PUSCH indicated by the DCI;

[0020] The fifth cell and the first cell belong to the same or different cell groups.

[0021] According to an aspect of an embodiment of the present application, a report receiving device is provided, which is applied to a network device, and the device comprises:

[0022] a receiver which receives a PUCCH sent by a terminal device on a first cell when a report meets a trigger condition, the terminal device being configured with two cell groups, and the first cell being a cell configured with the PUCCH in one cell group;

[0023] a transmitter which sends a DCI on a second cell, and the receiver receives the report sent by the terminal device on a physical uplink shared channel (PUSCH) indicated by the DCI; wherein the second cell and the first cell belong to the one cell group,

[0024] Or, the receiver further receives the report sent by the terminal device on a PUSCH associated with the PUCCH, wherein the receiver receives the PUSCH on a fourth cell; wherein the fourth cell and the first cell belong to the one cell group.

[0025] According to an aspect of an embodiment of the present application, a report receiving device is provided, which is applied to a network device, and the device comprises:

[0026] a receiver which receives a PUCCH sent by a terminal device on a first cell when a report meets a trigger condition, the terminal device being configured with two cell groups, and the first cell being a cell configured with the PUCCH in one cell group;

[0027] a transmitter which sends a DCI on a fifth cell, and the receiver receives the report sent by the terminal device on a PUSCH indicated by the DCI;

[0028] The fifth cell and the first cell belong to the same or different cell groups.

[0029] One of the beneficial effects of the embodiments of the present application is that the terminal device can send the reports on the multiple carriers that meet the triggering conditions, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0030] Specific embodiments of the application are disclosed herein, and yet other embodiments will be apparent and / or readily inferred to those skilled in the art from the disclosure herein. It is contemplated that the embodiments of the application as described and / or shown herein can be used in a variety of applications, including, but not limited to, the applications described and / or shown herein. It is further contemplated that the embodiments of the application as described and / or shown herein can be used in a variety of combinations, permutations, and / or modifications, including, but not limited to, the combinations, permutations, and / or modifications described and / or shown herein. It is further contemplated that the embodiments of the application as described and / or shown herein can be used in a variety of combinations, permutations, and / or modifications, including, but not limited to, the combinations, permutations, and / or modifications described and / or shown herein.

[0031] Features described and / or shown with respect to one implementation can be used in one or more other implementations in the same or similar manner, in combination with or in place of other features in the other implementations.

[0032] It is emphasized that the use of the term "comprises / comprising" herein is intended to mean that the feature, item, step or component referred to follows, but does not preclude the presence or addition of one or more other features, items, steps or components. BRIEF DESCRIPTION OF DRAWINGS

[0033] Elements and features of the embodiments of the application described in one or more figures or implementations can be combined with elements and features of one or more other figures or implementations. Also, in the drawings, like reference numerals indicate corresponding parts throughout the several views, and can be used to indicate corresponding parts in more than one implementation.

[0034] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0035] FIG. 2 is a schematic diagram of event-driven reporting according to an embodiment of the present application;

[0036] FIG. 3 is another schematic diagram of event-driven reporting according to an embodiment of the present application;

[0037] FIG. 4 is a schematic diagram of a reporting sending method according to an embodiment of the present application;

[0038] FIG. 5 is an example diagram of a reporting sending method according to an embodiment of the present application;

[0039] FIG. 6 is another example diagram of a reporting sending method according to an embodiment of the present application;

[0040] FIG. 7 is another example diagram of a reporting sending method according to an embodiment of the present application;

[0041] FIG. 8 is another example diagram of the report sending method according to an embodiment of the present application;

[0042] FIG. 9 is a diagram of the report sending method according to an embodiment of the present application;

[0043] FIG. 10 is an example diagram of the report sending method according to an embodiment of the present application;

[0044] FIG. 11 is another example diagram of the report sending method according to an embodiment of the present application;

[0045] FIG. 12 is another example diagram of the report sending method according to an embodiment of the present application;

[0046] FIG. 13 is another example diagram of the report sending method according to an embodiment of the present application;

[0047] FIG. 14 is a diagram of the report sending method according to an embodiment of the present application;

[0048] FIG. 15 is an example diagram of the report sending method according to an embodiment of the present application;

[0049] FIG. 16 is another example diagram of the report sending method according to an embodiment of the present application;

[0050] FIG. 17 is another example diagram of the report sending method according to an embodiment of the present application;

[0051] FIG. 18 is another example diagram of the report sending method according to an embodiment of the present application;

[0052] FIG. 19 is a diagram of the report receiving method according to an embodiment of the present application;

[0053] FIG. 20 is a diagram of the report receiving method according to an embodiment of the present application;

[0054] FIG. 21 is a diagram of the report sending apparatus according to an embodiment of the present application;

[0055] FIG. 22 is another diagram of the report sending apparatus according to an embodiment of the present application;

[0056] FIG. 23 is another diagram of the report sending apparatus according to an embodiment of the present application;

[0057] FIG. 24 is a diagram of the report receiving apparatus according to an embodiment of the present application;

[0058] FIG. 25 is another diagram of the report receiving apparatus according to an embodiment of the present application;

[0059] FIG. 26 is a diagram of the terminal device according to an embodiment of the present application;

[0060] FIG. 27 is a diagram of the network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0061] The foregoing and other features of the present application will become apparent to those skilled in the art upon consideration of the following description of specific embodiments of the application, taken in conjunction with the accompanying drawings. In the description of embodiments of the application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific terminology so selected. A person skilled in the art will recognize that the principles of the application can be employed in any device that employs the principles of the application.

[0062] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the point of view, but do not indicate the spatial arrangement or time sequence of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "include", "comprise", "have" and the like are intended to mean the presence of the stated feature, element, component or assembly, but do not exclude the presence or addition of one or more other features, elements, components or assemblies.

[0063] In the embodiments of the present application, the singular form "a", "an", etc. includes the plural form, should be understood broadly as "one" or "a kind of", and not limited to the meaning of "one"; in addition, the term "said" should be understood as including both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least partially according to", and the term "based on" should be understood as "at least partially based on", unless the context clearly indicates otherwise.

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

[0065] In addition, the communication between devices in the communication system can be carried out according to any stage of the communication protocol, which can include but is 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 currently known or future to be developed communication protocols.

[0066] In embodiments of the present application, the term "network device" refers to, for example, a device that accesses a terminal device into a communication network and provides services for the terminal device in a communication system. The network device can include, but is 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), and the like.

[0067] In which, the base station can include, but is not limited to: node B (NodeB or NB), evolved node B (eNodeB or eNB), and 5G base station (gNB), IAB donor, etc., and can also include remote radio head (RRH), remote radio unit (RRU), relay, or low-power node (such as femto, pico, etc.). And the term "base station" can include some or all functions of them, and each base station can provide communication coverage for a specific geographic 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.

[0068] In 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. The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and the like.

[0069] In which, the terminal equipment can include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, cordless phone, smart phone, smart watch, digital camera, and the like.

[0070] For another example, in scenarios such as Internet of Things (IoT), a terminal device can also be a machine or device that performs monitoring or measurement, which can include but is not limited to: Machine Type Communication (MTC) terminal, vehicle-mounted communication terminal, Device to Device (D2D) terminal, Machine to Machine (M2M) terminal, and the like.

[0071] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as described above. In this article, "device" can refer to a network device or a terminal device without special indication.

[0072] The following describes the scenarios of the embodiments of the present application by way of examples, but the present application is not limited thereto.

[0073] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates the case of taking a terminal device and a network device as examples. As shown in FIG. 1, the communication system 100 can include a network device 101 and terminal devices 102 and 103. For simplicity, FIG. 1 only illustrates two terminal devices and one network device as examples, but the embodiments of the present application are not limited thereto.

[0074] In the embodiments of the present application, the network device 101 and the terminal devices 102 and 103 can perform existing services or future implementable services transmission. For example, these services can include but are not limited to: enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), and the like.

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

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

[0077] In the following description, the terms "PDCCH" and "physical downlink control channel" or "downlink control information" may be interchangeable without causing confusion, and the terms "PDSCH" and "physical downlink data channel" or "downlink data" may also be interchangeable. In addition, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0078] The terms "PUCCH" and "physical uplink control channel" or "uplink control information" may be interchangeable, and the terms "PUSCH" and "physical uplink data channel" or "uplink data" may also be interchangeable. In addition, transmitting or receiving a PUCCH can be understood as transmitting or receiving downlink control information carried by the PUCCH; transmitting or receiving a PUSCH can be understood as transmitting or receiving uplink data carried by the PUSCH.

[0079] The terminal device needs to send an event-driven report on certain time-frequency resources, and the determination of the resources needs corresponding information interaction, for example, the terminal device sends a first message to request dynamically scheduled resources or to inform whether semi-statically configured resources are actually used.

[0080] FIG. 2 is a schematic diagram of an event-driven report (i.e., mode B) according to an embodiment of the present application. As shown in FIG. 2, the first resource for sending the first message is a configured periodic PUCCH resource (only one period is shown in FIG. 2 for simplicity), the second resource for sending the event-driven report is a configured periodic PUSCH or PUCCH resource (only one resource is shown), and the first resource and the second resource have an association relationship, for example, one first resource is associated with one second resource.

[0081] As shown in FIG. 2, the terminal device measures one or more reference signals (RS1-RSN), and after detecting the occurrence of the event triggering the report, sends a first message to the network device to indicate that there is a report transmission on the second resource associated with the first message (first resource), and then sends the report on the associated second resource.

[0082] Conversely, if the terminal device does not detect the occurrence of the event, the terminal device can not send the first message, in this way, indicating to the network device that there is no report transmission on the second resource associated with the first message, so that the network device can schedule other terminal devices for transmission on the second resource, avoiding the waste of the second resource pre-configured in a semi-static manner. Without loss of generality, if the terminal device does not detect the occurrence of the event, the terminal device can also send the first message, but the content of the first message is different from before, at this time, the first message indicates to the network device that there is no report transmission on the second resource associated with the first message.

[0083] FIG. 3 is another schematic diagram of the event-driven report of the embodiments of the present application (i.e., mode A). As shown in FIG. 3, the first resource for sending the first message is a configured periodic PUCCH resource (only one resource is shown), and the second resource for sending the event-driven report is a PDCCH (or DCI) scheduled resource.

[0084] As shown in FIG. 3, the terminal device measures one or more reference signals (RS1-RSN), and after detecting the occurrence of the event triggering the report, sends a first message on the first resource to request the network device to send the resource required for sending the report (i.e., to request the second resource), and then receives a PDCCH, and sends the report on the second resource scheduled by the PDCCH. The report can be carried by a PUSCH or a PUCCH, and the first message is carried by a PUCCH. Here, the resource refers to a time-frequency resource.

[0085] One report is associated with one report configuration (i.e., report configuration information), and the two can be replaced with each other. For the parameters, modules or components shown in the figure, it is not limited that they must appear at the same time, and also includes the case that only part of the parameters, modules or components exist.

[0086] The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0087] Embodiments of the first aspect

[0088] The embodiments of the present application provide a report sending method, which is described from the terminal device side, wherein the terminal device is configured with two cell groups. FIG. 4 is a schematic diagram of the report sending method of the embodiments of the present application, and for the aforementioned mode A, as shown in FIG. 4, the method includes:

[0089] 401, when a report meets a triggering condition, the terminal device sends a PUCCH on a first cell, the first cell being a cell configured with a PUCCH in a cell group;

[0090] 402, the terminal device receives a downlink control information (DCI) on a second cell, and sends a report on a physical uplink shared channel (PUSCH) indicated by the DCI;

[0091] Wherein, the second cell and the first cell belong to the one cell group.

[0092] In some embodiments, the two cell groups are a primary PUCCH group and a secondary PUCCH group respectively. The following cell group can also be replaced by a PUCCH group or a PUCCH cell group. The cell can also be replaced by a carrier or a component carrier (CC). Each PUCCH group includes one or more cells, and only one cell in each PUCCH group has a PUCCH configuration, i.e. is configured with PUCCH-Config. The cell is referred to as a PUCCH-configured cell, and the PUCCH-configured cell in a PUCCH group is referred to as a first cell below. The terminal device can only send a PUCCH on the first cell and cannot send a PUCCH on other cells in the PUCCH group. For example, the first cell in the primary PUCCH group is a special cell (SpCell), i.e. a primary cell (PCell) or a primary secondary cell (PScell), and the first cell in the secondary PUCCH group is a secondary cell (Scell), referred to as a PUCCH secondary cell (PUCCH Scell). More detailed definitions of the primary PUCCH group and the secondary PUCCH group can be referred to related technologies. Here, the primary PUCCH group and the secondary PUCCH group are taken as examples for illustration, and the embodiments of the present application are not limited thereto. The "primary PUCCH group" and "secondary PUCCH group" can be replaced by "first PUCCH group" and "second PUCCH group" respectively, and can also be extended to more than two PUCCH groups.

[0093] The embodiments of the present application do not limit the event triggering the report. For example, the event can be that the measurement result (L1-RSRP) of a certain new beam (one of RS1 to RSN) is higher than the measurement result of the current beam by a certain value, or the measurement result of the current beam is lower than a certain value. The embodiments of the present application do not limit the content of the report. For example, the report includes the reference signal index and the L1-RSRP based on the reference signal measurement, and the report can include one or more reference signal indexes and L1-RSRP. The report is used to report the beam information, and the purpose is to report the beam and the measurement result for the beam. The report can also be replaced by the beam report.

[0094] In the embodiments of the present application, "report" refers to "event-driven report". "Event driven" can be replaced by "UE initiated" or "event triggered". DCI can be replaced by PDCCH or uplink DCI, wherein the uplink DCI includes DCI format 0_1 or DCI format 0_2.

[0095] In some embodiments, it is assumed that one report is associated with an event, when the event meets the triggering condition, the report associated with the event becomes the report meeting the triggering condition (triggered report), and the terminal device sends the report associated with the event. In order to send the report, the terminal device sends the PUCCH associated with the report to request the time-frequency resource for sending the report from the network device. Then, the terminal device receives the DCI and sends the report on the PUSCH scheduled by the DCI.

[0096] In some embodiments, the report sending method further includes: (not shown)

[0097] The terminal device receives first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of a first cell group, and / or receives second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of a second cell group.

[0098] For example, the report configuration (Report Configuration) of the terminal device is indicated or configured by RRC signaling. Each report has a report configuration, for example, provided by RRC IE CSI-ReportConfig. The terminal device can be configured with one or more report configurations CSI-ReportConfig, i.e., the network device configures a set of CSI-ReportConfig for a set of reports. A set of report configuration information for a set of reports refers to a set of CSI-ReportConfig configured for a set of reports, where each report has a CSI-ReportConfig. CSI-ReportConfig provides the necessary configuration information for a report, for example, the configuration information includes the identity of the report configuration (report configuration ID). The configuration information can also include the triggering condition that the report needs to meet, i.e., when the event meets the triggering condition, the terminal device sends the report; for example, the configuration information includes the measurement resource (reference signal) configuration, assuming that the report is sent on the third cell, the measurement resource of the report can be located in the same or different cell as the third cell. The network device configures a set of CSI-ReportConfig for the terminal device, where N1 (N1≥0) CSI-ReportConfig is configured on cell A (i.e., configured within the ServingCellConfig of cell A), and N2 (N2≥0) CSI-ReportConfig is configured on cell B (i.e., configured within the ServingCellConfig of cell B). For example, the CSI-ReportConfig is configured within the CSI-MeasConfig included in the ServingCellConfig. Therefore, a set of CSI-ReportConfig can be configured on one or more cells, i.e., located in one or more cells. In the case where the terminal device is configured with one primary PUCCH group and one secondary PUCCH group, the first set of report configuration information can be configured on one or more cells (not necessarily all cells) in the primary PUCCH group (the first cell group), and the second set of report configuration information can be configured on one or more cells (not necessarily all cells) in the secondary PUCCH group (the second cell group).

[0099] For example, "sending a report on PUSCH" refers to sending the report content related to the report configuration (CSI-ReportConfig) on PUSCH. The terminal device can determine the report content that needs to be sent according to one CSI-ReportConfig, and the report content will be described later.

[0100] In some embodiments, the reported content includes a set of measurement results and / or a set of reference signal IDs. For example, the measurement results include L1-RSRP and / or L1-SINR. For example, the reference signal IDs include SSB index and / or CSI-RS index. For example, the SSB index is SSBRI (SSB Resource Indicator). For example, the CSI-RS index is CRI (CSI-RS Resource Indicator).

[0101] In some embodiments, the reporting further includes at least one of a reporting configuration ID, a cell ID, and a local cell ID, wherein the local cell ID is numbered in a cell group, e.g., the local cell ID is numbered in a primary PUCCH group or in a secondary PUCCH cell group, which can be a cell group to which a first cell sending the PUCCH belongs.

[0102] For example, N1 (N1>1) CSI-ReportConfig configured on cell A and N2 (N2>1) CSI-ReportConfig configured on cell B are associated with one PUCCH, assuming one of the CSI-ReportConfig associated report is triggered, the network device cannot know which one of the N1+N2 reports the terminal device wants to send after receiving the PUCCH, therefore the terminal device can carry information for identifying the report in the report, for example, the report includes report configuration ID (CSI-ReportConfigId, i.e. the ID of CSI-ReportConfig), which is used to identify a certain CSI-ReportConfig. In addition, since N1 CSI-ReportConfig (belongs to cell A) and N2 CSI-ReportConfig (belongs to cell B) are independently numbered, for example, N1 CSI-ReportConfigId on cell A is 0 to N1-1, N2 CSI-ReportConfigId on cell B is 0 to N2-1, therefore it cannot be determined according to one CSI-ReportConfigId whether it belongs to cell A or cell B. In this case, for example, the terminal device can include CSI-ReportConfigId and cell ID in the report, the cell ID is used to determine a cell, and the CSI-ReportConfigId is used to determine a CSI-ReportConfig in the determined cell; for another example, assuming that the N1+N2 CSI-ReportConfig associated with one PUCCH belongs to multiple cells (cell A and cell B) is always in the same PUCCH group, the terminal device can include CSI-ReportConfigId and local cell ID in the report, the local cell ID is numbered in one PUCCH group, and the local cell ID can uniquely identify a cell in one PUCCH group.

[0103] For example, if the terminal device sends multiple reports meeting the triggering condition on the PUSCH, each report includes the report configuration ID and the cell ID.

[0104] In some embodiments, the number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports meeting the triggering condition in one cell group, or the first value is equal to the number of report configuration information in one cell group. The one cell group can be the primary PUCCH group or the secondary PUCCH group, and can be the cell group to which the first cell sending the PUCCH belongs.

[0105] For example, assume that the terminal device is configured with M1 (M1≥1) CSI-ReportConfig (e.g., configured with M1 CSI-ReportConfig within one PUCCH group), i.e., configured with M1 reports, where M2 (1≤M2≤M1) reports satisfy the triggering condition. In the case that the terminal device receives the DCI triggering the reporting, to avoid ambiguity between the network device and the terminal device on the number of reporting bits (i.e., the payload size), it is necessary to define the number of reports sent by the terminal device on the PUSCH indicated by the DCI. The number of reports sent by the terminal device is a first number M0 (1≤M0≤M1), which can be determined according to the following manners. For example, M0 is configured by RRC signaling, which can be configured in units of PUCCH groups, or configured in units of terminal devices; for example, M0 is predefined, i.e., a fixed value, for example, fixed as 1; for example, M0 is equal to the number of reports satisfying the triggering condition in one PUCCH group, i.e., M0=M2 in one PUCCH group; for example, M0 is equal to the number of CSI-ReportConfig in one PUCCH group, i.e., M0=M1 in one PUCCH group.

[0106] For example, if M0 is configured, regardless of the number of reports satisfying the triggering condition, the terminal device always determines the number of reporting bits B (B≥1) according to the assumption that M0 reports satisfy the triggering condition. If the number of reports actually satisfying the triggering condition is less than M0, then the B bits include B1 (B1≥1) bits and B2 (B2≥1) bits (B1+B2=B), where B1 bits are generated by the terminal device according to the reports actually satisfying the triggering condition, and B2 bits are padding bits. If the number of reports actually satisfying the triggering condition is greater than or equal to M0, the terminal device selects M0 reports therefrom, and generates B bits according to the selected M0 reports. For example, the bit width of the measurement result and / or the bit width of the reference signal ID is fixed, or is known to the terminal device and the network device. For example, the above operation is performed in each PUCCH group.

[0107] For example, in the case that M0 is fixed as 1, the actual transmitted reporting bits are determined according to the maximum value among M1 reporting bits, where the M1 reporting bits are determined according to M1 CSI-ReportConfig respectively. The terminal device can determine the reporting bits included in the report associated with each CSI-ReportConfig according to the CSI-ReportConfig. The terminal device is configured with M1 CSI-ReportConfig, and thus can determine M1 reporting bits for M1 reports, i.e., M1 reports generate M1 reporting bits respectively. Let the maximum value of M1 reporting bits be B. Although there can be multiple reports satisfying the triggering condition, the terminal device is limited to transmitting only one report on the PUSCH. Regardless of which of the M1 reports is transmitted, the actual transmitted reporting bits are B. If the reporting bits generated by the report are less than B, padding bits are used to fill them to B bits. Thus, regardless of which report is transmitted, the actual transmitted reporting bits are fixed and unchangeable, and the network device can always demodulate and decode according to the fixed number of bits. For example, the above operation is performed within each PUCCH group.

[0108] In some embodiments, the DCI indicates at least one of a report configuration ID, a cell ID, and a local cell ID, where the local cell ID is numbered in a cell group, e.g., the local cell ID is numbered in a primary PUCCH group or in a secondary PUCCH cell group.

[0109] For example, for N1 (N1>1) CSI-ReportConfig configured on cell A and N2 (N2>1) CSI-ReportConfig configured on cell B, each of the N1+N2 CSI-ReportConfig is associated with a PUCCH, assuming that one of the CSI-ReportConfig associated reports is triggered, so that the terminal device sends a PUCCH, the network device can know which of the N1+N2 reports the terminal device wants to send after receiving the PUCCH, so the network device can indicate which report the PUSCH is used to carry when scheduling the PUSCH by DCI, for example, by indicating the CSI-ReportConfigId in the DCI. In addition, since the N1 CSI-ReportConfig (belonging to cell A) and the N2 CSI-ReportConfig (belonging to cell B) are independently numbered, in this case, for example, the network device can indicate the CSI-ReportConfigId and the cell ID by DCI; for another example, assuming that the DCI and the PUCCH are always located in the same PUCCH group, the network device can indicate the CSI-ReportConfigId and the local cell ID by DCI, the local cell ID is numbered in the primary PUCCH group or the secondary PUCCH group, and the local cell ID can uniquely identify a cell in a PUCCH group. Taking the example of "DCI indicating the CSI-ReportConfigId and the local cell ID", it can be indicated in the DCI field, or an RRC parameter (for example, trigger state) associated with the CSI-ReportConfigId and the local cell ID can be indicated by the field of the DCI, and the embodiments of the present application do not limit this.

[0110] For example, if the DCI indicates that the terminal device sends N (N>1) reports meeting the triggering condition on the PUSCH, the DCI indicates N report configuration IDs and N cell IDs.

[0111] The following describes which cell or cell group the report configuration information, PUCCH, DCI and PUSCH are located in under mode A

[0112] In some embodiments, the terminal device transmits the PUCCH on the first cell and receives the DCI on the second cell, and the first cell and the second cell belong to one cell group, or belong to the same cell group, or the second cell is located in the cell group to which the first cell belongs. The "the second cell and the first cell belong to one cell group" means that the DCI can be located in any cell in the same cell group. In other words, if the terminal device transmits the PUCCH on the first cell, the terminal device receives the DCI on the cell belonging to the same cell group as the first cell, and transmits the report on the PUSCH scheduled by the DCI. The first cell can be a cell configured with PUCCH in the primary PUCCH group, or a cell configured with PUCCH in the secondary PUCCH group. The "cell where the DCI is located" refers to the cell where the "DCI reception" is located, i.e., the cell where the DCI is received, or the second cell where the DCI is received. The above "one cell group" refers to one primary PUCCH group or one secondary PUCCH group.

[0113] In some embodiments, the second cell is the first cell. That is, the cell where the DCI is located is the cell configured with PUCCH. Here, the reception of the DCI is limited to only the first cell. In other words, if a report triggers the terminal device to transmit the PUCCH on the first cell, the terminal device can only receive the DCI on the first cell, and transmit the report on the PUSCH scheduled by the DCI.

[0114] In some embodiments, when one of the reports in the first group of reports meets the triggering condition, the PUCCH is transmitted on the first cell of the first cell group; and when one of the reports in the second group of reports meets the triggering condition, the PUCCH is transmitted on the first cell of the second cell group.

[0115] For example, if a report associated with a CSI-ReportConfig meets the triggering condition, and the CSI-ReportConfig is configured on cell A, the terminal device transmits the PUCCH on the cell configured with PUCCH in the same PUCCH group as cell A, and requests the network device for resources for transmitting the report. In other words, if a report (CSI-ReportConfig) configured in a PUCCH group meets the triggering condition, the terminal device transmits the PUCCH on the first cell in the PUCCH group.

[0116] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group.

[0117] For example, a terminal device is configured a set of CSI-ReportConfig, which can only be configured on a cell configured with PUCCH. A set of CSI-ReportConfig can be configured on a cell configured with PUCCH in a primary PUCCH group, or can be configured on a cell configured with PUCCH in a secondary PUCCH group.

[0118] In some embodiments, the first set of reporting configuration information of the first set of reporting is associated with one PUCCH, or the reporting configuration information of each reporting in the first set of reporting is respectively associated with one PUCCH; and / or, the second set of reporting configuration information of the second set of reporting is associated with one PUCCH, or the reporting configuration information of each reporting in the second set of reporting is respectively associated with one PUCCH.

[0119] For example, as described before, the "reporting configuration information of a set of reporting" refers to "a set of CSI-ReportConfig configured for a set of reporting", which can be associated with one periodic PUCCH resource, i.e., multiple reports share one PUCCH, or each CSI-ReportConfig in a set of CSI-ReportConfig can be associated with one periodic PUCCH resource, i.e., each report has a dedicated PUCCH. For the former, the network device cannot know which report in multiple reports the terminal device wants to send after receiving the PUCCH, so the terminal device can carry information for identifying the report in the report, such as report configuration ID (CSI-ReportConfigId) and the like. For the latter, the network device can know the report the terminal device wants to send after receiving the PUCCH, so the network device can indicate which report the PUCCH is used to carry when scheduling the PUSCH by using DCI, such as indicating the report configuration ID and the like. If the report associated with a CSI-ReportConfig meets the triggering condition, the terminal device sends PUCCH on the PUCCH resource associated with the CSI-ReportConfig.

[0120] For example, for a set of CSI-ReportConfig configured in one PUCCH group, a set of CSI-ReportConfig is associated with one PUCCH in the same PUCCH group, or each CSI-ReportConfig in a set of CSI-ReportConfig is associated with one PUCCH in the same PUCCH group.

[0121] In some embodiments, the PUSCH is transmitted on a third cell, which belongs to a cell group with the first cell, or belongs to a cell group with the second cell, or is the first cell, or is the second cell.

[0122] For example, the third cell is the cell where the PUSCH is located, or the cell where the PUSCH is transmitted, i.e., the cell where the PUSCH is transmitted. The cell where the PUSCH is located can belong to a PUCCH group with the cell where the PUCCH is configured, or belong to a PUCCH group with the cell where the DCI is located. Alternatively, the PUSCH is limited to only be located in the cell where the PUCCH is configured, or only be located in the cell where the DCI is located.

[0123] In some embodiments, the second cell is the cell where the report configuration information of the transmitted report is configured. And / or, the third cell is the cell where the report configuration information of the transmitted report is configured.

[0124] For example, as mentioned above, the PUSCH can be indicated by the DCI to carry which report. Assuming that report A is indicated by the DCI, and the CSI-ReportConfig of the report A is configured on cell B, the DCI is limited to be transmitted on cell B, i.e., the terminal device can only receive the DCI indicating the report A on cell B. The DCI indicates the CSI-ReportConfigId, and the DCI does not need to indicate the cell ID, i.e., does not need to indicate the cell where the CSI-ReportConfig is configured, and the cell where the DCI is located is the cell where the CSI-ReportConfig is configured. Similarly, the method of determining the cell where the DCI is located is also applicable to determining the cell where the PUSCH is located.

[0125] For example, assuming that each CSI-ReportConfig is associated with a PUCCH, the network device can know the CSI-ReportConfig associated with the PUCCH after receiving the PUCCH, and know that the terminal device wants to transmit the report associated with the CSI-ReportConfig. The terminal device receives the DCI transmitted by the network device, and transmits the report on the PUSCH indicated by the DCI. If the CSI-ReportConfig is configured on cell A, the PUSCH indicated by the DCI must also be transmitted on cell A.

[0126] The method described above is illustrated by a specific example as follows.

[0127] The following examples are based on some common assumptions. Specifically, in the following examples, a terminal device supporting carrier aggregation (CA) is configured with 4 component carriers (CCs), i.e., CC0~CC3. The component carrier can also be replaced with carrier or cell. In cells 0~3, only cell 0 and cell 2 are configured with PUCCH, i.e., PUCCH can only be transmitted on cell 0 or cell 2. The primary PUCCH group includes cell 0 and cell 1, and the secondary PUCCH group includes cell 2 and cell 3. The terminal device is configured with 4 event-driven reports, i.e., report 0~report 3, through reporting configurations (CSI-ReportConfig) 0~3. Reporting configurations 0 and 1 are configured on the cells of the primary PUCCH group, and reporting configurations 2 and 3 are configured on the cells of the secondary PUCCH group. One or more reporting configurations can be configured on one cell. Reporting configurations 0~3 are only used to distinguish the 4 reporting configurations, and do not mean that the CSI-ReportConfigId of the 4 reporting configurations is 0~3 respectively. The reporting configuration ID (CSI-ReportConfigId) is numbered independently in units of cells. Reports 0~3 are reports for cells 0~3 respectively, in other words, the measurement results included in reports 0~3 are determined according to reference signals 0~3 located on cells 0~3 respectively. For example, the measurement result is L1-RSRP or L1-SINR, and the reference signal is SSB or CSI-RS.

[0128] FIG. 5 is an example diagram of a report sending method according to an embodiment of the present application. As shown in FIG. 5, report configurations 0 and 1 are configured on cell 0, and the report configurations 0 and 1 are associated with a PUCCH (PUCCH0) on the cell 0; report configurations 2 and 3 are configured on cell 2, and the report configurations 2 and 3 are associated with a PUCCH (PUCCH1) on the cell 2. If any one of the report 0 and the report 1 meets a triggering condition, the terminal device sends the PUCCH0 on the cell 0, for example, the PUCCH0 is a periodic PUCCH resource, and the terminal device sends the PUCCH on one of the PUCCH resources. If neither of the report 0 and the report 1 meets the triggering condition, the terminal device does not send the PUCCH0 on the cell 0. Therefore, the network device can know whether there is a report to be sent in the primary PUCCH group according to whether the PUCCH0 is received. If the terminal device receives a DCI (DCI0) triggering a report event-driven report on the cell of the primary PUCCH group, the report 0 and / or the report 1 are sent on a PUSCH (PUSCH0) indicated by the DCI0. Since the report 0 and the report 1 share the PUCCH0, the network device cannot know which report the terminal device wants to send after receiving the PUCCH0. By carrying the report configuration ID of the report 0 and / or the report 1 in the PUSCH0, it can be indicated to the network device which reports in the primary PUCCH group are carried by the PUSCH0. The above description of the primary PUCCH group also applies to the secondary PUCCH group, which will not be described again. FIG. 5 does not limit the timing relationship of the PUCCH or the DCI or the PUSCH transmission between different PUCCH groups, and FIG. 5 does not represent a strict time sequence.

[0129] FIG. 6 is another example diagram of a report sending method according to an embodiment of the present application. For example, as shown in FIG. 6, the difference between FIG. 6 and FIG. 5 is that the report configuration i is configured on the cell i (i = 0-3). Only the operations different from those of FIG. 5 will be described below. Since the report configuration ID (CSI-ReportConfigId) is independently numbered in units of cells, a single report configuration ID cannot uniquely identify one of the four reports (for example, the CSI-ReportConfigId of the report configurations 0 and 1 are both numbered from 0, and both can be 0). Therefore, in addition to sending the report configuration ID on the PUSCH, the terminal device also sends the cell information to which the report configuration ID belongs. Since all the reports sent on the PUSCH belong to the same PUCCH group, the local cell ID numbered in the PUCCH group can be used, for example, the local cell ID of the cell 0 in the primary PUCCH group is 0, the local cell ID of the cell 1 in the primary PUCCH group is 1, the local cell ID of the cell 2 in the secondary PUCCH group is 0, and the local cell ID of the cell 3 in the secondary PUCCH group is 1.

[0130] FIG. 7 is another example diagram of the report sending method according to an embodiment of the present application. For example, as shown in FIG. 7, report configurations 0 and 1 are configured on cell 0, and the report configurations 0 and 1 are respectively associated with PUCCH 0 and PUCCH 1 on cell 0; report configurations 2 and 3 are configured on cell 2, and the report configurations 2 and 3 are respectively associated with PUCCH 2 and PUCCH 3 on cell 2. If report i meets the triggering condition, the terminal device sends PUCCH i (i = 0-3); otherwise, PUCCH i is not sent. If the terminal device receives DCI (DCI 0) triggering the report event-driven report on the cell of the primary PUCCH group, the terminal device sends report 0 and / or report 1 on the PUSCH (PUSCH 0) indicated by DCI 0. According to the one-to-one mapping relationship between the report configuration and the PUCCH, the network device can know which report the terminal device wants to send after receiving the PUCCH. Since there can be multiple reports meeting the triggering condition, the terminal device needs to know which report to send on the scheduled PUSCH after receiving the DCI. Therefore, the report configuration ID can be indicated by the DCI. The above description of the primary PUCCH group also applies to the secondary PUCCH group.

[0131] FIG. 8 is another example diagram of the report sending method according to an embodiment of the present application. For example, FIG. 8 gives an example, and the difference between FIG. 8 and FIG. 7 is that the report configuration i is configured on cell i (i = 0-3). Only the operations different from those of FIG. 7 are described below. Since the report configuration ID (CSI-ReportConfigId) is independently numbered in units of cells, a single report configuration ID cannot uniquely identify a certain report of the four reports. Therefore, in addition to indicating the report configuration ID, the DCI also indicates the cell information to which the report configuration ID belongs. Assuming that report 1 associated with report configuration 1 meets the triggering condition, the terminal device sends PUCCH 1 and receives DCI. To determine which report to send on the PUSCH scheduled by the DCI, for example (not shown in the figure), the DCI can indicate the CSI-ReportConfigId of report configuration 1 and the local cell ID of cell 1; for another example (as shown in the figure), the DCI can indicate the CSI-ReportConfigId of report configuration 1, and the terminal device receives the DCI on cell 1, considering that the DCI indicates the CSI-ReportConfigId of cell 1, i.e., the cell in which the DCI is located is the cell in which the report configuration 1 is configured.

[0132] It is notable that the above Fig. 4 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be adjusted as appropriate, and in addition, some operations can be added or some operations can be deleted. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above Fig. 4.

[0133] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone or one or more of the above embodiments can be combined. The embodiments of the present application are described by taking two reports as an example, and can be extended to more than two reports, and will not be described herein.

[0134] According to the embodiments of the present application, in mode A, the report configuration information, the PUCCH, the DCI and the PUSCH are located in at least one cell group. The terminal device can send the reports on the multiple carriers that satisfy the triggering conditions, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0135] Embodiments of the second aspect

[0136] The embodiments of the present application provide a report sending method, which is described from the terminal device side, and the same content as the embodiments of the first aspect is omitted. The difference between the embodiments of the first aspect is that the present embodiments are described for mode B. Fig. 9 is a schematic diagram of a report sending method of the embodiments of the present application, which is applied to a terminal device configured with two cell groups, as shown in Fig. 9, the method comprises:

[0137] 901, when one report satisfies the triggering condition, the terminal device sends a PUCCH on a first cell, the first cell is a cell configured with a PUCCH in a cell group, and sends a report on a PUSCH associated with the PUCCH, wherein the PUSCH is sent on a fourth cell;

[0138] The fourth cell and the first cell belong to one cell group.

[0139] In some embodiments, the implementation of the two cell groups and the report satisfying the triggering condition can refer to the embodiments of the first aspect, which will not be described herein.

[0140] In some embodiments, the report sending method further comprises: (not shown)

[0141] The terminal device receives first group reporting configuration information of a first group of reports, wherein the first group reporting configuration information is configured on one or more cells of a first cell group, and / or receives second group reporting configuration information of a second group of reports, wherein the second group reporting configuration information is configured on one or more cells of a second cell group. For example, the first group of CSI-ReportConfig is configured in the primary PUCCH group, and the second group of CSI-ReportConfig is configured in the secondary PUCCH group. The embodiments can refer to the embodiments of the first aspect, which will not be repeated here.

[0142] In some embodiments, the content related to the report includes a group of measurement results and / or a group of reference signal IDs. The report configuration ID (CSI-ReportConfigId) can also be included, which can refer to the embodiments of the first aspect, which will not be repeated here.

[0143] In some embodiments, the number of reports carried by the PUSCH is determined by the first value, and the specific embodiments can refer to the embodiments of the first aspect, which will not be repeated here.

[0144] The following describes where the reporting configuration information, PUCCH and PUSCH are located in the cell or cell group under mode B.

[0145] In some embodiments, the PUCCH and the PUSCH are configured by RRC signaling, and the two have an association relationship. In the case that one report meets the triggering condition, the terminal device sends the PUCCH associated with the report to notify the network device that there is a report on the PUSCH associated with the PUCCH. Then, the terminal device sends the report on the PUSCH. Assuming that the terminal device sends the PUCCH on the first cell and sends the PUSCH on the fourth cell, the first cell and the fourth cell belong to one PUCCH group, or belong to the same PUCCH group. Or, the fourth cell is located in the cell group to which the first cell belongs. The fourth cell refers to the "cell where the PUSCH is located" or the "cell where the PUSCH is sent", that is, the cell where the PUSCH is sent. Here, it is assumed that the terminal device sends the report on the PUSCH, that is, the report is carried by the PUSCH. The report can also be carried by the PUCCH, that is, the PUSCH can be replaced by the PUCCH.

[0146] In some embodiments, the fourth cell is the first cell. That is, the PUSCH is limited to only the first cell in the same PUCCH group.

[0147] In some embodiments, the PUCCH is transmitted on the first cell of the first cell group when one of the first group of reports meets the triggering condition; and the PUCCH is transmitted on the first cell of the second cell group when one of the second group of reports meets the triggering condition.

[0148] For example, if one of the reports associated with a CSI-ReportConfig meets the triggering condition, the terminal device transmits the PUCCH on one of the cells configured with PUCCH, which is in the same PUCCH group as the CSI-ReportConfig.

[0149] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group.

[0150] For example, the first group of CSI-ReportConfig can only be configured on the cells configured with PUCCH within the primary PUCCH group, and the second group of CSI-ReportConfig can only be configured on the cells configured with PUCCH within the secondary PUCCH group.

[0151] In some embodiments, the first group of report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or the second group of report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH.

[0152] For example, the first group of CSI-ReportConfig shares one PUCCH, or each CSI-ReportConfig in the first group of CSI-ReportConfig has a dedicated PUCCH, and the same applies to the second group of CSI-ReportConfig.

[0153] In some embodiments, the fourth cell is the cell on which the report configuration information of the transmitted report is configured. For example, if a CSI-ReportConfig of a report is configured on cell A, the PUSCH for carrying the report must also be configured on cell A. When the report meets the triggering condition, the report is transmitted on the PUSCH.

[0154] The above-described method is described below through specific examples, and the same as the previous embodiments will not be described again. For simplicity, only the primary PUCCH group is described as an example, and the following description also applies to the secondary PUCCH group.

[0155] FIG. 10 is an example diagram of a report sending method according to an embodiment of the present application. For example, as shown in FIG. 10, report configuration 0 and report configuration 1 are configured on cell 0, and PUSCH (PUSCH0) for carrying report 0 and / or report 1 is also configured on cell 0. Report configuration 0 and report configuration 1 are associated with PUCCH0, and PUCCH0 is associated with PUSCH0. If any one of report 0 and report 1 meets a triggering condition, the terminal device sends PUCCH0 on cell 0, and sends the report on PUSCH0 associated with PUCCH0. Since report 0 and report 1 share PUCCH0 and PUSCH0, the network device cannot know which report is carried on PUSCH0 after receiving PUCCH0. Therefore, the report configuration ID is carried in PUSCH0, indicating the report carried by PUSCH0 to the network device.

[0156] FIG. 11 is another example diagram of a report sending method according to an embodiment of the present application. For example, as shown in FIG. 11, report configuration 0 is configured on cell 0, and PUSCH (PUSCH0) for carrying report 0 is also configured on cell 0; report configuration 1 is configured on cell 1, and PUSCH (PUSCH1) for carrying report 1 is also configured on cell 1. Report configuration 0 and report configuration 1 are associated with PUCCH0, and PUCCH0 is associated with PUSCH0 and PUSCH1. If report 0 meets a triggering condition, the terminal device sends PUCCH0 on cell 0, and sends report 0 on PUSCH0 associated with PUCCH0. If report 1 meets a triggering condition, the terminal device sends PUCCH0 on cell 0, and sends report 1 on PUSCH1 associated with PUCCH0. In the diagram, only one report configuration is configured in one cell as an example, and in fact, one cell can also be configured with multiple report configurations. It is assumed that N (N > 1) report configurations of N reports are configured on cell 1, and PUSCH1 for carrying N reports is configured on cell 1. The network device knows that PUSCH1 carries N reports associated with cell 1, but cannot know which of the N reports meets the triggering condition. Since the report configuration ID is numbered within cell 1, by carrying the report configuration ID on PUSCH, it can be indicated which of the N reports is carried by PUSCH.

[0157] FIG. 12 is another example diagram of the report sending method according to the embodiments of the present application. For example, as shown in FIG. 12, the report configuration 0 and the report configuration 1 are configured on the cell 0, and the PUSCH (PUSCH0) for carrying the report 0 and the PUSCH (PUSCH1) for carrying the report 1 are also configured on the cell 0. The report configuration 0 and the report configuration 1 are respectively associated with the PUCCH0 and the PUCCH1, and the PUCCH0 and the PUCCH1 are respectively associated with the PUSCH0 and the PUSCH1. If the report 0 meets the triggering condition, the terminal device sends the PUCCH0 on the cell 0, and sends the report 0 on the PUSCH0 associated with the PUCCH0. If the report 1 meets the triggering condition, the terminal device sends the PUCCH1 on the cell 0, and sends the report 1 on the PUSCH1 associated with the PUCCH1. Since one report configuration is associated with one dedicated PUCCH and one dedicated PUSCH, the PUSCH does not need to carry the report configuration ID.

[0158] FIG. 13 is another example diagram of the report sending method according to the embodiments of the present application. For example, as shown in FIG. 13, the report configuration 0 is configured on the cell 0, and the PUSCH (PUSCH0) for carrying the report 0 is also configured on the cell 0; the report configuration 1 is configured on the cell 1, and the PUSCH (PUSCH1) for carrying the report 1 is also configured on the cell 1. The report configuration 0 and the report configuration 1 are respectively associated with the PUCCH0 and the PUCCH1, and the PUCCH0 and the PUCCH1 are respectively associated with the PUSCH0 and the PUSCH1. If the report 0 meets the triggering condition, the terminal device sends the PUCCH0 on the cell 0, and sends the report 0 on the PUSCH0 associated with the PUCCH0. If the report 1 meets the triggering condition, the terminal device sends the PUCCH1 on the cell 0, and sends the report 1 on the PUSCH1 associated with the PUCCH1. Since one report configuration is associated with one dedicated PUCCH and one dedicated PUSCH, the PUSCH does not need to carry the report configuration ID.

[0159] It is worth noting that the above FIG. 9 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above FIG. 9.

[0160] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0161] Through the embodiments of the present application, in mode B, the reporting configuration information, the PUCCH and the PUSCH are located in the same cell group. The terminal device can realize sending the reporting on multiple carriers that meet the triggering condition, and can achieve a good compromise between reporting flexibility and reporting overhead.

[0162] Embodiments of the third aspect

[0163] The embodiments of the present application provide a reporting sending method, which is described from the terminal device side. FIG. 14 is a schematic diagram of the reporting sending method of the embodiments of the present application, which is applied to a terminal device configured with two cell groups. As shown in FIG. 15, for mode A, the method comprises the following steps:

[0164] 1401, when one report meets the triggering condition, sending the PUCCH on the first cell, the first cell being a cell configured with the PUCCH in one cell group;

[0165] 1402, receiving the DCI on the fifth cell, and sending the report on the PUSCH indicated by the DCI;

[0166] Wherein, the fifth cell and the first cell belong to the same or different cell groups.

[0167] In some embodiments, the embodiments of the two cell groups and 1401 can refer to the embodiments of the first aspect, which will not be described here.

[0168] In some embodiments, the reporting sending method further comprises: (not shown)

[0169] The terminal device receives a first set of reporting configuration information of a first set of reports, wherein the first set of reporting configuration information is configured on one or more cells of the first cell group, and / or receives a second set of reporting configuration information of a second set of reports, wherein the second set of reporting configuration information is configured on one or more cells of the second cell group. For example, the first set of CSI-ReportConfig is configured in the primary PUCCH group, and the second set of CSI-ReportConfig is configured in the secondary PUCCH group. The embodiments thereof can refer to the embodiments of the first aspect, which will not be described here.

[0170] The following describes in which cell or cell group the reporting configuration information, the PUCCH and the PUSCH are located in mode A.

[0171] In some embodiments, the terminal device sends the PUCCH on the first cell, and receives the DCI on the fifth cell, and the first cell and the fifth cell can belong to one cell group, or belong to different cell groups, that is, no limitation is made to the cell where the DCI is located.

[0172] In some embodiments, the PUCCH is transmitted on the first cell of the first cell group when one of the first group of reports meets the triggering condition; and the PUCCH is transmitted on the first cell of the second cell group when one of the second group of reports meets the triggering condition. For details, refer to the embodiments of the first aspect, which will not be described here.

[0173] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group. For details, refer to the embodiments of the first aspect, which will not be described here.

[0174] In some embodiments, the first group of report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or the second group of report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH. For details, refer to the embodiments of the first aspect, which will not be described here.

[0175] In some embodiments, the sixth cell transmits the PUSCH, the sixth cell and the first cell or the fifth cell belong to one cell group, or the sixth cell is the cell configured by the report configuration information of the transmitted report. Alternatively, the sixth cell is the first cell or the fifth cell. For details, refer to the third cell of the embodiments of the first aspect, which will not be described here.

[0176] In some embodiments, the report includes at least one of a report configuration ID, a cell ID and a cell group ID, wherein the cell group ID indicates the first cell group or the second cell group.

[0177] For example, the report configuration ID is numbered independently within each PUCCH group, so two PUCCH groups may have the same report configuration ID, that is, one report configuration ID cannot uniquely determine one report. Since there is no restriction on the cell where the DCI is located, the PUSCH indicated by the DCI may carry the report associated with the report configuration ID of any PUCCH group. Using the report configuration ID and the PUCCH group ID, a report can be uniquely identified within two PUCCH groups. If the terminal device needs to carry information for identifying the report in the report, the report configuration ID and the PUCCH group ID can be included in the report.

[0178] In some embodiments, the DCI indicates at least one of a report configuration ID, a cell ID and a cell group ID, wherein the cell group ID indicates the first cell group or the second cell group.

[0179] For example, as mentioned before, a report can be uniquely identified by a report configuration ID and a PUCCH group ID in two PUCCH groups. If it is required to indicate by DCI which report is carried by a PUSCH, the report configuration ID and the PUCCH group ID can be indicated by DCI.

[0180] In some embodiments, the number of reports carried by a PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports in the two cell groups satisfying the triggering condition, or the first value is equal to the number of CSI-ReportConfig in the two cell groups.

[0181] For example, a terminal device receives a DCI triggering a report, and the terminal device can send a report in any PUCCH group on the PUSCH indicated by the DCI, so the union of the primary PUCCH group and the secondary PUCCH group can be regarded as a large PUCCH group, and the first value can be configured by RRC signaling (e.g., configured in units of terminal devices), or predefined, or equal to the number of reports in the large PUCCH group satisfying the triggering condition, or equal to the number of CSI-ReportConfig in the large PUCCH group.

[0182] The method described above is explained below by means of specific examples, and the same as before will not be repeated.

[0183] FIG. 15 is an example diagram of a report sending method according to an embodiment of the present application, and the example given in FIG. 15 is different from that in FIG. 5 in that, regardless of which cell in which PUCCH group a terminal device receives a DCI triggering a report, the terminal device can send at least one of report 0 to report 4 on the PUSCH indicated by the DCI. In other words, the DCI and the report sent on the PUSCH can be located in different PUCCH groups. Since the report configuration ID is independently numbered in each PUCCH group, a report can be uniquely identified by the report configuration ID and the PUCCH group ID. For a report carried on a PUSCH, the report configuration ID and the PUCCH group ID of the report are also carried on the PUSCH.

[0184] FIG. 16 is another example diagram of a report sending method according to an embodiment of the present application, and the example given in FIG. 16 is different from that in FIG. 6 in that, regardless of which cell in which PUCCH group a terminal device receives a DCI triggering a report, the terminal device can send at least one of report 0 to report 4 on the PUSCH indicated by the DCI. Since the report configuration ID is independently numbered in each cell, a report can be uniquely identified by the report configuration ID and the cell ID. For a report carried on a PUSCH, the report configuration ID and the cell ID of the report are also carried on the PUSCH.

[0185] FIG. 17 is another example diagram of the report sending method according to the embodiments of the present application. The example given in FIG. 17 is different from that in FIG. 7 in that, no matter on which cell in which PUCCH group the DCI triggering the report is received, the terminal device can send at least one of the reports 0 to 4 on the PUSCH indicated by the DCI. Since the report configuration ID is independently numbered in each PUCCH group, both the report configuration ID and the PUCCH group ID can uniquely identify a report. In the case where the DCI indicates the terminal device to send a certain report on the PUSCH, the DCI can indicate a report by indicating the report configuration ID and the PUCCH group ID.

[0186] FIG. 18 is another example diagram of the report sending method according to the embodiments of the present application. The example given in FIG. 20 is different from that in FIG. 7 in that, no matter on which cell in which PUCCH group the DCI triggering the report is received, the terminal device can send at least one of the reports 0 to 4 on the PUSCH indicated by the DCI. Since the report configuration ID is independently numbered in each cell, both the report configuration ID and the cell ID can uniquely identify a report. In the case where the DCI indicates the terminal device to send a certain report on the PUSCH, the DCI can indicate a report by indicating the report configuration ID and the cell ID.

[0187] It is worth noting that the above FIG. 14 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be properly adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can properly modify the above based on the above, and the present application is not limited to the above FIG. 14.

[0188] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and proper modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0189] According to the embodiments of the present application, the terminal device can send the reports meeting the triggering conditions on multiple carriers, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0190] In all the above embodiments, the case where the terminal device is configured with two PUCCH groups is described, and the method provided by the embodiments of the present application can also be extended to the case where the terminal device has only one PUCCH group, which is not limited by the present application.

[0191] For example, the terminal device has multiple cells, only one of which is configured with PUCCH, and it is considered that the terminal device has only one PUCCH group, and / or, in the case that the terminal device is not configured with a PUCCH secondary cell, it is considered that the terminal device has only one PUCCH group.

[0192] In the method described above, the method applicable to the primary PUCCH group is also applicable to the case that the terminal device has only one PUCCH group, and the present application does not limit this.

[0193] For example, in the case that one report meets the triggering condition, the terminal device transmits PUCCH on the cell configured with PUCCH; the terminal device receives DCI and transmits the report on the PUSCH indicated by the DCI; wherein the cell where the DCI is located and the cell configured with PUCCH can be the same or different.

[0194] Embodiments of the fourth aspect

[0195] The embodiments of the present application provide a report receiving method, which is described from the network device side. The embodiments of the fourth aspect can be combined with the embodiments of the first or third aspect, and the same content as the embodiments of the first or third aspect will not be described again.

[0196] FIG. 19 is a schematic diagram of a report receiving method according to an embodiment of the present application, as shown in FIG. 19, for mode A, the method comprises:

[0197] 1901, the network device receives PUCCH transmitted by the terminal device on the first cell when one report meets the triggering condition, the terminal device is configured with two cell groups, and the first cell is the cell configured with PUCCH in the cell group;

[0198] 1902, the network device transmits downlink control information (DCI) on the second cell, and receives the report transmitted by the terminal device on the physical uplink shared channel (PUSCH) indicated by the DCI; wherein the second cell and the first cell belong to one cell group;

[0199] Or, the network device transmits downlink control information (DCI) on the fifth cell, and receives the report transmitted by the terminal device on the physical uplink shared channel (PUSCH) indicated by the DCI; wherein the fifth cell and the first cell belong to the same or different cell groups.

[0200] It is noticeable that the above Fig. 19 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution sequence between the operations can be adjusted as appropriate, and in addition, some operations can be added or some operations can be deleted. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above Fig. 19.

[0201] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0202] Through the embodiments of the present application, the terminal device can transmit the report on the multiple carriers that meet the triggering condition, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0203] Embodiments of the fifth aspect

[0204] The embodiments of the present application provide a report receiving method, which is described from the network device side. The embodiments of the fifth aspect can be combined with the embodiments of the second aspect, and the same content as the embodiments of the second aspect will not be described again.

[0205] Fig. 20 is a schematic diagram of a report receiving method according to an embodiment of the present application. As shown in Fig. 20, the method comprises:

[0206] 2001, the network device receives a PUCCH transmitted by a terminal device on a first cell when a report meets a triggering condition, the terminal device is configured with two cell groups, and the first cell is a cell configured with a PUCCH in a cell group;

[0207] 2002, the network device further receives the report transmitted by the terminal device on a PUSCH associated with the PUCCH, and the network device receives the PUSCH on a fourth cell; and the fourth cell and the first cell belong to the one cell group.

[0208] It is noticeable that the above Fig. 20 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution sequence between the operations can be adjusted as appropriate, and in addition, some operations can be added or some operations can be deleted. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above Fig. 20.

[0209] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone or in combination of one or more of the above embodiments.

[0210] Through the embodiments of the present application, the terminal device can send the reports meeting the triggering condition on multiple carriers, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0211] Embodiments of the sixth aspect

[0212] The embodiments of the present application provide a report sending device. The device can be a terminal device configured with two cell groups, or can be one or more components or assemblies configured in the terminal device configured with two cell groups. Since the principle of solving the problem of the device is similar to the method of the embodiments of the first aspect, the specific implementation thereof can refer to the implementation of the method described in the embodiments of the first aspect, and the same or related contents will not be described repeatedly.

[0213] FIG. 21 is a schematic diagram of a report sending device according to an embodiment of the present application. As shown in FIG. 21, the report sending device 2100 includes:

[0214] a transmitter 2101 configured to send a PUCCH on a first cell when a report meets a triggering condition, the first cell being a cell configured with the PUCCH in a cell group;

[0215] a receiver 2102 configured to receive a downlink control information (DCI) on a second cell;

[0216] and the transmitter 2101 is configured to send the report on a physical uplink shared channel (PUSCH) indicated by the DCI;

[0217] wherein the second cell and the first cell belong to one cell group.

[0218] In some embodiments, the two cell groups are a primary PUCCH group and a secondary PUCCH group, respectively.

[0219] In some embodiments, the second cell is the first cell.

[0220] In some embodiments, the receiver 2102 is further configured to receive first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of a first cell group, and / or receive second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of a second cell group.

[0221] In some embodiments, the transmitter 2101 transmits the PUCCH on the first cell of the first cell group when one of the first group of reports meets the triggering condition;

[0222] In the case that one of the second group of reports meets the triggering condition, the transmitter 2101 transmits the PUCCH on the first cell of the second cell group.

[0223] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group.

[0224] In some embodiments, the first group of report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or,

[0225] The second group of report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH.

[0226] In some embodiments, the transmitter 2401 transmits the PUSCH on the third cell, the third cell belongs to one cell group with the first cell, or the third cell belongs to one cell group with the second cell.

[0227] In some embodiments, the third cell is the first cell, or the third cell is the second cell, or the third cell is the cell on which the report configuration information of the transmitted report is configured.

[0228] In some embodiments, the report includes at least one of the report configuration ID, the cell ID and the local cell ID, wherein the local cell ID is numbered in the cell group.

[0229] In some embodiments, the DCI indicates at least one of the report configuration ID, the cell ID and the local cell ID, wherein the local cell ID is numbered in the cell group.

[0230] In some embodiments, the second cell is the cell on which the report configuration information of the transmitted report is configured.

[0231] In some embodiments, the number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports meeting the triggering condition in one cell group, or the first value is equal to the number of report configuration information in one cell group.

[0232] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The report sending device 2100 can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0233] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 21, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc., and the present application is not limited thereto.

[0234] Through the embodiments of the present application, the terminal device can send reports on multiple carriers that meet the triggering condition, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0235] Embodiments of the seventh aspect

[0236] The embodiments of the present application provide a report sending device. The device can be, for example, a terminal device configured with two cell groups, or a certain component or assembly configured in a terminal device configured with two cell groups. Since the principle of solving the problem of the device is similar to the method of the embodiments of the second aspect, the specific implementation thereof can refer to the implementation of the method described in the embodiments of the second aspect, and the same or related content will not be described repeatedly.

[0237] FIG. 22 is another schematic diagram of the report sending device according to an embodiment of the present application. As shown in FIG. 22, the report sending device 2200 includes a transmitter 2201 configured to send a PUCCH on a first cell when a report meets a triggering condition, the first cell being a cell configured with the PUCCH in a cell group, and send the report on a PUSCH associated with the PUCCH, wherein the transmitter 2201 sends the PUSCH on a fourth cell;

[0238] The fourth cell and the first cell belong to one cell group.

[0239] In some embodiments, as shown in FIG. 22, the report sending device 2200 further includes a receiver 2202,

[0240] The receiver 2202 receives first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of a first cell group, and / or receives second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of a second cell group.

[0241] In some embodiments, the transmitter 2201 transmits the PUCCH on the first cell of the first cell group when one of the first group of reports meets the triggering condition;

[0242] The transmitter 2201 transmits the PUCCH on the first cell of the second cell group when one of the second group of reports meets the triggering condition.

[0243] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group.

[0244] In some embodiments, the first group of report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or,

[0245] The second group of report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH.

[0246] In some embodiments, the report includes a report configuration ID.

[0247] In some embodiments, the fourth cell is a cell on which the report configuration information of the transmitted report is configured.

[0248] In some embodiments, the number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports meeting the triggering condition in the cell group, or the first value is equal to the number of report configuration information in the cell group.

[0249] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The report transmitting apparatus 2200 can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0250] In addition, for the sake of simplicity, only the connection relationship or signal path between the various components or modules is exemplarily shown in FIG. 22, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The various components or modules described above can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0251] Through the embodiments of the present application, the terminal device can transmit reports meeting the triggering condition on multiple carriers, and can achieve a good compromise between reporting flexibility and reporting overhead.

[0252] Embodiments of the eighth aspect

[0253] Embodiments of the present application provide a report sending apparatus. The apparatus may, for example, be a terminal device configured with two cell groups, or may be one or more components or assemblies configured in a terminal device configured with two cell groups. Since the principle of solving problems of the apparatus is similar to the method of the embodiments of the third aspect, the specific implementation thereof can refer to the implementation of the method described in the embodiments of the third aspect, and the same or related contents will not be described repeatedly.

[0254] FIG. 23 is another schematic diagram of a report sending apparatus according to an embodiment of the present application. As shown in FIG. 23, the report sending apparatus 2300 includes:

[0255] a transmitter 2301 configured to send a PUCCH on a first cell when one report meets a triggering condition, the first cell being a cell in which a PUCCH is configured in one cell group;

[0256] a receiver 2302 configured to receive a DCI on a fifth cell,

[0257] and the transmitter 2301 is configured to send a report on a PUSCH indicated by the DCI; wherein the fifth cell and the first cell belong to the same or different cell groups.

[0258] In some embodiments, the report includes at least one of a report configuration ID, a cell ID, and a cell group ID, wherein the cell group ID indicates the first cell group or the second cell group.

[0259] In some embodiments, the DCI indicates at least one of a report configuration ID, a cell ID, and a cell group ID, wherein the cell group ID indicates the first cell group or the second cell group.

[0260] In some embodiments, the number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports meeting the triggering condition in the two cell groups, or the first value is equal to the number of report configuration information in the two cell groups.

[0261] In some embodiments, the receiver 2302 further receives first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of the first cell group, and / or receives second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of the second cell group.

[0262] In some embodiments, when one report in the first group of reports meets the triggering condition, the transmitter 2301 sends a PUCCH on a first cell of the first cell group;

[0263] In a case where one of the second group of reports meets the triggering condition, the transmitter 2301 transmits a PUCCH on the first cell of the second cell group.

[0264] In some embodiments, the first group of report configuration information is configured on the first cell of the first cell group, and / or the second group of report configuration information is configured on the first cell of the second cell group.

[0265] In some embodiments, the first group of report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or,

[0266] The second group of report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH.

[0267] In some embodiments, the transmitter 2301 transmits a PUSCH on the sixth cell, the sixth cell and the first cell belong to one cell group, or the sixth cell and the fifth cell belong to one cell group, or the sixth cell is the first cell, or the sixth cell is the fifth cell, or the sixth cell is the cell on which the report configuration information of the transmitted report is configured.

[0268] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The report transmitting apparatus 2300 can also include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0269] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 23, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0270] Through the embodiments of the present application, the terminal device can transmit the reports meeting the triggering condition on multiple carriers, and achieve a good compromise between reporting flexibility and reporting overhead.

[0271] Embodiments of the ninth aspect

[0272] The embodiments of the present application provide a report receiving apparatus. The apparatus may, for example, be a network device, and since the principle of solving the problem of the apparatus is similar to the method of the embodiments of the fourth aspect, the specific implementation thereof can refer to the implementation of the method described in the embodiments of the fourth aspect, and the same or related content will not be described repeatedly.

[0273] FIG. 24 is a schematic diagram of a report receiving apparatus according to an embodiment of the present application. As shown in FIG. 24, the report receiving apparatus 2400 includes:

[0274] a receiver 2401 configured to receive a PUCCH sent by a terminal device on a first cell when a report of the terminal device meets a triggering condition, the terminal device being configured with two cell groups, the first cell being a cell configured with a PUCCH in one of the cell groups;

[0275] a transmitter 2402 configured to send a downlink control information (DCI) on a second cell, and the receiver 2401 is configured to receive a report sent by the terminal device on a physical uplink shared channel (PUSCH) indicated by the DCI; wherein the second cell belongs to the same cell group as the first cell,

[0276] or, a transmitter 2402 configured to send a downlink control information (DCI) on a fifth cell, and the receiver 2401 is configured to receive a report sent by the terminal device on a physical uplink shared channel (PUSCH) indicated by the DCI; wherein the fifth cell and the first cell belong to the same or different cell groups.

[0277] Optionally, the transmitter 2402 is further configured to send first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of a first cell group, and / or send second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of a second cell group. For details, refer to the foregoing embodiments, which will not be described here.

[0278] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The report receiving apparatus 2400 can further include other components or modules, and the specific content of these components or modules can refer to related technologies.

[0279] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 24, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0280] Through the embodiments of the present application, the terminal device can send reports that meet the triggering condition on multiple carriers, and achieve a good compromise between reporting flexibility and reporting overhead.

[0281] Embodiments of the tenth aspect

[0282] The embodiment of the present application provides a report receiving device. The device can be a network device, and the principle of solving problems of the device is similar to the method of the embodiment of the fifth aspect, and therefore the specific implementation can refer to the implementation of the method of the embodiment of the fifth aspect, and the same or related contents are not described again.

[0283] Fig. 25 is a schematic diagram of the report receiving device of the embodiment of the present application. As shown in Fig. 25, the report receiving device 2500 comprises:

[0284] a receiver 2501 configured to receive the PUCCH sent by the terminal device on the first cell when a report meets a trigger condition, the terminal device being configured with two cell groups, and the first cell being a cell configured with the PUCCH in one cell group;

[0285] The receiver 2501 is further configured to receive the report sent by the terminal device on the PUSCH associated with the PUCCH, and the receiver 2501 receives the PUSCH on the fourth cell; and the fourth cell and the first cell belong to one cell group.

[0286] Optionally, the device can further comprise a transmitter 2502 configured to send the first group of report configuration information of the first group of reports, wherein the first group of report configuration information is configured on one or more cells of the first cell group, and / or send the second group of report configuration information of the second group of reports, wherein the second group of report configuration information is configured on one or more cells of the second cell group, and the specific implementation can refer to the foregoing embodiment, and details are not described herein. It should be noted that the above only describes the components or modules related to the present application, but the present application is not limited to this. The report receiving device 2500 can further comprise other components or modules, and the specific content of the components or modules can refer to the related art.

[0287] In addition, for the sake of simplicity, only the connection relationship or signal direction between the components or modules is shown in Fig. 25, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc., and the present application is not limited to this.

[0288] Through the embodiment of the present application, the terminal device can send the report meeting the trigger condition on multiple carriers, and a good compromise between reporting flexibility and reporting overhead can be achieved.

[0289] Embodiment of the eleventh aspect

[0290] The embodiment of the present application further provides a communication system, which can refer to Fig. 1, and the same content as the embodiments of the first to tenth aspects is not described again.

[0291] In some embodiments, the communication system 100 can at least include the terminal device 102 or 103 and / or the network device 101, as described below.

[0292] The embodiments of the present application also provide a terminal device, but the present application is not limited to this, and can also be other devices.

[0293] FIG. 26 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 26, the terminal device 2600 can include a processor 2610 and a memory 2620. The memory 2620 stores data and programs and is coupled to the processor 2610. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions.

[0294] For example, the processor 2610 can be configured to execute programs to implement the reporting sending method according to the first to third aspects.

[0295] As shown in FIG. 26, the terminal device 2600 can also include a communication module 2630, an input unit 2640, a display 2650, and a power supply 2660. The functions of the above-mentioned components are similar to those of the prior art, and will not be described here. It is worth noting that the terminal device 2600 does not necessarily include all the components shown in FIG. 26, and the above-mentioned components are not essential; in addition, the terminal device 2600 can also include components not shown in FIG. 26, which can be referred to the prior art.

[0296] The embodiments of the present application also provide a network device, which can be a base station for example, but the present application is not limited to this, and can also be other network devices.

[0297] FIG. 27 is a schematic diagram of a network device according to an embodiment of the present application. As shown in FIG. 27, the network device 2700 can include a processor 2710 (such as a central processing unit CPU) and a memory 2720. The memory 2720 is coupled to the processor 2710. The memory 2720 can store various data; in addition, it also stores programs 2730 for information processing, and executes the programs 2730 under the control of the processor 2710.

[0298] For example, the processor 2710 can be configured to execute programs to implement the reporting receiving method according to the fourth and fifth aspects.

[0299] In addition, as shown in FIG. 27, the network device 2700 can further include a transceiver 2740 and an antenna 2750, etc. The functions of the above components are similar to those in the prior art, and thus are not described here. It is worth noting that the network device 2700 does not necessarily include all the components shown in FIG. 27; in addition, the network device 2700 can also include components not shown in FIG. 27, which can be referred to the prior art.

[0300] The embodiments of the present application further provide a computer program, which, when executed in a terminal device, causes the terminal device to perform the reporting sending method in the first to third aspects.

[0301] The embodiments of the present application further provide a storage medium storing a computer program, which causes a terminal device to perform the reporting sending method in the first to third aspects.

[0302] The embodiments of the present application further provide a computer program, which, when executed in a network device, causes the network device to perform the reporting receiving method in the fourth and fifth aspects.

[0303] The embodiments of the present application further provide a storage medium storing a computer program, which causes a network device to perform the reporting receiving method in the fourth and fifth aspects.

[0304] The apparatuses and methods described above can be implemented by hardware, or by hardware combined with software. The present application relates to a computer readable program, which, when executed by a logic component, can cause the logic component to implement the apparatuses or constituent components described above, or 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.

[0305] The methods / apparatuses described in conjunction with the embodiments of the present application can be directly embodied as hardware, software modules executed by a processor, or a combination of the two. For example, one or more of the functional blocks in the functional block diagram, and / or a combination of one or more of the functional blocks, can correspond to individual software modules of a computer program flow, or to individual hardware modules. These software modules can correspond to individual steps shown in the figures, respectively. These hardware modules can be implemented by, for example, fixing the software modules with a field programmable gate array (FPGA).

[0306] The software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (e.g., mobile terminal) is a MEGA-SIM card or a large capacity flash memory device, the software modules can be stored in the MEGA-SIM card or the large capacity flash memory device.

[0307] One or more of the functional blocks described in the accompanying drawings and / or one or more combinations of the functional blocks can 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, discrete gate or transistor logic, discrete hardware components, or any appropriate combination thereof, for performing the functions described in this application. One or more of the functional blocks described in the accompanying drawings and / or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0308] The application has been described in connection with certain embodiments. However, one of ordinary skill in the art will readily recognize from the disclosure herein that changes and modifications can be made thereto without departing from the scope of the present application. Accordingly, nothing in the present application should be construed as a limitation on the scope of the present application, but is intended to cover all possible modifications and equivalents.

[0309] With respect to the embodiments including the above embodiments, the following supplementary notes are also disclosed:

[0310] 1. A report transmitting apparatus applied to a terminal device configured with two cell groups, wherein the apparatus comprises:

[0311] a transmitter that transmits a PUCCH on a first cell when a report meets a trigger condition, the first cell being a cell configured with a PUCCH in one cell group;

[0312] a receiver that receives a DCI on a fifth cell, and the transmitter transmits the report on a PUSCH indicated by the DCI;

[0313] The fifth cell and the first cell belong to the same or different cell groups.

[0314] 2.The apparatus of any one of the preceding clauses, wherein,

[0315] The report comprises at least one of a report configuration ID, a cell ID, and a cell group ID, wherein the cell group ID indicates a first cell group or a second cell group.

[0316] 3.The apparatus of any one of the preceding clauses, wherein,

[0317] The DCI indicates at least one of a report configuration ID, a cell ID, and a cell group ID, wherein the cell group ID indicates a first cell group or a second cell group.

[0318] 4.The apparatus of any one of the preceding clauses, wherein,

[0319] A number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to a number of reports in the two cell groups that satisfy a triggering condition, or the first value is equal to a number of report configuration information in the two cell groups.

[0320] 5.The apparatus of any one of the preceding clauses, wherein,

[0321] The receiver further receives a first set of report configuration information for a first set of reports, wherein the first set of report configuration information is configured on one or more cells of the first cell group, and / or receives a second set of report configuration information for a second set of reports, wherein the second set of report configuration information is configured on one or more cells of the second cell group.

[0322] 6.The apparatus of any one of the preceding clauses 5, wherein, when one report in the first set of reports satisfies a triggering condition, the transmitter transmits a PUCCH on a first cell of the first cell group.

[0323] In a case where one report in the second set of reports satisfies a triggering condition, the transmitter transmits a PUCCH on a first cell of the second cell group.

[0324] 7.The apparatus of any one of the preceding clauses 5, wherein,

[0325] The first set of report configuration information is configured on a first cell of the first cell group, and / or the second set of report configuration information is configured on a first cell of the second cell group.

[0326] 8.The apparatus of any one of the preceding clauses, wherein,

[0327] The first group of reporting configuration information of the first group of reports is associated with one PUCCH, or the reporting configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or,

[0328] The second group of reporting configuration information of the second group of reports is associated with one PUCCH, or the reporting configuration information of each report in the second group of reports is respectively associated with one PUCCH.

[0329] 9. The apparatus according to append 1, wherein the transmitter transmits PUSCH on a sixth cell, the sixth cell and the first cell belong to one cell group, or the sixth cell and the fifth cell belong to one cell group, or the sixth cell is the first cell, or the sixth cell is the fifth cell, or the sixth cell is a cell configured by reporting configuration information of the transmitted report.

[0330] 10. A report receiving apparatus applied to a network device, wherein the apparatus comprises:

[0331] a receiver which receives PUCCH transmitted by a terminal device on a first cell when one report meets a trigger condition, the terminal device is configured with two cell groups, and the first cell is a cell configured with PUCCH in one cell group;

[0332] a transmitter which transmits DCI on a fifth cell, and the receiver receives the report transmitted by the terminal device on PUSCH indicated by the DCI;

[0333] wherein the fifth cell and the first cell belong to the same or different cell groups.

Claims

1. A report transmission apparatus applied to a terminal device configured with two cell groups, wherein, The apparatus comprises: a transmitter which transmits a PUCCH on a first cell when a report meets a triggering condition, the first cell being a cell in a cell group on which a PUCCH is configured; a receiver which receives a downlink control information (DCI) on a second cell, and the transmitter transmits the report on a physical uplink shared channel (PUSCH) indicated by the DCI; wherein the second cell belongs to the cell group as the first cell.

2. The apparatus of claim 1, wherein, The second cell is the first cell.

3. The apparatus according to claim 1, wherein the receiver further receives first group report configuration information of a first group of reports, wherein the first group report configuration information is configured on one or more cells of a first cell group, and / or receives second group report configuration information of a second group of reports, wherein the second group report configuration information is configured on one or more cells of a second cell group.

4. The apparatus of claim 3, wherein, The transmitter transmits a PUCCH on a first cell of the first cell group when a report in the first group of reports meets a triggering condition. The transmitter transmits a PUCCH on a first cell of the second cell group when a report in the second group of reports meets a triggering condition.

5. The apparatus according to claim 3, wherein the first group report configuration information is configured on a first cell of the first cell group, and / or the second group report configuration information is configured on a first cell of the second cell group.

6. The apparatus of claim 3, wherein, The first group report configuration information of the first group of reports is associated with one PUCCH, or the report configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or The second group report configuration information of the second group of reports is associated with one PUCCH, or the report configuration information of each report in the second group of reports is respectively associated with one PUCCH.

7. The apparatus of claim 1, wherein, The transmitter transmits a PUSCH on a third cell, the third cell belonging to the cell group as the first cell, or the third cell belonging to the cell group as the second cell, or the third cell being the first cell, or the third cell being the second cell, or the third cell being a cell on which report configuration information of the transmitted report is configured.

8. The apparatus of claim 1, wherein, The report comprises at least one of a report configuration ID, a cell ID and a local cell ID, wherein the local cell ID is numbered in a cell group.

9. The apparatus of claim 1, wherein, The DCI indicates at least one of a report configuration ID, a cell ID and a local cell ID, wherein the local cell ID is numbered in a cell group.

10. The apparatus of claim 1, wherein, The second cell is a cell on which report configuration information of the transmitted report is configured.

11. A report transmission apparatus applied to a terminal device configured with two cell groups, wherein, The apparatus comprises: a transmitter which transmits a PUCCH on a first cell when a report meets a triggering condition, the first cell being a cell in a cell group on which a PUCCH is configured; and transmits the report on a PUSCH associated with the PUCCH, wherein the transmitter transmits the PUSCH on a fourth cell; The fourth cell belongs to the one cell group with the first cell.

12. The apparatus of claim 11, wherein, The fourth cell is the first cell.

13. The apparatus of claim 11, wherein, The apparatus further includes a receiver, The receiver receives first group reporting configuration information of a first group of reports, wherein the first group reporting configuration information is configured on one or more cells of a first cell group, and / or receives second group reporting configuration information of a second group of reports, wherein the second group reporting configuration information is configured on one or more cells of a second cell group.

14. The apparatus of claim 13, wherein, The transmitter transmits a PUCCH on a first cell of the first cell group when one report in the first group of reports satisfies a triggering condition. The transmitter transmits a PUCCH on a first cell of the second cell group when one report in the second group of reports satisfies a triggering condition.

15. The apparatus of claim 13, wherein, The first group reporting configuration information is configured on a first cell of the first cell group, and / or the second group reporting configuration information is configured on a first cell of the second cell group.

16. The apparatus of claim 13, wherein, The first group reporting configuration information of the first group of reports is associated with one PUCCH, or the reporting configuration information of each report in the first group of reports is respectively associated with one PUCCH; and / or, The second group reporting configuration information of the second group of reports is associated with one PUCCH, or the reporting configuration information of each report in the second group of reports is respectively associated with one PUCCH.

17. The apparatus of claim 11, wherein, The report includes a reporting configuration ID.

18. The apparatus of claim 11, wherein, The fourth cell is a cell on which reporting configuration information of a transmitted report is configured.

19. The apparatus of claim 1 or 11, wherein, The number of reports carried by the PUSCH is determined according to a first value, wherein the first value is configured or predefined, or the first value is equal to the number of reports in a cell group that satisfy a triggering condition, or the first value is equal to the number of reporting configuration information in a cell group.

20. A report receiving apparatus applied to a network device, wherein, The apparatus includes: a receiver that receives a PUCCH transmitted by a terminal device on a first cell when one report of the terminal device satisfies a triggering condition, the terminal device being configured with two cell groups, the first cell being a cell in one cell group on which a PUCCH is configured; a transmitter that transmits a downlink control information (DCI) on a second cell, and the receiver receives the report transmitted by the terminal device on a physical uplink shared channel (PUSCH) indicated by the DCI; wherein the second cell belongs to the one cell group with the first cell, or the receiver further receives the report transmitted by the terminal device on a PUSCH associated with the PUCCH, wherein the receiver receives the PUSCH on a fourth cell; wherein the fourth cell belongs to the one cell group with the first cell.

Citation Information

Patent Citations

  • Cell grouping for multi-cell scheduling

    US20240292409A1

  • Cell grouping for multi-cell scheduling

    WO2023137091A1

  • Channel state information reporting method and apparatus

    WO2024031696A1

  • Trigger conditions for event-driven UE beam reporting

    WO2024033844A1

  • CSI reporting in a multi-cell scheduling environment

    WO2024058168A1