Event-triggered beam reporting method and device, communication equipment and storage medium

Abstract

The invention relates to an event-triggered beam reporting method and device, communication equipment, a storage medium and a computer program product. The method is applied to a terminal, and comprises the following steps: if the instance number of trigger events of at least one new beam is greater than or equal to an instance number threshold in a detection time window, determining to initiate beam reporting; the transmission process of beam reporting is that the terminal sends first information on a first uplink resource and sends second information on a second uplink resource. By adopting the method, the signaling overhead can be saved, and the communication reliability is improved.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to an event-triggered beam reporting method, apparatus, communication equipment, storage medium, and computer program product. Background Art

[0002] In the traditional beam management process, the network can configure or activate the terminal to perform beam reporting according to a preset period, periodically or semi-persistently, so as to obtain beam data in a timely manner and control the optimal beam for transmission between the terminal and the network.

[0003] However, the terminal periodically or semi-persistently performs beam reporting, and the beam reported in the beam report has a lag, so the network cannot obtain the optimal beam in time, which leads to a decrease in transmission performance. Therefore, a beam reporting method is continued. Summary of the Invention

[0004] Embodiments of the present application provide an event-triggered beam reporting method, apparatus, communication device, storage medium, and computer program product.

[0005] An event-triggered beam reporting method, the method comprising:

[0006] If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated;

[0007] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0008] The method is applied to a terminal, and includes:

[0009] If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated;

[0010] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0011] In one of the embodiments, the first uplink resource includes PUCCH, and the first information includes at least 1 bit of information, and the first information is used to notify the base station that the beam report will be sent on the pre-configured second uplink resource, or to request the base station for the second uplink resource for sending the beam report.

[0012] In one embodiment, the method further comprises:

[0013] The first information sent on the first uplink resource is restricted by setting a counter and / or a prohibition timer.

[0014] In one embodiment, the sending condition of the first information sent on the first uplink resource satisfies at least one of the following conditions:

[0015] When the prohibit timer runs, the terminal does not send the first information sent on the first uplink resource;

[0016] If first information of other first uplink resources or second information of second uplink resources has been sent within the detection time window related to the first uplink resource transmission opportunity, the terminal does not send the first information on the first uplink resource.

[0017] In one embodiment, the activation mechanism of the prohibit timer supports at least any one of the following:

[0018] After sending the first information on the first uplink resource, starting the prohibition timer; or,

[0019] When sending the first information on the first uplink resource and obtaining the second uplink resource authorization, starting the prohibition timer; or,

[0020] After the second information is sent on the second uplink resource, the prohibit timer is started.

[0021] In one embodiment, the method further comprises:

[0022] Receive configuration information sent by the base station, where the configuration information includes at least one of the following information:

[0023] Detection time window, instance number threshold, maximum send count threshold, counter, and prohibition timer length.

[0024] In one embodiment, the trigger event includes at least one of a first trigger event, a second trigger event, and a third trigger event; and the trigger event is determined by:

[0025] First trigger event: the current beam quality is lower than the first threshold;

[0026] Second trigger event: the beam quality of at least one new beam reaches a second threshold, where the second threshold is higher than the current beam quality;

[0027] The third trigger event: the beam quality of at least one new beam reaches a third threshold, and the third threshold is higher than the Qth best beam quality of the activated transmission configuration indication TCI state, and the parameter Q≥1.

[0028] In one embodiment, the current beam quality includes at least one of the following:

[0029] Layer 1 reference signal received power L1-RSRP or layer 1 signal to interference plus noise ratio L1-SINR of the reference signal in the specified TCI state; or

[0030] L1-RSRP or L1-SINR of the synchronization signal SS / Physical Broadcast Channel PBCH block that is quasi-co-located with the reference signal in the specified TCI state.

[0031] In one of the embodiments, the beam report content of the beam report includes at least one of an optimal beam indication, beam quality, and associated parameter information.

[0032] In one embodiment, when the trigger event is the second trigger event, the beam report content includes the beam qualities of N new beams, or the beam qualities of N new beams and the current beam, where parameter N≥1, and the parameter N is configured by the base station.

[0033] In one embodiment, the configuration of the beam report content supports one of the following methods:

[0034] When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to enable beam reporting of the current beam, and the beam report content includes the N new beams and the beam quality of the current beam; otherwise, the beam report content only includes the beam quality of the N new beams; or,

[0035] When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to disable the beam report of the current beam, and the beam report content only includes the beam qualities of the N new beams; otherwise, the beam report content includes the beam qualities of the N new beams and the current beam; or,

[0036] When RRC signaling or RRC field is configured, the RRC signaling or RRC field is used to enable and / or disable the beam report of the current beam. When the RRC signaling or RRC field is a first value, the beam report content only includes the beam quality of the N new beams; when the RRC signaling or RRC field is a second value, the beam report content includes the beam quality of the N new beams and the current beam.

[0037] In one embodiment, the detection time window supports at least one of the following configurations:

[0038] The detection time window is the start time minus the end time; wherein the start time is (N)*T_PUCCH -T_proc - T_window; the end time is (N)*T_PUCCH - T_proc; (N)*T_PUCCH is the time corresponding to the Nth PUCCH transmission opportunity after the start time, T_proc is the processing time, and T_window is the duration of the detection time window; or,

[0039] The start time of the detection time window is T_Instance-T_window, the end time of the detection time window is the end time of T_Instance, T_Instance is the evaluation occasion of the triggering event instance, and T_window is the length of the detection time window; or,

[0040] The detection time window is determined based on the length T_window of the detection time window and / or the time slot offset and / or the measurement period configured by the network; or,

[0041] The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance is obtained; or,

[0042] The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance reaches an instance threshold; or,

[0043] The detection time window has a length of T_window, and a timer of the detection time window is started or restarted at the Nth PUCCH transmission opportunity after a new beam triggering event instance reaches an instance threshold;

[0044] T_window is predefined by the terminal or configured by the NW.

[0045] In one of the embodiments, when the RRC signaling or field is configured, the RRC signaling or field is used to indicate a beam reporting mode, and the beam reporting mode includes a first mode and a second mode.

[0046] In one embodiment, sending the second information on the second uplink resource includes:

[0047] When the beam reporting mode is the first mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report; the second uplink resource includes a physical uplink shared channel PUSCH indicated in downlink control information DCI;

[0048] When the beam reporting mode is the second mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report, and the second uplink resource includes a configured authorized physical uplink shared channel type 1 CG-PUSCH.

[0049] In one embodiment, if the first uplink resources overlap, and the overlapping resources are PUCCHs, the overlapping resource resolution mechanism includes at least any one of the following:

[0050] When a first uplink resource carrying first information collides / overlaps with a PUCCH carrying first target information, sorting is performed based on a first priority rule, and the information with the highest priority is sent based on the sorted priority; wherein the first target information includes a normal scheduling request normal SR and / or a normal link recovery request LRR; the first priority rule is: PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR; or,

[0051] When the first uplink resource carrying the first information collides / overlaps with the PUCCH carrying the second target information, sorting is performed based on the second priority rule, and the information with the highest priority is sent based on the sorted priority; wherein, the second target information includes one or more of hybrid automatic repeat request confirmation HARQ-ACK, CSI report, normal scheduling request normal SR, and normal link recovery request LRR; the second priority rule includes any one of the first sub-priority or the second sub-priority, and the first sub-priority is PUCCH carrying LRR>PUCCH carrying HARQ-ACK>the first uplink resource>PUCCH carrying normal SR>CSI; the second sub-priority is PUCCH carrying HARQ-ACK>PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR>CSI; or,

[0052] When the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI, or when the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI and meets the multiplexing time condition, sorting is performed based on the second priority rule, and the highest priority information is sent based on the sorted priority; otherwise, the PUCCH indicated by the DCI is sent and the first uplink resource is discarded.

[0053] In one embodiment, when the first uplink resources overlap, and the overlapping resources are PUSCHs, the overlapping resource resolution mechanism includes at least any one of the following:

[0054] When a first uplink resource carrying first information collides with / overlaps a PUSCH, the first uplink resource is preferentially processed and the PUSCH is discarded; or the first information carried by the first uplink resource is encoded into the PUSCH; or the discarding and / or multiplexing rules when a PUCCH carrying repeated transmissions of an SR collides with / overlaps a PUSCH are followed; or,

[0055] If the PUSCH does not use the uplink shared channel UL-SCH for transmission, discard the PUSCH; or,

[0056] If the PUSCH is transmitted using an uplink shared channel UL-SCH, the PUSCH is sent and the first uplink resource is discarded; or, the first information carried by the first uplink resource is encoded into the PUSCH;

[0057] When the first uplink resource carrying the first information collides / overlaps with the PUSCH of the target transmission type, the first uplink resource is sent and the PUSCH is canceled; wherein the PUSCH of the target transmission type includes at least one of the following: a PUSCH sent using repetition type A / B, a PUSCH transmitted in a single time slot, and a PUSCH including multi-slot transport block TB processing; or,

[0058] When the first uplink resource carrying the first information collides / overlaps with other PUSCH resources that are not indicated by DCI and are not repeatedly transmitted, the first uplink resource is encoded into the PUSCH, or the first information on the first uplink resource is discarded and the content on the PUSCH is sent; or

[0059] When the first uplink resource carrying the first information collides / overlaps with a PUSCH resource indicated by other DCI, discard the first information on the first uplink resource and send the content on the PUSCH; or

[0060] When the first uplink resource carrying the first information collides / overlaps with PUSCH resources indicated by other DCIs and satisfies a multiplexing time condition, the first uplink resource is encoded into the PUSCH.

[0061] In one embodiment, when the first uplink resources overlap, and the overlapping resources carry other first uplink resources, the overlapping resource resolution mechanism includes any one of the following:

[0062] When the first uplink resource is carrier c1 of the target serving cell, and the carrier c1 overlaps with multiple first uplink resources of the same CSI configuration triggered on the carrier set of the target serving cell, supporting sending the first information of the first uplink resource on the carrier c1; or,

[0063] When the first uplink resource overlaps with a first uplink resource of a different CSI configuration, the first information to be reported is determined according to the different CSI configurations, or the first information to be reported is selected based on a user.

[0064] In one embodiment, when the first uplink resources overlap, and the overlapping resources are uplink resources carrying other component carriers, the overlapping resource resolution mechanism includes any one of the following:

[0065] When the first uplink resource is carrier c1 of the target serving cell, and the carrier c1 overlaps with the sounding reference signals SRS of other component carriers on the carrier set of the target serving cell in the same symbol, the first information on the carrier c1 is sent.

[0066] An event-triggered beam reporting device, the device being applied to a terminal, the device comprising:

[0067] A determination module, configured to determine to initiate beam reporting if, within a detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to a threshold number of instances;

[0068] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0069] A communication device comprises a transmitter, a receiver and a processor, wherein when the processor executes the computer program, the following steps are implemented:

[0070] If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated;

[0071] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0072] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0073] If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated;

[0074] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0075] A computer program product includes a computer program. When the computer program is executed by a processor, the event-triggered beam reporting method provided in an embodiment of the present application is implemented. The method may be:

[0076] If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated;

[0077] The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0078] The above-mentioned event-triggered beam reporting method, apparatus, communication device, storage medium, and computer program product determine that beam reporting is initiated if, within a detection time window, the number of instances of at least one triggering event for the same new beam is greater than or equal to a threshold number of instances; wherein the transmission process of the beam reporting is that the terminal sends first information on a first uplink resource and second information on a second uplink resource. This method, by setting a dual verification mechanism for the detection time window and the number of event triggering instances, ensures that beam reporting depends on changes in beam quality, reduces uplink signaling overhead, and ensures timely reporting. Furthermore, the event-driven mechanism can significantly reduce terminal power consumption and improve communication reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 FIG2 is an application environment diagram of an event-triggered beam reporting method in one embodiment;

[0080] Figure 2 1 is a flow chart of a beam reporting method triggered by an event in one embodiment;

[0081] Figure 3 1. A schematic diagram of a flow chart of a step of limiting the first information sent on the first uplink resource in an embodiment;

[0082] Figure 4 FIG1 is a flow chart of steps for receiving configuration information sent by a base station in one embodiment;

[0083] Figure 5 Schematic diagram of the first detection time window in one embodiment;

[0084] Figure 6 Schematic diagram of the second detection time window in one embodiment;

[0085] Figure 7 Schematic diagram of the third detection time window in one embodiment;

[0086] Figure 8 Schematic diagram of the fourth detection time window in one embodiment;

[0087] Figure 9 1 is a flow chart of a method for sending second information on a second uplink resource in one embodiment;

[0088] Figure 10 This is a signaling interaction flow chart of an uplink transmission process in which a terminal initiates beam reporting based on dynamic scheduling of a second uplink resource by a gNB (base station) (i.e., the first mode) in one embodiment;

[0089] Figure 11 This is a signaling interaction flow chart of an uplink transmission process in which a terminal initiates beam reporting based on pre-configured resources in one embodiment;

[0090] Figure 12 FIG. 4 is a diagram showing the internal structure of a communication device in one embodiment. DETAILED DESCRIPTION

[0091] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0092] Figure 1 Schematic diagram of an application scenario of an event-triggered beam reporting method provided in an embodiment of the present application. Figure 1 As shown, the scenario includes a terminal 100 and a network node 200 (eg, a base station). Beam reporting is required between the terminal 100 and the network node 200 so that the network node 200 can obtain the best beam for data / control data in a timely manner.

[0093] Terminal 100 may be a wireless terminal, which may be a device that provides voice and / or other service data connectivity to a user, or a handheld device with wireless connectivity, or other processing device connected to a wireless modem. A wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN). A wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) or a computer with a mobile terminal. For example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device may exchange voice and / or data with a radio access network. A wireless terminal may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, access terminal, user terminal, user agent, or user equipment, without limitation herein.

[0094] Traditionally, the network can configure or activate terminals to periodically or semi-persistently report beams according to a preset cycle. This allows for timely acquisition of beam data and control over the optimal beam between the terminal and the network. However, with traditional terminal periodic or semi-persistent beam reporting, the reported beams are lagging, preventing the network from timely acquiring the optimal beam, leading to reduced transmission performance.

[0095] Based on the above-mentioned traditional technologies, the embodiments of the present application provide an event-triggered beam reporting method. A terminal performs event measurements within a detection time window and then reports beams based on user-initiated or event-driven reporting. This reduces unnecessary signaling overhead, improves resource utilization, and enhances system flexibility. Furthermore, this event-triggered beam reporting mechanism can significantly reduce terminal power consumption and improve communication reliability.

[0096] In addition, during the event-triggered beam reporting process, within the detection time window, the first uplink resource triggered by the same event may be frequently transmitted, or the first uplink resource triggered at the same time may be frequently transmitted, resulting in channel congestion and large resource overhead. In addition, the first uplink resource (which may be the first PUCCH) may overlap with other PUCCH, PUSCH and other resources during transmission. Therefore, after proposing the event-triggered beam reporting method, this application sets a timer and / or prohibition timer to limit the first information sent on the first uplink resource, avoid frequent uplink signaling, effectively reduce channel congestion and resource occupancy, and reduce device energy consumption. At the same time, a resource overlap processing mechanism is adopted to provide different processing mechanisms for different carried content, repetition types and resource types of overlapping PUCCH or PUSCH transmissions. In this way, a processing mechanism for different types of overlapping resources is designed for beam report uplink transmission, which greatly improves communication reliability and system robustness.

[0097] It should be understood that the three expressions of "event-triggered beam reporting", "event-driven beam reporting" and "user-initiated beam reporting" mentioned in the following embodiments of this application essentially describe the same thing, that is, the beam status reporting process that the terminal autonomously initiates based on preset trigger conditions. The core feature of this mechanism is that it gets rid of the fixed timing constraints of traditional periodic reporting and instead adopts a dynamic event judgment principle: when the UE detects that the quality of the service beam has deteriorated, finds a better candidate beam, or other network-predefined triggering conditions, it immediately and autonomously initiates a reporting process containing content such as beam index and channel quality indicators. Although there are differences in the terminology, all three point to this intelligent beam reporting method. Therefore, the following embodiments of this application are only described in terms of "event-triggered beam reporting", but other expressions of this intelligent reporting method of this application are not limited.

[0098] It should be noted that the beneficial effects or technical problems solved by the embodiments of the present application are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0099] Before introducing the specific embodiments of the present invention, the professional terms involved in the present invention are explained:

[0100] UEIBR (UE Initiated Beam Report): beam report initiated by user equipment;

[0101] UCI (Uplink Control Information): Uplink control information, including HARQ-ACK, SR, CSI, etc.

[0102] DCI (Downlink Control Information): downlink control information;

[0103] PUCCH (Physical Uplink Control Channel): physical uplink control channel;

[0104] PUSCH (Physical Uplink Shared Channel): physical uplink shared channel;

[0105] HARQ-ACK (Hybrid Automatic Repeat reQuest-Acknowledgement) hybrid automatic repeat request-acknowledgement;

[0106] SR (Scheduling Request): Scheduling request;

[0107] CSI (Channel State Information): channel state information;

[0108] SRS (Sounding Reference Signal): Sounding reference signal;

[0109] UL-SCH (Uplink Shared Channel): uplink shared channel;

[0110] CC (Carrier Component): carrier component;

[0111] RSRP (Reference Signal Received Power): Reference signal received power;

[0112] SINR (Signal to Interference plus Noise Ratio): Signal to Interference plus Noise Ratio, abbreviated as SINR.

[0113] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0114] In one embodiment, Figure 2 As shown, an event-triggered beam reporting method is provided, which is applied to Figure 1 The terminal device in the example is used to illustrate the process, including the following steps:

[0115] Step 202: If within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined to initiate beam reporting.

[0116] The transmission process of beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0117] Specifically, when the terminal continuously monitors beam quality within a preconfigured detection time window, it instantiates and records each detected new beam triggering event, including key information such as the event type, beam index, timestamp, and measurement results. The terminal then maintains a dynamic event instance counter to count the number of triggering events for the same new beam in real time. When the accumulated value of this counter reaches or exceeds a network-preconfigured instance number threshold (this threshold is typically set based on service reliability requirements and is not limited in this disclosure), the terminal determines that a target event (e.g., any of the first, second, or third events) has occurred and initiates a beam reporting process triggered by this event. After the terminal determines to perform beam reporting, it uses a two-stage transmission mechanism: first, it sends first information on a first uplink resource. This first information is used to notify the network (e.g., the base station) that the beam report will be sent on a preconfigured second uplink resource, or to request the base station for a second uplink resource for beam report transmission. Subsequently, based on the triggering of the network by the first information, the terminal sends second information on the second uplink resource. The second information includes an event-triggered beam report. The beam report may include, but is not limited to, at least one of the optimal beam indication, beam quality, and associated parameter information, so that the network can obtain the optimal beam based on the beam report, thereby improving network transmission performance.

[0118] In an optional embodiment, the first uplink resource includes a first PUCCH. The first information includes at least 1 bit of information. The first information is used to notify the base station that the beam report will be sent on a preconfigured second uplink resource, or to request the base station to use the second uplink resource for sending the beam report.

[0119] Specifically, when the terminal has been allocated a pre-configured second uplink resource, the first information serves as a notification signal, informing the base station of the subsequent beam reporting process: a beam report will be sent on the predetermined second uplink resource. When the terminal needs to dynamically obtain reporting resources, the first information serves as a resource request signal, requesting the base station to allocate a second uplink resource for beam reporting.

[0120] In the above-mentioned event-triggered beam reporting method, a dual verification mechanism is established by setting the detection time window and the number of event triggering instances to ensure that beam reporting depends on changes in beam quality, thereby reducing uplink signaling overhead and ensuring timely reporting. Moreover, the event-driven mechanism can significantly reduce terminal power consumption and improve communication reliability.

[0121] In one embodiment, within the detection time window, the first uplink resource triggered by the same event may be frequently sent, and the first uplink resource triggered at the same time may be frequently sent, causing channel congestion and large resource overhead. Figure 3 As shown, the method further includes:

[0122] Step 301: Limit first information sent on a first uplink resource by setting a counter and / or a prohibition timer.

[0123] In implementation, the terminal is provided with an event-triggered counter and a configurable prohibition timer, which together constitute a dual signaling restriction mechanism: each time the first information is sent once on the first uplink resource (for example, PUCCH), the corresponding counter will be incremented (that is, the counting rule of the counter is: when the first information is sent on the first uplink resource, the counter is incremented by one). When the cumulative number of transmissions exceeds a preset threshold (instance threshold), the terminal will automatically suspend the transmission of the first information to prevent signaling storms caused by continuous fluctuations in the channel environment; and / or, the prohibition timer can be started after each transmission of the first information, and the repeated transmission of the first information is prohibited during the startup and operation of the prohibition timer. The duration of the prohibition timer can be dynamically adjusted according to the network configuration.

[0124] Optionally, setting a counter is mainly used to prevent long-term signaling overload, while a prohibition timer controls short-term transmission density. The network side flexibly configures the counting threshold and timer duration through RRC signaling to implement a differentiated control mechanism.

[0125] In an optional embodiment, when applying a timer to limit the first information sent on the first uplink resource, the sending conditions corresponding to the timer can be pre-set. Specifically, the sending conditions related to the number of sending times are: the number of sending times is less than the preset maximum number of sending times, or (number of sending times × sending period) is less than the maximum sending time interval.

[0126] In this embodiment, by setting a counter and / or prohibiting a timer, the amount of first information sent on the first uplink resource is limited, thereby avoiding the frequent sending of the first uplink resource triggered at the same time, effectively avoiding the congestion risk of the control channel, standardizing the beam reporting process, and improving the stability and accuracy of the beam reporting.

[0127] In one embodiment, the configuration of the counter and / or disable timer supports at least one of the following mechanisms:

[0128] oCounters and or inhibit timer configurations associated to each new beam;

[0129] oCounters and or disable timer counter configuration associated to each measurement time window;

[0130] oCounters and or inhibit timers configured associated to each TCI status indication.

[0131] In one embodiment, the counter and / or the inhibit timer are reset to support at least one of the following conditions:

[0132] #1: Upon receiving RS reconfiguration / update or MAC-CE signaling for a new beam, the UE resets the technology for the new beam and counts each new beam that has not been updated, or the UE resets the counts for all new beams.

[0133] #2: The TCI status of the current beam being measured is updated and the UE resets the counts for all new beams.

[0134] #3: UEI beam report is sent, the UE only resets the count of new beams that meet the triggering conditions and are reported by the UEI beam report, or the UE resets the count of all new beams.

[0135] #4: A network NW response (eg, including at least a DCI in the first mode) is detected.

[0136] #5: The configured time window arrives or the timer expires. Predefined or preconfigured time windows or detection time windows are supported.

[0137] #6: Threshold for RRC signaling reconfiguration event evaluation.

[0138] #7: RRC parameters related to CSI reporting configuration of UEI beam reporting are reconfigured.

[0139] In this way, by setting a counter and / or prohibiting timer, the amount of first information sent on the first uplink resource is limited. Combined with the specific embodiments below, specific circumstances of applying the counter and / or prohibiting timer to limit the sending of the first information are given.

[0140] In one embodiment, in response to the problem that the first uplink resource triggered by the same event is frequently sent, or the first uplink resource triggered at the same time is frequently sent, causing channel congestion and large resource overhead, the terminal is provided with a sending condition for the first information sent on the first uplink resource, and the sending condition satisfies at least one of the following conditions:

[0141] 1. When the prohibit timer runs, the terminal does not send the first information sent on the first uplink resource;

[0142] 2. If first information on other first uplink resources or second information on second uplink resources has been sent within the detection time window related to the first uplink resource transmission opportunity, the terminal does not send the first information on the first uplink resource.

[0143] Specifically, in this beam reporting mechanism, the terminal sets a sending condition control mechanism for the first information sent on the first uplink resource (PUCCH) to ensure the rationality and effectiveness of signaling transmission. Specifically, when the prohibition timer is in the running state, the terminal will suppress (e.g., prohibit) the transmission of the first information, thereby effectively avoiding the problem of excessive signaling. Secondly, within the detection time window (which is associated with the transmission timing of the first uplink resource), if the terminal detects that there has been the transmission of first information on other first uplink resources or second information (complete beam report) on the second uplink resource (PUSCH), the terminal will also skip the current transmission opportunity, that is, it will not send the first information on the first uplink resource.

[0144] In this embodiment, the prohibition timer avoids signaling congestion from the perspective of time continuity, while the inspection of the transmission history within the detection time window prevents repeated reporting from the dimension of spatial resources, thereby saving resource overhead.

[0145] In one embodiment, the activation mechanism of the prohibit timer supports at least one of the following:

[0146] (1) After the first information is sent on the first uplink resource, the prohibit timer is started.

[0147] (2) When the first information is sent on the first uplink resource and the second uplink resource authorization is obtained, the prohibit timer is started.

[0148] (3) After the second information is sent on the second uplink resource, the prohibit timer is started.

[0149] Specifically, in the above-mentioned prohibition timer start-up mechanism, the first information, the second information or the second uplink resource authorization is sent, and the first symbol after the last symbol of the sent information or the first symbol after the resource authorization is the start time of the prohibition timer.

[0150] In the prohibit timer start mechanism of the beam reporting process, the terminal defines three ways to start the prohibit timer. For the first start mechanism: when the terminal sends the first information on the first uplink resource (such as PUCCH), the prohibit timer is started. Among them, the start reference point of the prohibit timer is defined as the first symbol immediately after the last symbol of the first information. Through the synchronous control of the physical layer symbol level, the seamless connection between the completion of signaling transmission and the start of the timer is achieved, avoiding the management and control blind spot caused by processing delay. The second start mechanism: signaling control is designed for the second uplink resource authorization scenario. When the terminal obtains the scheduling authorization for the second uplink resource (such as PUSCH) after sending the first information, the prohibit timer is started. Among them, the prohibit timer start time is precisely located at the first available symbol position where the authorization information is successfully decoded. This design not only takes into account the transmission integrity of the control signaling, but also ensures that the control state can be entered immediately after the resource authorization. For the third start-up mechanism: applicable to transmission control of complete beam reports, its prohibition timer start logic is similar to the first start-up mechanism, but the object of action is changed to the second information (including beam reports) on the second uplink resource. The prohibition timer is immediately started at the first symbol immediately after the last symbol of the second information transmission.

[0151] These three activation mechanisms together constitute a multi-level timing control system: all inhibit timer activation mechanisms use symbol-level precise timing references. Through the coordination of the physical layer and the MAC layer, they ensure that the inhibit timer activation is strictly synchronized with the actual signaling transmission, ensuring beam management flexibility and providing overload protection for the control channel.

[0152] In one embodiment, Figure 4 As shown, the method further includes:

[0153] Step 401: Receive configuration information sent by a base station.

[0154] The configuration information includes at least one of a detection time window, an instance quantity threshold, a maximum sending times threshold, a counter, and a prohibition timer time length.

[0155] During implementation, the terminal establishes a beam monitoring and reporting control system by receiving configuration information sent by the base station. Among them, the detection time window in the configuration information is a key parameter used to limit the time range of signal quality assessment. Its core function is to provide a stable observation benchmark for the beam or channel measurement of the terminal (UE) to ensure that the beam status assessment has sufficient time continuity. The instance quantity threshold is the key judgment criterion for event triggering. It requires that the beam quality change of the same beam must meet the minimum continuous stability requirement. The maximum transmission number threshold is used to prevent channel resource overload; and the time length parameters of the counter and prohibition timer together form a dynamic signaling flow control mechanism. The counter mechanism is used to control the cumulative reporting frequency, and the prohibition timer is used to manage the minimum time interval between adjacent reports.

[0156] Optionally, these parameters included in the configuration information can be flexibly combined and configured through RRC signaling, so that the network can implement differentiated beam management strategies for different business scenarios. This is not limited to the embodiments of the present disclosure.

[0157] In this embodiment, by configuring the information of the beam reporting content and structuring the beam reporting content, flexible adjustment of the key information contained in the beam report can be achieved to adapt to the needs of different scenarios, so that network nodes can obtain a refined channel status portrait, and ultimately achieve precise and differentiated beam management.

[0158] In one embodiment, the triggering event includes at least one of a first triggering event, a second triggering event, and a third triggering event; and the triggering event is determined by:

[0159] First trigger event: the current beam quality is lower than the first threshold;

[0160] Second trigger event: the beam quality of at least one new beam reaches a second threshold, and the second threshold is higher than the current beam quality;

[0161] Third trigger event: the beam quality of at least one new beam reaches a third threshold, the third threshold is higher than the Qth best beam quality of the activated transmission configuration indication TCI state, and the parameter Q≥1.

[0162] In implementation, the first trigger event is determined when the measured quality of the current serving beam (typically based on RSRP or SINR) is continuously below a preconfigured first threshold (denoted by Threshold 1). Specifically, the first trigger event is detected through periodic beam measurements and is triggered when all of the following conditions are met:

[0163] If the L1-RSRP measurement value of the current beam is lower than Threshold 1 for N consecutive times (where N ≥ 1 and N can be pre-configured by the network node) within the detection time window length T_measure, a first trigger event instance is recorded; and when the number of first trigger event instances reaches the maximum number of first trigger event instances, it is determined that a first trigger event has occurred.

[0164] The second trigger event is determined by checking that, among all the candidate beams measured, at least one beam has a measurement quality that satisfies both of the following conditions:

[0165] 1. The beam quality of at least one new beam (for example, the L1-RSRP of the beam) is higher than a preconfigured second threshold Threshold2;

[0166] 2. The beam quality of the new beam (such as RSRP+OffsetA) is higher than the beam quality of the current beam (that is, it can be reflected by the second threshold being higher than the current beam quality).

[0167] Optionally, the second trigger event is usually used for intra-cell beam optimization, which requires eliminating interference beams confused by PCI (Physical Cell Identity) and ensuring beam quality stability through the Time-to-Trigger mechanism.

[0168] The method for determining the third trigger event is a further enhancement of the method for determining the second trigger event. The method for determining the third trigger event is: the beam quality of at least one new beam satisfies the following conditions:

[0169] 1. The beam quality of the new beam is higher than the pre-configured third threshold Threshold3;

[0170] 2. The new beam quality is better than the Qth best preset beam quality (i.e., this can be reflected by the third threshold being higher than the Qth best beam quality in the activated transmission configuration indicator (TCI) state). The Qth best beam quality refers to the beam quality of the Qth best beam among all beams sorted by beam quality. This parameter Q is pre-configured by the network node and is greater than or equal to 1.

[0171] In this embodiment, three methods for determining preconfigured trigger events are given. The occurrence of an event is determined by this determination method, and beam reporting triggered by the event is performed, thereby improving the timeliness of beam reporting, ensuring that network nodes obtain key beam information in a timely manner, quickly adjusting beam management strategies, and improving communication reliability.

[0172] In an optional embodiment, the measurement signal of the current beam quality includes at least one of the following:

[0173] If the RS of the new beam is a CSI-RS configured in a CSI-RS resource set with duplication, the measurement signal of the current beam quality is the reference signal of the TCI state specified by CSI-ReportConfig (in the same CC as CSI-ReportConfig, or in a CC indicated by RRC parameters);

[0174] Otherwise, the measurement signal of the current beam quality is the SS / PBCH block that is quasi-co-located with the reference signal of the specified TCI state (in the same CC as the CSI-ReportConfig, or in the CC indicated by the RRC parameters).

[0175] In an optional embodiment, the measurement signal of the new beam quality includes at least one of the following:

[0176] - RS signals included in the new beam resource set configured by RRC parameters;

[0177] - A repeated CSI-RS resource set is configured.

[0178] In an optional embodiment, the beam reporting content and the beam quality metric include at least one of the following:

[0179] Layer 1 reference signal received power L1-RSRP;

[0180] Layer 1 signal-to-noise-and-interference ratio L1-SINR.

[0181] The L1-RSRP reporting format contains at least one or more of the following: CRI or SSBRI of beam #1, ... CRI or SSBRI of beam #N, L1-RSRP of beam #1, differential L1-RSRP of beam #2, ..., differential L1-RSRP #1 of beam #N, and differential L1-RSRP of the current beam.

[0182] The differential L1-RSRP for beams #2 to #N and the current beam is calculated based on the difference between the measured L1-RSRP corresponding to the CRI / SSBRI for beams #2 to #N and the current beam and the measured L1-RSRP corresponding to the CRI / SSBRI for beam #1, that is, the difference between (the measured L1-RSRP corresponding to the CRI / SSBRI for beams #2 to #N and the current beam) and (the measured L1-RSRP corresponding to the CRI / SSBRI for beam #1).

[0183] In an optional embodiment, when N > 1, the measurement time window, and the instance number threshold are configured, when the beam is reported as CRI / SSBRI, for each reported CRI / SSBRI, an indication field is used to indicate whether the CRI / SSBRI meets the second trigger event. The indication field is determined by the device implementation and / or enabled by RRC signaling or RRC fields.

[0184] In implementation, when the network configures multi-beam reporting parameters (N>1) and sets a detection time window and instance number threshold, the terminal introduces an intelligent trigger event indication feature for CRI (CSI-RS Resource Indicator) and SSBRI (SS / PBCH Block Resource Indicator) beam reports. For each reported CRI / SSBRI beam index, the terminal uses a dedicated indication field (typically a 1-bit flag) to clearly indicate whether the beam meets the second trigger event criteria (e.g., beam quality consistently exceeding a specific threshold). The generation and use of this indication field allows the device to autonomously determine whether to include this indication information based on implementation requirements. Furthermore, the network can explicitly enable or disable this feature through RRC signaling or specific RRC fields, achieving standardized control. In implementation, the terminal continuously monitors the quality of each beam within the detection time window. If a CRI / SSBRI measurement result meets the instance number threshold within the window (e.g., repeatedly exceeding the quality threshold), the terminal sets the valid flag in the corresponding indication field.

[0185] In one of the embodiments, the beam report content of the beam report includes at least one of an optimal beam indication, beam quality, and associated parameter information.

[0186] Specifically, the network configuration supports various combinations of core elements, including optimal beam indication, beam quality metrics, and associated parameter information, for the composition of beam reports. The optimal beam indication identifies the recommended beam index, providing a clear target for network-side beam scheduling. Beam quality metrics objectively reflect channel conditions through standardized metrics (such as RSRP, RSRQ, or SINR). Associated parameter information can include auxiliary decision-making data such as the spatiotemporal relationship characteristics between beams (such as QCL type), the terminal's recommended beamforming configuration (QCL relationship), and the number of spatial multiplexing layers (in MIMO scenarios).

[0187] Based on the definition of the beam report content given in the previous embodiment, when the trigger event is the second trigger event, the beam report content is described from the perspective of the beam type included in the beam report. In one optional embodiment, the beam report content includes the beam qualities of N new beams, or the beam qualities of N new beams and the current beam, where parameter N ≥ 1 and parameter N is configured by the base station.

[0188] Specifically, when the trigger event is the second trigger event, the terminal can choose to report the quality information of N new beams, or report the beam quality of N new beams and the current beam, based on parameter N configured by the network (e.g., base station). The base station can dynamically control the value of parameter N through RRC signaling, flexibly adjusting the level of detail in the report based on factors such as current network load, service demand, or mobility characteristics. Optionally, in dense scenarios, more new beam information can be requested to improve scheduling accuracy, while in simple environments, the beam report content can be streamlined to reduce signaling overhead.

[0189] In this embodiment, all reported beam quality data is based on statistical results within the detection time window, ensuring the reliability and representativeness of the information. This hierarchical content design, combined with a configurable parameter system, achieves an optimal balance between reporting accuracy and signaling efficiency while ensuring that critical information is not lost, providing effective support for the implementation of differentiated beam management strategies.

[0190] In one embodiment, the configuration of the beam report content supports one of the following methods:

[0191] Mode 1: When RRC signaling or the RRC field is configured, the RRC signaling or the RRC field is used to enable the beam report of the current beam. The beam report content includes the N new beams and the beam quality of the current beam. Otherwise, the beam report content only includes the beam quality of the N new beams.

[0192] Method 2: When RRC signaling or RRC field is configured, RRC signaling or RRC field is used to disable the beam report of the current beam, and the beam report content only includes the beam quality of N new beams; otherwise, the beam report content includes the beam quality of N new beams and the current beam.

[0193] Method three: when RRC signaling or RRC field is configured, RRC signaling or RRC field is used to enable and / or disable the beam report of the current beam. When the RRC signaling or RRC field is the first value, the beam report content only includes the beam qualities of N new beams; when the RRC signaling or RRC field is the second value, the beam report content includes the beam qualities of N new beams and the current beam.

[0194] The composition structure of the beam report content achieves flexible and configurable fine-grained control through RRC signaling, which is specifically reflected in three configuration methods: Method 1 adopts the "enable priority" principle. When the network pre-configures specific RRC signaling or RRC fields, the beam report content includes N new beams and the beam quality of the current beam. Otherwise (that is, when the RRC signaling or RRC field for enabling beam reporting of the current beam is not configured), only the beam qualities of the N new beams are reported by default; the second method adopts the "disable priority" logic. When the network disables the beam reporting of the current beam through specific RRC signaling or RRC field, the beam report content only includes the beam qualities of the N new beams. Otherwise (that is, when the RRC signaling or RRC field for disabling beam reporting of the current beam is not configured), the new and old beam qualities are reported at the same time by default; the third method provides the most flexible switch control. The value of the RRC field (for example, the first value and the second value) directly corresponds to the two reporting modes. The network can dynamically switch according to real-time needs. When the RRC signaling or RRC field is the first value, the beam report content only includes the beam qualities of the N new beams. When the RRC signaling or RRC field is the second value, the beam report content includes the beam qualities of the N new beams and the current beam.

[0195] In this embodiment, beam report content is controlled through RRC signaling or RRC field bit mapping, meeting the varying information requirements in different scenarios while maintaining protocol uniformity. By synergizing physical layer and higher-layer signaling, on-demand optimization of signaling overhead is achieved while ensuring beam management accuracy.

[0196] In one embodiment, the detection time window supports at least one of the following configurations:

[0197] Method 1: The detection time window is the start time - end time;

[0198] The start time is (N)*T_PUCCH - T_proc - T_window and the end time is (N)*T_PUCCH - T_proc.

[0199] In practice, the start time of the detection time window is determined by three key parameters: Figure 6 As shown, ( Figure 6 Taking the event instance threshold = 3 and N = 1 as an example), (N)*T_PUCCH means that (N)*T_PUCCH is the time corresponding to the Nth PUCCH transmission opportunity after the start time, that is, Figure 6The higher arrow in the figure indicates the time. T_proc is the processing time, which is the fixed time overhead required by the terminal to process the measurement results. This is the time gap between the duration of the detection time window, T_window, and T_PUCCH. T_window is the duration of the detection time window itself. Thus, the start time of the detection time window is determined by deducting the processing time and the duration of the detection time window from (N)*T_PUCCH. The end time of the detection time window is set to (N)*T_PUCCH minus the processing time.

[0200] Among them, T_window is predefined by the terminal or configured by the network.

[0201] In method 2, the start time of the detection time window is T_Instance-T_window, and the end time is the target T_Instance end time.

[0202] Where T_Instance is the evaluation instance of the trigger event, and T_window is the length of the detection time window. T_window is predefined by the terminal or configured by the network.

[0203] In practice, the definition of the detection time window adopts a dynamic calculation method based on event triggering, where T_Instance is the evaluation occasion of the triggering event instance (i.e. Figure 5 The lower arrow in the figure indicates the evaluation instance for each triggering event instance. It represents the moment when the beam state meets a preset condition (e.g., quality falls below a threshold). The T_window parameter defines the duration of the detection time window. Thus, the start time of the detection time window can be configured to be offset by T_window from a certain T_Instance (the moment when the triggering event instance is determined). For example, if a certain T_Instance is the third T_Instance (when the event instance threshold is 3), the start time of the detection time window can be determined by subtracting the preconfigured detection time window duration T_window from (N) * T_Instance. The end time of the detection time window can be determined by the end time of a certain T_Instance (e.g., if a certain T_Instance is the third T_Instance).

[0204] Mode three: The detection time window is determined based on the length T_window of the detection time window configured by the network and / or the time slot offset and / or the measurement period.

[0205] In implementation, fine-grained spatiotemporal control of the beam measurement process is achieved through flexible network-side configuration of key parameters such as T_window (window duration), slot offset, and measurement period. The T_window parameter directly determines the window's time span, providing a stable observation duration benchmark for beam quality assessment. The slot offset precisely locates the window's starting position on the system timeline, ensuring strict synchronization of measurements with network scheduling. The measurement period parameter establishes a repetitive observation rhythm, enabling the terminal to update beam status information at regular intervals.

[0206] Mode 4: The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance is obtained.

[0207] In practice, the length of the detection window is ultimately constrained by a parameter T_window configured by the network or predefined by the terminal. This parameter defines the time range during which the terminal continuously observes the quality of the new beam (i.e., including the start and end times of the detection window). Furthermore, within the time range defined by T_window, the detection window timer supplements the configuration of the detection window.

[0208] Specifically, when the terminal first detects a new beam triggering event that meets the conditions, it immediately starts or restarts the timer in the detection time window and begins accumulating quality measurement data for the beam (new beam). The detection time window ends when the next new beam triggering event that meets the conditions is detected. The duration of this detection time window is limited to T_window and does not exceed the time range of T_window.

[0209] Mode 5: The length of the detection time window is T_window. After a new beam triggering event instance reaches an instance threshold, the timer of the detection time window is started or restarted.

[0210] In practice, the length of the detection window, T_window, is configured by the network or predefined by the terminal. The terminal uses T_window as the final constraint to limit the time range of the detection window. Furthermore, within the time range defined by T_window, the detection window timer is used to supplement the determination of the detection window.

[0211] Specifically, when the terminal detects a new beam triggering event instance, it will start the event instance counter to accumulate statistics. When the accumulated number of instances reaches the preset instance threshold, the terminal will start or restart the timer of the detection time window and accumulate beam quality measurement data. Figure 6 As shown, Figure 6The time (PUCCH transmission opportunity) corresponding to the transmission opportunity for the event-triggered beam reporting (i.e., PUCCH) is identified in the , and the second trigger event triggers the beam reporting at the time corresponding to the PUCCH transmission opportunity. At the same time, the terminal starts or restarts the timer of the detection time window, and uses the start time of the timer as the start time of the detection time window, and the time corresponding to the next PUCCH transmission opportunity as the end time of the detection time window. The duration of the detection time window is limited to T_window and does not exceed the time range of T_window. For example, if the T_window time ends before the time corresponding to the next PUCCH transmission opportunity is reached, the detection time window ends.

[0212] Mode six: the detection time window has a length of T_window, and the timer of the detection time window is started or restarted at the Nth PUCCH transmission opportunity after the new beam triggering event instance reaches the instance threshold.

[0213] Among them, T_window is predefined by the terminal or configured by the network.

[0214] In practice, the length of the detection window, T_window, can be predefined by the terminal or dynamically configured by the network. The terminal uses T_window as the final constraint to limit the detection window's duration. Furthermore, within the T_window-limited time range, the detection window's timer is used to supplement the configuration of the detection window's duration.

[0215] Specifically, when the terminal detects a new beam triggering event instance and the cumulative number reaches the instance threshold configured by the network, the terminal will not start the measurement window immediately, but will wait until the Nth PUCCH transmission opportunity to activate or reset the timer. Figure 7 As shown, in Figure 7 In the example, taking the instance threshold = 3 and N = 1 as an example, after triggering 3 event instances, it is determined to send a PUCCH (the highest arrow represents the sending of a PUCCH), and based on the sending of the PUCCH, the timer of the detection time window is started or restarted to count the detection time window. When the next PUCCH is sent, the detection time window ends. For another example, Figure 8 As shown, in Figure 8 Taking the instance threshold = 3, N = 2 as an example, after triggering 3 event instances, the time corresponding to the PUCCH transmission opportunity is determined ( Figure 8 Indicated by the small square on the time axis (horizontal axis), but since N=2, PUCCH is not sent at this time, and when the time corresponding to the second PUCCH transmission opportunity is reached (i.e. Figure 8When the terminal sends a PUCCH (indicated by the highest arrow corresponding to the first T_PUCCH from left to right), the terminal starts or restarts the detection time window timer to count the detection time window. The detection time window ends when the terminal sends the next PUCCH (N=2). During this process, the detection time window ends with the T_window end time as a constraint. Similarly, the duration of the detection time window is limited to T_window and does not exceed the time range of T_window.

[0216] In one of the embodiments, when RRC signaling or RRC field is configured, the RRC signaling or RRC field is used to indicate a beam reporting mode, wherein the beam reporting mode includes a first mode and a second mode.

[0217] Regarding the two modes of beam reporting, in one embodiment, as Figure 9 As shown, the specific processing process of sending the second information on the second uplink resource includes:

[0218] Step 901: When the beam reporting mode is the first mode, second information is sent on the second uplink resource.

[0219] The second information includes an event-driven beam report. The second uplink resource includes a physical uplink shared channel PUSCH indicated in downlink control information DCI.

[0220] In implementation, for the first beam reporting mode, the terminal completes event-driven beam reporting through a two-stage transmission mechanism. Specifically, the terminal transmits structured second information on a second uplink resource. This second uplink resource consists of a physical uplink shared channel (PUSCH) resource block explicitly indicated by the base station via downlink control information (DCI). Its resource allocation parameters include key information such as time-frequency location and modulation and coding scheme (MCS).

[0221] The second information, a complete beam report, may include key parameters such as the optimal beam index, RSRP / RSRQ / SINR measurements for multiple candidate beams, and an indication of inter-beam QCL relationships. The entire transmission process strictly adheres to the timing requirements of DCI scheduling. Upon receiving the DCI containing the PUSCH resource grant, the terminal encapsulates and transmits the second information in the designated timeslot and resource block.

[0222] Step 902: When the beam reporting mode is the second mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report.

[0223] The second uplink resource includes a configured authorized physical uplink shared channel type 1 CG-PUSCH.

[0224] In implementation, for the second mode of beam reporting, the terminal uses a pre-configured resource mechanism to complete event-driven beam status reporting. In this second mode, the network pre-allocates a Type 1 Configuration Grant Physical Uplink Shared Channel (Type 1 CG-PUSCH) as a dedicated secondary uplink resource through RRC signaling. Upon detecting a beam event trigger that meets the conditions, the terminal can directly send structured secondary information on this pre-configured resource without waiting for dynamic scheduling grant.

[0225] The second information is a complete beam report, which includes the event type identifier (such as beam failure recovery request or high-quality beam discovery indication), the optimal candidate beam index, detailed measurement results of multiple beams (including layer 1 indicators such as RSRP, RSRQ and SINR), and related QCL relationship information. The configuration parameters of type 1 CG-PUSCH resources (such as period, time-frequency position, MCS, etc.) are statically set through high-level signaling.

[0226] In one embodiment, the second information of the second uplink resource is sent in at least one of the following ways:

[0227] (1) The second uplink resource has only a single event-triggered beam report;

[0228] (2) The second uplink resource includes beam reports triggered by multiple events associated with the first uplink resource.

[0229] For method (1): an additional indication field of "CSI report configuration" is provided in the report format of the beam report. The payload size of the beam report triggered by a single event can be determined according to the maximum payload size in the associated CSI report configuration. If the payload size of the UEI beam report is less than the maximum report payload, zero padding can be added. The beam report triggered by the event reported by the second uplink resource shall meet the triggering conditions.

[0230] In an optional embodiment, if beam reporting procedures are initiated by multiple terminals, at least one of the following options is included:

[0231] 1. The terminal selects one of the configurations;

[0232] 2. Report the UEI beam report with the highest priority;

[0233] 3. For UEI beam reports with the same priority, report the report triggered by the most recent measurement event;

[0234] 4. Submit the report triggered by the most recent measurement event.

[0235] In an optional embodiment, for two modes of sending the second information of the second uplink resource, associated information is provided below:

[0236] For the first mode, multiple CSI report configurations associated with the same first uplink resource should be associated with the same aperiodic CSI triggering state.

[0237] For the second mode, multiple CSI reporting configurations associated with the same first uplink resource should be associated with the same second uplink resource.

[0238] For method (2): An additional indication field for "CSI report configuration" is provided in the report format for each beam report. CSI report configurations associated with the same PUCCH resource are sorted in ascending order according to the corresponding CSI report configuration ID. The number of bits in the additional indication field is the same as the number of CSI report configurations associated with the same PUCCH resource. The beam report triggered by the event reported by the second uplink resource shall meet the triggering conditions.

[0239] In an optional embodiment, the payload size of each event-triggered beam report is determined according to the maximum payload size in the associated CSI reporting configuration. If the payload size of the UEI beam report is smaller than the maximum report payload, zero padding may be added.

[0240] In an optional embodiment, if the multiple beam reports exceed the maximum payload of the second information of the second uplink resource, at least one of the following options is included:

[0241] 1. The UE device selects to discard one or more of the configurations until the reported content is within the maximum payload range of the second information;

[0242] 2. Report beam reports with higher priority within the payload and discard wavenumber reports with lower priority until the reported content is within the maximum payload range of the second message;

[0243] 3. For UEI beam reports with the same priority, discard them in order from farthest to closest according to the time when the measurement event triggered the report, until the report content is within the maximum payload range of the second information;

[0244] 4. Discard the reports in order from the earliest to the latest according to the time when the measurement event triggered the report, until the reported content is within the maximum payload range of the second information.

[0245] In one of the embodiments, to address the problem that the first uplink resource may overlap with resources such as PUCCH and PUSCH during transmission, a resource overlap resolution mechanism is proposed in the disclosed embodiment. Different resource overlap mechanisms are given for different types of resource overlap (PUCCH, PUSCH) and different resource overlap situations. Several types of resource overlap mechanisms are introduced in detail below.

[0246] (1) If the first uplink resource overlaps, and the overlapping resource is PUCCH, the overlapping resource resolution mechanism includes at least one of the following:

[0247] When a first uplink resource carrying first information collides / overlaps with a PUCCH carrying first target information, sorting is performed based on a first priority rule, and the information with the highest priority is sent based on the sorted priority; wherein the first target information includes a normal scheduling request normal SR and / or a normal link recovery request LRR; the first priority rule is: PUCCH carrying LRR>first uplink resource>PUCCH carrying normal SR; or,

[0248] When the first uplink resource carrying the first information collides / overlaps with the PUCCH carrying the second target information, they are sorted based on the second priority rule, and the information with the highest priority is sent based on the sorted priority; wherein the second target information includes one or more of the hybrid automatic repeat request confirmation HARQ-ACK, CSI report, normal scheduling request normal SR, and normal link recovery request LRR; the second priority rule includes any one of the first sub-priority or the second sub-priority, the first sub-priority is PUCCH carrying LRR>PUCCH carrying HARQ-ACK>first uplink resource>PUCCH carrying normal SR>CSI; the second sub-priority is PUCCH carrying HARQ-ACK>PUCCH carrying LRR>first uplink resource>PUCCH carrying normal SR>CSI; or,

[0249] When the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI, or when the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI and the multiplexing time condition is met, sorting is performed based on the second priority rule, and the highest priority information is sent based on the sorted priority; otherwise, the PUCCH indicated by the DCI is sent and the first uplink resource is discarded.

[0250] Specifically, when a resource conflict occurs between a terminal's first uplink resource (PUCCH carrying the first information) and a PUCCH carrying the first target information (normal SR or LRR), the terminal uses a predefined first priority rule for arbitration. This first priority rule includes a three-level priority hierarchy: Link Recovery Request (LRR) is the highest priority signaling to ensure rapid recovery from emergency link failures; the first uplink resource carrying the first information is the second priority to maintain continuity of beam management; and Normal Scheduling Request (normal SR) is the lowest priority signaling, serving as the base level. When a resource collision occurs, the terminal immediately interrupts the preparation process for sending the low-priority signaling, prioritizing the complete transmission of the high-priority information.

[0251] When a terminal encounters a collision or overlap between its first uplink resource (a PUCCH carrying first information) and a PUCCH carrying second target information, the terminal defines a second priority rule for arbitration. For example, when a first uplink resource collides with a PUCCH carrying second target information, such as HARQ-ACK, CSI, normal SR, or LRR, the terminal prioritizes the conflicting information according to the network-configured second priority rule (which includes two optional sub-priority schemes), sending the highest-priority signaling first. The two sub-priority schemes differ primarily in how they prioritize HARQ-ACK and LRR. The first sub-priority scheme prioritizes the urgency of link recovery, while the second prioritizes the timeliness of HARQ feedback. In another conflict scenario, when the first uplink resource collides with a PUCCH dynamically scheduled by DCI, the terminal introduces a multiplexing time condition as an additional criterion: if the time condition is met, the priority arbitration mechanism is also activated; otherwise, the DCI-scheduled PUCCH is unconditionally prioritized and the first uplink resource is discarded. Optionally, resource overlap / resource collision in another conflict scenario can be further divided into two cases: repeated transmission of the first uplink resource and non-repeated transmission of the first uplink resource:

[0252] (a) When the first uplink resource carrying the first information is configured for repeated transmission, or the PUCCH resource indicated by the overlapping DCI is configured for repeated transmission, the repeatedly transmitted PUCCHs are sorted according to the second priority rule: HARQ-ACK>UEIBR>normal SR>CSI, and low-priority information is discarded on the overlapping resources.

[0253] (b) When the first uplink resource carrying the first information is non-repeatedly transmitted and overlaps with other PUCCH resources not indicated by DCI, or overlaps with other PUCCH resources indicated by DCI and meets the multiplexing time condition, the repeatedly transmitted PUCCHs are sorted according to the second priority rule: HARQ-ACK>UEIBR>normal SR>CSI, so as to multiplex high-priority PUCCHs and discard low-priority information.

[0254] (2) In one embodiment, when the resources of the first uplink resource overlap, and the overlapping resource is a PUSCH, a mechanism for resolving the overlapping resource includes at least any one of the following:

[0255] 1) When the first uplink resource carrying the first information collides / overlaps with the PUSCH, give priority to the first uplink resource and discard the PUSCH; or, encode the first information carried by the first uplink resource into the PUSCH; or, follow the discarding and / or multiplexing rules when the PUCCH carrying the repeated transmission of the SR collides / overlaps with the PUSCH; or,

[0256] 2) If PUSCH does not use the uplink shared channel UL-SCH for transmission, discard PUSCH; or,

[0257] 3) If the PUSCH is transmitted using the uplink shared channel UL-SCH, the PUSCH is sent and the first uplink resource is discarded; or the first information carried by the first uplink resource is encoded into the PUSCH;

[0258] 4) When the first uplink resource carrying the first information collides / overlaps with the PUSCH of the target transmission type, the first uplink resource is sent and the PUSCH is canceled; wherein the PUSCH of the target transmission type includes at least one of the following: PUSCH sent using repetition type A / B, PUSCH transmitted in a single time slot, PUSCH including multi-slot transport block TB processing; or,

[0259] 5) When the first uplink resource carrying the first information collides / overlaps with other PUSCH resources that are not indicated by the DCI and are not repeatedly transmitted, the first uplink resource is encoded into the PUSCH, or the first information on the first uplink resource is discarded and the content on the PUSCH is sent; or,

[0260] 6) When the first uplink resource carrying the first information collides / overlaps with the PUSCH resource indicated by other DCI, the first information on the first uplink resource is discarded and the content on the PUSCH is sent; or

[0261] 7) When the first uplink resource carrying the first information collides / overlaps with the PUSCH resource indicated by other DCI and satisfies the multiplexing time condition, the first uplink resource is encoded into the PUSCH.

[0262] In implementation, for scenarios where primary uplink resources (such as PUCCH) carrying primary information collide or overlap with PUSCH resources, the terminal has designed a resource overlap resolution mechanism to achieve differentiated service assurance. This resource overlap resolution mechanism establishes seven specific handling strategies based on PUSCH transmission characteristics, resource scheduling type, and multiplexing conditions. For PUSCH transmitted on the conventional uplink shared channel (UL-SCH), the terminal allows the primary information to be retained through information multiplexing when the multiplexing time condition is met. Otherwise, the PUSCH or the primary uplink resource is retained based on service priority. For PUSCH transmitted on non-UL-SCH or special transmission types (such as repetition type A / B and single-slot transmission), a mandatory priority rule is adopted, typically canceling the PUSCH to ensure critical control signaling. For PUSCH resources dynamically scheduled by DCI, the multiplexing time condition is further introduced as a judgment basis. Information multiplexing is performed when the multiplexing time condition is met, otherwise the scheduled service data is prioritized.

[0263] (3) In one embodiment, when the resources of the first uplink resources overlap, and the overlapping resources carry other first uplink resources, a mechanism for resolving the overlapping resources includes any one of the following:

[0264] ①, when the first uplink resource is carrier c1 of the target serving cell, and carrier c1 overlaps with multiple first uplink resources of the same CSI configuration triggered on the carrier set of the target serving cell, supporting sending the first information of the first uplink resource on carrier c1; or,

[0265] ②. When the first uplink resource overlaps with the first uplink resource of a different CSI configuration, the first information to be reported is determined according to the different CSI configurations, or the first information to be reported is selected based on the user.

[0266] Specifically, the terminal has designed a resource conflict resolution mechanism to address conflicts in primary uplink resources (such as PUCCH) between different carriers. When the primary uplink resource on carrier c1 of the target serving cell overlaps with multiple resources triggered by the same CSI configuration within the carrier set of that cell, the terminal is forced to transmit the primary information on carrier c1. This ensures the continuity of critical carrier control signaling and avoids information loss due to carrier selection. For resource conflicts caused by different CSI configurations, the terminal provides a more flexible handling strategy: it allows for automatic selection of reporting content based on CSI configuration priority (such as the priority difference between periodic CSI and aperiodic CSI), while also enabling the terminal to independently determine reporting information based on local policies (such as channel quality assessment). This allows for a deterministic carrier selection rule to maintain configuration consistency when the same CSI configuration conflicts. For conflicts between different configurations, a configurable strategy is used to balance standardization requirements and flexibility. The network can specify a specific conflict resolution mode through RRC signaling, ensuring reliable transmission of critical control signaling while optimizing resource utilization efficiency for multi-carrier terminals.

[0267] (4) In one embodiment, when the resources of the first uplink resource overlap, and the overlapping resources are uplink resources carrying other component carriers, the overlapping resource resolution mechanism includes any one of the following:

[0268] When the first uplink resource is carrier c1 of the target serving cell, and carrier c1 overlaps with sounding reference signals SRS of other component carriers on the carrier set of the target serving cell in the same symbol, first information on carrier c1 is sent.

[0269] In practice, when the first uplink resource on the main carrier c1 of the target service cell (such as the PUCCH carrying critical control signaling) conflicts with the sounding reference signal (SRS) of other component carriers at the same time-frequency symbol position, the terminal adopts a deterministic priority protection mechanism: unconditionally prioritize the transmission of the first information on carrier c1. In specific implementation, the terminal will detect symbol-level resource conflicts through the physical layer resource mapping module. When it is identified that the first information on the main carrier c1 overlaps with the SRS of other carriers, it will automatically suppress the SRS transmission preparation process to ensure the complete transmission of the control signaling on the c1 carrier. The network side can further refine the applicable conditions of this resource overlap resolution rule through RRC signaling (such as restricting SRS of a specific priority from being subject to this rule), maintaining the coordinated operation of multi-carrier terminals while ensuring core functions.

[0270] In one embodiment, Figure 10 Provided is a signaling interaction flow chart of the uplink transmission process of the terminal initiating beam reporting based on the dynamic scheduling of the second uplink resource (i.e., the first mode) by the gNB (base station). Figure 10 As shown, the method includes the following steps:

[0271] Step 1: The base station sends down the CSI configuration, measurement-related parameters, and pre-configured first uplink resources for the beam reporting process triggered by an event, and periodically sends CSI measurement information.

[0272] Step 2: The user configures the measurement information and related parameters for the beam reporting process triggered by an event: detection time window T1, number of instances M, first uplink resource transmission counter UEICOUNTER, and maximum number of transmissions UEIMAX, and the length of the prohibition timer.

[0273] Step 3: Within the configured detection time window T1, the user measures the beam quality of the new beam and determines the trigger event instances.

[0274] Step 4: If, within a configured detection time window T1, the number of trigger event instances of at least one new beam is greater than or equal to a configurable quantity M, then beam reporting triggered by the event occurs.

[0275] Step 5: The user configures the first uplink resource and the first information for beam reporting, and determines the condition for allowing transmission: UEICOUNTER < UEIMAX and the prohibition timer is not running. If transmission is allowed, perform a resource overlap detection and processing mechanism for the first information of the first uplink resource to eliminate the impact of resource overlap;

[0276] Step 6: The terminal sends the first information on the first uplink resource to request the uplink resource for beam reporting;

[0277] Step 7: After sending the first information, the terminal starts the first prohibition timer and updates the transmission counter UEICOUNT = UEICOUNT + 1.

[0278] Step 8: The terminal receives the downlink transmission from the base station and sends the second information on the second uplink resource indicated by the DCI. The second information contains the beam report triggered by the event.

[0279] Step 9: After sending the second information, the terminal starts the second prohibition timer.

[0280] Step 10: Repeat Steps 3 to 9 until the detection time window T1 arrives, and the beam reporting for this round is completed.

[0281] In one embodiment, Figure 11 A signaling interaction flowchart for an uplink transmission process of terminal-initiated beam reporting based on pre-configured resources is provided. As Figure 11 shown, the method includes the following steps.

[0282] Step 1: The base station sends the CSI configuration, measurement-related parameters, and pre-configured first uplink resources and second uplink resources of the beam reporting process triggered by the event, and periodically sends CSI measurement information.

[0283] Step 2: The terminal configures the measurement information and related parameters of the beam reporting process triggered by the event: detection time window T1, number of instances M, first resource sending counter UEICOUNTER and maximum number of sending times UEIMAX, and prohibition timer length.

[0284] Step 3: Within the detection time window T1, the terminal measures the beam quality of the new beam and determines the triggering event instance.

[0285] Step 4: If the number of triggering event instances for at least one new beam is greater than or equal to a configurable number M within a configurable detection time window T1, then trigger beam reporting based on the event.

[0286] Step 5: The terminal configures the first uplink resource and the first information of the beam report, and performs a determination of the conditions for allowing transmission and a resource overlap processing mechanism.

[0287] Step 6: The terminal sends the first information on the first uplink resource to notify the base station gNB that the beam report will be sent on the pre-configured uplink resource.

[0288] Step 7: After sending the first information, the terminal starts the first prohibition timer and updates the sending counter.

[0289] Step 8: The terminal sends second information on the pre-configured second uplink resource (i.e., the second uplink resource). The second information includes an event-triggered beam report.

[0290] Step 9: After sending the second information, the terminal starts a second prohibition timer.

[0291] Step 10: Repeat steps 3 to 9 until the detection time window T1 arrives, and the beam reporting for this round is completed.

[0292] It should be understood that although Figures 2 to 4 , Figures 9 to 11 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figures 2 to 4 , Figures 9 to 11At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The order of execution of these steps or stages is not necessarily one by one, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0293] In one embodiment, an event-triggered beam reporting device is provided, which is applied to a terminal and includes:

[0294] A determination module, configured to determine to initiate beam reporting if, within a detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to a threshold number of instances;

[0295] The transmission process of beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

[0296] In one of the embodiments, the first uplink resource includes PUCCH, and the first information includes at least 1 bit of information, and the first information is used to notify the base station that the beam report will be sent on the pre-configured second uplink resource, or to request the base station for the second uplink resource for sending the beam report.

[0297] In one embodiment, the apparatus further comprises:

[0298] The restriction processing module is used to limit the first information sent on the first uplink resource by setting a counter and / or a prohibition timer.

[0299] In one embodiment, the sending condition of the first information sent on the first uplink resource satisfies at least one of the following conditions:

[0300] When the prohibit timer runs, the terminal does not send the first information sent on the first uplink resource;

[0301] If first information of other first uplink resources or second information of second uplink resources has been sent within the detection time window related to the first uplink resource transmission opportunity, the terminal does not send the first information on the first uplink resource.

[0302] In one embodiment, the activation mechanism of the prohibit timer supports at least any one of the following:

[0303] After sending the first information on the first uplink resource, starting the prohibition timer; or,

[0304] When sending the first information on the first uplink resource and obtaining the second uplink resource authorization, starting the prohibition timer; or,

[0305] After the second information is sent on the second uplink resource, the prohibit timer is started.

[0306] In one embodiment, the apparatus further comprises:

[0307] A receiving module, configured to receive configuration information sent by the base station; the configuration information includes at least one of the following information:

[0308] Detection time window, instance number threshold, maximum send count threshold, counter, and prohibition timer length.

[0309] In one embodiment, the trigger event includes at least one of a first trigger event, a second trigger event, and a third trigger event; and the trigger event is determined by:

[0310] First trigger event: the current beam quality is lower than the first threshold;

[0311] Second trigger event: the beam quality of at least one new beam reaches a second threshold, where the second threshold is higher than the current beam quality;

[0312] The third trigger event: the beam quality of at least one new beam reaches a third threshold, and the third threshold is higher than the Qth best beam quality of the activated transmission configuration indication TCI state, and the parameter Q≥1.

[0313] In one embodiment, the current beam quality includes at least one of the following:

[0314] Layer 1 reference signal received power L1-RSRP or layer 1 signal to interference plus noise ratio L1-SINR of the reference signal in the specified TCI state; or

[0315] L1-RSRP or L1-SINR of the SS / Physical Broadcast Channel (PBCH) block quasi-co-located with the reference signal in the specified TCI state.

[0316] In one of the embodiments, the beam report content of the beam report includes at least one of an optimal beam indication, beam quality, and associated parameter information.

[0317] In one embodiment, when the trigger event is the second trigger event, the beam report content includes the beam qualities of N new beams, or the beam qualities of N new beams and the current beam, where parameter N≥1, and the parameter N is configured by the base station.

[0318] In one embodiment, the apparatus further includes a beam report content configuration module, wherein the beam report content configuration module is configured to perform any one of the following configurations:

[0319] When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to enable a beam report for the current beam, and the beam report content includes the N new beams and the beam quality of the current beam; otherwise, the beam report content only includes the beam quality of the N new beams;

[0320] or,

[0321] When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to disable beam reporting for the current beam, and the beam report content includes only the beam qualities of the N new beams; otherwise, the beam report content includes the beam qualities of the N new beams and the current beam;

[0322] or,

[0323] When RRC signaling or RRC field is configured, the RRC signaling or RRC field is used to enable and / or disable the beam report of the current beam. When the RRC signaling or RRC field is a first value, the beam report content only includes the beam quality of the N new beams; when the RRC signaling or RRC field is a second value, the beam report content includes the beam quality of the N new beams and the current beam.

[0324] In one embodiment, the apparatus further includes: a time window processing module, the time window processing module being configured to execute at least one of the following methods to configure the detection time window;

[0325] The detection time window is the start time minus the end time; wherein the start time is (N)*T_PUCCH -T_proc - T_window; the end time is (N)*T_PUCCH - T_proc; (N)*T_PUCCH is the time corresponding to the Nth PUCCH transmission opportunity after the start time, T_proc is the processing time, and T_window is the duration of the detection time window; or,

[0326] The start time of the detection time window is T_Instance-T_window, the end time of the detection time window is the end time of T_Instance, T_Instance is the evaluation occasion of the triggering event instance, and T_window is the length of the detection time window; or,

[0327] The detection time window is determined based on the length T_window of the detection time window and / or the time slot offset and / or the measurement period configured by the network; or,

[0328] The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance is obtained; or,

[0329] The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance reaches an instance threshold; or,

[0330] The detection time window has a length of T_window, and a timer of the detection time window is started or restarted at the Nth PUCCH transmission opportunity after a new beam triggering event instance reaches an instance threshold;

[0331] T_window is predefined by the terminal or configured by the NW.

[0332] In one embodiment, the apparatus further includes a sending module, configured to, when the beam reporting mode is the first mode, send second information on a second uplink resource, wherein the second information includes an event-driven beam report; the second uplink resource includes a physical uplink shared channel (PUSCH) indicated in downlink control information (DCI);

[0333] When the beam reporting mode is the second mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report, and the second uplink resource includes a configured authorized physical uplink shared channel type 1 CG-PUSCH.

[0334] In one embodiment, the device further includes: a first resource overlap resolution module, the first resource overlap resolution module being configured to sort the first uplink resource carrying the first information based on a first priority rule when the first uplink resource carrying the first information collides / overlaps with the PUCCH carrying the first target information, and to send the highest priority information based on the sorted priority; wherein the first target information includes a normal scheduling request normal SR and / or a normal link recovery request LRR; the first priority rule is: PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR; or,

[0335] When the first uplink resource carrying the first information collides / overlaps with the PUCCH carrying the second target information, sorting is performed based on the second priority rule, and the information with the highest priority is sent based on the sorted priority; wherein, the second target information includes one or more of hybrid automatic repeat request confirmation HARQ-ACK, CSI report, normal scheduling request normal SR, and normal link recovery request LRR; the second priority rule includes any one of the first sub-priority or the second sub-priority, and the first sub-priority is PUCCH carrying LRR>PUCCH carrying HARQ-ACK>the first uplink resource>PUCCH carrying normal SR>CSI; the second sub-priority is PUCCH carrying HARQ-ACK>PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR>CSI; or,

[0336] When the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI, or when the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI and meets the multiplexing time condition, sorting is performed based on the second priority rule, and the information with the highest priority is sent based on the sorted priority; otherwise, the PUCCH indicated by the DCI is sent and the first uplink resource is discarded.

[0337] In one embodiment, the device further includes: a second resource overlap resolution module, the second resource overlap resolution module being configured to, when a first uplink resource carrying first information collides / overlaps with a PUSCH, give priority to processing the first uplink resource and discard the PUSCH; or, encode the first information carried by the first uplink resource into the PUSCH; or, follow the discarding and / or multiplexing rules when a PUCCH carrying repeated transmissions of an SR collides / overlaps with the PUSCH; or,

[0338] If the PUSCH does not use the uplink shared channel UL-SCH for transmission, discard the PUSCH; or,

[0339] If the PUSCH is transmitted using an uplink shared channel UL-SCH, the PUSCH is sent and the first uplink resource is discarded; or, the first information carried by the first uplink resource is encoded into the PUSCH;

[0340] When the first uplink resource carrying the first information collides / overlaps with the PUSCH of the target transmission type, the first uplink resource is sent and the PUSCH is canceled; wherein the PUSCH of the target transmission type includes at least one of the following: a PUSCH sent using repetition type A / B, a PUSCH transmitted in a single time slot, and a PUSCH including multi-slot transport block TB processing; or,

[0341] When the first uplink resource carrying the first information collides / overlaps with other PUSCH resources that are not indicated by DCI and are not repeatedly transmitted, the first uplink resource is encoded into the PUSCH, or the first information on the first uplink resource is discarded and the content on the PUSCH is sent; or

[0342] When the first uplink resource carrying the first information collides / overlaps with a PUSCH resource indicated by other DCI, discard the first information on the first uplink resource and send the content on the PUSCH; or

[0343] When the first uplink resource carrying the first information collides / overlaps with PUSCH resources indicated by other DCIs and satisfies a multiplexing time condition, the first uplink resource is encoded into the PUSCH.

[0344] In one embodiment, the device further includes: a third resource overlap resolution module, the third resource overlap resolution module being configured to support sending the first information of the first uplink resource on the carrier c1 when the first uplink resource is the carrier c1 of the target serving cell and the carrier c1 overlaps with multiple first uplink resources of the same CSI configuration triggered on the carrier set of the target serving cell; or

[0345] When the first uplink resource overlaps with a first uplink resource of a different CSI configuration, the first information to be reported is determined according to the different CSI configurations, or the first information to be reported is selected based on a user.

[0346] In one embodiment, the device also includes: a fourth resource overlap resolution module, which is used to send the first information on the carrier c1 when the first uplink resource is the carrier c1 of the target service cell, and the carrier c1 overlaps with the sounding reference signal SRS of other component carriers on the carrier set of the target service cell in the same symbol.

[0347] For the specific definition of the event-triggered beam reporting device, please refer to the definition of the event-triggered beam reporting method above, which will not be repeated here. The various modules in the above-mentioned event-triggered beam reporting device can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0348] This embodiment provides a communication device. Figure 12 . Figure 12 It is a structural diagram of a terminal device provided by an embodiment of the present invention. Figure 12 The terminal device 1200 shown includes: at least one processor 1201, a memory 1202, at least one network interface 1204, and a user interface 1203. The various components in the terminal device 1200 are coupled together via a bus system 1205. It is understood that the bus system 1205 is used to achieve connection and communication between these components. In addition to including a data bus, the bus system 1205 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the bus system 1205 is not shown in FIG. Figure 12 Various buses are labeled as bus system 1205. In addition, the embodiment of the present invention further includes a transceiver 1206. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0349] The user interface 1203 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen).

[0350] It is understood that the memory 1202 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 RAM bus random access memory (DRRAM). The memory 1202 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0351] In some embodiments, the memory 1202 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 12021 and application programs 12022 .

[0352] The operating system 12021 includes various system programs, such as the framework layer, core library layer, and driver layer, for implementing various basic services and handling hardware-based tasks. Application programs 12022 include various application programs, such as a media player (MediaPlayer) and a browser (Browser), for implementing various application services. Programs implementing the methods of the embodiments of the present invention may be included in application programs 12022.

[0353] In this embodiment of the present invention, by calling a program or instruction stored in memory 1202, specifically, a program or instruction stored in application 12022, a transmitter is configured to perform event-driven beam reporting based on beam reporting configuration information. A receiver is configured to receive radio resource control signaling sent by a network node, the radio resource control signaling including beam reporting configuration information for event measurement.

[0354] Some or all of the methods disclosed in the above embodiments of the present invention may also be applied to processor 1201, or implemented by processor 1201, or implemented by processor 1201 in conjunction with other components (e.g., a transceiver). Processor 1201 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be performed by hardware integrated logic circuits or software instructions within processor 1201. Processor 1201 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present invention may be directly executed by a hardware decoding processor or by a combination of hardware and software modules within the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1202, and processor 1201 reads information in memory 1202 and, in conjunction with its hardware, completes the steps of the above method.

[0355] It is understood that the embodiments described in the embodiments of the present invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or a combination thereof.

[0356] For software implementation, the techniques described in the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present invention. The software code can be stored in a memory and executed by the processor 1201. The memory can be implemented in the processor 1201 or external to the processor 1201.

[0357] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0358] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0359] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0360] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the above-described method embodiments. Any reference to memory, storage, database, or other media used in the embodiments provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0361] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0362] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. An event-triggered beam reporting method, characterized in that: The method is applied to a terminal, and includes: If, within the detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to the instance quantity threshold, it is determined that the beam report is initiated; The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

2. The method according to claim 1, characterized in that The first uplink resource includes PUCCH, and the first information is used to notify the base station that the beam report will be sent on the pre-configured second uplink resource, or to request the base station for the second uplink resource for sending the beam report.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first information sent on the first uplink resource is restricted by setting a counter and / or a prohibition timer.

4. The method according to claim 1 or 2, characterized in that The sending condition of the first information sent on the first uplink resource satisfies at least one of the following conditions: When the prohibit timer runs, the terminal does not send the first information sent on the first uplink resource; If first information of other first uplink resources or second information of second uplink resources has been sent within the detection time window related to the first uplink resource transmission opportunity, the terminal does not send the first information on the first uplink resource.

5. The method according to claim 4, characterized in that The activation mechanism of the prohibit timer supports at least one of the following: After sending the first information on the first uplink resource, starting the prohibition timer; or, When sending the first information on the first uplink resource and obtaining the second uplink resource authorization, starting the prohibition timer; or, After the second information is sent on the second uplink resource, the prohibit timer is started.

6. The method according to claim 1, characterized in that The method further comprises: Receive configuration information sent by the base station, where the configuration information includes at least one of the following information: Detection time window, instance number threshold, maximum send count threshold, counter, and prohibition timer length.

7. The method according to claim 2, characterized in that The trigger event includes at least one of a first trigger event, a second trigger event, and a third trigger event; the trigger event is determined by: First trigger event: the current beam quality is lower than the first threshold; Second trigger event: the beam quality of at least one new beam reaches a second threshold, where the second threshold is higher than the current beam quality; A third triggering event: the beam quality of at least one new beam reaches a third threshold, where the third threshold is higher than the Qth best beam quality of the activated transmission configuration indication TCI state.

8. The method according to claim 7, characterized in that The current beam quality includes at least one of the following: L1-RSRP or L1-SINR of the reference signal in the specified TCI state; or, L1-RSRP or L1-SINR of the SS / PBCH block quasi-co-located with the reference signal in the specified TCI state.

9. The method according to claim 7, characterized in that The beam report content of the beam report includes at least one of an optimal beam indication, beam quality, and associated parameter information.

10. The method according to claim 9, characterized in that When the trigger event is the second trigger event, the beam report content includes the beam qualities of N new beams, or the beam qualities of N new beams and the current beam.

11. The method according to claim 10, characterized in that The configuration of the beam report content supports one of the following methods: When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to enable a beam report for the current beam, and the beam report content includes the N new beams and the beam quality of the current beam; otherwise, the beam report content only includes the beam quality of the N new beams; or, When RRC signaling or an RRC field is configured, the RRC signaling or RRC field is used to disable beam reporting for the current beam, and the beam report content includes only the beam qualities of the N new beams; otherwise, the beam report content includes the beam qualities of the N new beams and the current beam; or, When RRC signaling or RRC field is configured, the RRC signaling or RRC field is used to enable and / or disable the beam report of the current beam. When the RRC signaling or RRC field is a first value, the beam report content only includes the beam quality of the N new beams; when the RRC signaling or RRC field is a second value, the beam report content includes the beam quality of the N new beams and the current beam.

12. The method according to claim 1, characterized in that The detection time window supports at least one of the following configuration modes: The detection time window is the start time minus the end time; wherein the start time is (N)*T_PUCCH - T_proc - T_window; the end time is (N)*T_PUCCH - T_proc; (N)*T_PUCCH is the time corresponding to the Nth PUCCH transmission opportunity after the start time, T_proc is the processing time, and T_window is the duration of the detection time window; or, The start time of the detection time window is T_Instance-T_window, the end time of the detection time window is the end time of T_Instance, T_Instance is the evaluation occasion of the triggering event instance, and T_window is the length of the detection time window; or, The detection time window is determined based on the length T_window of the detection time window and / or the time slot offset and / or the measurement period configured by the network; or, The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance is obtained; or, The length of the detection time window is T_window, and the timer of the detection time window is started or restarted after a new beam triggering event instance reaches an instance threshold; or, The detection time window has a length of T_window, and a timer of the detection time window is started or restarted at the Nth PUCCH transmission opportunity after a new beam triggering event instance reaches an instance threshold; T_window is predefined by the terminal or configured by the NW.

13. The method according to claim 11, characterized in that When configuring the RRC signaling or field, the RRC signaling or field is used to indicate a beam reporting mode, and the beam reporting mode includes a first mode and a second mode.

14. The method according to claim 1 or claim 13, characterized in that The sending the second information on the second uplink resource includes: When the beam reporting mode is the first mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report; the second uplink resource includes a physical uplink shared channel PUSCH indicated in downlink control information DCI; When the beam reporting mode is the second mode, second information is sent on a second uplink resource, where the second information includes an event-driven beam report, and the second uplink resource includes a configured authorized physical uplink shared channel type 1 CG-PUSCH.

15. The method according to claim 1, wherein If the first uplink resources overlap, and the overlapping resources are PUCCHs, the overlapping resource resolution mechanism includes at least one of the following: When a first uplink resource carrying first information collides / overlaps with a PUCCH carrying first target information, sorting is performed based on a first priority rule, and the information with the highest priority is sent based on the sorted priority; wherein the first target information includes a normal scheduling request normal SR and / or a normal link recovery request LRR; the first priority rule is: PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR; or, When the first uplink resource carrying the first information collides / overlaps with the PUCCH carrying the second target information, sorting is performed based on the second priority rule, and the information with the highest priority is sent based on the sorted priority; wherein, the second target information includes one or more of hybrid automatic repeat request confirmation HARQ-ACK, CSI report, normal scheduling request normal SR, and normal link recovery request LRR; the second priority rule includes any one of the first sub-priority or the second sub-priority, and the first sub-priority is PUCCH carrying LRR>PUCCH carrying HARQ-ACK>the first uplink resource>PUCCH carrying normal SR>CSI; the second sub-priority is PUCCH carrying HARQ-ACK>PUCCH carrying LRR>the first uplink resource>PUCCH carrying normal SR>CSI; or, When the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI, or when the first uplink resource carrying the first information collides / overlaps with the PUCCH indicated by the DCI and meets the multiplexing time condition, sorting is performed based on the second priority rule, and the highest priority information is sent based on the sorted priority; otherwise, the PUCCH indicated by the DCI is sent and the first uplink resource is discarded.

16. The method according to claim 1, wherein When the first uplink resources overlap, and the overlapping resources are PUSCHs, the overlapping resource resolution mechanism includes at least one of the following: When a first uplink resource carrying first information collides with / overlaps a PUSCH, the first uplink resource is preferentially processed and the PUSCH is discarded; or the first information carried by the first uplink resource is encoded into the PUSCH; or the discarding and / or multiplexing rules when a PUCCH carrying repeated transmissions of an SR collides with / overlaps a PUSCH are followed; or, If the PUSCH does not use the uplink shared channel UL-SCH for transmission, discard the PUSCH; or, If the PUSCH is transmitted using an uplink shared channel UL-SCH, the PUSCH is sent and the first uplink resource is discarded; or, the first information carried by the first uplink resource is encoded into the PUSCH; When the first uplink resource carrying the first information collides / overlaps with the PUSCH of the target transmission type, the first uplink resource is sent and the PUSCH is canceled; wherein the PUSCH of the target transmission type includes at least one of the following: a PUSCH sent using repetition type A / B, a PUSCH transmitted in a single time slot, and a PUSCH including multi-slot transport block TB processing; or, When the first uplink resource carrying the first information collides / overlaps with other PUSCH resources that are not indicated by DCI and are not repeatedly transmitted, the first uplink resource is encoded into the PUSCH, or the first information on the first uplink resource is discarded and the content on the PUSCH is sent; or When the first uplink resource carrying the first information collides / overlaps with a PUSCH resource indicated by other DCI, discard the first information on the first uplink resource and send the content on the PUSCH; or When the first uplink resource carrying the first information collides / overlaps with PUSCH resources indicated by other DCIs and satisfies a multiplexing time condition, the first uplink resource is encoded into the PUSCH.

17. The method according to claim 1, wherein When the first uplink resources overlap, and the overlapping resources carry other first uplink resources, the overlapping resource resolution mechanism includes any one of the following: When the first uplink resource is carrier c1 of the target serving cell, and the carrier c1 overlaps with multiple first uplink resources of the same CSI configuration triggered on the carrier set of the target serving cell, supporting sending first information of the first uplink resource on the carrier c1; or, When the first uplink resource overlaps with a first uplink resource of a different CSI configuration, the first information to be reported is determined according to the different CSI configurations, or the first information to be reported is selected based on a user.

18. The method according to claim 1, wherein When the first uplink resources overlap, and the overlapping resources are uplink resources carrying other component carriers, the overlapping resource resolution mechanism includes any one of the following: When the first uplink resource is carrier c1 of the target serving cell, and the carrier c1 overlaps with the sounding reference signals SRS of other component carriers on the carrier set of the target serving cell in the same symbol, the first information on the carrier c1 is sent.

19. An event-triggered beam reporting device, characterized in that: The device is applied to a terminal, and includes: A determination module, configured to determine to initiate beam reporting if, within a detection time window, the number of instances of triggering events for at least the same new beam is greater than or equal to a threshold number of instances; The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

20. A communication device, characterized in that: include: transmitters, receivers, and processors; The processor is configured to determine to initiate beam reporting if the number of instances of triggering events of at least one new beam is greater than or equal to an instance number threshold within a detection time window; The transmission process of the beam reporting is that the terminal sends the first information on the first uplink resource and sends the second information on the second uplink resource.

21. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 18 are implemented.

22. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 18 are implemented.

Images