Event-triggered reporting

Abstract

Example embodiments relate to event triggered reporting. For example, a method can include obtaining a first priority level associated with a first event triggered channel state information, CSI, report for transmission to a network node; and determining, based at least in part on the first priority level, whether to transmit the first event triggered CSI report, or a message associated with the first event triggered CSI report, to the network node at a time occasion.

Description

Cross-references to related applications

[0001] This application claims the benefit of FI application No. 20245405, filed on April 4, 2024, which is incorporated herein by reference in its entirety. Technical Field

[0002] The example implementation involves event-triggered reporting. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) communication systems. Regarding 5G NR communication systems and future communication systems, throughput and network capacity can be increased by using massive MIMO technology with beamforming, whereby network entities can establish relatively narrow beams directed to individual user terminals and communicate through them.

[0004] The process of determining which beam or beams to use is often referred to as beam management and may involve reporting beam measurements and / or indicating which beam or beams to switch to. Summary of the Invention

[0005] The scope of protection sought by the various embodiments of the present invention is defined by the independent claims. Embodiments and features (if any) described in this specification that are not within the scope of the independent claims should be interpreted as examples that help to understand the various embodiments of the invention.

[0006] A first aspect provides an apparatus comprising: components for obtaining a first priority level associated with a channel state information (CSI) report for transmission to a network node triggered by a first event; and components for determining, at least in part based on the first priority level, whether to transmit the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time.

[0007] In some example embodiments, the message associated with the first event-triggered CSI report may include at least one of the following: a request for one or more uplink resources for subsequently sending the first event-triggered CSI report; or an indication that the first event-triggered CSI report will be reported at a subsequent time.

[0008] In some example embodiments, the apparatus may further include: a component for obtaining a second priority level associated with a second event-triggered CSI report to be sent to a network node at that time, wherein the component for determining is configured to: determine, at least in part, based on a first priority level and a second priority level, a message to be sent to the network at that time, either a first event-triggered CSI report or a second event-triggered CSI report, or associated with a first event-triggered CSI report or a second event-triggered CSI report.

[0009] In some example embodiments, the component for determining may be configured to: also determine, based on the following, to send at least one of a first event-triggered CSI report or a second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report: determine that only one event-triggered CSI report can be sent at that time, or only one message associated with the event-triggered CSI report can be sent.

[0010] In some example embodiments, the component for determination may be configured to: also determine, based on the following, to send at least one of the first event-triggered CSI report or the second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report: identify that the event that triggered the second event-triggered CSI report occurred within a time period N prior to that time opportunity.

[0011] In some example embodiments, the time period N can be received from a network node. In some example embodiments, the time period N can be hardcoded in the device.

[0012] In some example embodiments, where the first priority level is higher than the second priority level, the component for determining can be configured to determine: at that time point, to send a CSI report triggered by the first event, or a message associated with the CSI report triggered by the first event, to the network node.

[0013] In some example embodiments, when the second priority level is higher than the first priority level, the component for determining can be configured to determine: at that time, to send a CSI report triggered by the second event, or a message associated with a CSI report triggered by the first event, to the network node.

[0014] In some example embodiments, when the first priority level and the second priority level are the same, the component used for determination can be configured to determine: based on one or more other parameters, at that time point, to send to the network node one of a first event-triggered CSI report and a second event-triggered CSI report, or a message associated with either the first event-triggered CSI report or the second event-triggered CSI report. The one or more other parameters may include at least one of the following: the temporal order of the first and second events associated with the first and second event-triggered CSI reports, respectively; the corresponding payload size associated with the respective first and second event-triggered CSI reports; the corresponding serving cell identifier associated with the first and second events; or parameters configured by the network.

[0015] In some example embodiments, the apparatus may further include: components for receiving a report configuration associated with a CSI report triggered by at least a first event, wherein at least a first priority level is a value indicated in a predetermined field of the report configuration. In some example embodiments, the report configuration may indicate an event that will trigger the generation of a CSI report triggered by at least the first event. In some example embodiments, at least the first priority level may be indicated by a numerical value. In some example embodiments, a lower numerical value may indicate a higher priority level. In some example embodiments, a higher numerical value may indicate a higher priority level.

[0016] In some example embodiments, the device may also include components of at least a first priority level for receiving updates from a network node or another network node.

[0017] In some example embodiments, at least a CSI report triggered by a first event may be associated with a beam reporting event. In some example embodiments, at least a CSI report triggered by a first event may be associated with at least one of the following: an event where the quality of the current beam is worse than a certain threshold; an event where the quality of at least one new beam becomes a threshold better than the quality of the current beam; an event where the quality of the new beam is better than a certain threshold; or an event where the quality of the current beam is worse than a first threshold and the quality of at least one new beam is better than a second threshold.

[0018] In some example embodiments, the device may include a user terminal.

[0019] The second aspect provides a method comprising: obtaining a first priority level associated with a channel state information (CSI) report for transmission to a network node that is triggered by a first event; and determining, at least in part based on the first priority level, whether to transmit the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time.

[0020] In some example embodiments, the message associated with the first event-triggered CSI report may include at least one of the following: a request for one or more uplink resources for subsequently sending the first event-triggered CSI report; or an indication that the first event-triggered CSI report will be reported at a subsequent time.

[0021] In some example embodiments, the method may further include: obtaining a second priority level associated with a second event-triggered CSI report to be sent to a network node at that time, wherein determining includes, at least in part, based on the first priority level and the second priority level, determining to send at that time at at least one of the first event-triggered CSI report or the second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report, to the network.

[0022] In some example embodiments, the determination to send at least one of a first event-triggered CSI report or a second event-triggered CSI report, or a message associated with a first event-triggered CSI report or a second event-triggered CSI report, may also be based on: determining that only one event-triggered CSI report can be sent at that time, or only one message associated with an event-triggered CSI report can be sent.

[0023] In some example embodiments, the determination may also be based on the following: identifying that the event that triggered the second event-triggered CSI report occurred within a time period N prior to that time event.

[0024] In some example embodiments, the time period N can be received from a network node. In some example embodiments, the time period N can be hardcoded into the apparatus used to perform the method.

[0025] In some example embodiments, when the first priority level is higher than the second priority level, it can be determined that: at that time, a CSI report triggered by the first event, or a message associated with the CSI report triggered by the first event, is sent to the network node.

[0026] In some example embodiments, when the second priority level is higher than the first priority level, it can be determined that: at that time, a CSI report triggered by the second event, or a message associated with a CSI report triggered by the first event, is sent to the network node.

[0027] In some example embodiments, when the first priority level and the second priority level are the same, it can be determined that, based on one or more other parameters, at that time, one of a first event-triggered CSI report and a second event-triggered CSI report, or a message associated with either the first event-triggered CSI report or the second event-triggered CSI report, is sent to the network node. One or more other parameters may include at least one of the following: the temporal order of the first and second events associated with the first and second event-triggered CSI reports, respectively; the corresponding payload size associated with the respective first and second event-triggered CSI reports; the corresponding serving cell identifier associated with the first and second events; or network configuration parameters.

[0028] In some example embodiments, the method may further include: receiving a report configuration associated with a CSI report triggered by at least a first event, wherein at least a first priority level is a value indicated in a predetermined field of the report configuration. In some example embodiments, the report configuration may indicate an event that will trigger the generation of a CSI report triggered by at least the first event. In some example embodiments, at least the first priority level may be indicated by a numerical value. In some example embodiments, a lower numerical value may indicate a higher priority level. In some example embodiments, a higher numerical value may indicate a higher priority level.

[0029] In some example embodiments, the method may also include receiving an update of at least a first priority level from a network node or another network node.

[0030] In some example embodiments, at least a CSI report triggered by a first event may be associated with a beam reporting event. In some example embodiments, at least a CSI report triggered by a first event may be associated with at least one of the following: an event where the quality of the current beam is worse than a certain threshold; an event where the quality of at least one new beam becomes a threshold better than the quality of the current beam; an event where the quality of the new beam is better than a certain threshold; or an event where the quality of the current beam is worse than a first threshold and the quality of at least one new beam is better than a second threshold.

[0031] In some example embodiments, the method can be executed by a user terminal.

[0032] A third aspect provides a non-transitory computer-readable medium having computer-readable code stored thereon, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: obtaining a first priority level associated with a channel state information (CSI) report for transmission to a network node triggered by a first event; and determining, at least in part based on the first priority level, whether to transmit the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time.

[0033] In some example embodiments, the third aspect may include any other features mentioned in the second aspect.

[0034] A fourth aspect provides a computer program including a set of instructions that, when executed on an apparatus, is configured to cause the apparatus to perform a method comprising: obtaining a first priority level associated with a channel state information (CSI) report for transmission to a network node triggered by a first event; and determining, at least in part based on the first priority level, whether to transmit the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time.

[0035] In some example embodiments, the fourth aspect may include any other features mentioned in the second aspect.

[0036] A fifth aspect provides an apparatus having at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: obtain a first priority level associated with a channel state information (CSI) report for transmission to a network node triggered by a first event; and determine, at least in part based on the first priority level, whether to transmit the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time.

[0037] In some example embodiments, the fifth aspect may include any other features mentioned in the second aspect.

[0038] A sixth aspect provides an apparatus comprising: means for detecting a plurality of events for triggering a corresponding report to be transmitted to a network node; means for obtaining a corresponding priority level associated with the corresponding report; means for identifying a report from the corresponding report, or a message associated with the report from the corresponding report, for transmission at a first time point; and means for determining to send the identified report, or the message associated with the identified report, to the network node at the first time point, wherein the identification is at least partially based on the corresponding priority level.

[0039] In some example embodiments, the first timing opportunity may be selected from a set of available timing opportunities, and is the first timing opportunity that occurs after multiple events have been detected.

[0040] In some example embodiments, the component for determination is configured to: further determine whether to send the identified report, or a message associated with the identified report, is based on the following: the event that triggered the identified report occurred within a time period N prior to the first timing. In some example embodiments, the time period N can be received from the network node. In some example embodiments, the time period N can be hardcoded in the device.

[0041] In some example implementations, the identified reports are associated with the highest priority level.

[0042] In some example embodiments, the component for determining may also be configured to: determine, at a second time point following the first time point, send a different identified report, or a message associated with a different identified report, to the network node, wherein the different identified report is associated with the next available highest priority level.

[0043] In some example embodiments, identification may be based on one or more other parameters when the corresponding priority levels associated with two or more corresponding reports indicate the same priority level.

[0044] In some example embodiments, one or more other parameters may include at least one of the following: the temporal order in which the events that trigger two or more corresponding reports occur; the corresponding payload size associated with the two or more corresponding reports; the corresponding serving cell identifier associated with the events that trigger two or more corresponding reports; or network configuration parameters.

[0045] In some example embodiments, the message associated with the identified report may include at least one of the following: a request for uplink resources(s) for subsequent transmission of the identified report; or an indication that the identified report will be reported at a subsequent time.

[0046] In some example embodiments, the apparatus may further include a component for storing a corresponding report configuration associated with the corresponding report, wherein the corresponding priority level may include a corresponding value indicated in a predetermined field of the corresponding report configuration.

[0047] In some example implementations, the corresponding report configuration can indicate the corresponding event that triggers the corresponding report.

[0048] In some example embodiments, the corresponding priority level may include a corresponding numerical value. In some example embodiments, a lower numerical value may indicate a higher priority level, and vice versa.

[0049] In some example embodiments, the apparatus may further include a component for receiving at least one updated priority level from a network node or another network node.

[0050] In some example implementations, the corresponding report may be associated with the corresponding beam reporting event.

[0051] In some example embodiments, the reporting of a corresponding report may be associated with at least one of the following: an event where the quality of the current beam is worse than a certain quality threshold; an event where the quality of at least one new beam becomes a threshold better than the current beam; an event where the quality of a new beam is better than a certain quality threshold; or an event where the quality of the current beam is worse than a first quality threshold and the quality of at least one new beam is better than a second threshold.

[0052] In some example embodiments, the device may include a user terminal.

[0053] The seventh aspect provides a method comprising: detecting a plurality of events for triggering a corresponding report to be transmitted to a network node; obtaining a corresponding priority level associated with the corresponding report; a component for identifying a report from the corresponding report, or a message associated with a report from the corresponding report, for transmission at a first timing point; and determining to send the identified report, or a message associated with the identified report, to the network node at the first timing point, wherein the identification is at least partially based on the corresponding priority level.

[0054] In some example embodiments, the first timing opportunity may be selected from a set of available timing opportunities, and is the first timing opportunity that occurs after multiple events have been detected.

[0055] In some example embodiments, the determination to send the identified report, or a message associated with the identified report, may also be based on the following: the event that triggered the identified report occurred within a time period N prior to the first timing. In some example embodiments, the time period N may be received from the network node. In some example embodiments, the time period N may be hardcoded in the device.

[0056] In some example implementations, the identified reports are associated with the highest priority level.

[0057] In some example embodiments, it is determined that a different identified report, or a message associated with a different identified report, can be sent to a network node at a second time point after the first time point, wherein the different identified report is associated with the next available highest priority level.

[0058] In some example embodiments, identification may be based on one or more other parameters when the corresponding priority levels associated with two or more corresponding reports indicate the same priority level.

[0059] In some example embodiments, one or more other parameters may include at least one of the following: the temporal order in which the events that trigger two or more corresponding reports occur; the corresponding payload size associated with the two or more corresponding reports; the corresponding serving cell identifier associated with the events that trigger two or more corresponding reports; or network configuration parameters.

[0060] In some example embodiments, the message associated with the identified report may include at least one of the following: a request for uplink resources(s) for subsequent transmission of the identified report; or an indication that the identified report will be reported at a subsequent time.

[0061] In some example embodiments, the method may further include: storing a corresponding report configuration associated with the corresponding report, wherein the corresponding priority level may include a corresponding value indicated in a predetermined field of the corresponding report configuration.

[0062] In some example implementations, the corresponding report configuration can indicate the corresponding event that triggers the corresponding report.

[0063] In some example embodiments, the corresponding priority level may include a corresponding numerical value. In some example embodiments, a lower numerical value may indicate a higher priority level, and vice versa.

[0064] In some example embodiments, the method may further include receiving at least one updated priority level from a network node or another network node.

[0065] In some example embodiments, the corresponding report may be associated with a corresponding beam reporting event. In some example embodiments, the reporting of the corresponding report may be associated with at least one of the following: an event where the quality of the current beam is worse than a certain quality threshold; an event where the quality of at least one new beam becomes a threshold better than the current beam; an event where the quality of the new beam is better than a certain quality threshold; or an event where the quality of the current beam is worse than a first quality threshold and the quality of at least one new beam is better than a second threshold.

[0066] In some example embodiments, the method can be executed at a user terminal.

[0067] An eighth aspect provides a non-transitory computer-readable medium having computer-readable code stored thereon, the computer-readable code causing at least one processor, when executed, to perform a method comprising: detecting a plurality of events for triggering a corresponding report for transmission to a network node; obtaining a corresponding priority level associated with the corresponding report; identifying a report from the corresponding report, or a message associated with the report from the corresponding report, for transmission at a first time point; and determining to send the identified report, or the message associated with the identified report, to the network node at the first time point, wherein the identification is at least partially based on the corresponding priority level.

[0068] In some example embodiments, the eighth aspect may include any other features mentioned in the seventh aspect.

[0069] A ninth aspect provides a computer program including a set of instructions that, when executed on an apparatus, is configured to cause the apparatus to perform a method comprising: detecting a plurality of events for triggering a corresponding report for transmission to a network node; obtaining a corresponding priority level associated with the corresponding report; identifying a report from the corresponding report, or a message associated with the report from the corresponding report, for transmission at a first timing point; and determining to send the identified report, or the message associated with the identified report, to the network node at the first timing point, wherein the identification is at least partially based on the corresponding priority level.

[0070] In some example embodiments, the ninth aspect may include any other features mentioned in the seventh aspect.

[0071] A tenth aspect provides an apparatus having at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: detect a plurality of events for triggering a corresponding report to be transmitted to a network node; obtain a corresponding priority level associated with the corresponding report; identify a report from the corresponding report, or a message associated with the report from the corresponding report, for transmission at a first timing point; and determine to send the identified report, or the message associated with the identified report, to the network node at the first timing point, wherein the identification is at least partially based on the corresponding priority level.

[0072] In some example embodiments, the tenth aspect may include any other features mentioned in the seventh aspect.

[0073] The eleventh aspect provides an apparatus comprising: a component for configuring a user terminal with at least one priority level associated with a channel state information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with the at least one event-triggered CSI report configuration; and a component for receiving, at least in part, a first event-triggered CSI report or a message associated with the first event-triggered CSI report from or not from the user terminal at a given time, based on at least the at least one priority level.

[0074] In some example embodiments, the device may include a network node. For example, the network node may include an eNB, gNB, or TRP.

[0075] The twelfth aspect provides a method comprising: configuring a user terminal with at least one priority level associated with a channel state information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with a CSI report configuration triggered by at least one event; and receiving, at least in part, a first event-triggered CSI report or a message associated with a first event-triggered CSI report from or not from the user terminal at a time juncture based on at least the at least one priority level.

[0076] In some example embodiments, the method can be performed by a network node. For example, the network node may include an eNB, gNB, or TRP.

[0077] The thirteenth aspect provides a computer program including a set of instructions that, when executed on an apparatus, is configured to cause the apparatus to perform a method comprising: configuring a user terminal with at least one priority level associated with a channel state information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with the at least one event-triggered CSI report configuration; and receiving, at a time opportune moment, a first event-triggered CSI report or a message associated with the first event-triggered CSI report from or not from the user terminal, at least in part based on the at least one priority level.

[0078] The fourteenth aspect provides a non-transitory computer-readable medium storing computer-readable code thereon, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: configuring a user terminal with at least one priority level associated with a channel state information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with the at least one event-triggered CSI report configuration; and receiving, at least in part based on the at least one priority level, a first event-triggered CSI report, or a message associated with the first event-triggered CSI report, from or not from the user terminal at a given time.

[0079] The fifteenth aspect provides an apparatus having at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: configure a user terminal with at least one priority level associated with a channel state information (CSI) report configuration triggered by a corresponding at least one event, or with a message associated with the at least one event-triggered CSI report configuration; and to receive, at least in part based on the at least one priority level, a first event-triggered CSI report or a message associated with the first event-triggered CSI report from or not from the user terminal at a given time. Attached Figure Description

[0080] The invention will now be described by way of non-limiting example with reference to the accompanying drawings, in which:

[0081] Figure 1 A system according to an example embodiment is shown;

[0082] Figure 2 It is a flowchart indicating the operation according to the example embodiment;

[0083] Figure 3 This is a block diagram of a user terminal according to an example embodiment;

[0084] Figure 4 This is a schematic diagram of a timeline including one or more messages according to an example embodiment;

[0085] Figure 5 This is a flowchart indicating operations according to another example embodiment;

[0086] Figure 6 This is a flowchart indicating the operation according to another example embodiment;

[0087] Figure 7 This is a flowchart indicating the operation according to another example embodiment;

[0088] Figure 8 It can be a block diagram of a device configured according to an example embodiment; and

[0089] Figure 9 A non-transitory computer-readable medium is shown, which may include instructions that, when executed by a device, can perform operations according to an example embodiment. Detailed Implementation

[0090] The example implementation involves event-triggered reporting.

[0091] Example embodiments may specifically relate to event-triggered reporting, wherein one or more events at a user terminal trigger the transmission of one or more reports to a network node.

[0092] Example implementations may involve prioritizing event-triggered reports, wherein determining whether to send a particular event-triggered report or a message associated with a particular event-triggered report to a network node is based at least in part on the priority level associated with the event-triggered report.

[0093] In this context, the associated messages may include requests for uplink resources for sending a specific event-triggered report to a network node and / or instructions to the network node that the specific event-triggered report will be sent at a subsequent time.

[0094] The example embodiments will describe beam management, but are not limited to such examples.

[0095] Regarding 5G NR, Massive Multiple-Input Multiple-Output (MIMO) and beamforming technologies are used to provide enhanced throughput and capacity. MIMO employs multiple antenna arrays and spatial multiplexing to transmit independent and individually coded data signals or data streams. When used at network nodes that may be part of a Radio Access Network (RAN), this allows simultaneous communication with multiple user terminals on the same time and frequency resources. Beamforming is used in conjunction with MIMO to provide directional beams for sending data streams to the appropriate user terminals with good connectivity and reduced interference. Beam management can refer to the process by which a particular device determines which beam(s)(s) to use. Beam management can involve beamforming, beam selection, and beam switching, with the aim of maintaining good connectivity despite issues such as path loss and / or changes in user terminal location and / or orientation. Beam management is particularly, but not exclusively, applicable to 5G NR frequency range 2 (FR2) communication.

[0096] According to 3GPP Release 17, beam management can employ a so-called unified TCI state framework applicable to both downlink and uplink channels. This framework allows network nodes to indicate to user terminals the beam to which they wish to switch using a TCI state corresponding to a target beam. Channels may include at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Channel State Information Reference Signal (CSI-RS), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), or Sounding Reference Signal (SRS) channels. For example, a network node may indicate a target TCI state to a user terminal, which may include an indication of at least one Specific Source Reference Signal (RS) associated with the target beam, which the user terminal can use for subsequent transmission and / or reception assumptions. It is assumed that those skilled in the art are familiar with beam management in this context, including intra-cell and inter-cell beam management.

[0097] According to 3GPP Release 19, the goal is user terminal event-triggered measurement reporting. In other words, it is the user terminal, rather than the network node, that initiates beam switching, thereby reducing overhead and / or latency. Similarly, a unified TCI state framework can be used. In Release 19 (and possibly beyond), event-triggered measurement reporting (e.g., L1 measurements) is the target for MIMO enhancements and LTM (L2-triggered mobility, lower-layer-triggered mobility, and L1 / L2-triggered / centralized mobility).

[0098] For example, a user terminal can monitor and measure one or more RSs of the current beam and one or more other beams to determine whether one or more predetermined trigger conditions are met. If so, the user terminal can determine that a specific event has occurred, which can trigger the transmission of a report, such as a Channel State Information (CSI) report, to the network node.

[0099] The report may include one or more measurement results related to one or more measured beams and / or indications of one or more beams to be switched to.

[0100] The time and frequency resources used by user terminals to report measurement results and / or indications can be controlled by network nodes.

[0101] The report may include, for example, CSI information, including, for example, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), L1-RSRP CapabilityIndex, L1-SINR CapabilityIndex, and / or Time Domain Channel Attribute (TDCP).

[0102] Reports can be sent on one or more time and frequency resources. Time resources can be referred to as time slots. Time slots can be pre-configured and known to the user terminal, or they can be signaled from network nodes.

[0103] In some cases, a user terminal may request network nodes to allocate one or more uplink resources for sending reports.

[0104] A user terminal can send a message associated with a CSI report to a network node at a specific time to request uplink resources(s). The user terminal can then receive uplink resource allocations from the network node, which may include the reporting time. The user terminal can then send a report at the reporting time.

[0105] In some cases, a user terminal may need to instruct a network node to send a report, and thus may send a message providing such instruction to the network node at a specific time.

[0106] User terminals can be configured with multiple event-triggered reporting settings.

[0107] Multiple event-triggered reporting configurations can be associated with corresponding sets of configuration information that indicate how specific events can be triggered and how they can be reported to network nodes.

[0108] Specific reporting configurations can include, for example, definitions of how the user terminal should report measurement results, triggering criteria, one or more RSs used to perform the measurement, and / or reporting formats. Variations are possible.

[0109] A specific report configuration may include, for example, instructions for one or more resources on which: (i) a specific report is sent and / or (ii) an associated message is sent, such as a request for (one or more) uplink resources and / or an instruction to send a report, as described above.

[0110] Multiple report configurations can be received from network nodes and set at the user terminal, for example, stored at the user terminal.

[0111] A conflict may occur if two or more reports are configured to use the same time resources (time timing) or if the UE cannot send two or more reports that use the same time resources (but may use different frequency resources) to send a report (and other CSI reports, such as aperiodic / semi-persistent or periodic) or associated message triggered by the corresponding event. This is because the network node may not be able to identify which of the two or more events triggered the received report or associated message, and / or the UE may need to be able to determine which of these reports it should send.

[0112] If two or more reporting configurations specify different time resources for sending corresponding event-triggered reports or associated messages, the user terminal may not be able to process the transmission of two or more reports or associated messages simultaneously.

[0113] If two or more reporting configurations instruct the same time resources to be used to send corresponding event-triggered reports (and other CSI reports, such as non-periodic / semi-persistent or periodic) or associated messages, the user terminal may not be able to process the transmission of two or more reports or associated messages simultaneously.

[0114] In other example embodiments, the message associated with the event-triggered report may be a scheduling request (SR), a PRACH preamble, an SRS, a PUCCH (e.g., a UCI format carried in a PUCCH), or one of other UL signals indicating the event.

[0115] In other example embodiments, priority values ​​can be assigned to messages associated with event-triggered reports. As an example, a message associated with an event-triggered report (which may be associated with a priority value) can be used to determine which report to send. In some examples, the message associated with an event-triggered report may be a scheduling request (SR), which can be assigned a priority value. In some examples, the UE may be configured with one or more SRs (or messages associated with (multiple) event-triggered reports or reports), each SR associated with a specific priority value configured for a particular report.

[0116] Typically, if events are triggered close together in time, the number of independent events corresponding to two or more reporting configurations may exceed the user terminal's capacity and / or the amount of uplink resources available to send event-triggered reports or associated messages. For example, if network nodes allocate uplink resources based on the chronological order of events, there may not be enough time resources available to report later events that may be more important than earlier ones (e.g., time-critical).

[0117] The example implementations are intended to avoid and / or mitigate such problems, as will be explained below.

[0118] Figure 1 A network scenario 100 is shown, including network node 120 and user terminal 122.

[0119] Although one user terminal 122 is shown, in other example embodiments, multiple user terminals may be present, which may be configured to operate in the same or similar manner as explained below.

[0120] Network node 120 may include, but is not limited to, gNB (in the context of 5G / NR or future generation technologies), or Transmit and Receive Point (TRP) or relay node.

[0121] Network node 120 can be connected to one or more other network nodes (not shown) and / or one or more other network functions (not shown), which may include part of the core network or a similar network.

[0122] User terminal 122 may include user equipment (UE), such as, but not limited to, mobile phones, tablet computers, laptop computers, personal computers, Internet of Things (IoT) devices, digital assistants, or wearable terminals (such as smartwatches).

[0123] User terminal 122 can be configured to transmit data to network node 120 via air interface 124 using one or more uplink channels. Network node 120 can be configured to receive data transmitted by user terminal 122 via air interface 124 using one or more uplink channels. One or more uplink (time and frequency) resources can be used to transmit data, and time resources may be referred to as timing or time slots below.

[0124] Network node 120 can be configured to transmit data to user terminal 122 via air interface 124 using one or more downlink channels. User terminal 122 can be configured to receive data transmitted by network node 120 via air interface 124 using one or more downlink channels. Data can be transmitted using one or more downlink (time and frequency) resources, and the time resource may be referred to hereinafter as timing or time opportunity.

[0125] Figure 1 The diagram shows that network node 120 uses the current beam 126 for downlink communication; one or more other beams 127, 128 are available, and user terminal 122 can determine, based on one or more measurements performed by the user terminal, that it is now or at a later time preferred for downlink communication.

[0126] Air interface 124 may include a cellular air interface associated with both network node 120 and user terminal 122 being configured to support a radio access technology (RAT) (such as 5G / NR or future generation RAT).

[0127] User terminal 122 may store or otherwise access the collection of configuration data 130.

[0128] Configuration data 130 can be received at an earlier time from network node 120 or a different network node (not shown).

[0129] The configuration data 130 can be updated by network node 120 or different network nodes (not shown) at one or more subsequent times.

[0130] Configuration data 130 may include datasets representing multiple report configurations 130A–130D.

[0131] In other example embodiments, there may be fewer or more report configurations.

[0132] Report configurations 130A–130D can be associated with different corresponding events, referred to herein as E-1 to E-4, and therefore can be associated with reports that generate different event triggers.

[0133] Each of the report configurations 130A–130D may include information 132, such as one or more of the following: a definition of the triggering criteria associated with the corresponding events E-1 to E-4, how the corresponding event can be reported (sent) to network node 120 once triggered, one or more RSs for performing the measurements associated with the corresponding event, and a report format. For example, information 132 may indicate that a particular event should be reported to network node 120 once triggered, and / or a request for one or more uplink resources(s) for sending the report(s) should be sent to network node 120, and / or an instruction to send the report(s) should be sent to network node 120.

[0134] The report configurations 130A–130D can provide specific timing for sending the reports(s) or associated messages(s). The timing can be an absolute timing or a timing relative to the current timing (e.g., offset from the current timing).

[0135] This information can also indicate the priority level associated with the corresponding events E-1 through E-4, and thus indicate the reporting triggered by the event. The priority level can be indicated in specific field 134 of the reporting configuration 130A–130D.

[0136] Priority levels can be used according to example embodiments described later.

[0137] Events E-1 through E-4 may be related to beam reporting events, but are not limited to them.

[0138] For example, user terminal 122 may be able to measure RS corresponding to the current beam and one or more “other” or “new” beams.

[0139] Quality metrics such as L1 reference signal received power (L1-RSRP) can be measured. In other example embodiments, other quality metrics (such as L1-SINR) can be measured additionally or alternatively.

[0140] Events E-1 through E-4 may include, but are not limited to, the following examples, where the associated triggering criteria are indicated:

[0141] E-1: First event, in which the quality metric of the current beam is worse than a certain threshold;

[0142] E-2: The second event in which the quality metric of at least one new beam becomes a better threshold than that of the current beam;

[0143] E-3: The third event, in which the quality metric of the new beam is better than a certain threshold; and

[0144] E-4: The fourth event, in which the quality metric of the current beam is worse than the first threshold, and the quality metric of at least one new beam is better than the second threshold.

[0145] In other example embodiments, the number of events may be less than four or greater than four.

[0146] Figure 2 This is a flowchart illustrating operation 200 according to one or more example embodiments. Operation 200 can be performed in hardware, software, firmware, or a combination thereof. For example, operation 200 can be performed individually or collectively by components, wherein the components may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the operation. For example, operation 200 can be performed by a user terminal, such as by... Figure 1 The user terminal 122 executes.

[0147] The first operation 201 may include obtaining a first priority level associated with a report triggered by a first event and sent to a network node.

[0148] In this context, the term “obtain” can mean receiving, accessing, exporting, or something similar.

[0149] The second operation 202 may include determining, at least in part, based on a first priority level, whether to send a first event-triggered report or a message associated with a first event-triggered report to a network node at a specific time.

[0150] In some example implementations, event-triggered reports may include CSI reports.

[0151] In some example embodiments, the message associated with the first event-triggered report may include at least one of the following: a request for uplink resources for subsequently sending the first event-triggered CSI report; or an indication that the first event-triggered CSI report will be reported at a subsequent time.

[0152] In some example embodiments, another operation may include obtaining a second priority level associated with a report triggered by a second event that is sent to a network node at a specific time.

[0153] In such an example, the second operation 202 can be performed at least in part based on the first priority level and the second priority level.

[0154] In some example embodiments, the second operation 202 may also be performed based on identifying that the event that triggered the CSI report for the second event occurred within a predetermined time period N prior to a specific time timing.

[0155] For example, the predetermined time period N can be received from the network node (i.e. configured by the network node) or alternatively hardcoded into the user terminal 122.

[0156] For example, the predetermined time period N can be specified and applied by user terminal 122 based on technical specifications (such as 3GPP specifications).

[0157] In some example embodiments, where the first priority level is higher than the second priority level, the second operation 202 may include determining at a specific time juncture (i) to send a first event-triggered CSI report or a message associated with a first event-triggered CSI report to a network node, and (ii) not to send a second event-triggered CSI report or a message associated with a second event-triggered CSI report to a network node.

[0158] In some example embodiments, CSI can be reported in MAC CE. In some example embodiments, any of the examples herein can be applied to MAC CE CSI reporting, MAC CE reporting, PUSCH CSI reporting, or PUCCH CSI reporting, or associated with them.

[0159] In some example embodiments, when the second priority level is higher than the first priority level, the second operation 202 may include determining at a specific time point (i) to send a second event-triggered CSI report or a message associated with a first event-triggered CSI report to a network node, and (ii) not to send a first event-triggered CSI report or a message associated with a first event-triggered CSI report to a network node.

[0160] In some example embodiments, when the first priority level and the second priority level are the same, the second operation 202 may include determining, based on one or more other parameters, that: at a specific time point, to send to the network node one of the first event-triggered CSI report and the second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report.

[0161] For example, one or more other parameters may include at least one of the following: the chronological order of the first and second events associated with the CSI report triggered by the first event and the CSI report triggered by the second event, respectively; the corresponding payload size associated with the respective CSI report triggered by the first event and the CSI report triggered by the second event; the corresponding serving cell identifier associated with the first and second events; or network configuration parameters. In another example, one or more other parameters may include a coresetPoolIndex value used for scheduling uplink resources, where the lowest value indicates the highest priority, and vice versa.

[0162] In some example implementations, for event-based reporting, reports associated with lower serving cell identifiers are prioritized.

[0163] In some example implementations, for event-based reporting, a report associated with a lower serving cell identifier can be used to determine the priority value of an event-triggered report.

[0164] In some example implementations, the serving cell that is the SpCell (i.e., the primary cell) has higher priority than other serving cells.

[0165] In some example embodiments, the priority levels(s) mentioned in the first operation 201 may be indicated by numerical values ​​or alternative indications.

[0166] In some example implementations, lower values ​​(such as zero or one) may indicate a relatively higher priority level (i.e., more important), while higher values ​​(such as four) may indicate a relatively lower priority level (i.e., least important), and vice versa.

[0167] In some example embodiments, one or more priority levels can be configured and / or updated by network node 120 or another network node (not shown). For example, network node 120 or another network node can use a MAC control element (MACCE) to update one or more priority levels.

[0168] In some example embodiments, the priority level associated with a report triggered by a specific event can be indicated in the predefined information field 134 of the associated report configuration 130A–130D.

[0169] The report configuration 130A–130D can be stored at or accessed by user terminal 122.

[0170] In the absence of a priority level associated with a report triggered by a specific event, the lowest priority level can be assumed.

[0171] Alternatively, a report configuration identifier can be used to determine the priority level. A lower configuration identifier indicates a higher priority level.

[0172] Alternatively, one or more other parameters may determine the priority level, such as at least one of the following: the chronological order of the first and second events associated with the first event-triggered report and the second event-triggered report, respectively; the corresponding payload size associated with the corresponding first event-triggered report and the second event-triggered report (e.g., the largest payload may have the highest priority level, and vice versa); the corresponding serving cell identifier associated with the first and second events (e.g., the smallest cell identifier may have the highest priority level, and vice versa); or parameters of network configuration.

[0173] In some example embodiments, the above operation can be extended to include one or more additional priority levels (i.e., more than two priority levels) associated with reports triggered by one or more other events.

[0174] In some example embodiments, when the second operation 202 determines that a report or associated message triggered by a specific event will not be sent at a specific time, the report or associated message may remain pending; that is, it may be sent at the next available time, provided that there are no other reports or associated messages triggered by events with a higher priority level to be sent at the next available time.

[0175] Figure 3 yes Figure 1 A block diagram of user terminal 122, which includes certain modules that may be related to the example embodiment.

[0176] User terminal 122 may include the above configuration data 130.

[0177] User terminal 122 may also include a monitoring module 310 for accessing triggering criteria for at least events E-1 to E-4 from configuration data 130.

[0178] The monitoring module 310 can be configured in use to determine, based on the received measurement results, whether one or more specific events E-1 to E-4 have been triggered, and to perform further actions, such as those described above with reference to the second operation 202.

[0179] The monitoring module 310 can obtain one or a corresponding priority level from the information field 134 of the configuration data 130, such as in response to one or more specific events being triggered.

[0180] Alternatively, user terminal 122 may also include a priority sorting module 320 for accessing the corresponding priority level from the information field from configuration data 130; the priority level module 320 may indicate the priority level order to monitoring module 310, for example, in response to monitoring module indicating that one or more specific events have been triggered.

[0181] In the example shown, events E-1 through E-4 have corresponding priority levels “1”, “0”, “2”, and “3”, where lower values ​​indicate a relatively higher priority level (i.e., the most important), and higher values ​​indicate a relatively lower priority level (the least important). Therefore, event E-2 has the highest priority level, and event E-4 has the lowest priority level. In some examples, events can be configured with specific priority values. In further examples, reports triggered on a reporting configuration can use the priority values ​​of events to determine priority (between different events and / or other CSI reporting time types).

[0182] In one example, the CSI reporting time type could include non-periodic, semi-persistent, or periodic.

[0183] Figure 4 An example event timing diagram 400 is shown according to some example embodiments, wherein the first event and the second event occur at user terminal 122.

[0184] The event timing diagram 400 includes a timeline 410, which is divided into time units, which may include any form of time unit, such as a time slot, symbol, or millisecond.

[0185] In the example shown, the first event 401 is triggered, and then the second event 402 is triggered.

[0186] Suppose that both the first event 401 and the second event 402 require the network (e.g., network node 120) to allocate uplink resources for sending the corresponding first event report and second event report. Therefore, user terminal 122 can determine that it needs to request the allocation of uplink resources from network node 120 associated with sending the first event report and the second event report.

[0187] In this example, the next available time opportunity for sending an event report and / or for requesting the allocation of uplink resources is the first time opportunity 420.

[0188] According to some example embodiments, user terminal 122 may optionally determine that it can only send one of the first event report and the second event report and / or the message for requesting the allocation of uplink resources for the first event report and the second event report at the first time point 420.

[0189] According to some example embodiments, the user terminal 122 may also optionally determine that the second event 402 occurs or is triggered within a predetermined time period N 460 prior to the first time timing 420.

[0190] For example, a predetermined time period N 460 can be defined by symbols, time slots, or milliseconds.

[0191] User terminal 122 can respond by obtaining the corresponding priority level "1" or "0" associated with the first event 401 and the second event 402 (or the first event report and the second event report).

[0192] User terminal 122 may determine not to send a message requesting the allocation of uplink resources for the first event report at the first timing 420, because in this example, the corresponding priority level "1" indicates a lower priority level than the priority level of the second event report, which is "0". User terminal 122 may instead determine to send a message 403 requesting the allocation of uplink resources for the second event report, which has a higher priority level, at the first timing 420.

[0193] User terminal 122 may then receive message 404 at a subsequent time 425, in which uplink resources are allocated for reporting a second event report at a second time 430.

[0194] User terminal 122 may then send a second event report 405 at the second time point 430.

[0195] Optionally, user terminal 122 may postpone and subsequently send message 406 at a third time point 440 to request the allocation of uplink resources for the first event report.

[0196] User terminal 122 may then receive message 407 at a subsequent time, in which uplink resources are allocated for reporting the first event report at the fourth time point 450.

[0197] User terminal 122 may then send the first event report 408 at the fourth time point 450.

[0198] For example, if the second event 402 occurs or is triggered within a predetermined time period N 460 (or alternatively a different predetermined time period) prior to the reporting opportunity allocated for sending the first event report, the same priority ordering process can be applied. In this case, the reporting opportunity allocated for the first event report can instead be used for sending the second event report or for a request to allocate uplink resources for the second event report.

[0199] As will be understood from the above, the process can be extended to more than two events, such as up to four events in this particular example, as long as the corresponding priority level can be obtained or derived.

[0200] In some example embodiments, the event and associated report may be associated with a beam reporting event at user terminal 122. For example, the event may be associated with at least one of the following:

[0201] The first event is when the quality metric of the current beam is worse than a certain threshold.

[0202] The second event is that the quality metric of at least one new beam becomes a better threshold than that of the current beam;

[0203] The third event is that the quality metric of the new beam is better than a certain threshold; or

[0204] The fourth event is that the quality metric of the current beam is worse than the first threshold, and the quality metric of at least one new beam is better than the second threshold.

[0205] Other events are also excluded from this list.

[0206] Figure 5 This is a flowchart illustrating operation 500 according to one or more other example embodiments. Operation 500 can be performed in hardware, software, firmware, or a combination thereof. For example, operation 500 can be performed individually or collectively by a component, wherein the component may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the operation. For example, operation 500 can be performed by a user terminal, such as by... Figure 1 The user terminal 122 executes.

[0207] The first operation 501 may include detecting multiple events used to trigger a corresponding report to be transmitted to a network node.

[0208] The corresponding report can be a CSI report.

[0209] Since the event was triggered at user terminal 122, the corresponding report can be referred to as a beam management (UEIBM) report initiated by the user terminal or user equipment.

[0210] The second operation 502 may include obtaining the appropriate priority level associated with the corresponding report.

[0211] In this context, the term “obtain” can mean receiving, accessing, exporting, or something similar.

[0212] The third operation 503 may include identifying a report from a corresponding report, or identifying a message associated with a report from a corresponding report, for transmission at a specific time point.

[0213] The fourth operation 504 may include determining at a first opportune moment to send the identified report, or a message associated with the identified report, to the network node, wherein the selection is at least in part based on a corresponding priority level.

[0214] In some example embodiments, the first timing is selected from a set (e.g., a pool) of available timings (e.g., which may be provided in the reporting configuration) and is the timing that occurs next after multiple events have been detected.

[0215] In some example embodiments, the fourth operation 504 may also be based on the fact that the event triggering the identified report occurred within a time period N prior to the first timing. As mentioned above, the time period N may be predetermined and received from the network node, or hard-coded in the user terminal 122.

[0216] In some example implementations, the identified reports are associated with the highest priority level.

[0217] In some example embodiments, another operation may include determining at a second time point, following the first time point, to send a different identified report, or a message associated with a different identified report, to the network node. The different selected identified report may be a report associated with the next available highest priority level.

[0218] In some example embodiments, when the corresponding priority levels associated with two or more corresponding reports indicate the same priority level, identification may be based on one or more other parameters. One or more other parameters may include at least one of the following: the chronological order of the first and second events associated with the first event-triggered report and the second event-triggered report, respectively; the corresponding payload size associated with the corresponding first event-triggered report and the second event-triggered report; the corresponding serving cell identifier associated with the first event and the second event; or network configuration parameters. In another example, one or more other parameters may include a coresetPoolIndex value used for scheduling uplink resources, where the lowest value indicates the highest priority level, and vice versa.

[0219] In some example embodiments, the message associated with the identified report may include at least one of the following: a request for uplink resources(s) for subsequent transmission of the identified report; an indication that the identified report will be reported at a subsequent time; or an indication of an event associated with the identified report.

[0220] In some example embodiments, user terminal 122 may store a corresponding report configuration associated with the corresponding report, wherein the corresponding priority level includes a corresponding value indicated in a predetermined field of the corresponding report configuration. The corresponding report configuration may also indicate a corresponding event that triggers the corresponding report.

[0221] In some example implementations, the corresponding priority level may include a corresponding numerical value. For example, a lower numerical value may indicate a higher priority level, and vice versa.

[0222] In some example embodiments, another operation may include receiving at least one updated priority level from a network node or another network node.

[0223] In some example embodiments, the reporting of a corresponding report is associated with a corresponding beam reporting event. For example, a corresponding report may be associated with at least one of the following:

[0224] The first event is that the current beam's quality metric is worse than the quality threshold.

[0225] The second event is that the quality metric of at least one new beam becomes a better threshold than that of the current beam;

[0226] The third event is that the quality metric of the new beam is better than the quality threshold; or

[0227] The fourth event is that the quality metric of the current beam is worse than the first quality threshold, and the quality metric of at least one new beam is better than the second quality threshold.

[0228] Other events are also excluded from this list.

[0229] about Figure 2 The described features are also applicable to targets Figure 5 The described operation.

[0230] Figure 6 This is a flowchart illustrating operation 600 according to one or more other example embodiments. Operation 600 can be performed in hardware, software, firmware, or a combination thereof. For example, operation 600 can be performed individually or collectively by a component, wherein the component may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the operation. For example, operation 600 can be performed by a user terminal, such as by... Figure 1 The user terminal 122 executes.

[0231] The first operation 601 may include maintaining a list of events used to trigger corresponding reports (such as CSI or UEIBM reports), which may be maintained in order of their associated priority levels.

[0232] by Figure 3 Taking the 130A–130D report configuration as an example, the list can include an ordered list:

[0233] E-2: Priority level 0;

[0234] E-1: Priority level 1;

[0235] E-3: Priority Level 2; and

[0236] E-4: Priority level 3.

[0237] The second operation 602 may include scheduling uplink timing for sending a report (or a message associated with the report).

[0238] by Figure 4 Taking timeline 410 as an example, the uplink timing can include at least some of the first to fourth timings 420, 430, 440, and 450.

[0239] The third operation 603 can determine whether a new event has been detected. If the third operation 603 determines that no new event has been detected, the fourth operation 604 may include sending a report associated with the highest priority level at the next uplink timing.

[0240] Therefore, even if one or more of the other events E-1, E-3, and E-4 are triggered earlier in time, a report associated with event E-2 can still be sent at the first timing point 420.

[0241] Event E-2 can now be removed from the maintained list. In this case, the list is updated so that event E-1 has the highest priority.

[0242] If the third operation 603 determines that a new event has been detected, the fifth operation 605 may include adding the new event to a maintained list, for example, in order of its associated priority level.

[0243] Therefore, if a new event E-5 with an associated priority level of 1 is detected after removing event E-2 from the maintained list, it can be added to the updated list, which then includes:

[0244] E-1: Priority level 1;

[0245] E-5: Priority level 1;

[0246] E-3: Priority Level 2; and

[0247] E-4: Priority level 3.

[0248] Then, the next iteration of the fourth operation 604 will determine that the two events E-1 and E-5 have the same priority level, and thus at least one additional parameter can be used to determine which report or associated message will be sent at the second time point 430.

[0249] For example, the determination may be based on at least one of the following: the chronological order of the occurrence of the first event E-1 and the fifth event E-5, the corresponding payload size associated with the corresponding first report and the fifth report, the corresponding serving cell identifier associated with the first event E-1 and the fifth event E-5, or parameters of the network configuration.

[0250] Assuming the first event E-1 and the fifth event E-5 occur in chronological order, a report or related message on the first event E-1 will be sent at the second time point 430.

[0251] about Figure 2 and Figure 5 The described features are also applicable to targets Figure 6 The described operation.

[0252] In any of the above examples, other example embodiments may provide at the network node (e.g., at...). Figure 1One or more operations performed at network node 120. For example, network node 120 or another network node can configure one or more of the aforementioned priority levels for user terminal 122 (or multiple user terminals). For example, network node 120 can configure user terminal 122 with at least one priority level associated with a corresponding at least one event-triggered reporting configuration, or with a message associated with at least one event-triggered reporting configuration. In this context, the term "configuration" can include network node 120 providing or generating at least one event-triggered reporting configuration (including at least one priority level) and sending it to user terminal 122, or causing at least one existing event-triggered reporting configuration at user terminal 122 to be updated using at least one priority level.

[0253] Figure 7 This is a flowchart illustrating operation 700 according to one or more other example embodiments. Operation 700 can be performed in hardware, software, firmware, or a combination thereof. For example, operation 700 can be performed individually or collectively by a component, wherein the component may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the operation. For example, operation 700 can be performed by a network node, such as by... Figure 1 Execute on network node 120.

[0254] The first operation 701 may include configuring at least one priority level for the user terminal associated with a CSI report configuration triggered by at least one corresponding event, or with a message associated with a CSI report configuration triggered by at least one event.

[0255] The second operation 702 may include receiving, at least in part, a CSI report triggered by the first event, or a message associated with the CSI report triggered by the first event, from or not from the user terminal at a time punctuation based on at least one priority level.

[0256] Example device

[0257] Figure 8An example device 800 capable of supporting at least some of the embodiments is illustrated. The illustrated device 800 may include the aforementioned user terminal 122 or be configured to control its functions. Alternatively, device 800 may include the aforementioned network entity 120. Device 800 includes a processor 810, which may include, for example, a single-core or multi-core processor, wherein a single-core processor includes one processing core, and a multi-core processor includes multiple processing cores. Processor 810 typically includes a control device. Processor 810 may include more than one processor. Processor 810 may be a control device. Processor 810 may include at least one application-specific integrated circuit (ASIC). Processor 810 may include at least one field-programmable gate array (FPGA). Processor 810 may be a component for executing method steps stored in device 800. Processor 810 may be configured at least partially by computer instructions to perform actions.

[0258] A processor may include, or may be constituted, one or more circuits configured to perform phases of the methods according to embodiments described herein. As used herein, the term “circuit” may refer to one or more or all of the following: (a) a purely hardware circuit implementation, such as an implementation of analog and / or digital circuits only; and (b) a combination of hardware circuits and software, such as, where applicable: (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to cause a device (such as network entity 120) or a device configured to control its functions to perform various functions; and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) for operation, but may be absent when not required for operation.

[0259] This definition of "circuit" applies to all uses of the term in this application, including in any claim. As a further example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0260] Device 800 may include memory 820. Memory 820 may include random access memory and / or permanent memory. Memory 820 may include at least one RAM chip. Memory 820 may include, for example, solid-state, magnetic, optical, and / or holographic memory. Memory 820 may be at least partially accessed by processor 810. Memory 820 may be at least partially contained within processor 810. Memory 820 may be a component for storing information. Memory 820 may include computer instructions configured to be executed by processor 810. When computer instructions configured to cause processor 810 to perform certain actions are stored in memory 820, and device 800 is generally configured to operate using computer instructions from memory 820 under the guidance of processor 810, processor 810 and / or at least one of its processing cores may be considered to be configured to perform said certain actions. Memory 820 may be at least partially contained within processor 810. Memory 820 may be at least partially external to device 800, but accessible by device 800.

[0261] Device 800 may include a transmitter 830. Device 800 may include a receiver 840. Transmitter 830 and receiver 840 may be configured to transmit and receive information according to at least one cellular or noncellular standard, respectively.

[0262] Transmitter 830 may include more than one transmitter. Receiver 840 may include more than one receiver. For example, transmitter 830 and / or receiver 840 may be configured to operate according to Global System for Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), 5G / NR, 5G-Advanced (i.e., NR Rel-18, 19 and beyond), Long Term Evolution (LTE), IS-95, Wireless Local Area Network (WLAN), Ethernet and / or Global Interoperability for Microwave Access (WiMAX) standards.

[0263] Device 800 may include a near-field communication (NFC) transceiver 850. The NFC transceiver 850 may support at least one NFC technology, such as NFC, Bluetooth, Wibree, or similar technologies.

[0264] Device 800 may include a user interface (UI) 860. UI 860 may include at least one of a display, keyboard, touchscreen, vibrator (arranged to signal to a user by causing device 800 to vibrate), speaker, and microphone. A user may be able to operate device 800 via UI 860, for example, answering incoming calls, making phone or video calls, browsing the internet, managing digital files stored in memory 820 or accessible in the cloud via transmitter 830 and receiver 840 or via NFC transceiver 850, and / or playing games.

[0265] Device 800 may include or be arranged to accept a user identity module 870. User identity module 870 may include, for example, a user identity module SIM card that can be installed in device 800. User identity module 870 may include information identifying the subscription of a user of device 800. User identity module 870 may include encrypted information that can be used to verify the identity of the user of device 800 and / or facilitate the encryption of communicated information and billing of the user of device 800 for communications via device 800.

[0266] The processor 810 may be equipped with a transmitter arranged to output information from the processor 810 to other devices included in the device 800 via electrical wires within the device 800. Such a transmitter may include a serial bus transmitter arranged to output information to a memory 820 for storage, for example, via at least one electrical wire. In addition to a serial bus, the transmitter may include a parallel bus transmitter.

[0267] Similarly, processor 810 may include a receiver arranged to receive information from other devices included in device 700 via electrical leads within device 800. Such a receiver may include a serial bus receiver arranged, for example, to receive information from receiver 840 via at least one electrical lead for processing in processor 810. In addition to a serial bus, the receiver may also include a parallel bus receiver.

[0268] Device 800 may include Figure 8 Other devices not shown. For example, in the case where device 800 includes a smartphone, it may include at least one digital camera. Some devices 800 may include a rear camera and a front camera, wherein the rear camera may be used for digital photography, and the front camera for video calling. Device 800 may include a fingerprint sensor arranged to at least partially authenticate the user of device 800. In some embodiments, device 800 lacks at least one of the above-mentioned devices. For example, some devices 800 may lack an NFC transceiver 850 and / or a user identity module 870.

[0269] Processor 810, memory 820, transmitter 830, receiver 840, NFC transceiver 850, UI 860, and / or user identity module 870 can be interconnected in various ways via electrical leads within device 800. For example, each of the above devices can be individually connected to the main bus within device 800 to allow the devices to exchange information. However, as those skilled in the art will recognize, this is merely an example, and various ways of interconnecting at least two of the above devices can be chosen according to embodiments without departing from the scope of the invention.

[0270] Figure 9 A non-transitory medium 900 according to some embodiments is shown. The non-transitory medium 900 is a computer-readable storage medium. It may be, for example, a CD, DVD, USB stick, Blu-ray disc, etc. The non-transitory medium 900 stores computer program instructions that cause a device to perform any of the aforementioned processes, such as those disclosed in the flowcharts and related features of this specification.

[0271] The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details, such as examples of length, width, shape, etc., have been provided in the foregoing description to provide a thorough understanding of embodiments of the invention. However, those skilled in the art will recognize that the invention can be practiced without one or more specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the invention.

[0272] While the examples above illustrate the principles of embodiments in one or more specific applications, it will be apparent to those skilled in the art that numerous modifications in form, use, and implementation details can be made without inventiveness or departing from the principles and concepts of the invention. Therefore, the invention is not intended to be limited except as set forth in the claims below.

[0273] The verbs “comprising” and “including” are used in this document as open-ended restrictions, neither excluding nor requiring the presence of any unrecorded features. Unless otherwise expressly stated, the features recited in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of “a” or “an” (i.e., the singular form) in this document does not exclude the plural.

[0274] The term "component" as used in the specification and claims may refer to one or more individual elements configured to perform a corresponding described function, or it may refer to several elements performing such one or more functions. Furthermore, the functions described in the claims may be performed by the same individual components or a combination of the same components. For example, the performance of such one or more functions may be caused in a device by a processor executing instructions stored in the device's memory.

Claims

1. An apparatus comprising: Components for obtaining a first priority level associated with a Channel State Information (CSI) report triggered by a first event and sent to a network node; as well as A component for determining, at least in part, whether to send the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node at a given time, based on the first priority level.

2. The apparatus according to claim 1, The message associated with the CSI report triggered by the first event includes at least one of the following: A request for one or more uplink resources for subsequently sending a CSI report triggered by the first event; or The CSI report triggered by the first event will be reported at a subsequent time point.

3. The apparatus according to claim 1 or claim 2, further comprising: Components for obtaining a second priority level associated with a CSI report triggered by a second event and sent to the network node at the specified time. The component used for determination is configured as follows: The timing of sending at least one of the first event-triggered CSI reports or the second event-triggered CSI reports, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report, to the network is determined at least in part based on the first priority level and the second priority level.

4. The apparatus according to claim 3, The component used for determination is configured to: further determine, based on the following, to send at least one of the first event-triggered CSI report or the second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report: It is determined that only one event-triggered CSI report can be sent at the stated time, or only one message associated with the event-triggered CSI report can be sent.

5. The apparatus according to claim 3 or claim 4, The component used for determination is configured to: further determine, based on the following, to send at least one of the first event-triggered CSI report or the second event-triggered CSI report, or a message associated with the first event-triggered CSI report or the second event-triggered CSI report: The event that triggers the CSI report for the second event occurs within a time period N prior to the stated time.

6. The apparatus according to any one of claims 3 to 5, Wherein, when the first priority level is higher than the second priority level, the component used for determination is configured to determine: At the specified time, send the CSI report triggered by the first event, or a message associated with the CSI report triggered by the first event, to the network node.

7. The apparatus according to any one of claims 3 to 6, Wherein, when the second priority level is higher than the first priority level, the component used for determination is configured to determine: At the specified time, send the CSI report triggered by the second event, or a message associated with the CSI report triggered by the first event, to the network node.

8. The apparatus according to any one of claims 3 to 7, Where the first priority level and the second priority level are the same, the component used for determination is configured to determine: Based on one or more other parameters, a message is sent to the network node at the specified time point, either a CSI report triggered by the first event or a CSI report triggered by the second event, or a message associated with either the CSI report triggered by the first event or the CSI report triggered by the second event.

9. The apparatus according to claim 8, The one or more other parameters mentioned above include at least one of the following: The chronological order of the occurrence of the first and second events, which are respectively associated with the CSI report triggered by the first event and the CSI report triggered by the second event; The corresponding payload size associated with the corresponding first event-triggered CSI report and the second event-triggered CSI report; The corresponding serving cell identifier associated with the first event and the second event; or Network configuration parameters.

10. The apparatus according to any one of the preceding claims, further comprising: A component for receiving report configurations associated with at least the CSI report triggered by the first event, and At least the first priority level is a value indicated in a predetermined field of the report configuration.

11. The apparatus according to any one of the preceding claims, wherein The CSI report triggered by at least the first event is associated with the beam reporting event.

12. The apparatus according to claim 11, wherein The beam reporting event includes at least one of the following: Events where the quality of the current beam is worse than a certain threshold; An event in which the quality of at least one new beam becomes a threshold better than that of the current beam; The event that the quality of the new beam is better than a certain threshold; or An event in which the quality of the current beam is worse than the first threshold and the quality of at least one new beam is better than the second threshold.

13. A method comprising: Obtain the first priority level associated with the Channel State Information (CSI) report triggered by the first event and sent to the network node; as well as The decision to send the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node is based at least in part on the first priority level.

14. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Obtain the first priority level associated with the Channel State Information (CSI) report triggered by the first event to be sent to the network node; and The decision to send the first event-triggered CSI report, or a message associated with the first event-triggered CSI report, to the network node is based at least in part on the first priority level.

15. An apparatus comprising: A component for configuring a user terminal with at least one priority level associated with a Channel State Information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with a CSI report configuration triggered by said at least one event; as well as A component for receiving, at least in part, a CSI report triggered by a first event, or a message associated with a CSI report triggered by the first event, from or not from a user terminal at a given time and location based on at least one priority level.

16. The apparatus of claim 15, wherein the message associated with the CSI report triggered by the first event includes at least one of the following: A request for one or more uplink resources for which the user terminal subsequently sends a CSI report triggered by the first event; or The CSI report triggered by the first event will be reported by the user equipment at a subsequent time point.

17. The apparatus according to claim 15 or 16, further comprising: A component for sending a report configuration associated with at least the CSI report triggered by the first event, and At least the first priority level is a value indicated in a predetermined field of the report configuration.

18. The apparatus according to any one of claims 15 to 17, wherein At least the CSI report triggered by the first event is associated with the beam reporting event.

19. The apparatus according to any one of claims 15 to 18, wherein the apparatus comprises at least one of a network node, an eNB, a gNB, or a TRP.

20. A method comprising: Configure a user terminal with at least one priority level associated with a Channel State Information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with a CSI report configuration triggered by said at least one event; as well as At least in part based on at least one priority level, at a given time, a CSI report triggered by a first event, or a message associated with a CSI report triggered by the first event, is received from or not received from the user terminal.

21. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Configure the user terminal with at least one priority level associated with a Channel State Information (CSI) report configuration triggered by at least one corresponding event, or with a message associated with a CSI report configuration triggered by said at least one event; and At least in part based on at least one priority level, at a given time, a CSI report triggered by a first event, or a message associated with a CSI report triggered by the first event, is received from or not received from the user terminal.

Images