Report transmission method, terminal, and network side device

By sending report trigger indication information on the PUCCH resource and determining the PUSCH time domain position according to DCI, the problem of terminal trigger report reporting delay is solved, and more efficient report transmission is achieved.

WO2026233277A1PCT designated stage Publication Date: 2026-11-12VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/094757
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In existing technologies, the reporting timeline for terminal-triggered reports is not applicable, resulting in reporting delays and reduced real-time performance. How to effectively transmit terminal-triggered reports is an urgent problem to be solved.

Method used

When the reporting triggering conditions are met, the terminal sends a report triggering indication message on the PUCCH resource and ensures accurate transmission of the report by scheduling the time domain position of the PUSCH according to the DCI.

Benefits of technology

By optimizing the terminal's report transmission process, reporting delays were reduced, and the real-time performance and accuracy of reports were improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026094757_12112026_PF_FP_ABST
    Figure CN2026094757_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of wireless communications, and discloses a report transmission method, a terminal, and a network side device. The report transmission method in the embodiments of the present application comprises: when it is determined that a reporting trigger condition for a first report is satisfied, a terminal sends report trigger indication information on a physical uplink control channel (PUCCH) resource associated with the first report; the terminal detects downlink control information (DCI), wherein the DCI is used for scheduling a physical uplink shared channel (PUSCH) carrying the first report; the terminal determines a time domain position of the PUSCH on the basis of a target rule; and the terminal transmits the first report on the PUSCH on the basis of the determined time domain position.
Need to check novelty before this filing date? Find Prior Art

Description

The report's transmission methods, terminals, and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510598863.1, filed on May 9, 2025, entitled "Report Transmission Method, Terminal and Network Side Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of wireless communication technology, specifically relating to a report transmission method, terminal, and network-side device. Background Technology

[0004] In related technologies, a scheme for terminal-triggered beam measurement and reporting has been proposed. In this scheme, the terminal reports the beam measurement results when a reporting trigger event (or trigger condition) is met.

[0005] In related technologies, a Physical Uplink Shared Channel (PUSCH) scheduled by Downlink Control Information (DCI) can be used to carry terminal-triggered reports associated with the active state of Channel State Information (CSI) indicated in the DCI. In current protocols, the scheduling interval between PUSCHs scheduled by DCI to carry aperiodic CSI reports needs to consider the demodulation and decoding time of the Physical Downlink Control Channel (PDCCH), CSI calculation time, and PUSCH preparation time. However, for terminal-triggered reporting, the acquisition time of reported measurement results may differ from related technologies, and the timeline in related technologies may not be applicable to terminal-triggered reports. Therefore, how to transmit terminal-triggered reports is a technical problem that needs to be solved in related technologies. Summary of the Invention

[0006] This application provides a report transmission method, terminal, and network-side device, which can solve the technical problem of how to transmit terminal-triggered reports.

[0007] In a first aspect, a method for transmitting a report is provided, comprising: upon determining that a reporting triggering condition for a first report is met, a terminal transmits report triggering indication information on a Physical Uplink Control Channel (PUCCH) resource associated with the first report; the terminal detects Downlink Control Information (DCI), wherein the DCI is used to schedule a Physical Uplink Shared Channel (PUSCH) carrying the first report; the terminal determines the time-domain location of the PUSCH according to a target rule; and the terminal transmits the first report on the PUSCH based on the determined time-domain location.

[0008] Secondly, a method for transmitting a report is provided, comprising: a network-side device receiving a report triggering indication information sent by a terminal on a PUCCH resource, wherein the PUCCH resource is a PUCCH resource associated with a first report, and the report triggering indication information is used to indicate that the reporting triggering condition of the first report is met; the network-side device sending a DCI to the terminal, wherein the DCI is used to schedule a PUSCH carrying the first report; the network-side device determining the time-domain position of the PUSCH according to a target rule; and the network-side device receiving the first report transmitted by the terminal on the PUSCH based on the determined time-domain position.

[0009] Thirdly, a report transmission apparatus is provided, comprising: a sending module, configured to send report triggering indication information on a PUCCH resource associated with the first report when it is determined that the reporting triggering condition of the first report is met; a receiving module, configured to detect downlink control information (DCI), wherein the DCI is used to schedule the PUSCH carrying the first report; a processing module, configured to determine the time domain position of the PUSCH according to a target rule; and the sending module is further configured to transmit the first report on the PUSCH based on the determined time domain position.

[0010] Fourthly, a report transmission device is provided, characterized in that it comprises:

[0011] The receiving module is used to receive report trigger indication information sent by the terminal on the PUCCH resource, wherein the PUCCH resource is the PUCCH resource associated with the first report, and the report trigger indication information is used to indicate that the reporting trigger condition of the first report is met;

[0012] A sending module is used to send a DCI to the terminal, wherein the DCI is used to schedule the PUSCH carrying the first report;

[0013] The processing module is used to determine the time-domain location of the PUSCH according to the target rules;

[0014] The receiving module is further configured to receive the first report transmitted by the terminal on the PUSCH based on the determined time-domain location.

[0015] Fifthly, a report transmission device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0016] In a sixth aspect, 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.

[0017] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the first aspect, and the communication interface is configured to be coupled to the processor.

[0018] Eighthly, a network-side device is provided, the network-side device 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 second aspect.

[0019] A ninth aspect provides a network-side device including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the second aspect, and the communication interface is configured to be coupled to the processor.

[0020] In a tenth aspect, 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 described in the first aspect, or implement the steps of the method described in the second aspect.

[0021] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0022] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0023] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0024] In this embodiment, when the reporting triggering condition of the first report is met, the terminal sends a report triggering indication information on the PUCCH resource associated with the first report; the terminal detects a DCI, wherein the DCI is used to schedule the PUSCH carrying the first report; the terminal determines the time-domain position of the PUSCH according to a target rule; and the terminal transmits the first report on the PUSCH based on the determined time-domain position. The technical solution provided by this embodiment enables the transmission of terminal-triggered reports. Attached Figure Description

[0025] Figure 1 shows a block diagram of a wireless communication system that can be applied to an embodiment of this application;

[0026] Figure 2 shows a schematic diagram of the calculation time corresponding to a non-periodic CSI report;

[0027] Figure 3 shows a flowchart of a report transmission method provided in an embodiment of this application;

[0028] Figure 4 shows a flowchart of another report transmission method provided in an embodiment of this application;

[0029] Figure 5 shows a schematic diagram of the structure of a report transmission device provided in an embodiment of this application;

[0030] Figure 6 shows a schematic diagram of another report transmission device provided in an embodiment of this application;

[0031] Figure 7 shows a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0032] Figure 8 shows a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0033] Figure 9 shows a schematic diagram of the hardware structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0034] 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.

[0035] 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, not limited in number; 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, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0036] 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 the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0037] 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.

[0038] 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 also be referred to as User Equipment (UE), and 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.Among them, base stations can 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, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "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.

[0039] In NR, CSI measurement and reporting are based on the CSI framework. The CSI framework comprises at least one of the following: CSI report settings, CSI resource settings, a Non-Zero Power (nzp)-CSI Reference Signal (CSI-RS) resource set, and a Synchronization Signal Block (SSB) resource set. The CSI report configuration can be set to periodic reporting, semi-persistent reporting, or aperiodic reporting. Similarly, the time-domain characteristics of the resources corresponding to the CSI resource settings can also be configured as periodic, semi-persistent, or aperiodic.

[0040] The configuration framework for CSI measurement and reporting includes the following:

[0041] 1) A CSI report setting can be associated with a maximum of 3 CSI resource settings (including: CSI resource settings for channel measurement, CSI resource settings for interference measurement (CSI-IM), and CSI resource settings for interference measurement (NZP-CSI-RS)).

[0042] 2) An aperiodic CSI resource setting may contain multiple CSI-RS resource sets (NZP-CSI-RS resource set or CSI-IM resource set) and one SSB measurement resource set, while a periodic or semi-continuous CSI resource setting may contain only one CSI-RS resource set and one SSB measurement resource set.

[0043] 3) A CSI-RS resource set can contain multiple CSI-RS resources (CSI-IM or NZP-CSI-RS);

[0044] 4) An SSB measurement resource set includes multiple SSBs.

[0045] For beam measurement, current standards only support beam measurement via CSI-RS or SSB, with CSI-RS for beam measurement having only 1 to 2 ports. SSB is a periodic reference signal, while CSI-RS for beam measurement can be periodic, semi-continuous, or aperiodic.

[0046] Beam measurement in Releases 15 and 16 was limited to the serving cell. Release 15 only supported L1 reference signal received power (L1-RSRP) measurement, while Release 16 introduced L1 signal-to-noise and interference ratio (L1-SINR) to account for inter-cell or inter-user interference in beam measurement. Release 17's cross-cell beam management and cross-cell multi-transmitter / receiver node projects supported L1 beam measurement of neighboring cells that are on the same frequency and synchronized with the current serving cell. Release 18's 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.

[0047] For beam reporting, the current standard requires the terminal to select appropriate beams for reporting based on the full-bandwidth beam measurement results. The full-bandwidth beam measurement parameters can be L1-RSRP / L1 reference signal received quality (L1-RSRQ) / 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 for reporting, based on the measurement parameters. For group-based beam reporting, Release 15 / 16 specifies that the terminal selects a pair of beams that can be simultaneously received by the UE for reporting based on the measurement results. The reported content includes the measurement resource index and its corresponding measurement value. The measurement resource index (CSI-RS Resource Indicator (CRI) / SSB Resource Indicator (SSBRI)) is the index of the measurement resource in its corresponding measurement resource set (NZP-CSI-RS-ResourceSet or CSI-SSB-ResourceSet). The time-domain characteristics of the reported data are similar to those of CSI-RS measurement resources, including periodic reporting, semi-continuous reporting, and aperiodic reporting, as detailed below:

[0048] 1) Periodic reporting: Associated with periodic CSI-RS resources, the reporting resource is PUCCH resource, which is configured by the network through RRC;

[0049] 2) Semi-persistent reporting; can be associated with periodic or semi-persistent CSI-RS resources. The reported resources can be PUCCH resources or PUSCH resources. The PUCCH resources are determined by the signaling of the Medium Access Control Element (MAC CE) and the PUSCH resources are determined by the Downlink Control Information (DCI).

[0050] 3) Aperiodic reporting: It can be associated with periodic, semi-persistent, or aperiodic CSI-RS resources. The reporting resource is the PUSCH resource, which is determined by DCI.

[0051] 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 each cell reporting 4 beam measurement results, that is, a maximum of 16 beams and their corresponding measurement results.

[0052] To reduce reporting overhead and beam reporting latency, Release 19 introduces a terminal event-triggered L1 beam reporting technology. This means that the terminal only performs L1 beam reporting when the conditions corresponding to the triggering event are met. This terminal event-triggered L1 beam reporting technology operates within a unified Transmission Configuration Indicator (TCI) framework.

[0053] To reduce signaling overhead and simplify beam indication mechanisms, Release 17 introduced unified TCI. The unified TCI framework supports two modes: joint and separate. In joint mode, the uplink and downlink channels share the same beam, as does the reference signal. In separate mode, the downlink and reference signal beams are the same, as are the uplink and reference signal beams, but the uplink and downlink beams are different.

[0054] For joint mode, the network-side device only needs to configure one TCI state list, and then determine the UE's beam through MAC CE activation and DCI indication. For separate mode, the network-side device needs one TCI state list for downlink channels and reference signals, and one TCI uplink state (TCI-UL-State) list for uplink channels and reference signals. For TCI state activation and indication in separate mode, MAC CE activates beam pairs (i.e., one TCI state + one TCI-UL-State), and then DCI determines a beam pair from the activated beam pairs.

[0055] Currently, the status of discussions within 3GPP regarding terminal-triggered beam measurement and reporting technologies is as follows:

[0056] 1. Triggering events include:

[0057] Event 2: The number of times that at least one same candidate beam has a corresponding measurement result greater than the measurement result of the beam currently used by the terminal by a certain threshold within a time window is not less than a preset number of times, or there exists at least one candidate beam whose corresponding measurement result is greater than the measurement result of the beam currently used by the terminal;

[0058] Event 1: The number of times that the measurement result corresponding to the currently used beam is lower than a certain threshold within a time window is not less than a preset number of times, or the measurement result corresponding to the currently used beam is lower than a certain threshold;

[0059] Event 7: Within a time window, the number of times that the measurement result corresponding to at least one same candidate beam is greater than the measurement result corresponding to the TCI state with the Q-th (Q<P) highest measurement result among the currently activated P TCI states by a certain threshold is not less than a preset number of times, or there exists a candidate beam whose corresponding measurement result is greater than the measurement result corresponding to the TCI state with the Q-th (Q<P) highest measurement result among the currently activated P TCI states by a certain threshold.

[0060] 2. Determination of the corresponding measurement RS for the trigger event:

[0061] 1) The measurement RS corresponding to the candidate beam: determined by Radio Resource Control (RRC) configuration;

[0062] 2) The measurement RS corresponding to the beam currently used by the terminal: determined according to the Indicated TCI state, including two solutions: one is determined according to the Quasi co-location (QCL) source RS (e.g., CSI-RS) of the Indicated TCI state; the other is determined according to the QCL root source RS (e.g., SSB) of the indicated TCI state;

[0063] 3) The measurement RS corresponding to the TCI state with the Q-th (Q<P) highest measurement result among the currently activated P TCI states: determined according to the activated TCI state, including two solutions: one is determined according to the QCL source RS (e.g., CSI-RS) of the activated TCI state; the other is determined according to the QCL root source RS (e.g., SSB) of the activated TCI state.

[0064] 3. Reporting mode (for Event 2):

[0065] 1) Mode A

[0066] Step-1: The terminal sends a trigger reporting indication message (1 bit) on the PUCCH resource;

[0067] Step-2: The terminal receives feedback information from the network side (e.g., Physical downlink control channel (PDCCH)). The PDCCH is used to schedule a Physical Uplink Shared Channel (PUSCH) resource that carries a report.

[0068] The PUSCH resource is a PUSCH resource indicated by DCI used to carry terminal trigger reports associated with CSI active state (trigger state), and the CSI trigger state is only associated with the report configuration reported by the terminal trigger.

[0069] Step-3: The terminal sends a report on the PUSCH resource.

[0070] 2) Mode B

[0071] Step-1: The terminal sends a trigger reporting indication message (1 bit) on the PUCCH resource;

[0072] Step-2: The terminal sends a report on the pre-allocated uplink resources (Configured Grant PUSCH, CG-PUSCH) on the network.

[0073] 4. Reporting content (for event 2):

[0074] a) Report N beams, and at least one of the N beams satisfies the condition;

[0075] b) Whether the RRC configuration terminal always reports the measurement results of the current beam; if always reported, then report N+1 beams;

[0076] Regarding the time window used for event evaluation, for a new beam, if it meets the event triggering conditions and the corresponding timer is not running, the terminal will open a time window. At the same time the time window is opened, the corresponding timer also starts running.

[0077] Regarding CSI calculation time, the current protocol only specifies the calculation time for non-periodic CSI reports based on non-periodic CSI-RS resources. Specifically, as shown in Figure 2, the following two conditions must be met:

[0078] 1) Taking timing lead into account, the first uplink symbol carrying the aperiodic CSI report cannot be earlier than Z. ref ;

[0079] Among them, Z ref T after the last symbol of the DCI that triggered the CSI report proc,CSI The first uplink symbol after T (and the case containing the cyclic prefix CP), where T proc,CSI = (Z)(2048+144)·k2 -μ ·T c +T switch Where, k = 64, T c = 1 / (480*1000*4096), T switch The time required for antenna switching is sent to the UE.

[0080] 2) Taking timing lead into account, the first uplink symbol carrying the nth non-periodic CSI report cannot be earlier than Z′. ref ;

[0081] Among them, Z′ ref The last symbol of the most recent RS resource among the aperiodic CSI-RS resource for channel measurements, the aperiodic CSI-IM resource for interference measurements, and the aperiodic NZP CSI-RS resource for interference measurements associated with the nth triggered CSI report is T′. proc,CSI =(Z′(2048+144)·k2 -μ ·T c The first uplink symbol after (and the case where it contains the cyclic prefix CP);

[0082] The values ​​of μ, Z, and Z' are as follows:

[0083] μ is the minimum value among {SCS corresponding to the PDCCH where DCI is located, SCS corresponding to the non-periodic CSI-RS activated by DCI, and SCS corresponding to the PUSCH carrying the CSI report}.

[0084] Since a CSI trigger state indicated by a DCI can be associated with M (M≥1) CSI reports, therefore

[0085] For beam reporting based on L1-RSRP (i.e., the reported measurement quantity corresponding to the CSI report is RSRP), the corresponding Z and Z' values ​​are Z3 and Z3'.

[0086] For beam reporting based on L1-SINR (i.e., the reported measurement quantity corresponding to the CSI report is SINR), the corresponding Z and Z' values ​​are Z1 and Z1', as shown in Table 1.

[0087] Table 1.

[0088] In the table above, Xu is determined based on the UE's reporting capability beamReportTiming, and KB... l The value is determined by the UE reporting capability beamSwitchTiming, where l = 1, 2, 3, 4.

[0089] In Mode A above, the PUSCH scheduled by the DCI is used to carry the terminal trigger report associated with the CSI trigger state indicated in the DCI. In the current protocol, the scheduling interval between PUSCHs scheduled by the DCI to carry aperiodic CSI reports needs to consider PDCCH demodulation and decoding time, CSI calculation time, and PUSCH preparation time. However, for terminal trigger reporting, the acquisition time of the reported measurement results may differ from related technologies. For example, the reported measurement results of terminal trigger reporting may be obtained before the first Physical Uplink Control Channel (PUCCH) indication. Continuing to use the traditional timeline increases the latency of terminal trigger reporting and reduces the real-time performance of the reported results.

[0090] Therefore, how to transmit terminal-triggered reports is a technical problem that needs to be solved in related technologies.

[0091] To address the aforementioned issues, this application provides a report transmission scheme.

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

[0093] Figure 3 illustrates a flowchart of a report transmission method according to an embodiment of this application, which can be executed by a terminal. In other words, the method can be executed by software or hardware installed on the terminal. As shown in Figure 3, the method may include the following steps.

[0094] S310, if the reporting triggering condition of the first report is met, the terminal sends a report triggering indication message on the PUCCH resource associated with the first report.

[0095] In some embodiments, the first report triggered by the terminal may include at least one of a beam report and a CSI report.

[0096] In some embodiments, the report triggering indication information may be a 1-bit information used to indicate that the first report triggered by the terminal needs to be reported.

[0097] S320, the terminal detects DCI, wherein the DCI is used to schedule the PUSCH carrying the first report.

[0098] After receiving the aforementioned report trigger indication information, in order to enable the terminal to have uplink resources for reporting the first report, the network-side device can send a DCI to the terminal and schedule the PUSCH used to carry the first report through the DCI.

[0099] S330, the terminal determines the time domain location of the PUSCH according to the target rule.

[0100] S340, the terminal transmits the first report on the PUSCH based on the determined time-domain location.

[0101] The technical solution provided in this application embodiment enables terminal-triggered report transmission when the reporting triggering condition for the first report is met. The terminal sends a report triggering indication on the PUCCH resource associated with the first report. After detecting the DCI of the PUSCH carrying the first report, the terminal determines the time-domain position of the PUSCH according to a target rule (which may differ from the method used to determine the timeline in related technologies). Then, the terminal can transmit the first report on the PUSCH based on the determined time-domain position. The technical solution provided in this application embodiment enables terminal-triggered report transmission.

[0102] In some embodiments, the terminal determining the time-domain location of the PUSCH according to the target rule may include: when the PUSCH is used to carry the first report and does not carry a transport block, the terminal determines the time slot offset value K2 of the PUSCH according to the Time Domain Resource Assignment (TDRA) field in the DCI and the resource allocation table of the PUSCH, and determines the time-domain location of the PUSCH based on the time slot offset value K2.

[0103] The TDRA field is used to indicate the time domain location corresponding to the PUSCH. This time domain location is the time domain location of the PUSCH indicated by the network-side device, and the PUSCH resource allocation table is the PUSCH resource allocation table agreed upon by the protocol.

[0104] In these embodiments, when the PUSCH is used to carry the first report but does not carry a transport block, the terminal determines the PUSCH slot offset value K2 based on the TDRA field in the DCI and the PUSCH resource allocation table. This slot offset value K2 indicates the slot offset of the PUSCH relative to the PDCCH that schedules the PUSCH (i.e., the PDCCH carrying the aforementioned DCI). Through these embodiments, when uploading the first report triggered by the terminal, the PUSCH slot offset value can be determined based on the TDRA field in the DCI and the PUSCH resource allocation table.

[0105] In some embodiments, the terminal determining the time-domain location of the PUSCH according to the target rule may include: when the PUSCH is used to carry the first report and does not carry a transport block, the terminal determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report, and determines the time-domain location of the PUSCH based on the time slot offset value K2, wherein the second report is at least one of the terminal-triggered reports associated with the CSI trigger state, the second report includes the first report, and the CSI trigger state is the CSI trigger state indicated by the CSI request field in the DCI.

[0106] Optionally, in the above embodiments, the report configurations corresponding to the terminal-triggered reports associated with the CSI trigger state can all be event-triggered report configurations.

[0107] Optionally, in the above embodiments, the time slot offset list in the report configuration corresponding to the second report can be determined by the configuration of the network-side device.

[0108] In the above embodiments, when the PUSCH is used to carry the first report and does not carry a transport block, the terminal determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report.

[0109] In some embodiments, the terminal determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report. This may include: the terminal determining the slot offset value K2 of the PUSCH as follows based on the TDRA field and the slot offset list in the report configuration corresponding to the second report:

[0110] Where N is the number of second reports, Y j This is the list of time slot offsets in the report configuration corresponding to the (j+1)th second report, where m is the value of the TDRA field.

[0111] In some embodiments, when the time slot offset list in the report configuration corresponding to the first report is defaulted, the terminal can determine the time slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the resource allocation list of the PUSCH, thereby improving the accuracy of the determined time domain location of the PUSCH.

[0112] In some embodiments, if the report configuration corresponding to the first report includes a time slot offset list, the terminal can determine the time slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report, thereby improving the accuracy of the determined time domain location of the PUSCH.

[0113] In some embodiments, the reporting content included in the first report transmitted on the PUSCH is determined based on a target measurement resource, which is the measurement resource associated with the first report prior to the PUSCH resource.

[0114] Optionally, the target measurement resource can be one of the following: the transmission timing of the nearest target reference signal before the first time step, the transmission timing of the nearest target reference signal that meets the reporting trigger condition before the first time step, the transmission timing of the nearest target reference signal within the nearest time window before the PUCCH resource, or the transmission timing of the nearest target reference signal that meets the reporting trigger condition within the nearest time window before the PUCCH resource. Wherein, the first time step is a CSI reference resource determined based on the protocol agreement and the PUCCH resource, the target reference signal is the reference signal associated with the first report, and the time window is a period of time configured by the network side or agreed upon by the protocol for evaluating the reporting trigger condition. Through these embodiments, measurement results corresponding to the measurement resources associated with the first report before the PUCCH resource can be transmitted through the PUSCH resource, thereby ensuring that the measurement results reported by the terminal are consistent with the measurement results when the reporting trigger condition is met, avoiding misleading the network side's understanding.

[0115] In some embodiments, the terminal transmits the first report on the PUSCH based on the determined time-domain location, including: if the first symbol of the PUSCH is not earlier than a first symbol, the terminal transmits the first report on the PUSCH, wherein the first symbol is the first symbol after K time units following the last symbol of the DCI.

[0116] In the above embodiments, if the first symbol of the PUSCH is not earlier than the first symbol, the terminal transmits the first report through the PUSCH. If the first symbol of the PUSCH is earlier than the first symbol, the terminal can ignore the detected DCI, for example, not transmit the first report on the PUSCH, or discard the first report, thereby ensuring the transmission of the first report.

[0117] In some implementations of the above embodiments, the PUSCH is used to carry the first report and does not contain a transport block and a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

[0118] In other embodiments of the above examples, the PUSCH is used to carry the first report and includes at least one of a transport block and a HARQ-ACK.

[0119] In some implementations of the above embodiments, the value of K is determined by the network-side device configuration or protocol agreement.

[0120] In some embodiments of the above examples, the K time units include at least one of the time for decoding DCI and the preparation time for PUSCH.

[0121] In some embodiments of the above examples, K time units may be equal to T. proc,2 Among them, T proc,2 Prepare the PUSCH time for the UE as specified in the protocol.

[0122] In some implementations of the above embodiments, the K time units are the CSI calculation time corresponding to the first report.

[0123] Optionally, K is less than Z, where Z time units represent the CSI calculation time corresponding to the third report, and the third report satisfies at least one of the following:

[0124] The reporting type is periodic reporting;

[0125] The reporting type is semi-continuous reporting;

[0126] The reporting type is non-periodic reporting.

[0127] The reported measurement is the same as the first report, for example, both are beam reports, that is, the reported measurement is L1-RSRP or L1-SINR.

[0128] The technical solutions provided in this application can determine the time domain location and transmission timeline of PUSCH resources under Mode A, improve the terminal triggering reporting process, and enhance the overall feasibility of the technical solutions.

[0129] In some embodiments, a method for controlling the power accumulation value is provided, the method comprising: when the path loss (PL) offset corresponding to the closed loop power control index l is updated, the UE resets the power accumulation value corresponding to the closed loop power control index l, wherein the closed loop power control index l is determined by the TCI state.

[0130] Optionally, the PL offset corresponds to the same TCI state as l.

[0131] Optionally, the closed-loop power control index l can be a closed-loop power control index of PUSCH, PUCCH, or SRS.

[0132] In these embodiments, the PL offset update can be understood as the UE receiving a MAC CE update that updates the PL offset.

[0133] When the PL offset is updated, the transmit power will suddenly change based on the current accumulated power state, which will be significantly different from the power value expected by the network-side equipment. This will result in the uplink transmission power being too low or too high, causing performance loss in uplink transmission. Therefore, in the above embodiment, when the PL offset is updated, the closed-loop power is reset to 0, thereby avoiding this problem.

[0134] In some embodiments, a method for determining transmission power is provided, which may include the following steps:

[0135] Step 1: The UE receives configuration information from the network-side device. The configuration information includes a first set of first power values ​​and a second set of first power values. The first set of first power values ​​and the second set of first power values ​​are not exactly the same.

[0136] Step 2: If PL offset is not equal to 0, the UE uses the second set of first power values ​​in the configuration information to determine the uplink transmission transmit power; or, if PL offset is equal to 0 or not configured, the UE uses the first set of first power values ​​in the configuration information to determine the uplink transmission transmit power.

[0137] Optionally, the uplink transmission includes PUSCH / PUCCH / Sounding Reference Signal (SRS) transmission.

[0138] Optionally, for PUSCH, the first power value is at least one of the following: p0-NominalWithGrant, p0-NominalWithoutGrant, and for PUCCH, the first power value is p0-nomina.

[0139] The technical solution provided by the above embodiments determines different first power values ​​based on the value of PL offset, which can help the UE determine the matching power and ensure the performance of uplink transmission.

[0140] Based on the same technical concept, this application also provides another method for transmitting reports. This method is executed by the network-side device corresponding to method 300.

[0141] It should be noted that the following embodiments only describe the operation of the network-side device. For other matters not covered, please refer to the above description of method 300.

[0142] Figure 4 shows a schematic flowchart of a report transmission method provided in an embodiment of this application. This method 400 can be executed by a network-side device. In other words, the method can be executed by software or hardware installed on the network-side device. As shown in Figure 4, the method mainly includes the following steps.

[0143] S410, the network-side device receives report trigger indication information sent by the terminal on the PUCCH resource, wherein the PUCCH resource is the PUCCH resource associated with the first report, and the report trigger indication information is used to indicate that the reporting trigger condition of the first report is met.

[0144] S420, the network-side device sends a DCI to the terminal, wherein the DCI is used to schedule the PUSCH carrying the first report;

[0145] S430, the network-side device determines the time-domain location of the PUSCH according to the target rules;

[0146] S440, the network-side device receives the first report transmitted by the terminal on the PUSCH based on the determined time-domain location.

[0147] With the technical solution provided in this application, for a terminal-triggered report, the network-side device can use rules corresponding to the terminal to determine the time domain location of the PUSCH, and receive the first report transmitted by the terminal at the determined time domain location, thereby ensuring the successful transmission of the first report.

[0148] In some embodiments, the network-side device determines the time-domain location of the PUSCH according to a target rule, including one of the following:

[0149] When the PUSCH is used to carry the first report and does not carry a transport block, the network-side device determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the resource allocation table of the PUSCH, and determines the time domain position of the PUSCH based on the slot offset value K2.

[0150] When the PUSCH is used to carry the first report but does not carry a transport block, the network-side device determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report. Based on the time slot offset value K2, the time domain position of the PUSCH is determined. The second report is at least one of the terminal-triggered reports associated with the CSI trigger state. The second report includes the first report. The CSI trigger state is the CSI trigger state indicated by the CSI request field in the DCI.

[0151] In some embodiments, the network-side device determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report, including:

[0152] The network-side device determines the PUSCH slot offset value K2 as follows based on the slot offset list in the report configuration corresponding to the TDRA domain and the second report:

[0153] Where N is the number of second reports, Y j This is the list of time slot offsets in the report configuration corresponding to the (j+1)th second report, where m is the value of the TDRA field.

[0154] In some embodiments, if the time slot offset list in the report configuration corresponding to the first report is defaulted, the network-side device can determine the time slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the resource allocation list of the PUSCH.

[0155] In some embodiments, when the report configuration corresponding to the first report includes a time slot offset list, the network-side device determines the time slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report. This can improve the accuracy of the determined time domain location of the PUSCH.

[0156] In some embodiments, the network-side device receives the first report transmitted by the terminal on the PUSCH based on the determined time-domain location, including:

[0157] If the first symbol of the PUSCH is not earlier than the first symbol, the network-side device receives the first report transmitted by the terminal on the PUSCH, wherein the first symbol is the first symbol after K time units following the last symbol of the DCI.

[0158] In the above embodiments, when the first symbol of the PUSCH is not earlier than the first symbol, the network-side device receives the first report transmitted by the terminal on the PUSCH, while when the first symbol of the PUSCH is earlier than the first symbol, the network-side device does not receive it on the PUSCH, thereby reducing unnecessary operations.

[0159] In some implementations of the above embodiments, the PUSCH is used to carry the first report and does not include a transport block and HARQ-ACK.

[0160] In other embodiments of the above examples, the PUSCH is used to carry the first report and includes at least one of a transport block and a HARQ-ACK.

[0161] In some implementations of the above embodiments, the value of K is determined by the network-side device configuration or protocol agreement.

[0162] In some embodiments of the above examples, the K time units include at least one of the time for decoding DCI and the preparation time for PUSCH.

[0163] In some embodiments of the above examples, K time units may be equal to T. proc,2 Among them, T proc,2 Prepare the PUSCH time for the UE as specified in the protocol.

[0164] In some implementations of the above embodiments, the K time units are the CSI calculation time corresponding to the first report.

[0165] Optionally, K is less than Z, where Z time units represent the CSI calculation time corresponding to the third report, and the third report satisfies at least one of the following:

[0166] The reporting type is periodic reporting;

[0167] The reporting type is semi-continuous reporting;

[0168] The reporting type is non-periodic reporting.

[0169] The reported measurement is the same as the first report, for example, both are beam reports, that is, the reported measurement is L1-RSRP or L1-SINR.

[0170] Through the technical solutions provided in the embodiments of this application, the network-side device can determine the time-domain location and transmission timeline of the PUSCH resource under Mode A, improve the terminal-triggered reporting process, and enhance the overall feasibility of the technical solution.

[0171] The report transmission method provided in this application can be executed by a report transmission device. This application uses an example of a report transmission device executing the report transmission method to illustrate the report transmission device provided in this application.

[0172] This application provides a report transmission device. As an example, the report transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0173] The report transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0174] Specifically, referring to Figure 5, when the report transmission device is a terminal or a component within a terminal, the report transmission device 500 includes a sending module 501, used to send report triggering indication information on the PUCCH resource associated with the first report when the reporting triggering condition of the first report is met; a receiving module 502, used to detect downlink control information (DCI), wherein the DCI is used to schedule the PUSCH carrying the first report; a processing module 503, used to determine the time domain position of the PUSCH according to target rules; and the sending module 501 is further used to transmit the first report on the PUSCH based on the determined time domain position.

[0175] In some embodiments, the processing module 503 determines the time-domain location of the PUSCH according to the target rule, including one of the following:

[0176] When the PUSCH is used to carry the first report and does not carry a transport block, the time slot offset value K2 of the PUSCH is determined according to the Time Domain Resource Indicator (TDRA) field in the DCI and the resource allocation table of the PUSCH, and the time domain position of the PUSCH is determined based on the time slot offset value K2.

[0177] When the PUSCH is used to carry the first report but does not carry a transport block, the time slot offset value K2 of the PUSCH is determined according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report. Based on the time slot offset value K2, the time domain position of the PUSCH is determined. The second report is at least one of the terminal-triggered reports associated with the CSI trigger state. The second report includes the first report. The CSI trigger state is the CSI trigger state indicated by the CSI request field in the DCI.

[0178] In some embodiments, the processing module 503 determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report, including:

[0179] Based on the slot offset list in the report configuration corresponding to the TDRA domain and the second report, the slot offset value K2 of the PUSCH is determined as follows:

[0180] Where N is the number of second reports, Y j This is the list of time slot offsets in the report configuration corresponding to the (j+1)th second report, where m is the value of the TDRA field.

[0181] In some embodiments, the processing module 503 determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the configured PUSCH resource allocation list, including: when the slot offset list in the report configuration corresponding to the first report is defaulted, determining the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the PUSCH resource allocation list; or, the processing module determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report, including: when the report configuration corresponding to the first report includes a slot offset list, determining the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report.

[0182] In some embodiments, the reporting content included in the first report transmitted on the PUSCH is determined based on a target measurement resource, which is the measurement resource associated with the first report prior to the PUSCH resource.

[0183] In some embodiments, the processing module 503 transmits the first report on the PUSCH based on the determined time-domain location, including:

[0184] If the first symbol of the PUSCH is not earlier than the first symbol, the terminal transmits the first report on the PUSCH, wherein the first symbol is the first symbol after K time units following the last symbol of the DCI.

[0185] In some embodiments, the PUSCH is used to carry the first report and does not contain transport blocks and HARQ-ACK.

[0186] In some embodiments, the PUSCH is used to carry the first report and includes at least one of a transport block and a HARQ-ACK.

[0187] In some embodiments, the value of K is determined by the network-side device configuration or protocol agreement.

[0188] In some embodiments, the K time units include at least one of the time for decoding the DCI and the preparation time for the PUSCH.

[0189] In some embodiments, the K time units are the CSI calculation time corresponding to the first report.

[0190] In some embodiments, K is less than Z, and Z time units represent the CSI calculation time corresponding to the third report, wherein the third report satisfies at least one of the following:

[0191] The reporting type is periodic reporting;

[0192] The reporting type is semi-continuous reporting;

[0193] The reporting type is non-periodic reporting.

[0194] The reported measurement is the same as the first report.

[0195] Referring to Figure 6, when the report transmission device is a network-side device or a component within a network-side device, the report transmission device 600 includes a receiving module 601, configured to receive report triggering indication information sent by a terminal on a PUCCH resource, wherein the PUCCH resource is the PUCCH resource associated with the first report, and the report triggering indication information is used to indicate that the reporting triggering condition of the first report is met; a sending module 602, configured to send a DCI to the terminal, wherein the DCI is used to schedule the PUSCH carrying the first report; a processing module 603, configured to determine the time-domain position of the PUSCH according to a target rule; and the receiving module 601, further configured to receive the first report transmitted by the terminal on the PUSCH based on the determined time-domain position.

[0196] In some embodiments, the processing module 603 determines the time-domain location of the PUSCH according to the target rule, including one of the following:

[0197] When the PUSCH is used to carry the first report and does not carry a transport block, the time slot offset value K2 of the PUSCH is determined according to the TDRA field in the DCI and the resource allocation table of the PUSCH, and the time domain position of the PUSCH is determined based on the time slot offset value K2.

[0198] When the PUSCH is used to carry the first report but does not carry a transport block, the time slot offset value K2 of the PUSCH is determined according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report. Based on the time slot offset value K2, the time domain position of the PUSCH is determined. The second report is at least one of the terminal-triggered reports associated with the CSI trigger state. The second report includes the first report. The CSI trigger state is the CSI trigger state indicated by the CSI request field in the DCI.

[0199] In some embodiments, the processing module 603 determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report, including:

[0200] Based on the slot offset list in the report configuration corresponding to the TDRA domain and the second report, the slot offset value K2 of the PUSCH is determined as follows:

[0201] Where N is the number of second reports, Y j This is the list of time slot offsets in the report configuration corresponding to the (j+1)th second report, where m is the value of the TDRA field.

[0202] In some embodiments, the processing module 603 determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the configured PUSCH resource allocation list, including: when the slot offset list in the report configuration corresponding to the first report is defaulted, determining the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the PUSCH resource allocation list; or,

[0203] The processing module 603 determines the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report, including: when the report configuration corresponding to the first report contains a slot offset list, determining the slot offset value K2 of the PUSCH based on the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report.

[0204] In some embodiments, the processing module 603 receives the first report transmitted by the terminal on the PUSCH based on the determined time-domain location, including:

[0205] If the first symbol of the PUSCH is not earlier than the first symbol, the receiving terminal transmits the first report on the PUSCH, wherein the first symbol is the first symbol after K time units following the last symbol of the DCI.

[0206] In some embodiments, the PUSCH is used to carry the first report and does not contain transport blocks and HARQ-ACK.

[0207] In some embodiments, the PUSCH is used to carry the first report and includes at least one of a transport block and a HARQ-ACK.

[0208] The report transmission device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 3 to 4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0209] As shown in Figure 7, this application embodiment also provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instructions that can run on the processor 701. For example, when the communication device 700 is a terminal, the program or instructions executed by the processor 701 implement the various steps of the above-described report transmission method 300 embodiment and achieve the same technical effect. When the communication device 700 is a network-side device, the program or instructions executed by the processor 701 implement the various steps of the above-described report transmission method 400 embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0210] 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 in the method embodiment shown in FIG3. 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 can achieve the same technical effect. The terminal can be the report transmission device shown in FIG5. Specifically, FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0211] The terminal 800 includes, but is not limited to, at least some of the following components: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0212] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 810 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 8 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.

[0213] It should be understood that, in this embodiment, the input unit 804 may include a graphics processor 8041 and a microphone 8042. The graphics processor 8041 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 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 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.

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

[0215] The memory 809 can be used to store software programs or instructions, as well as various data. The memory 809 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 809 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 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0216] Processor 810 may include one or more processing units; optionally, processor 810 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 810.

[0217] The radio frequency unit 801 is used to send a report trigger indication information on the PUCCH resource associated with the first report when the reporting trigger condition of the first report is met; and to detect downlink control information (DCI), wherein the DCI is used to schedule the PUSCH carrying the first report.

[0218] Processor 810 is used to determine the time-domain location of the PUSCH according to the target rules;

[0219] The radio frequency unit 801 is also configured to transmit the first report on the PUSCH based on the determined time-domain location.

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

[0221] 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 shown in FIG4. 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 can achieve the same technical effect.

[0222] Specifically, this application embodiment also provides a network-side device, which can be the report transmission device shown in FIG. 6. As shown in FIG. 9, the network-side device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904, and a memory 905. The antenna 901 is connected to the radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be transmitted and sends it to the radio frequency device 902, which processes the received information and then transmits it through the antenna 901.

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

[0224] The baseband device 903 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG9. One of the chips is, for example, a baseband processor, which is connected to the memory 905 via a bus interface to call the program or instructions in the memory 905 to execute the network-side device operation shown in the above method embodiment.

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

[0226] The radio frequency device 902 is used to receive report trigger indication information sent by the terminal on the PUCCH resource, wherein the PUCCH resource is the PUCCH resource associated with the first report, and the report trigger indication information is used to indicate that the reporting trigger condition of the first report is met; and to send DCI to the terminal, wherein the DCI is used to schedule the PUSCH carrying the first report;

[0227] Processor 904 is used to determine the time-domain location of the PUSCH according to the target rules;

[0228] The radio frequency device 902 is also configured to receive the first report transmitted by the terminal on the PUSCH based on the determined time-domain location.

[0229] In addition, the network-side device 900 of this application embodiment also includes: a program or instructions stored in a memory 905 and executable on a processor 94. The processor 904 calls the program or instructions in the memory 905 to execute the methods executed by each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0230] 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-described report transmission method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0231] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. 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.

[0232] 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-reported transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0233] 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.

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

[0235] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the report transmission method 300 as described above, and the network-side device can be used to execute the steps of the report transmission method 400 as described above.

[0236] 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.

[0237] 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 the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0238] 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. A method for transmitting a report, comprising: in a case where a reporting trigger condition of a first report is determined to be satisfied, a terminal sending report trigger indication information on a physical uplink control channel (PUCCH) resource associated with the first report; the terminal detecting a downlink control information (DCI), wherein the DCI is used for scheduling a physical uplink shared channel (PUSCH) carrying the first report; the terminal determining a time domain position of the PUSCH according to a target rule; the terminal transmitting the first report on the PUSCH based on the determined time domain position.

2. The method of claim 1, wherein, The terminal determining the time domain position of the PUSCH according to a target rule includes one of the following: in a case where the PUSCH is used for carrying the first report and does not carry a transport block, the terminal determining a time domain resource allocation (TDRA) field in the DCI and a resource allocation table of the PUSCH to determine a time slot offset value K2 of the PUSCH, and determining the time domain position of the PUSCH based on the time slot offset value K2; in a case where the PUSCH is used for carrying the first report and does not carry a transport block, the terminal determining a TDRA field in the DCI and a time slot offset list in a report configuration corresponding to a second report to determine a time slot offset value K2 of the PUSCH, and determining the time domain position of the PUSCH based on the time slot offset value K2, wherein the second report is at least one of reports triggered by the terminal in a CSI trigger state, the second report includes the first report, and the CSI trigger state is a CSI trigger state indicated by a CSI request field in the DCI.

3. The method of claim 2, wherein, The terminal determining the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report includes: The terminal determines a time slot offset value K2 of the PUSCH according to the TDRA field and a time slot offset list in a report configuration corresponding to the second report, and the time slot offset value K2 is: where N is the number of second reports, Y j is a list of slot offsets in the report configuration corresponding to the j+1th second report, and m is the value of the TDRA field. 4.The method of claim 2, wherein The terminal determining the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a PUSCH resource allocation list configured includes: in a case where the time slot offset list in the report configuration corresponding to the first report is default, the terminal determining the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the resource allocation list of the PUSCH; or The terminal determining the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report includes: in a case where the time slot offset list is included in the report configuration corresponding to the first report, the terminal determining the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report.

5. The method of claim 1, wherein, Reporting content included in the first report transmitted on the PUSCH is determined based on a target measurement resource, and the target measurement resource is a measurement resource associated with the first report before the PUCCH resource.

6. The method of claim 1, wherein, transmit the first report on the PUSCH based on the determined time domain position, including: transmit the first report on the PUSCH in a case that a first symbol of the PUSCH is not earlier than a first symbol, wherein the first symbol is a first symbol after K time units after a last symbol of the DCI.

7. The method of claim 6, wherein, the PUSCH is used to carry the first report and does not include a transport block and a HARQ-ACK.

8. The method of claim 6, wherein, the PUSCH is used to carry the first report and includes at least one of a transport block and a HARQ-ACK.

9. The method of claim 6, wherein, a value of K is configured by a network side device or agreed by a protocol.

10. The method of claim 9, wherein, the K time units include at least one of a time of decoding the DCI and a preparation time of the PUSCH.

11. The method of claim 9, wherein, the K time units are a CSI calculation time corresponding to the first report.

12. The method of claim 11, wherein, K is less than Z, and Z time units are a CSI calculation time corresponding to a third report, the third report satisfying at least one of: a reporting type is periodic reporting; a reporting type is semi-persistent reporting; a reporting type is aperiodic reporting a measurement quantity of reporting is the same as the first report.

13. A transmission method of a report, including: a network side device receiving report trigger indication information sent by a terminal on a PUCCH resource, wherein the PUCCH resource is a PUCCH resource associated with a first report, and the report trigger indication information is used to indicate that a reporting trigger condition of the first report is met; the network side device sending a DCI to the terminal, wherein the DCI is used to schedule a PUSCH carrying the first report; the network side device determining a time domain position of the PUSCH according to a target rule; the network side device receiving the first report transmitted by the terminal on the PUSCH based on the determined time domain position.

14. The method of claim 13, wherein, the network side device determining a time domain position of the PUSCH according to a target rule, including one of: in a case that the PUSCH is used to carry the first report and does not carry a transport block, the network side device determines a time slot offset value K2 of the PUSCH according to a TDRA field in the DCI and a resource allocation table of the PUSCH, and determines the time domain position of the PUSCH based on the time slot offset value K2; in a case that the PUSCH is used to carry the first report and does not carry a transmission block, the network side device determines a time slot offset value K2 of the PUSCH according the TDRA field in the DCI and a time slot offset list in a report configuration corresponding to a second report, and determines the time domain position of the PUSCH based on the time slot offset value K 2, wherein the second report is at least one of reports triggered by a terminal associated with a CSI trigger state, the second report includes the first report, and the CSI trigger state is a CSI trigger state indicated by a CSI request field in the DCI.

15. The method of claim 14, wherein, the network side device determines a time slot offset value K2 of the PUSCH according to a TD-RA field in the DCI and a time slot offset list in a report configuration corresponding to a report, including: The network side device determines a time slot offset value K2 of the PUSCH according to the TDRA domain and a time slot offset list in a report configuration corresponding to the second report, and the time slot offset value K2 is: where N is the number of second reports, Y j is a list of slot offsets in the report configuration corresponding to the j+1th second report, and m is the value of the TDRA field.

16. The method of claim 14, wherein, the network-side device determines a slot offset value K2 of the PUSCH according to a TDRA field in the DCI and a configured PUSCH resource allocation list, including: in a case where a slot offset list in a report configuration corresponding to the first report is default, the network-side device determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a resource allocation list of the PUSCH; or, the network-side device determines the slot offset value K2 of the PUSCH according to a TDRA field in the DCI and a slot offset list in a report configuration corresponding to the second report, including: in a case where the slot offset list is included in the report configuration corresponding to the first report, the network-side device determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the slot offset list in the report configuration corresponding to the second report.

17. The method of claim 13, wherein, the network-side device receives the first report transmitted by the terminal on the PUSCH based on the determined time domain position, including: in a case where a first symbol of the PUSCH is not earlier than a first symbol, the network-side device receives the first report transmitted by the terminal on the PUSCH, wherein the first symbol is a first symbol after K time units after a last symbol of the DCI.

18. The method of claim 17, wherein, the PUSCH is used to carry the first report and does not include a transport block and HARQ-ACK.

19. The method of claim 17, wherein, the PUSCH is used to carry the first report and includes at least one of a transport block and HARQ-ACK.

20. A reporting transmission apparatus, comprising: a sending module configured to send report trigger indication information on a PUCCH resource associated with a first report in a case where a reporting trigger condition of the first report is determined to be met; a receiving module configured to detect a DCI (Downlink Control Information), wherein the DCI is used to schedule a PUSCH (Physical Uplink Shared Channel) carrying the first report; a processing module configured to determine a time domain position of the PUSCH according to a target rule; the sending module is further configured to transmit the first report on the PUSCH based on the determined time domain position.

21. The apparatus of claim 20, wherein, the processing module determines the time domain position of the PUSCH according to the target rule, including one of: in a case where the PUSCH is used to carry the first report and does not carry a transport block, determining a slot offset value K2 of the PUSCH according to a TDRA (Time Domain Resource Allocation) field in the DCI and a resource allocation table of the PUSCH, and determining the time domain position of the PUSCH based on the slot offset value K2; In a case where the PUSCH is used to carry the first report and does not carry a transport block, determining, according to a time slot offset list in the TDRA field in the DCI and a report configuration corresponding to a second report, a time slot offset value K2 of the PUSCH, and determining a time domain position of the PUSCH based on the time slot offset value K2, wherein the second report is at least one of reports triggered by a terminal associated with a CSI trigger state, the second report includes the first report, and the CSI trigger state is a CSI trigger state indicated by a CSI request field in the DCI.

22. The apparatus of claim 21, wherein, The processing module determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report, including: The terminal determines a time slot offset value K2 of the PUSCH according to the TDRA field and a time slot offset list in a report configuration corresponding to the second report, and the time slot offset value K2 is: where N is the number of second reports, Y j is a list of slot offsets in the report configuration corresponding to the j+1th second report, and m is the value of the TDRA field.

23. The apparatus of claim 21, wherein, The processing module determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report, including: The processing module determines the time slot offset value K2 of the PUSCH according to the TDRA field in the DCI and the time slot offset list in the report configuration corresponding to the second report, including:

24. The apparatus of claim 20, wherein, The sending module transmits the first report on the PUSCH based on the determined time domain position, including: In a case where a first symbol of the PUSCH is not earlier than a first symbol, transmitting the first report on the PUSCH, wherein the first symbol is a first symbol after K time units after a last symbol of the DCI.

25. A report transmission apparatus, comprising: a receiving module configured to receive report trigger indication information sent by a terminal on a PUCCH resource, wherein the PUCCH resource is a PUCCH resource associated with a first report, and the report trigger indication information is used to indicate that a reporting trigger condition of the first report is met; a sending module configured to send a DCI to the terminal, wherein the DCI is used to schedule a PUSCH carrying the first report; a processing module configured to determine a time domain position of the PUSCH according to a target rule; The receiving module is further configured to receive the first report transmitted by the terminal on the PUSCH based on the determined time domain position.

26. The apparatus of claim 25, wherein, The processing module determines the time domain position of the PUSCH according to the target rule, including one of the following: In a case that the PUSCH is used to carry the first report and does not carry a transport block, determining a slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a resource allocation table of the PUSCH, and determining a time domain position of the PUSCH based on the slot offset value K2; In a case that the PUSCH is used to carry the first report and does not carry a transport block, determining a slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a slot offset list in a report configuration corresponding to a second report, and determining a time domain position of the PUSCH based on the slot offset value K2, wherein the second report is at least one of reports triggered by a terminal associated with a CSI trigger state indicated by a CSI request field in the DCI, and the second report includes the first report.

27. The apparatus of claim 26, wherein, The processing module determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a slot offset list in a report configuration corresponding to a second report, and comprises: According to the TDRA field and a slot offset list in a report configuration corresponding to the second report, a slot offset value K2 of the PUSCH is determined as: where N is the number of second reports, Y j is the slot offset list in the report configuration corresponding to the j+1th second report, and m is the value of the TDRA field.

28. The apparatus of claim 26, wherein, The processing module determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a slot offset list in a report configuration corresponding to a second report, and comprises: The processing module determines the slot offset value K2 of the PUSCH according to the TDRA field in the DCI and a slot offset list in a report configuration corresponding to a second report, and comprises:

29. The apparatus of claim 25, wherein, The receiving module receives the first report transmitted by the terminal on the PUSCH based on the determined time domain position, and comprises: In a case that a first symbol of the PUSCH is not earlier than a first symbol, receiving the first report transmitted by the terminal on the PUSCH, wherein the first symbol is a first symbol after K time units after a last symbol of the DCI.

30. A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the method for transmitting a report according to any one of claims 1 to 12.

31. A network side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs of instructions being executed by the processor to implement the steps of the method for transmitting a report according to claim 13 to 19.

32. A readable storage medium, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the reporting transmission method according to any one of claims 1 to 12, or implement the steps of the reporting transmission method according to any one of claims 13 to 19.