Managing event-triggered beam reporting

Abstract

The present disclosure relates to an apparatus comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform: detecting an event that triggers a report. In response to detecting the event, determining whether a reporting condition for the report is satisfied. In response to the reporting condition being satisfied, starting a timer. In response to the timer expiring, determining to discard or cancel the report triggered by the event.

Description

Cross-reference to related applications

[0001] This application claims the benefit of FI application No. 20245363, filed on March 28, 2024, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0002] The various example embodiments described herein relate to the field of wireless communications. Some example embodiments relate to beam reporting triggered by management events. Background Technology

[0003] Various communication systems (e.g., the 3GPP 5G NR) can be configured to include channel state information (CSI) measurements and beamforming initiated by user equipment (UE) or triggered by events. However, if the UE is unable to report event-triggered information due to factors such as lack of resource allocation or other uplink transmissions or signal prioritization, this type of reporting may include outdated information. Summary of the Invention

[0004] The present invention is provided to present, in a simplified form, the selection of concepts further described below in the detailed embodiments. The present invention is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0005] The exemplary embodiments of this disclosure enable conditions to configure a user equipment (UE) to discard or cancel event-triggered reporting. This benefit can be achieved through the features of the independent claims. Further exemplary embodiments are provided in the dependent claims, detailed description, and drawings.

[0006] According to a first aspect, an apparatus is disclosed. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, together with the at least one processor, to cause the apparatus to at least: detect an event that triggers a report; in response to detecting the event, determine whether reporting conditions for reporting are met; in response to the reporting conditions being met, start a timer; in response to the timer expiring, determine whether to discard or cancel the report triggered by the event.

[0007] Such a device can prevent the reporting of outdated event-triggered information in situations where, for example, there is no prioritization of resource allocation or other UL transmissions or signals for reporting.

[0008] According to an example embodiment of the first aspect, the timer can be associated with an event-triggered channel state information report.

[0009] According to an example embodiment of the first aspect, the reporting condition may be available at least after a period of time has elapsed following the transmission of another report associated with the reference signal and / or before the transmission of another report associated with the reference signal, wherein the detected event is associated with the reference signal. Using such a device, reporting can be prevented in the event of a recent similar report or an upcoming similar report.

[0010] According to an example embodiment of the first aspect, at least one memory and computer program code may be configured, together with at least one processor, to cause the device to also perform: obtaining a time period from a network device or from a specification-defined or hard-coded time period.

[0011] According to an example embodiment of the first aspect, a time period can be specified or configured according to at least one of the following: time, number of reporting opportunities, number of reporting instances, number of reporting opportunities per unit time, number of reporting instances per unit time, number of uplink signals requesting resources per unit time, or number of uplink signals indicating events per unit time.

[0012] According to an example embodiment of the first aspect, at least one memory and computer program code can be configured, together with at least one processor, to cause the device to also perform: after a timer is started, determining whether a stop condition or a cancellation condition is met.

[0013] The timer stops when the stop condition is met. The timer is canceled when the cancellation condition is met.

[0014] According to an example embodiment of the first aspect, the stop condition or cancellation condition may be at least one of the following: a new timer is started for the same event, a report triggered by the event is transmitted, and a response to the transmitted report is received.

[0015] According to an example embodiment of the first aspect, the timer can be configured according to at least one of the following: time, number of reporting opportunities, number of reporting instances, number of reporting opportunities per unit time, number of reporting instances per unit time, number of uplink signals requesting resources per unit time, or number of uplink signals indicating events per unit time.

[0016] According to an example embodiment of the first aspect, determining to discard event-triggered reports may include at least one of the following: determining not to perform measurements on event-triggered reports; determining not to generate event-triggered reports; or determining to discard generated event-triggered reports.

[0017] According to an example embodiment of the first aspect, at least one memory and computer program code can be configured, together with at least one processor, to cause the device to also perform: obtaining a timer value from a network device or from a specification definition or as a hard-coded value.

[0018] According to an example embodiment of the first aspect, at least one memory and computer program code may be configured, together with at least one processor, to cause the device to further perform: in response to at least one of: transmitting an uplink channel, or transmitting a signal requesting uplink resources for an event-triggered report or triggering an event-triggered report; generating an event-triggered report; and transmitting the event-triggered report.

[0019] According to an example embodiment of the first aspect, at least one memory and computer program code may be configured, together with at least one processor, to cause the device to also perform: in response to a reporting condition not being met, determining to discard or cancel an event-triggered report.

[0020] According to a second aspect, a computer-implemented method is disclosed. The method may include: detecting an event that triggers a report; determining, in response to detecting the event, whether reporting conditions for reporting are met; starting a timer in response to the reporting conditions being met; and determining, in response to the timer expiring, whether to discard or cancel the report triggered by the event.

[0021] According to a third aspect, a computer-readable medium is disclosed. This computer-readable medium may include program instructions for causing a device to execute at least the following: detecting an event that triggers a report; determining, in response to detecting an event, whether reporting conditions for reporting are met; starting a timer in response to the reporting conditions being met; and determining, in response to the timer expiring, to discard or cancel the report triggered by the event.

[0022] According to a fourth aspect, a computer program is disclosed. This computer program may include instructions for causing a device to perform at least the following operations: detecting an event that triggers a report; determining, in response to detecting an event, whether reporting conditions for reporting are met; starting a timer in response to the reporting conditions being met; and determining, in response to the timer expiring, to discard or cancel the report triggered by the event.

[0023] Any example embodiment may be combined with one or more other example embodiments. Many accompanying features can be more readily understood by referring to the following detailed description taken in conjunction with the accompanying drawings. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of the exemplary embodiments and form part of this specification, illustrate exemplary embodiments and, together with the description, aid in understanding the exemplary embodiments. In the drawings: Figure 1An example embodiment of a cellular communication network is illustrated; Figure 2 Example functions of a device according to an example embodiment are shown; Figure 3 A signaling diagram according to an example embodiment is shown; and Figure 4 A schematic block diagram of an apparatus according to an example embodiment is shown.

[0025] In the accompanying drawings, the same reference numerals are used to denote the same parts. Detailed Implementation

[0026] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below, in conjunction with the drawings, is intended as a description of the examples and is not intended to represent the only form in which the examples can be constructed or utilized. This specification sets forth the functionality of the examples and the sequence of steps for constructing and operating the examples. However, the same or equivalent functionality and sequence can be implemented through different examples.

[0027] Although the specification may refer to "a," "an," or "some" (or more) embodiments in several places, this does not necessarily mean that each such reference refers to the same (or more) embodiments, or that the feature may not be applicable to other embodiments. Individual features of different embodiments may also be combined to provide other embodiments. Furthermore, the words "comprising" and "including" should be understood not to limit the described embodiments / examples to consisting only of those features already mentioned, and such embodiments / examples may also include features / structures not specifically mentioned.

[0028] Furthermore, although numerical terms such as “first”, “second”, etc., may be used herein to describe various embodiments, elements, or features, it should be understood that these embodiments, elements, or features should not be limited by such numerical terms. The numerical terms used herein are only for distinguishing one embodiment, element, or feature from another embodiment, element, or feature. For example, a first panel discussed below may be referred to as a second panel, and vice versa, without departing from the teachings of this disclosure.

[0029] However, in the following description, radio access architectures based on LTE-Advanced (LTE-A) or New Radio (NR, 5G) will be used as examples of access architectures to which the embodiments can be applied, to illustrate different exemplary embodiments, without limiting the embodiments to such architectures. The embodiments can also be applied to other kinds of communication networks with suitable means by appropriately adjusting parameters and processes. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), LTE (same as E-UTRA), Wireless Local Area Network (WiAN or WiFi), Global Microwave Access Interoperability (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0030] Figure 1 An example of a simplified system architecture is depicted, showing only a few components and functional entities. All components and functional entities are logical units, and their implementation may differ from that shown. Figure 1 The connections shown are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically includes, in addition to... Figure 1 Other functions and structures besides those shown.

[0031] However, the embodiments are not limited to the system given as an example, but those skilled in the art can apply the solution to other communication systems with the necessary properties.

[0032] Figure 1 The example shows a portion of an exemplary radio access network 100.

[0033] Figure 1 User equipment 101, 101' configured to wirelessly connect to node 102 on one or more communication channels is shown. Node 102 is also connected to core network 105. In one example, node 102 may be an access node, such as an (e / g)NodeB that provides services to devices in a cell. In one example, node 102 may be a non-3GPP access node. The physical link from the device to the (e / g)NodeB is referred to as an uplink or reverse link, and the physical link from the (e / g)NodeB to the device is referred to as a downlink or forward link. It should be understood that the (e / g)NodeB or its functionality can be implemented using any entity suitable for this purpose, such as a node, host, server, or access point.

[0034] A communication system typically includes multiple (e / g)NodeBs, which may also be configured to communicate with each other via wired or wireless links designed for this purpose. These links can be used for signaling purposes. An (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. A NodeB may also be referred to as a base station, access point, or any other type of interface device, including relay stations capable of operating in a wireless environment. An (e / g)NodeB includes or is coupled to a transceiver. From the transceiver of the (e / g)NodeB, a connection is provided to an antenna element that establishes a bidirectional radio link to the device. The antenna element may include multiple antennas or antenna elements. The (e / g)NodeB is also connected to the core network 105 (CN or Next Generation Core NGC). Depending on the system, the CN-side counterpart may be a Serving Gateway (S-GW, for routing and forwarding user data packets), a Packet Data Network Gateway (P-GW) for providing connectivity from a User Equipment (UE) to an external packet data network, a Mobility Management Entity (MME), or an Access and Mobility Management Function (AMF), etc.

[0035] User equipment (also referred to as UE, user equipment, user terminal, terminal equipment, etc.) exemplifies a type of device to which air interface resources are allocated and assigned, and thus any features described herein with respect to user equipment can be implemented by corresponding devices (such as relay nodes). An example of such a relay node is a Layer 3 relay (self-backhaul relay) toward a base station.

[0036] User equipment (UAE) generally refers to a device that includes wireless mobile communication devices (e.g., portable or non-portable computing devices) operating with or without a Subscriber Identity Module (SIM), including but not limited to the following types of devices: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), cell phones, devices using wireless modems (alarm or measuring devices, etc.), laptops and / or touchscreen computers, tablets, game consoles, laptops, and multimedia devices. It should be understood that a device can also be a virtually exclusive uplink-only device, an example of which is a camera or camcorder that uploads images or video clips to a network. A device can also be a device capable of operating in an Internet of Things (IoT) network, a scenario in which the ability to transmit data over a network to objects is provided without human-to-human or human-to-computer interaction is required (e.g., in smart grids and connected vehicles). UAE can also utilize the cloud. In some applications, UAE may include a portable user device with radio components (such as a watch, headset, glasses, other wearable accessories, or wearable devices), and computation is performed in the cloud. The device (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more UAE functions. User equipment can also be referred to as subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE), and only some names or devices are mentioned here.

[0037] The various techniques described in this paper can also be applied to cyber-physical systems (CPS) (systems that control collaborative computing elements of physical entities). CPS can realize and utilize a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems, which are inherently mobile physical systems, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0038] Furthermore, although the device is described as a single entity, different units, processors, and / or memory units may be implemented. Figure 1 (Not all of them are shown in the text).

[0039] 5G enables the use of multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites that collaborate with smaller stations and employ various radio technologies based on service demands, use cases, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications (e.g., massive machine-type communications (mMTC), including vehicle safety, various sensors, and real-time control). 5G is expected to have multiple radio interfaces: sub-6GHz, cmWave, and mmWave, and will also be able to integrate with existing legacy radio access technologies such as LTE. Integration with LTE can be implemented, at least initially, as a system where macro coverage is provided by LTE, and 5G radio interface access originates from small cells through aggregation to LTE. In other words, 5G is planned to support inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as sub-6GHz-cmWave and sub-6GHz-cmWave-mmWave). One of the concepts believed to be used in 5G networks is network slicing, in which multiple independent and dedicated virtual sub-networks (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0040] The current architecture in LTE networks is entirely distributed across radios and entirely centralized in the core network. Low-latency applications and services in 5G require bringing content closer to the radio, leading to local offloading and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be discontinuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content near cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networking and processing, and can also be categorized as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, micro-cloud, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0041] The communication system can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize the services provided by them. The communication network can also support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Depicted by “Cloud” 107). Communication systems may also include a central control entity, which provides facilities for different operators’ networks to collaborate, for example, in spectrum sharing.

[0042] Edge cloud technologies can be incorporated into radio access networks (RANs) by leveraging network function virtualization (NVF) and software-defined networking (SDN). Using edge cloud technologies can mean that access node operations are performed, at least partially, in servers, hosts, or nodes operatively coupled to a remote radio head or base station, including the radio portion. Node operations can also be distributed across multiple servers, nodes, or hosts. The application of a cloud RAN architecture enables the execution of real-time RAN functions on the RAN side (in the distributed unit, DU102) and non-real-time functions in a centralized manner (in the centralized unit, CU104).

[0043] It should also be understood that the division of labor between core network operations and base station operations may differ from that in LTE, or even not exist at all. Some other technological advancements that may be used include big data and all-IP, which could change the way networks are built and managed. 5G (or New Radio, NR) networks are designed to support multiple hierarchical structures, where MEC servers can be placed between the core and base stations or nodeBs (gNBs). It should be understood that MEC can also be applied to 4G networks.

[0044] 5G can also leverage satellite communications to enhance or supplement 5G service coverage, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on transportation, or ensuring the availability of critical communications and future rail / sea / air communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems, but can also utilize low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite 103 in a mega-constellation can cover a network entity of several supporting satellites that create a ground cell. Ground cells can be created via ground relay nodes 102 or by gNBs located on the ground or in satellites.

[0045] It will be apparent to those skilled in the art that the described system is merely an example of a portion of a radio access system, and in practice, the system may include multiple (e / g) NodeBs, user equipment may access multiple radio cells, and the system may also include other devices such as physical layer relay nodes or other network elements. At least one (e / g) NodeB may be a Home (e / g) NodeB. Furthermore, multiple different types of radio cells and multiple radio cells may be provided within the geographical area of ​​the radio communication system. Radio cells may be macrocells (or umbrella cells), which are large cells typically with diameters up to tens of kilometers, or smaller cells such as microcells, femtocells, or picocells. Figure 1 The (e / g)NodeB can provide any type of these cells. Cellular radio systems can be implemented as multi-layer networks comprising several types of cells. Typically, in a multi-layer network, one access node provides one type of cell, thus requiring multiple (e / g)NodeBs to provide this network structure.

[0046] To meet the needs of improved communication system deployment and performance, the concept of "plug and play" (e / g) NodeB has been introduced. Typically, in addition to home (e / g) NodeBs (H(e / g) NodeBs), networks capable of using "plug and play" (e / g) NodeBs also include home NodeB gateways or HNB-GWs ( Figure 1 (Not shown in the image). HNB gateways (HNB-GWs), typically installed within a carrier's network, can aggregate traffic from a large number of HNBs back to the core network.

[0047] In 5G and above, event-triggered beamforming is envisioned to reduce overhead and / or latency. Devices configured for event-triggered reporting can be configured to utilize conditions to prevent outdated reporting, for example, as described below. Figure 2 and Figure 3 As described.

[0048] Figure 2 Example functionality is shown for a device (UE) configured to enable conditions for managing event-triggered reporting, according to an example embodiment.

[0049] refer to Figure 2In operation 201, the UE detects an event that triggers a report. This event could be, for example, a beam switching requirement due to a change in UE orientation, a rapid degradation in the quality of the current beam, or a new beam having better quality than the current beam. This detection could include the UE monitoring a reference signal (RS) to assess whether beam reporting triggering conditions have been met. The beam report could be a Channel State Information (CSI) report. In operation 202, it is determined whether the reporting conditions are met. In an example embodiment, the reporting conditions may include at least a time period that has elapsed after the transmission of another report associated with the reference signal and / or a time period that is available before the transmission of another report associated with the reference signal, wherein the detected event is associated with the same reference signal. In an example embodiment, the reporting conditions are at least a time period that has elapsed after the transmission of another report associated with the event and / or a time period that is available before the transmission of another report associated with the event, wherein the detected event is the same as the event associated with that time period. In an example embodiment, when that time is running (i.e., the event has already been triggered), the UE may not trigger a new report of the same event. This behavior of the timer and / or the reporting conditions may be specific to the reporting configuration. In an example embodiment, another report associated with the reference signal may be an event-triggered report or an event-triggered transmission timing. In an example embodiment, another report associated with the reference signal may be a non-event-triggered report or a non-event-triggered transmission timing. In an example embodiment, the time period may be obtained by the device from a network device or from a specification-defined time period or as a hard-coded time period.

[0050] In an example embodiment, the reporting condition may include a first time period elapsed after the transmission of a first report associated with a reference signal, and a second time period becoming available before the transmission of a second report associated with the reference signal. The first time period may have the same value as the second time period. In an example embodiment, the first and second time periods may be obtained by the device from a network device or from a specification definition or as hard-coded time periods. In an example embodiment, the reporting condition may include an uplink (UL) signal being triggered by the UE to request UL resources for reporting. In an example embodiment, the reporting condition may include the UE having configured the report on the UL resource. In an example embodiment, the reporting condition may include the UE having generated a report.

[0051] In example embodiments, the UE may be configured with one or more timers. A timer within one or more timers may be configured for a specific event defined in the reporting configuration. A timer within one or more timers may be configured for a specific event across configured reporting configurations. A timer within one or more timers may be configured for a specific (event-based) reporting configuration. A timer within one or more timers may be configured for a specific set of (event-based) reporting configurations.

[0052] refer to Figure 2 If the reporting conditions are met (Operation 202: Yes), a timer is started in Operation 204. In an example embodiment, the timer is associated with an event-triggered Channel State Information (CSI) report. In an example embodiment, starting the timer may include initializing the timer. The timer value may be represented, for example, in milliseconds, time slots, or symbols. In an example embodiment, the timer may be configured to count time, the number of reporting opportunities of the UE, the number of reporting instances, the number of reporting opportunities per unit time, the number of reporting instances per unit time, the number of uplink signals requesting resources per unit time, the number of uplink signals indicating events per unit time, or a combination of one or more of the previous examples. The UE may obtain a timer value (a timer threshold) before the timer is started. In an example embodiment, the timer value may be obtained by the device from a network device or from a specification definition or as a hard-coded value. In an example embodiment, the configuration for event-triggered reporting may include a timer value. In an example embodiment, the timer value may be specific to a particular reporting configuration or a specific event that triggers the report. In an example embodiment, the UE may request a timer value from the network. In the example embodiment, the timer value may be predefined by the specification or the network, or it may be configured by the network. In the example embodiment, if the reporting condition is not met (Operation 202: No), the event-triggered report is discarded or canceled in Operation 203. In the example embodiment, discarding or canceling the report may mean that the UE does not report the specific report or that the UE cancels the pending trigger for reporting the specific report.

[0053] In an example implementation, the timer may be associated with a specific report. As an example, the timer may be report-specific, meaning it is associated with the generated report.

[0054] In example embodiments, timers can be associated with and / or configured for specific events. As an example, a timer can be specific to an event identifier (ID), meaning the timer is associated with a configured event identifier. In example embodiments, a timer can be associated with a specific event type. As an example, event IDs with the same event type (e.g., threshold-based events or RS comparison type events) can share timer configurations.

[0055] In example implementations, timers may be associated with specific reporting configurations and / or specific reporting settings.

[0056] In example embodiments, timers can be associated with and / or configured with a set of reporting configurations and / or a set of reporting settings.

[0057] In the example embodiment, the timer value can be configurable. The timer value can be configured by the network.

[0058] In example embodiments, while the timer is running, the UE may not trigger new or additional reports for the same reporting configuration or reporting settings and / or for the same event. In one example, when the timer expires, the UE may trigger a report for the reporting settings / events (which are associated with the timer).

[0059] In the example implementation, the timer can prevent the UE from reporting a new event triggered for the same event or the same reporting configuration. For example, while the timer is running, the UE may not trigger a new report for the same event that has already been triggered for the same reporting configuration.

[0060] In an example embodiment, the timer can prevent the UE from reporting reports triggered by one or more events associated with the timer or by new events configured for reporting.

[0061] refer to Figure 2 In operation 205, it is determined whether the timer has expired. Timer expiration can be understood as the elapsed time period since the timer's inception satisfying the timer value obtained by the UE. If the timer has expired (operation 205: Yes), then in operation 203, the event-triggered report is discarded or canceled. In an example embodiment, discarding or canceling the report may include the UE not generating the report. In an example embodiment, discarding or canceling the report may include not transmitting the generated report (partially or entirely) and deleting the generated report. In an example embodiment, discarding or canceling the report may include not performing measurements on the report.

[0062] refer to Figure 2If the timer has not yet expired (Operation 205: No), then in Operation 206, it is determined whether the stop condition or cancellation condition is met. In one example, a stopped timer may be restarted. In an example embodiment, the stop condition may include starting a (new) timer or restarting the current timer (i.e., with the configured value) for the same event that triggered the report (or reporting configuration / setting). In an example embodiment, the stop condition may include the UE transmitting a report triggered by an event. In an example embodiment, the stop condition may include the UE receiving a response to the transmitted report. If the stop condition is met (Operation 206: Yes), then the timer is stopped in Operation 207. In an example embodiment, stopping the timer in Operation 207 may include reinitializing the timer value or deleting the timer. In an example embodiment, stopping the timer may include restarting the timer. In an example embodiment, the cancellation condition may include a new timer being started for the same event that triggered the report. In an example embodiment, the cancellation condition may include the UE transmitting a report triggered by an event. In an example embodiment, the cancellation condition may include the UE receiving a response to the transmitted report. If the cancellation condition is met (Operation 206: Yes), then the timer is cancelled in Operation 207. In an example embodiment, canceling a counter may include reinitializing the timer value or deleting the timer. If the stop or cancellation condition is not met (operation 206: No), the process continues by determining in operation 205 whether the timer has expired.

[0063] Figure 3 A signaling diagram illustrating an example of information exchange in a communication network configured to enable event-triggered reporting conditions is shown. Figure 3 In this context, the term "RAN" is used for a network, which can be, for example, a gNB or a distributed access node, including, for example, centralized units (CUs) and distributed units (DUs), enabling the execution of real-time RAN functions on the RAN side (in the DU) and non-real-time functions in a centralized manner (in the CU). The term "UE" is used for a device or subset of devices configured to implement event-triggered reporting.

[0064] refer to Figure 3The UE detects an event that triggers a report (box 3-1). In box 3-2, the UE evaluates the reporting conditions. In an example embodiment, the reporting conditions may include at least a time period that has elapsed after the transmission of another report associated with the reference signal and / or a time period that is available before the transmission of another report associated with the reference signal, wherein the detected event triggering the report is associated with the same reference signal. In an example embodiment, the other report associated with the reference signal may be an event-triggered report or an event-triggered transmission timing. In an example embodiment, the other report associated with the reference signal may be a non-event-triggered report or a non-event-triggered transmission timing. In an example embodiment, the time period may be obtained by the device from a network device or from a specification-defined time period or as a hard-coded time period. In an example embodiment, the reporting conditions may include a first time period that has elapsed after the transmission of a first report associated with the reference signal, and a second time period that is available before the transmission of a second report associated with the reference signal. The first time period may have the same value as the second time period. In an example embodiment, the first and second time periods may be obtained by the device from a network device or from a specification-defined time period or as hard-coded time periods. In an example embodiment, the reporting conditions may include an uplink (UL) signal that has been triggered by the UE to request UL resources for reporting. In an example embodiment, the reporting condition may include that the UE has already configured the report on the UL resource. In an example embodiment, the reporting condition may include that the UE has already generated a report.

[0065] refer to Figure 3 When the reporting conditions are met, the UE requests UL resources from the RAN for reporting (Message 3-3). Additionally, the UE may send the detected event ID along with the request. The UE obtains a timer value from the RAN (Message 3-4). In the example embodiment, the timer value may be obtained by the device from the network device, defined in the specification, or as a hard-coded value. In the example embodiment, the configuration for triggering event reporting may include the timer value. In the example embodiment, the timer value may be specific to a particular reporting configuration or a specific event that triggers the report. In the example embodiment, the UE may request the timer value from the network. In the example embodiment, the timer value may be predefined by the specification or the network, or it may be configured by the network. In block 3-5, the UE starts the timer. Before the UE sends a report to the RAN (Message 3-7), it is determined in block 3-6 that the timer has not yet expired. The RAN transmits an acknowledgment of the transmitted report to the UE (Message 3-8). The UE evaluates in block 3-9 that the stop or cancellation conditions have been met, and then stops or cancels the timer in block 3-10.

[0066] Figure 4An example embodiment of apparatus 400 configured to implement one or more example embodiments is shown. Apparatus 400 may include, for example, a base station, gNB, terminal device, user node, user equipment, cloud node, or a device generally configured to implement the functions described herein. Although apparatus 400 is shown as a single device, it should be understood that, where applicable, the functions of apparatus 400 may be distributed across multiple devices.

[0067] The device 400 may include at least one processor 402. At least one processor 402 may include one or more of various processing devices or processor circuits, such as, for example, a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits, such as, for example, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.

[0068] The device 400 may also include at least one memory 404. At least one memory 404 may be configured to store, for example, computer program code, such as operating system software and application software. At least one memory 404 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or combinations thereof. For example, at least one memory 404 may be embodied as a magnetic storage device (such as a hard disk drive, floppy disk, magnetic tape, etc.), a magneto-optical storage device, or a semiconductor memory (such as a mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

[0069] The device 400 may also include a communication interface 408 configured to enable the device 400 to transmit information to and / or receive information from other devices. In one example, the device 400 may use the communication interface 408 to transmit or receive signaling information and data according to at least one data communication or cellular communication protocol. The communication interface 408 may be configured to provide at least one radio connection, such as, for example, a 3GPP mobile broadband connection (e.g., 3G, 4G, 5G, 6G, etc.). The communication interface 408 may include or be configured to be coupled to at least one antenna to transmit and / or receive radio frequency signals. One or more of various types of connections may also be implemented as a separate communication interface, which may be coupled or configured to be coupled to one or more of a plurality of antennas. The communication interface 408 may include a receiver, a transmitter, or a transceiver.

[0070] When the device 400 is configured to perform a certain function, one or more components of the device 400 (e.g., at least one processor 402 and / or at least one memory 404) may be configured to perform that function. Furthermore, when at least one processor 402 is configured to perform some function, that function may be implemented using, for example, program code 406 included in at least one memory 404.

[0071] The functions described herein can be performed at least in part by one or more computer program product components (e.g., software components). According to an example embodiment, device 400 may include a processor or processor circuitry, such as a microcontroller, configured by program code and performing embodiments of the described operations and functions when the program code is executed. Program code 406 is provided as an example of instructions that, when executed by at least one processor 402, cause the device to perform. Alternatively or additionally, the functions described herein can be performed at least in part by one or more hardware logic components. Examples, but not limited to, illustrative types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and graphics processing units (GPUs).

[0072] Apparatus 400 may be configured to perform or cause to perform any aspect of the methods(s) described herein. Furthermore, a computer program may include instructions for causing the apparatus to perform any aspect of the methods(s) described herein when executed. The computer program may be stored on a computer-readable medium. Additionally, apparatus 400 may include components for performing any aspect of the methods(s) described herein. In one example, the component may include at least one processor 402 and at least one memory 404 including program code 406 (instructions) configured to cause apparatus 400 to perform the methods(s) when executed by at least one processor 402. Typically, computer program instructions may be executable on components that provide general processing functionality. Therefore, the methods(s) may be computer-implemented, for example, algorithms(s) executable by general processing functionality (an example of which is at least one processor 402). The component may include transmitting and / or receiving components, such as one or more radio transmitters or receivers that may be coupled to or configured to be coupled to one or more antennas, or multiple transmitters or receivers of wired communication interfaces.

[0073] As used herein, the term "circuit" refers to all of the following: (a) hardware circuit implementations only, such as implementations in analog and / or digital circuits only, and (b) combinations of circuits and software (and / or firmware), such as (if applicable): (i) combinations of (multiple) processors or (ii) portions of (multiple) processors / software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device to perform various functions, and (t) circuits, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software or firmware to operate, even if the software or firmware is not physically present. This definition of circuit applies to all uses of the term in this application. As another example, as used herein, the term "circuit" will also cover implementations of processors (or multiple processors) or portions of processors and their accompanying software and / or firmware only. The term "circuit" will also cover, for example (if applicable) baseband integrated circuits or application processor integrated circuits for mobile devices, or similar integrated circuits in sensors, cellular network devices, or other network devices.

[0074] Although the subject matter has been described in language specific to structural features and / or actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary embodiments for implementing the claims, and other equivalent features and actions are intended to fall within the scope of the claims.

[0075] It should be understood that the above benefits and advantages may relate to one example embodiment or several example embodiments. The example embodiments are not limited to embodiments that solve any or all of the above problems or have any or all of the above benefits and advantages. It will also be understood that references to items may refer to one or more of these items.

[0076] The blocks or operations of the methods or functions described herein can be performed in any suitable order, or simultaneously where appropriate. Furthermore, individual blocks or operations can be removed from any method without departing from the scope of the subject matter described herein. Aspects of any of the example embodiments described above can be combined with aspects of any other example embodiments described to form further example embodiments without losing the desired effect.

[0077] It should be understood that the above description is given by way of example only, and various modifications can be made by those skilled in the art. The above specification, example embodiments, and data provide a complete description of the structure and use of exemplary embodiments. Although various example embodiments have been described above with a degree of specificity or by reference to one or more individual embodiments, many changes can be made to the disclosed example embodiments by those skilled in the art without departing from the scope of this specification.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory including computer program code; The at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least the following: Detect the events that trigger the report; In response to detecting the event, determine whether the reporting condition is met; in response to the reporting condition being met, start a timer; and In response to the timer expiring, determine whether to discard or cancel the event-triggered report.

2. The apparatus of claim 1, wherein the timer is associated with an event-triggered channel state information report.

3. The apparatus of claim 1 or 2, wherein the reporting condition is available at least after a period of time has elapsed following the transmission of another report associated with the reference signal and / or before the transmission of another report associated with the reference signal, wherein the detected event is associated with the reference signal.

4. The apparatus of claim 3, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to further perform: The time period is obtained from network devices, from a specification definition, or as a hard-coded time period.

5. The apparatus according to claim 3 or 4, wherein, The time period is specified or configured based on at least one of the following: time, number of reporting opportunities, number of reporting instances, number of reporting opportunities per unit time, number of reporting instances per unit time, number of uplink signals requesting resources per unit time, or number of uplink signals indicating events per unit time.

6. The apparatus according to any one of claims 1 to 5, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to further perform: After the timer is started, it is determined whether the stop condition or cancellation condition has been met; In response to the stopping condition being met, the timer is stopped, and The timer is cancelled in response to the cancellation condition being met.

7. The apparatus according to claim 6, wherein, The stopping condition is at least one of the following: a new timer is started for the same event, a report triggered by the event is transmitted, and a response to the transmitted report is received.

8. The apparatus according to any one of claims 1 to 7, wherein, The timer is configured based on at least one of the following: time, number of reporting opportunities, number of reporting instances, number of reporting opportunities per unit time, number of reporting instances per unit time, number of uplink signals requesting resources per unit time, or number of uplink signals indicating events per unit time.

9. The apparatus according to any one of claims 1 to 8, wherein, The report that determines the event to be discarded includes at least one of the following: Determine that measurements will not be performed on reports triggered by the aforementioned event; Determine not to generate a report triggered by the event; as well as Determine to discard the report triggered by the generated event.

10. The apparatus according to any one of claims 1 to 9, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to further perform: The timer value is obtained from the network device, from the specification definition, or as a hard-coded value.

11. The apparatus according to any one of claims 1 to 10, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to further perform: The timer is started in response to at least one of the following: Transmit uplink channel, or transmit uplink resources for a report triggered by the event, or a signal that triggers the report triggered by the event. Generate and transmit the event-triggered report.

12. The apparatus according to any one of claims 1 to 11, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to further perform: In response to the reporting conditions not being met, it is determined to discard or cancel the report triggered by the event.

13. A computer-implemented method, comprising: Detect the events that trigger the report; In response to the detection of the event, determine whether the reporting conditions have been met; In response to the reporting condition being met, a timer is started; as well as In response to the timer expiring, determine whether to discard or cancel the report triggered by the event.

14. A computer-readable medium comprising program instructions for causing a device to execute at least the following: Detect the events that trigger the report; In response to the detection of the event, determine whether the reporting conditions for reporting are met; In response to the reporting condition being met, a timer is started; as well as In response to the timer expiring, determine whether to discard or cancel the event-triggered report.

15. A computer program comprising instructions for causing a device to perform at least the following operations: Detect the events that trigger the report; In response to the detection of the event, determine whether the reporting conditions for reporting are met; In response to the reporting condition being met, a timer is started; as well as In response to the timer expiring, determine whether to discard or cancel the event-triggered report.

Images