Information reporting method and apparatus, information receiving method and apparatus, device, readable storage medium and computer program product

Abstract

The present application relates to the technical field of communications, and in particular to an information reporting method and apparatus, an information receiving method and apparatus, a device, a readable storage medium and a computer program product. The method comprises: a terminal sends first information on a first uplink resource, or a terminal sends first information on the first uplink resource and sends second information on a second uplink resource, wherein the first information is used for indicating whether the terminal has executed sending of the second information, and the second information comprises related information for reporting information content.

Description

Information reporting and receiving methods, devices, equipment, readable storage media, and computer program products

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410403498.X, filed in China on April 3, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to an information reporting and receiving method, apparatus, device, readable storage medium, and computer program product. Background Technology

[0004] Currently, beam reports are carried via uplink control information (UCI), which lacks a retransmission mechanism, except for Hybrid Automatic Repeat Request-ACK (HARQ-ACK). Therefore, for terminal-triggered Layer 1 / Layer 2 (L1 / L2) beam reports carried via UCI, if the network-side equipment does not detect the beam report, it cannot determine whether the user equipment (UE) failed to send the report due to unmet conditions or poor channel conditions. In this situation, ensuring the reliability of terminal-triggered beam reports requires further optimization. Summary of the Invention

[0005] This application provides an information reporting and receiving method, apparatus, device, readable storage medium, and computer program product, which can solve the problem that when the network-side device does not detect the terminal's reported information, the reason for the non-detection cannot be known, resulting in low reliability of information reporting triggered by the terminal.

[0006] Firstly, an information reporting method is provided, including:

[0007] The terminal sends the first information on the first uplink resource;

[0008] or,

[0009] The terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource;

[0010] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content.

[0011] Secondly, an information receiving method is provided, including:

[0012] The network-side device receives the first information on the first uplink resource;

[0013] or,

[0014] The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource.

[0015] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

[0016] Thirdly, an information reporting device is provided, comprising:

[0017] The first transmitting module is used for:

[0018] The terminal sends the first information on the first uplink resource;

[0019] or,

[0020] The terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource;

[0021] The first information is used to indicate whether the terminal should send the second information, and the second information includes relevant information about the reported information content from the first sending module.

[0022] Fourthly, an information receiving device is provided, comprising:

[0023] The first receiving module is used for:

[0024] The network-side device receives the first information on the first uplink resource;

[0025] or,

[0026] The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource.

[0027] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

[0028] Fifthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0029] Sixthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0030] The terminal sends the first information on the first uplink resource;

[0031] or,

[0032] The terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource;

[0033] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content.

[0034] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0035] The network-side device receives the first information on the first uplink resource;

[0036] or,

[0037] The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource.

[0038] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content.

[0039] Eighthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first or second aspect.

[0040] A ninth aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second aspect.

[0041] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first or second aspect.

[0042] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the method as described in the first or second aspect.

[0043] In this embodiment, the terminal sends first information on the first uplink resource and decides whether to send second information on the second uplink resource based on the actual situation. The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content. In this way, even if the network-side device fails to detect the terminal's reported information (i.e., the second information), the network-side device can still know whether the terminal has performed the information reporting behavior (i.e., whether it has sent the second information) based on the first information. The network-side device can determine that the failure to receive the information may be due to poor channel conditions, rather than the terminal failing to meet the reporting trigger event. This allows the network-side device to perform adaptive processing in the future, improving the reliability of the terminal's triggered information reporting. Attached Figure Description

[0044] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0045] Figure 2a is a flowchart illustrating the information reporting method provided in an embodiment of this application;

[0046] Figure 2b is a flowchart illustrating the information receiving method provided in an embodiment of this application;

[0047] Figure 3a is a schematic diagram of one of the application scenarios provided in the embodiments of this application;

[0048] Figure 3b is a second schematic diagram of an application scenario provided in the embodiments of this application;

[0049] Figure 3c is a third schematic diagram of the application scenario provided in the embodiments of this application;

[0050] Figure 3d is a fourth schematic diagram of the application scenario provided in the embodiments of this application;

[0051] Figure 3e is a schematic diagram of the fifth application scenario provided in the embodiments of this application;

[0052] Figure 4a is a schematic diagram of the information reporting device provided in an embodiment of this application;

[0053] Figure 4b is a schematic diagram of the information receiving device provided in an embodiment of this application;

[0054] Figure 5 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0055] Figure 6 is a schematic diagram of the structure of the terminal provided in an embodiment of this application;

[0056] Figure 7 is a schematic diagram of the structure of a network-side device provided in an embodiment of this application;

[0057] Figure 8 is a second schematic diagram of the network-side device provided in an embodiment of this application. Detailed Implementation

[0058] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0059] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0060] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

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

[0062] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The base station may be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmission Reception Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0063] Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Core network functions (BSF), application functions (AF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example for description, and does not limit the specific type of core network equipment.

[0064] To better understand the technical solution of this application, the following will be introduced first:

[0065] Based on event-triggered measurement and reporting

[0066] In the current standard, event-triggered measurements and reported measurements are L3 measurement results, primarily used to assess cell quality for handover purposes. The UE will only perform L3 measurements on neighboring cells when the quality of the serving cell falls below a certain threshold (i.e., event A2 in Table 1 below); and the UE will only perform L3 reporting when the measurement results of the neighboring cell meet a certain event (i.e., one of the events in Table 1 below). For the event definitions in Table 1 below, L3 reporting currently uses a Measurement Configuration (MeasConfig) associated with a Reporting Configuration (ReportConfig) and a Measurement Object (MeasObject). The ReportConfig is associated with an event configuration. In L3 reporting, to enable the network to determine the event corresponding to the reported content, in addition to the L3 measurement results, the terminal also reports the MeasConfig id.

[0067] Table 1

[0068] The parameters in Table 1 are explained as follows:

[0069] Ms: Service cell measurement results;

[0070] Mn: Neighbor cell measurement results, without considering any offset;

[0071] Ofn: Specific offset of the neighboring cell measurement object;

[0072] Ocn: Neighboring cell-level specific offset;

[0073] Mp: Measurement result of the primary serving cell (SpCell), without considering any offset;

[0074] Ofp: SpCell measures a specific offset of an object;

[0075] Ocp: SpCell cell-level specific offset;

[0076] Hys: The hysteresis parameter of the event;

[0077] Off: The offset parameter of the event;

[0078] Mi: Interference measurement result;

[0079] Beam measurement and reporting

[0080] Beam measurement

[0081] Analog beamforming is transmitted across the full bandwidth, and each polarization element on the panel of each high-frequency antenna array can only transmit an analog beam in a time-division multiplexed manner. The beamforming weights of the analog beam are achieved by adjusting the parameters of devices such as the RF front-end phase shifter.

[0082] Currently, in academia and industry, the training of simulated beamforming vectors is usually carried out using a polling method. That is, each element of each antenna panel in each polarization direction sends training signals (i.e., candidate beamforming vectors) sequentially at a predetermined time in a time-division multiplexing manner. After measurement, the terminal feeds back a beam report, which is used by the network-side equipment to implement simulated beam transmission in the next transmission service.

[0083] Currently, the standard only supports beam measurement using either the Channel State Information-Reference Signal (CSI-RS) or the Synchronization Signal Block (SSB). The CSI-RS used for beam measurement has only 1 to 2 ports. The SSB is a periodic reference signal, while the CSI-RS used for beam measurement can be periodic, semi-continuous, or aperiodic.

[0084] Beam measurement is divided into L1 beam measurement and L3 beam measurement. L1 beam measurement in Releases 15 and 16 was limited to the serving cell. Release 15 only supported Layer 1 Reference Signal Receiving Power (L1-RSRP) measurement, while Release 16 introduced L1-SINR, incorporating inter-cell or inter-user interference into the beam measurement. Release 17, under the Cross-Cell Beam Management and Cross-Cell Multi-Transmit / Receive Nodes project, supported L1 beam measurement of neighboring cells that are on the same frequency and synchronized with the current serving cell. Release 18, under the Mobility Enhancement project, supported L1 beam measurement of neighboring cells that are asynchronous and on different frequencies. Both currently only support SSB-based L1-RSRP measurement. After performing L1 beam measurement based on the network-configured measurement resources, the terminal selects a portion of the beams to report based on the measurement results.

[0085] Beam reporting

[0086] Currently, the standard supports reporting L1 beam measurements in the following quantities: L1-Reference Signal Receiving Power (L1-RSRP), L1-Reference Signal Received Quality (L1-RSRQ), and L1-Signal Interference Noise Ratio (L1-SINR). Beam reporting can be group-based or non-group-based. For non-group-based beam reporting, the terminal selects up to four beams from all measurement resources configured on the network side, based on the measurement quantity. For group-based beam reporting, in Release 15 / 16, the terminal selects a pair of beams that can be simultaneously received by the UE based on the measurement results.

[0087] In the existing protocol, if the report quantity field in the higher-layer parameter CSI ReportConfig is configured as "cri-RSRP", "cri-SINR", "ssb-Index-SINR", or "ssb-Index-RSRP", it indicates that the current CSI report is a beam report. Furthermore, when the groupBasedBeamReporting field is "enabled", the UE can only report one beam: containing two channel measurement resource (CMR) identifiers (CSI-RS Resource Indication (CRI) or SSB Resource Indication (SSBRI)) and their corresponding L1-RSRP / L1-SINR values. When the groupBasedBeamReporting field is "disabled", the UE may report the CMR identifiers and their corresponding L1-RSRPs for four beams. When the number of reported beams is greater than 1, the L1-RSRP / L1-SINR values, except for the maximum L1-RSRP / L1-SINR value, are reported differentially from the maximum value. In the Release 17 multi-transmitter-receiver node project, the group-based beam reporting method was enhanced. The terminal can select up to 4 pairs of beams that the UE can simultaneously receive from the network-configured measurement resources for reporting, and different beams in each pair correspond to different transmit-receiver nodes, thus ensuring that the network can simultaneously transmit this pair of beams. In the Release 18 L1 / L2-Triggered Mobility (hereinafter referred to as LTM) project, L1 reporting for handover, namely ltm-CSI-ReportConfig, was introduced. In an L1 report for handover, the terminal can report up to 4 cells, with 4 beam measurement results reported for each cell, i.e., a maximum of 16 beams and their corresponding measurement results.

[0088] In the current standard, the content of L1 beam reports is placed in CSI part I, and the UCI bit length is fixed.

[0089] UCI and Media Access Layer Control Element (MAC CE)

[0090] In the current standard, beam reporting is carried out via UCI and sent to the network. Since the uplink resources carrying beam reports are allocated by the network specifically for beam reporting, and the UE must generally report measurement results on the corresponding resources, and the terminal does not cache the report content after reporting, the network can directly determine whether the report was successfully received by checking the corresponding uplink resources. For cases where transmission is unsuccessful, the network can either re-trigger the beam report or wait for the next cycle; the specific operation depends on the network implementation. Therefore, the standard does not define an acknowledgment feedback mechanism for beam reports based on UCI. For data transmission based on MAC CE, since the MAC CE is generated and cached by the MAC layer, the MAC layer will only release the cached data after the terminal receives a new physical downlink control channel (PDCCH) with the same Hybrid Automatic Repeat Request (HARQ) process ID as the one transmitting the MAC CE.

[0091] Currently, beam reports are all carried via UCI, which lacks a retransmission mechanism except for HARQ-ACK. Therefore, for terminal-triggered L1 / L2 beam reports carried via UCI, if the network-side equipment does not detect the beam report, it's impossible to determine whether the UE failed to send the report due to unmet conditions or poor channel conditions. In this situation, ensuring the reliability of terminal-triggered beam reports requires further optimization.

[0092] The information reporting method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0093] Referring to Figure 2a, this embodiment of the application provides an information reporting method, the execution subject of which is a terminal, and the method includes:

[0094] Step 201: The terminal sends the first information on the first uplink resource; or, the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0095] The first information contains information related to the terminal sending the second information, and the second information contains information related to the content of the reported information.

[0096] In this embodiment, the terminal sends first information on the first uplink resource and decides whether to send second information on the second uplink resource based on the actual situation. The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content. In this way, even if the network-side device fails to detect the terminal's reported information (i.e., the second information), the network-side device can still know whether the terminal has performed the information reporting behavior (i.e., whether it has sent the second information) based on the first information. The network-side device can determine that the failure to receive the information may be due to poor channel conditions, rather than the terminal failing to meet the reporting trigger event. This allows the network-side device to perform adaptive processing in the future, improving the reliability of the terminal's triggered information reporting.

[0097] It should be noted that the above-mentioned reported information content refers to the specific information content that the terminal needs to report. For example, if the terminal needs to report beam information, the specific reported information content can be beam-related information; if the terminal needs to report channel status information, the specific reported information content can be channel status-related information.

[0098] Optionally, the first symbol of the second uplink resource is not earlier than the last symbol of the first uplink resource.

[0099] In one optional implementation, the terminal sends first information on the first uplink resource, including:

[0100] If at least one reporting trigger event is met, the terminal sends the first information on the first uplink resource.

[0101] The aforementioned reporting trigger event refers to the criterion used by the terminal to determine whether to perform information reporting. This criterion can be pre-configured by the network-side device or pre-defined by the protocol. It is understood that there is a correspondence between the reporting trigger event and the specific information content to be reported, and this correspondence is known to both the terminal and network-side devices. In other words, the corresponding information to be reported can be determined simply by identifying which reporting trigger event is satisfied. This application does not limit the specific events / conditions included in the reporting trigger event; trigger events / conditions used in existing information reporting mechanisms can be adopted.

[0102] The aforementioned reporting trigger event may specifically include one or more trigger events. When a trigger event is met, the terminal performs information reporting. The reporting trigger event may also include one or more conditions. When a condition is met, the terminal performs information reporting. In this embodiment, the reporting trigger event for terminal information reporting is used as the triggering criterion for the terminal to send the first information.

[0103] It should be noted that multiple reporting trigger events can be pre-configured or pre-defined for various information reporting needs. As long as at least one of the events is met, it is determined that the terminal needs to perform information reporting. Accordingly, the terminal needs to send the first information on the first uplink resource to inform the network-side device that the terminal will perform information reporting.

[0104] In one alternative implementation, transmitting the second information on the second uplink resource includes:

[0105] If the first condition is met, the terminal sends the second information on the second uplink resource;

[0106] The first condition includes at least one of the following:

[0107] (1) At least one reporting trigger event is satisfied;

[0108] (2) The payload size of the second information is not 0.

[0109] In this embodiment of the application, the basis for the terminal to determine whether to send specific reporting information content (i.e., the second information) is the first condition mentioned above.

[0110] It should be noted that, in the embodiments of this application, the specific way in which the terminal sends the first information on the first uplink resource can be as described above, where the terminal sends the first information on the first uplink resource when at least one reporting trigger event is satisfied, or the terminal can periodically send the first information on the first uplink resource in a periodic manner.

[0111] In one alternative implementation, the first information includes at least one of the following:

[0112] (1) First indication information, used to indicate the reporting trigger event that has been satisfied; Optionally, the first indication information may be a bit information used to indicate that there is currently a reported trigger event that has been satisfied, for example, the value of the bit information is 1, used to indicate that there is currently a reported trigger event that has been satisfied; or, the first indication information may be an identifier of the reported trigger event that has been satisfied, that is, by sending the identifier information of the specific reported trigger event that has been satisfied, it can be indicated which reported trigger events have been satisfied;

[0113] (2) The second indication information is used to indicate the status of the reported trigger event. The status of each reported trigger event can be specifically indicated by a bitmap. For example, an N-bit bitmap can be designed, where N is the number of reported trigger events configured. Each bit corresponds to one reported trigger event. The status of each reported trigger event is indicated by the value of each bit. For example, if the bitmap is 10110, then the status of the first, third, and fourth reported trigger events is satisfied, and the status of the second and fifth reported trigger events is not satisfied. It can be understood that if there is no reported trigger event that is currently satisfied, then all bits in the bitmap can be 0 to indicate that the reported trigger event has not been satisfied.

[0114] (3) The third instruction information is used to indicate the payload size of the second information;

[0115] (4) Fourth indication information, used to indicate the second uplink resource. Optionally, if no reporting trigger event is met, or the payload size of the second information is 0, then the first information does not contain the indication information of the second uplink resource, that is, it does not contain the third indication information.

[0116] In one alternative implementation, the second information includes at least one of the following:

[0117] (1) Relevant information of RSs that meet the reporting trigger event in the first measurement resource set;

[0118] Optionally, the relevant information of RS includes at least one of the following:

[0119] (1.1) The identifier of the RS, such as the RS index or RS id;

[0120] (1.2) Measurement results of RS;

[0121] (1.3) The cell identifier associated with RS;

[0122] (2) The fifth indication information is used to indicate the reporting trigger events that have been met; the specific reporting trigger events that have been met are indicated by the identifier or bitmap, so that the network side device can know what information the terminal will report.

[0123] (3) The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event;

[0124] (4) The seventh instruction information is used to indicate the target cell, which is associated with the reported triggering event.

[0125] In one alternative implementation, the first set of measurement resources is determined according to at least one of the following:

[0126] (1) A set of one or more measurement resources associated with the target report configuration;

[0127] (2) One or more sets of measurement resources associated with the target cell;

[0128] (3) A set of one or more measurement resources configured by network-side devices;

[0129] (4) The set of measurement resources determined by the terminal according to preset rules.

[0130] Specifically, the preset rules include at least one of the following:

[0131] The set of measurement resources determined based on the Quasi Co-Location (QCL) Type D source Reference Signal (RS) of all active Transmission Configuration Indicator (TCI) states;

[0132] The set of measurement resources determined by the QCL Type D source RS of the TCI state indicated by the network;

[0133] The set of measurement resources determined by the QCL Type D source RS of the TCI state of all network configurations;

[0134] The set of measurement resources determined based on the QCL Type D source RS of all inactive TCI states;

[0135] The set of measurement resources determined by the QCL Type D source RS for all active but unindicated TCI states;

[0136] In one optional implementation, the terminal sends first information on the first uplink resource, including:

[0137] If at least one reporting trigger event is met, the terminal periodically sends the first information on the first uplink resource until the second condition is met.

[0138] In this embodiment, the terminal reporting the first information can specifically adopt a periodic retransmission method to avoid transmission failure due to poor channel conditions in a single report, and to ensure that the network-side device can know that the terminal is about to report the second information; a stop judgment condition is set for this periodic retransmission, namely the aforementioned second condition, which includes at least one of the following:

[0139] (1) There is no reporting trigger event that is satisfied; if there is no reporting trigger event that is satisfied, the terminal will not perform information reporting, and therefore there is no need to send the first information.

[0140] (2) The terminal detects the first downlink control information (DCI). The first DCI is used to schedule or indicate the second uplink resources. The fact that the terminal can detect the first DCI used to schedule or indicate the second uplink resources indicates that the network-side device has received the first information and knows that the terminal will send the second information. The network-side device dynamically schedules or indicates the second uplink resources through the first DCI and indirectly informs the terminal that it has successfully received the first information. At this time, the terminal does not need to send the first information again.

[0141] (3) The terminal detects the third information, or the terminal successfully receives the third information. The third information is feedback information that the network-side device has successfully received the first information. Similarly to the first DCI mentioned above, the network-side device can directly inform the terminal that it has successfully received the first information through the third information. At this time, the terminal does not need to send the first information again.

[0142] (4) The first uplink resource is later than the second uplink resource; it is understandable that the first information is sent using the periodic retransmission method, so the first uplink resource corresponding to the first information is also a periodic resource. Therefore, theoretically, there will be a first uplink resource later than the second uplink resource. If the first uplink resource is later than the second uplink resource, it means that the terminal has started to send the second information at this time, and there is no need to send the first information. For example, there are resources 1, 2, 3, 4, 5, and 6 in chronological order. The periodic resources (i.e., the first uplink resources) corresponding to the first information are resources 1, 3, and 5. If the terminal sends the second information in resource 4 (i.e., the second uplink resource), then resource 5 is later than resource 4. Accordingly, the terminal will send the first information in resources 1 and 3, and stop sending the first information in resource 5.

[0143] (5) The number of times the first information is transmitted is greater than or equal to a first preset threshold. The first preset threshold may be pre-configured by the network-side device or pre-defined by the protocol.

[0144] In one alternative implementation, the first DCI includes at least one of the following:

[0145] (1) DCI used to schedule the first physical uplink shared channel (PUSCH), the first PUSCH is used to carry the fourth information;

[0146] (2) The DCI used to indicate the second PUSCH, which is associated with the non-periodic CSI report and is used to carry the fourth information; that is, the second PUSCH used to indicate the non-periodic CSI report is also used for the reporting of the second information.

[0147] The fourth piece of information includes at least one of the following:

[0148] (1) The second information determined based on all satisfied reporting trigger events; that is, the uplink resources scheduled or indicated by the first DCI may be used to report the second information corresponding to all satisfied reporting trigger events;

[0149] (2) The second information determined based on one of the reported trigger events among all the satisfied reported trigger events; that is, the uplink resources scheduled or indicated by the first DCI can be the second information corresponding to one of the reported trigger events among all the satisfied reported trigger events, that is, resources that can be separately scheduled or indicated for a single satisfied reported trigger event.

[0150] In one optional implementation, the first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through the first bit field. The first bit field is an extended bit field or a redundant bit field in the first DCI. When the network-side device schedules or indicates the second uplink resource through the first DCI, it can adopt a new DCI format, such as the extended bit field in the above-mentioned DCI, or it can use the redundant bit field in the existing DCI format.

[0151] Alternatively, the first DCI can be scrambled with the first Radio Network Temporary Identity (RNTI) to indicate that the physical downlink control channel (PDCCH) is dedicated to scheduling uplink resources carrying the fourth information. That is, the DCI can be scrambled with a specific RNTI to indicate new information.

[0152] In one alternative implementation, the method further includes:

[0153] The terminal receives the second DCI from the network-side equipment;

[0154] The second DCI includes at least one of the following:

[0155] (1) Retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0156] That is, the network side can instruct the terminal via DCI to retransmit the second information corresponding to the fulfilled reporting trigger event. This fulfilled reporting trigger event includes those fulfilled in previous reporting processes. Thus, if a terminal performs information reporting during a certain reporting process, but the network side fails to receive the reported information due to poor channel conditions, the network side can instruct the terminal via DCI to retransmit the previously reported information in subsequent reporting processes, ensuring that all reported information corresponding to fulfilled reporting trigger events is sent to the network side. Specifically, the retransmission indication information for the second information corresponding to at least one fulfilled reporting trigger event includes at least one of the identification information of the at least one fulfilled reporting trigger event and retransmission indication information. The retransmission indication information can be indicated by 1 bit, i.e., "1" indicates retransmission.

[0157] (2) Reporting instruction information of the second information corresponding to at least one reported triggering event that has been satisfied.

[0158] That is, the network side can instruct the terminal to report the second information corresponding to the fulfilled reporting trigger event through DCI. The fulfilled reporting trigger event can be included in the current information reporting process. The fulfilled reporting trigger event indicated by the terminal in the first information means that the network side, based on the fulfilled reporting trigger event indicated by the terminal in the first information, instructs the terminal to report the corresponding second information through DCI. Specifically, the reporting indication information corresponding to the second information of at least one fulfilled reporting trigger event includes at least one of the identification information of the at least one fulfilled reporting trigger event and the reporting indication information. The reporting indication information can be indicated by 1 bit, i.e., "0" represents reporting. The reporting indication information and the retransmission indication information can be indicated by different values ​​corresponding to the same 1-bit indication field.

[0159] (3) Indication information of the second uplink resource;

[0160] That is, the network side uses DCI to indicate the uplink resources carrying at least one of the retransmission and reporting of the second information mentioned above.

[0161] Optionally, the second DCI and the first DCI may be the same DCI or different DCIs, and this application embodiment does not specifically limit this.

[0162] In one alternative implementation, the method further includes:

[0163] The terminal determines the second uplink resource based on at least one of the following:

[0164] (1) The Physical Uplink Control Channel (PUCCH) configured by the network-side equipment; the network-side equipment pre-configures PUCCH resources dedicated to carrying the second information; the PUCCH resources can be periodic resources;

[0165] (2) The network-side device is configured with a Configured Grant Physical Uplink Shared Channel (CG-PUSCH); the network-side device pre-configures CG-PUSCH resources dedicated to carrying the second information;

[0166] (3) Uplink resources dynamically scheduled by network-side equipment; uplink resources specifically used to carry the second information by network-side equipment.

[0167] (4) The PUSCH triggered by the network-side device to carry non-periodic CSI reports; that is, the PUSCH resources used to carry non-periodic CSI reports are also used to carry the second information.

[0168] In one optional implementation, the terminal transmits second information on the second uplink resource, including:

[0169] The terminal periodically sends the second information on the second uplink resource until the number of transmissions of the second information reaches a second preset threshold. This first preset threshold can be pre-configured by the network-side device or pre-defined by the protocol.

[0170] In one alternative implementation, the method further includes:

[0171] When the terminal determines the second uplink resource based on the uplink resources dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, if the reporting trigger event corresponding to the second information is not satisfied before or simultaneously with the third uplink resource used to carry the retransmission of the second information, the terminal executes at least one of the following:

[0172] (1) Report the indication information that the reporting trigger event corresponding to the second information has not been met;

[0173] (2) Report the latest measurement results of the corresponding RS in the second information. That is, provide the latest measurement results to avoid network-side devices rescheduling and retransmitting.

[0174] In this embodiment of the application, the network-side device can instruct the terminal to retransmit the second information. However, as time progresses, the terminal previously triggered the reporting of the second information because the reporting trigger event was met. When the network-side device instructs the second information to be retransmitted, the reporting trigger event may not be met. In the case where the reporting trigger event is not met, the terminal reports at least one of the following: the indication information that the reporting trigger event corresponding to the second information is not met and the latest measurement result of the RS corresponding to the second information.

[0175] In one alternative implementation, the method further includes:

[0176] When the terminal determines the second uplink resource based on the uplink resources dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reported trigger event changes, or the RS that satisfies the reported trigger event changes, the terminal executes any one of the following:

[0177] (1) Report the latest measurement results of RS that meet the reporting trigger event;

[0178] (2) Report the measurement results of all RSs that meet the reporting trigger event.

[0179] The change of the aforementioned satisfied reporting trigger event may include a change in the specific satisfied reporting trigger event (e.g., from event 1, 2, 4 to event 3, 5, 8) or a change in the number of satisfied reporting trigger events (e.g., from event 1, 2, 4 to event 1, 2, 4, 8), or both; similarly, a change in the RS satisfying the reporting trigger event may include a change in the specific satisfied reporting trigger event RS or a change in the number of satisfied reporting trigger events RS, or both;

[0180] Referring to Figure 2b, this embodiment of the application provides an information receiving method, the execution subject of which is a network-side device, and the method includes:

[0181] Step 211: The network-side device receives the first information on the first uplink resource; or, the network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource.

[0182] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

[0183] It should be noted that, as the peer device interacting with the terminal, the execution steps and interactive information involved in the solution should be understood in the same way as those on the terminal side. This ensures the correct execution of the solution between the two. Therefore, the content in the solution for the network side device can be understood by referring to the description of the solution on the terminal side, and will not be repeated here.

[0184] In one optional implementation, receiving the second information on the second uplink resource includes:

[0185] When the network-side device determines that the first condition is met based on the first information, it receives the second information on the second uplink resource;

[0186] The first condition includes at least one of the following:

[0187] At least one reporting trigger event has been satisfied;

[0188] The payload size of the second piece of information is not 0.

[0189] In one alternative implementation, the method further includes at least one of the following:

[0190] The network-side device sends a first DCI to the terminal, the first DCI being used to schedule or indicate the second uplink resource;

[0191] The network-side device sends a third message to the terminal, the third message being feedback information that the network-side device has successfully received the first message;

[0192] The network-side device configures a first preset threshold for the terminal, which is used to indicate the maximum number of times the first information can be transmitted.

[0193] In one alternative implementation, the first DCI includes at least one of the following:

[0194] DCI used to schedule the first PUSCH, which is used to carry the fourth information;

[0195] The DCI is used to indicate the second PUSCH, which is associated with the non-periodic CSI report and is used to carry the fourth information;

[0196] The fourth piece of information includes at least one of the following:

[0197] The second information is determined based on all the reported trigger events that have been satisfied;

[0198] The second information is determined based on one of the reported trigger events that are satisfied.

[0199] In one optional implementation, the first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through a first bit field, wherein the first bit field is an extended bit field or a redundant bit field in the first DCI.

[0200] or,

[0201] The first DCI is scrambled by the first RNTI to indicate that the PDCCH is dedicated to scheduling uplink resources carrying the fourth information.

[0202] In an optional implementation, the method further includes:

[0203] The network-side device sends a second DCI to the terminal;

[0204] Wherein, the second DCI includes at least one of the following:

[0205] The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0206] The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0207] The indication information for the second uplink resource.

[0208] In an optional implementation, the method further includes:

[0209] The network-side device determines the second uplink resource by at least one of the following:

[0210] The PUCCH configured on the network-side device;

[0211] The CG-PUSCH configured on the network-side device;

[0212] The uplink resources dynamically scheduled by the network-side equipment;

[0213] The PUSCH triggered by the network-side device to carry non-periodic CSI reports.

[0214] In an optional implementation, the method further includes:

[0215] The network-side device configures a second preset threshold for the terminal, which is used to indicate the maximum number of times the second information can be transmitted.

[0216] In one alternative implementation, the first information includes at least one of the following:

[0217] The first indication information is used to indicate the reported trigger event that has been satisfied;

[0218] The second instruction information is used to indicate the status of the reported triggering event;

[0219] The third instruction information is used to indicate the payload size of the second information;

[0220] The fourth indication information is used to indicate the second uplink resource.

[0221] In one alternative implementation, the second information includes at least one of the following:

[0222] The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources;

[0223] The fifth instruction information is used to indicate the reported trigger event that has been satisfied;

[0224] The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event;

[0225] The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

[0226] In one alternative implementation, the relevant information of the RS includes at least one of the following:

[0227] The identifier of the RS;

[0228] The measurement results of the RS;

[0229] The cell identifier associated with the RS.

[0230] In one alternative implementation, the first set of measurement resources is determined according to at least one of the following:

[0231] One or more sets of measurement resources associated with the target report configuration;

[0232] One or more sets of measurement resources associated with the target cell;

[0233] One or more sets of measurement resources configured by the network-side device;

[0234] The set of measurement resources determined by the terminal according to preset rules.

[0235] The technical solution is described below with reference to specific implementation methods:

[0236] Implementation Method 1: Mechanism for Repeated Transmission of First Information

[0237] When the reporting trigger event is met, the terminal begins periodically transmitting first information on the first uplink resource until the second condition described above is met. The first uplink resource is at least one of the periodically configured PUCCH resource and CG-PUSCH resource. Specifically, as shown in Figure 3a, when the terminal determines that the reporting trigger event is met, it begins repeatedly transmitting the first information on Resource#2, Resource#3, and Resource#4 until the terminal detects or successfully receives the first DCI or third information. Repeatedly transmitting the first information improves the transmission reliability of the first information.

[0238] Implementation Method 2: Per Event / Report Reporting Mechanism

[0239] Method 2.1: A report configuration is associated with N (N>1) trigger events, and the N trigger events correspond to N report contents. The report configuration is associated with a first uplink resource, which is used to carry first information. The first information has a length of N bits, indicating whether the N trigger events have occurred or whether the N trigger conditions have been met (e.g., "1" indicates occurrence or fulfillment, and "0" indicates non-occurrence or non-fulfillment). Alternatively, the first information has a length of N*ceil(log2M) bits (M is the payload size of the report content with the largest load among the N report contents), indicating whether the N trigger events have occurred or whether the trigger conditions have been met, and the payload size required for the report content corresponding to each trigger event when they have occurred or been met. When at least M (M≥1) of the N trigger events are met, the terminal sends the first information on the first uplink resource. After receiving the first information, the network-side device sends a first PDCCH, which is used to indicate or schedule a second uplink resource. The second uplink resource is used to carry the report content corresponding to one of the M events. As shown in Figure 3b, the first uplink resource is Resource#2, and the first information is 100110, meaning the conditions corresponding to events 1, 4, and 5 are met. The terminal then receives PDCCHs indicating or scheduling the uplink resources used to carry events 1, 4, and 5. Similarly, when the first information is the load size of the report content corresponding to each event, the process is the same as described above. It should be noted that, to ensure the order of reporting and the matching of reporting resources with load, a new field or redundant bits need to be added to the PDCCH to indicate which event's report content the uplink resource indicated or scheduled by the PDCCH is used to carry.

[0240] When the report content corresponding to a certain event is not successfully received by the gNB, the terminal expects the network to schedule an uplink resource to carry the unsuccessfully transmitted report content for retransmission. It should be noted that when another event is triggered and transmission needs to be scheduled simultaneously, the terminal determines which event's report content the PDCCH indicates or schedules for carrying. Specifically, as shown in Figure 3c, when the network-side device fails to receive the report content corresponding to event #3 carried by Resource #4, but successfully receives the first information "0101" carried by Resource #5, the network-side device will send a PDCCH to indicate or schedule uplink resources for carrying the corresponding report content of events #2 and #3. After receiving the PDCCH, the terminal places the report content corresponding to events #2 and #3 in Resource #6 for reporting.

[0241] Method 2.2: The process is the same as Method 2.1, but the configuration method differs. In Method 2.2, one report configuration is associated with only one trigger event. Different report configurations can be associated with different trigger events, but different report configurations can be associated with the same first uplink resource. N (N>1) report configurations are associated with N trigger events. The N reports correspond to N report contents. The N report configurations are associated with the same first uplink resource, which is used to carry the first information of the N report configurations. The length of the first information is N bits, indicating whether the trigger event corresponding to the N report configurations has occurred or whether the corresponding condition has been met. For example, "1" indicates occurrence or satisfaction, and "0" indicates no occurrence or satisfaction. Alternatively, the length of the first information is N*ceil(log2M) bits (M is the payload size of the report content with the largest load among the N report contents), indicating whether the trigger event corresponding to the N report configurations has occurred or whether the trigger condition has been met, and the payload size required for the report content corresponding to each report configuration under the condition of occurrence or satisfaction. When at least M (M≥1) of the N report configurations have their corresponding trigger events met, the terminal sends the first information on the first uplink resource. The transmission process on the first and second uplink resources is the same as in method 2.1, except that it is changed from being based on events to being based on reports.

[0242] Implementation Method 3: Retransmission Mechanism for the Second Message

[0243] Method 3.1: A report configuration is associated with a trigger event and a first uplink resource. When the condition corresponding to the trigger event is met, the terminal sends first information on the first uplink resource, i.e., "1" in Figure 3d. The report content corresponding to the report configuration is also reported on the uplink resource (i.e., Resource #3) indicated or scheduled by PDCCH#1. If the network-side device fails to receive the report content in Resource #3, it indicates or schedules uplink resource Resource #4 via PDCCH#2 to carry the report content for re-reporting, thereby improving the transmission reliability of the second information. However, if the terminal determines that the condition of the trigger event is not met before Resource #4, the terminal reports at least one of the following in Resource #4 to inform the network-side device that the condition corresponding to the event is no longer met, avoiding continuous retransmission scheduling by the network:

[0244] 1. Report indication information that the conditions corresponding to the triggering event are not met, such as "0" or an indication that the payload size is "0";

[0245] 2. Report the RS identifier included in the report content and the latest measurement results of the RS corresponding to the RS identifier;

[0246] Method 3.2: A report configuration is associated with a trigger event and a first uplink resource. When the condition corresponding to the trigger event is met, the terminal sends first information on the first uplink resource, i.e., "1" in Figure 3e. The terminal also reports the report content corresponding to the report configuration on the uplink resource indicated or scheduled by PDCCH#1 (i.e., Resource#3), i.e., reports the beam information {RS#1, RS#2} that meets the condition. As shown in Figure 3e, if the terminal determines before Resource#4 that the condition of the trigger event is met again and the beam information that meets the condition is {RS#1, RS#3}, then it will report the indication information that the event has been triggered on Resource#4, i.e., the first information. After reporting the first information on Resource#4, if the terminal receives a PDCCH for indicating or scheduling a second uplink resource (Resource#5). According to the method in Embodiment 2, since the PDCCH only indicates the event identifier or report identifier, for the same report configuration or associated with the same triggering event, the UE cannot distinguish whether the second uplink resource is used to carry the retransmission of beam information associated with {RS#1, RS#2} or the new transmission of beam information associated with {RS#1, RS#3}. Therefore, in order to standardize terminal behavior and maintain consistency with network-side equipment, the terminal can determine the reporting content according to at least one of the following rules:

[0247] 1. The terminal only reports the relevant information of the beam that currently meets the event conditions on the second uplink resource, namely {RS#1, RS#3 and the latest measurement results corresponding to both};

[0248] 2. The terminal reports the relevant information of all beams that have met the event conditions on the second uplink resource, namely {RS#1, RS#2, RS#3 and the latest measurement results corresponding to the three};

[0249] The information reporting and receiving method provided in this application can be executed by an information reporting and receiving device. This application uses an information reporting and receiving device executing the information reporting and receiving method as an example to illustrate the information reporting and receiving device provided in this application.

[0250] Referring to Figure 4a, this application embodiment provides an information reporting device, which can be applied to a terminal. The device includes:

[0251] The first transmitting module 401 is used for:

[0252] The terminal sends the first information on the first uplink resource;

[0253] or,

[0254] The terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource;

[0255] The first information is used to indicate whether the terminal has performed the sending of the second information, and the second information includes information related to the content of the reported information.

[0256] In one optional implementation, the first sending module is specifically used for:

[0257] If at least one reporting trigger event is met, the terminal sends the first information on the first uplink resource.

[0258] In one optional implementation, the first sending module is specifically used for:

[0259] If the first condition is met, the terminal sends the second information on the second uplink resource;

[0260] The first condition includes at least one of the following:

[0261] At least one reporting trigger event has been satisfied;

[0262] The payload size of the second piece of information is not 0.

[0263] In one optional implementation, the first sending module is specifically used for:

[0264] If at least one reporting trigger event is met, the terminal periodically sends the first information on the first uplink resource until the second condition is met;

[0265] The second condition includes at least one of the following:

[0266] There is no reported triggering event that has been satisfied;

[0267] The terminal detects a first DCI, which is used to schedule or indicate the second uplink resource.

[0268] The terminal detects the third information, or the terminal successfully receives the third information, wherein the third information is feedback information from the network-side device that successfully receives the first information;

[0269] The first uplink resource is later than the second uplink resource;

[0270] The number of times the first information is transmitted is greater than or equal to a first preset threshold.

[0271] In one alternative implementation, the first DCI includes at least one of the following:

[0272] DCI used to schedule the first PUSCH, which is used to carry the fourth information;

[0273] The DCI used to indicate the second PUSCH, which is associated with the aperiodic channel state information (CSI) report and is used to carry the fourth information;

[0274] The fourth piece of information includes at least one of the following:

[0275] The second information is determined based on all the reported trigger events that have been satisfied;

[0276] The second information is determined based on one of the reported trigger events that are satisfied.

[0277] In one optional implementation, the first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through a first bit field, wherein the first bit field is an extended bit field or a redundant bit field in the first DCI.

[0278] or,

[0279] The first DCI is scrambled by the first RNTI to indicate that the PDCCH is dedicated to scheduling uplink resources carrying the fourth information.

[0280] In one alternative embodiment, the device further includes:

[0281] The second receiving module is used for the terminal to receive the second DCI from the network-side device;

[0282] The second DCI includes at least one of the following:

[0283] The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0284] The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0285] The indication information for the second uplink resource.

[0286] In one alternative embodiment, the device further includes:

[0287] A first determining module is configured to enable the terminal to determine the second uplink resource based on at least one of the following:

[0288] PUCCH configured on network-side devices;

[0289] CG-PUSCH configured on network-side devices;

[0290] Uplink resources dynamically scheduled by network-side devices;

[0291] PUSCH triggered by network-side devices to carry non-periodic CSI reports.

[0292] In one alternative embodiment, the device further includes:

[0293] The first execution module is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reporting trigger event corresponding to the second information is not satisfied, the terminal performs a first operation.

[0294] The first operation includes:

[0295] Report an indication that the reporting trigger event corresponding to the second information has not been met;

[0296] Report the latest measurement results of the RS corresponding to the second information.

[0297] In one alternative embodiment, the device further includes:

[0298] The second execution module is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reported trigger event changes, or the RS that satisfies the reported trigger event changes, the terminal performs a second operation.

[0299] The second operation includes:

[0300] Report the latest measurement results of RS that meet the reporting trigger event;

[0301] Report the measurement results of all RSs that meet the reporting trigger event.

[0302] In one optional implementation, the first sending module is specifically used for:

[0303] The terminal periodically sends second information on the second uplink resource until the number of transmissions of the second information reaches a second preset threshold.

[0304] In one alternative implementation, the first information includes at least one of the following:

[0305] The first indication information is used to indicate the reported trigger event that has been satisfied;

[0306] The second instruction information is used to indicate the status of the reported triggering event;

[0307] The third instruction information is used to indicate the payload size of the second information;

[0308] The fourth indication information is used to indicate the second uplink resource.

[0309] In one alternative implementation, the second information includes at least one of the following:

[0310] The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources;

[0311] The fifth instruction information is used to indicate the reported trigger event that has been satisfied;

[0312] The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event;

[0313] The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

[0314] In one alternative implementation, the relevant information of the RS includes at least one of the following:

[0315] The identifier of the RS;

[0316] The measurement results of the RS;

[0317] The cell identifier associated with the RS.

[0318] In one alternative implementation, the first set of measurement resources is determined according to at least one of the following:

[0319] One or more sets of measurement resources associated with the target report configuration;

[0320] One or more sets of measurement resources associated with the target cell;

[0321] A set of one or more measurement resources configured by network-side devices;

[0322] The set of measurement resources determined by the terminal according to preset rules.

[0323] Referring to Figure 4b, this application embodiment provides an information receiving device, which can be applied to network-side equipment. The device includes:

[0324] The first receiving module 411 is used for:

[0325] The network-side device receives the first information on the first uplink resource;

[0326] or,

[0327] The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource.

[0328] The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

[0329] In one optional implementation, the first receiving module is configured to:

[0330] When the network-side device determines that the first condition is met based on the first information, it receives the second information on the second uplink resource;

[0331] The first condition includes at least one of the following:

[0332] At least one reporting trigger event has been satisfied;

[0333] The payload size of the second piece of information is not 0.

[0334] In one alternative embodiment, the device further includes:

[0335] The second transmitting module is used for at least one of the following:

[0336] The network-side device sends a first DCI to the terminal, the first DCI being used to schedule or indicate the second uplink resource;

[0337] The network-side device sends a third message to the terminal, the third message being feedback information that the network-side device has successfully received the first message;

[0338] The first configuration module is used for:

[0339] The network-side device configures a first preset threshold for the terminal, which is used to indicate the maximum number of times the first information can be transmitted.

[0340] In one alternative implementation, the first DCI includes at least one of the following:

[0341] DCI used to schedule the first PUSCH, which is used to carry the fourth information;

[0342] The DCI is used to indicate the second PUSCH, which is associated with the non-periodic CSI report and is used to carry the fourth information;

[0343] The fourth piece of information includes at least one of the following:

[0344] The second information is determined based on all the reported trigger events that have been satisfied;

[0345] The second information is determined based on one of the reported trigger events that are satisfied.

[0346] In one optional implementation, the first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through a first bit field, wherein the first bit field is an extended bit field or a redundant bit field in the first DCI.

[0347] or,

[0348] The first DCI is scrambled by the first RNTI to indicate that the PDCCH is dedicated to scheduling uplink resources carrying the fourth information.

[0349] In one alternative embodiment, the device further includes:

[0350] The third sending module is used for the network-side device to send the second DCI to the terminal;

[0351] Wherein, the second DCI includes at least one of the following:

[0352] The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0353] The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0354] The indication information for the second uplink resource.

[0355] In one alternative embodiment, the device further includes:

[0356] The second determining module is used by the network-side device to determine the second uplink resource by at least one of the following:

[0357] The PUCCH configured on the network-side device;

[0358] The CG-PUSCH configured on the network-side device;

[0359] The uplink resources dynamically scheduled by the network-side equipment;

[0360] The PUSCH triggered by the network-side device to carry non-periodic CSI reports.

[0361] In one alternative embodiment, the device further includes:

[0362] The second configuration module is used for:

[0363] The network-side device configures a second preset threshold for the terminal, which is used to indicate the maximum number of times the second information can be transmitted.

[0364] In one alternative implementation, the first information includes at least one of the following:

[0365] The first indication information is used to indicate the reported trigger event that has been satisfied;

[0366] The second instruction information is used to indicate the status of the reported triggering event;

[0367] The third instruction information is used to indicate the payload size of the second information;

[0368] The fourth indication information is used to indicate the second uplink resource.

[0369] In one alternative implementation, the second information includes at least one of the following:

[0370] The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources;

[0371] The fifth instruction information is used to indicate the reported trigger event that has been satisfied;

[0372] The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event;

[0373] The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

[0374] In one alternative implementation, the relevant information of the RS includes at least one of the following:

[0375] The identifier of the RS;

[0376] The measurement results of the RS;

[0377] The cell identifier associated with the RS.

[0378] In one alternative implementation, the first set of measurement resources is determined according to at least one of the following:

[0379] One or more sets of measurement resources associated with the target report configuration;

[0380] One or more sets of measurement resources associated with the target cell;

[0381] One or more sets of measurement resources configured by the network-side device;

[0382] The set of measurement resources determined by the terminal according to preset rules.

[0383] The information reporting device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0384] The information reporting device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2a to 3e and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0385] As shown in Figure 5, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores programs or instructions that can run on the processor 501. For example, when the communication device 500 is a terminal, the program or instructions executed by the processor 501 implement the various steps of the above-described method embodiments and achieve the same technical effect. When the communication device 500 is a network-side device, the program or instructions executed by the processor 501 implement the various steps of the above-described method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0386] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps as described in the method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 6 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0387] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0388] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 6 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0389] It should be understood that, in this embodiment, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0390] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0391] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0392] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0393] The processor 610 is used for the terminal to send first information on a first uplink resource and send second information on a second uplink resource;

[0394] The first information includes information related to the terminal sending the second information, and the second information includes information related to the reported information content.

[0395] In one alternative implementation, the processor 610 is configured to:

[0396] If at least one reporting trigger event is met, the terminal sends the first information on the first uplink resource.

[0397] In one alternative implementation, the processor 610 is configured to:

[0398] If the first condition is met, the terminal sends the second information on the second uplink resource;

[0399] The first condition includes at least one of the following:

[0400] At least one reporting trigger event has been satisfied;

[0401] The payload size of the second piece of information is not 0.

[0402] In one alternative implementation, the processor 610 is configured to:

[0403] If at least one reporting trigger event is met, the terminal periodically sends the first information on the first uplink resource until the second condition is met;

[0404] The second condition includes at least one of the following:

[0405] There is no reported triggering event that has been satisfied;

[0406] The terminal detects a first DCI, which is used to schedule or indicate the second uplink resource.

[0407] The terminal detects the third information, or the terminal successfully receives the third information, wherein the third information is feedback information from the network-side device that successfully receives the first information;

[0408] The first uplink resource is later than the second uplink resource;

[0409] The number of times the first information is transmitted is greater than or equal to a first preset threshold.

[0410] In one alternative implementation, the first DCI includes at least one of the following:

[0411] DCI used to schedule the first PUSCH, which is used to carry the fourth information;

[0412] The DCI used to indicate the second PUSCH, which is associated with the aperiodic channel state information (CSI) report and is used to carry the fourth information;

[0413] The fourth piece of information includes at least one of the following:

[0414] The second information is determined based on all the reported trigger events that have been satisfied;

[0415] The second information is determined based on one of the reported trigger events that are satisfied.

[0416] In one optional implementation, the first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through a first bit field, wherein the first bit field is an extended bit field or a redundant bit field in the first DCI.

[0417] or,

[0418] The first DCI is scrambled by the first RNTI to indicate that the PDCCH is dedicated to scheduling uplink resources carrying the fourth information.

[0419] In one alternative embodiment, the device further includes:

[0420] The processor 610 is used by the network-side device to send a second DCI to the terminal;

[0421] Wherein, the second DCI includes at least one of the following:

[0422] The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0423] The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event;

[0424] The indication information for the second uplink resource.

[0425] In one alternative implementation, the processor 610 is configured to allow the terminal to determine the second uplink resource based on at least one of the following:

[0426] PUCCH configured on network-side devices;

[0427] CG-PUSCH configured on network-side devices;

[0428] Uplink resources dynamically scheduled by network-side devices;

[0429] PUSCH triggered by network-side devices to carry non-periodic CSI reports.

[0430] In an optional implementation, the processor 610 is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reporting trigger event corresponding to the second information is not satisfied, the terminal performs a first operation.

[0431] The first operation includes:

[0432] Report an indication that the reporting trigger event corresponding to the second information has not been met;

[0433] Report the latest measurement results of the RS corresponding to the second information.

[0434] In an optional implementation, the processor 610 is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reported triggering event changes, or the RS that satisfies the reported triggering event changes, the terminal performs a second operation.

[0435] The second operation includes:

[0436] Report the latest measurement results of RS that meet the reporting trigger event;

[0437] Report the measurement results of all RSs that meet the reporting trigger event.

[0438] In one alternative implementation, the processor 610 is configured to:

[0439] The terminal periodically sends second information on the second uplink resource until the number of transmissions of the second information reaches a second preset threshold.

[0440] In one alternative implementation, the first information includes at least one of the following:

[0441] The first indication information is used to indicate the reported trigger event that has been satisfied;

[0442] The second instruction information is used to indicate the status of the reported triggering event;

[0443] The third instruction information is used to indicate the payload size of the second information;

[0444] The fourth indication information is used to indicate the second uplink resource.

[0445] In one alternative implementation, the second information includes at least one of the following:

[0446] The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources;

[0447] The fifth instruction information is used to indicate the reported trigger event that has been satisfied;

[0448] The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event;

[0449] The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

[0450] In one alternative implementation, the relevant information of the RS includes at least one of the following:

[0451] The identifier of the RS;

[0452] The measurement results of the RS;

[0453] The cell identifier associated with the RS.

[0454] In one alternative implementation, the first set of measurement resources is determined according to at least one of the following:

[0455] One or more sets of measurement resources associated with the target report configuration;

[0456] One or more sets of measurement resources associated with the target cell;

[0457] A set of one or more measurement resources configured by network-side devices;

[0458] The set of measurement resources determined by the terminal according to preset rules.

[0459] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0460] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0461] Specifically, this application embodiment also provides a network-side device. As shown in FIG7, the network-side device 700 includes: an antenna 71, a radio frequency (RF) device 72, a baseband device 73, a processor 74, and a memory 75. The antenna 71 is connected to the RF device 72. In the uplink direction, the RF device 72 receives information through the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be transmitted and sends it to the RF device 72, which then processes the received information and transmits it through the antenna 71.

[0462] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 73, which includes a baseband processor.

[0463] The baseband device 73 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG7. One of the chips is, for example, a baseband processor, which is connected to the memory 75 via a bus interface to call the program in the memory 75 and execute the network device operation shown in the above method embodiment.

[0464] The network-side device may also include a network interface 76, such as a Common Public Radio Interface (CPRI).

[0465] Specifically, the network-side device 700 in this application embodiment further includes: instructions or programs stored in memory 75 and executable on processor 74. Processor 74 calls the instructions or programs in memory 75 to execute the methods executed by each module shown in FIG4b and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0466] Specifically, this application embodiment also provides a network-side device. As shown in FIG8, the network-side device 800 includes: a processor 801, a network interface 802, and a memory 803. The network interface 802 is, for example, a common public radio interface (CPRI).

[0467] Specifically, the network-side device 800 in this application embodiment further includes: instructions or programs stored in memory 803 and executable on processor 801. Processor 801 calls the instructions or programs in memory 803 to execute the methods executed by each module shown in FIG4b and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0468] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0469] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0470] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0471] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0472] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0473] This application also provides a wireless communication system, including a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal-side method described above.

[0474] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0475] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0476] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An information reporting method, comprising: The terminal sends the first information on the first uplink resource; or, The terminal sends the first information on the first uplink resource and the second information on the second uplink resource; The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content.

2. The method according to claim 1, wherein, The terminal sends first information on the first uplink resource, including: If at least one reporting trigger event is met, the terminal sends the first information on the first uplink resource.

3. The method according to claim 1 or 2, wherein, Sending the second information on the second uplink resource includes: If the first condition is met, the terminal sends the second information on the second uplink resource; The first condition includes at least one of the following: At least one reporting trigger event has been satisfied; The payload size of the second piece of information is not 0.

4. The method according to any one of claims 1 to 3, wherein, The terminal sends first information on the first uplink resource, including: If at least one reporting trigger event is met, the terminal periodically sends the first information on the first uplink resource until the second condition is met; The second condition includes at least one of the following: There is no reported triggering event that has been satisfied; The terminal detects a first downlink control information (DCI), which is used to schedule or indicate the second uplink resource. The terminal detects the third information, or the terminal successfully receives the third information, wherein the third information is feedback information from the network-side device that successfully receives the first information; The first uplink resource is later than the second uplink resource; The number of times the first information is transmitted is greater than or equal to a first preset threshold.

5. The method according to claim 4, wherein, The first DCI includes at least one of the following: DCI used to schedule the first physical uplink shared channel (PUSCH), the first PUSCH being used to carry fourth information; The DCI used to indicate the second PUSCH, which is associated with the aperiodic channel state information (CSI) report and is used to carry the fourth information; The fourth piece of information includes at least one of the following: The second information is determined based on all the reported trigger events that have been satisfied; The second information is determined based on one of the reported trigger events that are satisfied.

6. The method according to claim 5, wherein, The first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through the first bit field, where the first bit field is an extended bit field or a redundant bit field in the first DCI. or, The first DCI is scrambled with the first Radio Network Temporary Identifier (RNTI) to indicate that the Physical Downlink Control Channel (PDCCH) is dedicated to scheduling uplink resources carrying the fourth information.

7. The method according to claim 1, further comprising: The terminal receives a second DCI from the network-side device; The second DCI includes at least one of the following: The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event; The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event; Indication information for the second uplink resource.

8. The method according to any one of claims 1 to 3, wherein the method further comprises: The terminal determines the second uplink resource based on at least one of the following: The Physical Uplink Control Channel (PUCCH) configured on the network-side equipment; The network-side device is configured with the authorized physical uplink shared channel CG-PUSCH. Uplink resources dynamically scheduled by network-side devices; PUSCH triggered by network-side devices to carry non-periodic CSI reports.

9. The method according to claim 8, further comprising: When the terminal determines the second uplink resource based on the uplink resources dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, if the reporting trigger event corresponding to the second information is not satisfied before or simultaneously with the third uplink resource used to carry the retransmission of the second information, the terminal performs at least one of the following: Report an indication that the reporting trigger event corresponding to the second information has not been met; Report the latest measurement results of the reference signal RS corresponding to the second information.

10. The method according to claim 8, further comprising: When the terminal determines the second uplink resource based on the uplink resources dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the satisfied reporting trigger event changes, or the RS satisfying the reporting trigger event changes, the terminal executes any one of the following: Report the latest measurement results of RS that meet the reporting trigger event; Report the measurement results of all RSs that meet the reporting trigger event.

11. The method according to any one of claims 1 to 8, wherein, The terminal sends second information on the second uplink resource, including: The terminal periodically sends second information on the second uplink resource until the number of transmissions of the second information reaches a second preset threshold.

12. The method according to any one of claims 1 to 3, wherein, The first information includes at least one of the following: The first indication information is used to indicate the reported trigger event that has been satisfied; The second instruction information is used to indicate the status of the reported triggering event; The third instruction information is used to indicate the payload size of the second information; The fourth indication information is used to indicate the second uplink resource.

13. The method according to any one of claims 1 to 3, wherein, The second information includes at least one of the following: The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources; The fifth instruction information is used to indicate the reported trigger event that has been satisfied; The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event; The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

14. The method according to claim 13, wherein, The relevant information of the RS includes at least one of the following: The identifier of the RS; The measurement results of the RS; The cell identifier associated with the RS.

15. The method according to claim 13, wherein, The first set of measurement resources is determined according to at least one of the following: One or more sets of measurement resources associated with the target report configuration; One or more sets of measurement resources associated with the target cell; A set of one or more measurement resources configured by network-side devices; The set of measurement resources determined by the terminal according to preset rules.

16. An information receiving method, comprising: The network-side device receives the first information on the first uplink resource; or, The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource. The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

17. The method according to claim 16, wherein, Receiving the second information on the second uplink resource includes: When the network-side device determines that the first condition is met based on the first information, it receives the second information on the second uplink resource; The first condition includes at least one of the following: At least one reporting trigger event has been satisfied; The payload size of the second piece of information is not 0.

18. The method according to claim 16 or 17, wherein, The method further includes at least one of the following: The network-side device sends a first DCI to the terminal, the first DCI being used to schedule or indicate the second uplink resource; The network-side device sends a third message to the terminal, the third message being feedback information that the network-side device has successfully received the first message; The network-side device configures a first preset threshold for the terminal, which is used to indicate the maximum number of times the first information can be transmitted.

19. The method according to claim 18, wherein, The first DCI includes at least one of the following: DCI used to schedule the first PUSCH, which is used to carry the fourth information; The DCI is used to indicate the second PUSCH, which is associated with the non-periodic CSI report and is used to carry the fourth information; The fourth piece of information includes at least one of the following: The second information is determined based on all the reported trigger events that have been satisfied; The second information is determined based on one of the reported trigger events that are satisfied.

20. The method according to claim 19, wherein, The first DCI indicates the indication information of the reporting trigger event corresponding to the fourth information through the first bit field, where the first bit field is an extended bit field or a redundant bit field in the first DCI. or, The first DCI is scrambled by the first RNTI to indicate that the PDCCH is dedicated to scheduling uplink resources carrying the fourth information.

21. The method according to claim 16, further comprising: The network-side device sends a second DCI to the terminal; Wherein, the second DCI includes at least one of the following: The retransmission indication information of the second information corresponding to at least one satisfied reporting trigger event; The reporting indication information of the second information corresponding to at least one satisfied reporting trigger event; Indication information for the second uplink resource.

22. The method according to any one of claims 16 or 17, further comprising: The network-side device determines the second uplink resource by at least one of the following: The PUCCH configured on the network-side device; The CG-PUSCH configured on the network-side device; The uplink resources dynamically scheduled by the network-side equipment; The PUSCH triggered by the network-side device to carry non-periodic CSI reports.

23. The method according to any one of claims 16 to 22, wherein the method further comprises: The network-side device configures a second preset threshold for the terminal, which is used to indicate the maximum number of times the second information can be transmitted.

24. The method according to claim 16 or 17, wherein, The first information includes at least one of the following: The first indication information is used to indicate the reported trigger event that has been satisfied; The second instruction information is used to indicate the status of the reported triggering event; The third instruction information is used to indicate the payload size of the second information; The fourth indication information is used to indicate the second uplink resource.

25. The method according to any one of claim 16 or 17, wherein, The second information includes at least one of the following: The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources; The fifth instruction information is used to indicate the reported trigger event that has been satisfied; The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event; The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

26. The method of claim 25, wherein, The relevant information of the RS includes at least one of the following: The identifier of the RS; The measurement results of the RS; The cell identifier associated with the RS.

27. The method according to claim 25, wherein, The first set of measurement resources is determined according to at least one of the following: One or more sets of measurement resources associated with the target report configuration; One or more sets of measurement resources associated with the target cell; One or more sets of measurement resources configured by the network-side device; The set of measurement resources determined by the terminal according to preset rules.

28. An information reporting device, comprising: The first transmitting module is used for: The terminal sends the first information on the first uplink resource; or, The terminal sends the first information on the first uplink resource and the second information on the second uplink resource; The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the reported information content.

29. The apparatus according to claim 28, wherein, The first sending module is specifically used for: If at least one reporting trigger event is met, the terminal periodically sends the first information on the first uplink resource until the second condition is met; The second condition includes at least one of the following: There is no reported triggering event that has been satisfied; The terminal detects a first DCI, which is used to schedule or indicate the second uplink resource. The terminal detects the third information, or the terminal successfully receives the third information, wherein the third information is feedback information from the network-side device that successfully receives the first information; The first uplink resource is later than the second uplink resource; The number of times the first information is transmitted is greater than or equal to a first preset threshold.

30. The apparatus of claim 28, further comprising: A first determining module is configured to enable the terminal to determine the second uplink resource based on at least one of the following: PUCCH configured on network-side devices; CG-PUSCH configured on network-side devices; Uplink resources dynamically scheduled by network-side devices; PUSCH triggered by network-side devices to carry non-periodic CSI reports.

31. The apparatus of claim 30, further comprising: The first execution module is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reporting trigger event corresponding to the second information is not satisfied, the terminal performs a first operation. The first operation includes: Report an indication that the reporting trigger event corresponding to the second information has not been met; Report the latest measurement results of the RS corresponding to the second information.

32. The apparatus of claim 30, further comprising: The second execution module is configured to, when the terminal determines the second uplink resource based on the uplink resource dynamically scheduled by the network-side device, or the PUCCH configured by the network-side device, or the CG-PUSCH configured by the network-side device, before or simultaneously with the third uplink resource used to carry the retransmission of the second information, if the reported trigger event changes, or the RS that satisfies the reported trigger event changes, the terminal performs a second operation. The second operation includes: Report the latest measurement results of RS that meet the reporting trigger event; Report the measurement results of all RSs that meet the reporting trigger event.

33. The apparatus according to claim 30, wherein, The first information includes at least one of the following: The first indication information is used to indicate the reported trigger event that has been satisfied; The second instruction information is used to indicate the status of the reported triggering event; The third instruction information is used to indicate the payload size of the second information; The fourth indication information is used to indicate the second uplink resource.

34. The apparatus according to claim 30, wherein, The second information includes at least one of the following: The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources; The fifth instruction information is used to indicate the reported trigger event that has been satisfied; The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event; The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

35. An information receiving device, comprising: The first receiving module is used for: The network-side device receives the first information on the first uplink resource; or, The network-side device sends the first information on the first uplink resource and receives the second information on the second uplink resource. The first information is used to indicate whether the terminal should send the second information, and the second information contains relevant information about the content of the reported information.

36. The apparatus of claim 35, further comprising: The second transmitting module is used for at least one of the following: The network-side device sends a first DCI to the terminal, the first DCI being used to schedule or indicate the second uplink resource; The network-side device sends a third message to the terminal, the third message being feedback information indicating that the network-side device has successfully received the first message.

37. The apparatus of claim 35, further comprising: The second determining module is used by the network-side device to determine the second uplink resource by at least one of the following: The PUCCH configured on the network-side device; The CG-PUSCH configured on the network-side device; The uplink resources dynamically scheduled by the network-side equipment; The PUSCH triggered by the network-side device to carry non-periodic CSI reports.

38. The apparatus according to claim 35, wherein, The first information includes at least one of the following: The first indication information is used to indicate the reported trigger event that has been satisfied; The second instruction information is used to indicate the status of the reported triggering event; The third instruction information is used to indicate the payload size of the second information; The fourth indication information is used to indicate the second uplink resource.

39. The apparatus according to claim 35, wherein, The second information includes at least one of the following: The relevant information of RSs that meet the reporting trigger event in the first set of measurement resources; The fifth instruction information is used to indicate the reported trigger event that has been satisfied; The sixth instruction information is used to indicate the target report configuration, which is associated with the reporting trigger event; The seventh indication information is used to indicate the target cell, which is associated with the reported triggering event.

40. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the information reporting method as claimed in any one of claims 1 to 15.

41. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the information receiving method as claimed in any one of claims 16 to 27.

42. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the information reporting method as claimed in any one of claims 1 to 15, or implement the steps of the information receiving method as claimed in any one of claims 16 to 27.

43. A computer program product comprising computer instructions that, when executed by a processor, implement the steps of the information reporting method as described in any one of claims 1 to 15, or implement the steps of the information receiving method as described in any one of claims 16 to 27.

Images