Measurement reporting delay

A timer-based mechanism for event instance detection in UEIBM addresses measurement reporting delays, ensuring timely and reliable beam reporting, thus improving network performance.

WO2026239185A1PCT designated stage Publication Date: 2026-11-19NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/053999
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-16
Filing Date
2026-04-22
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing technologies lack clear definitions for measurement reporting delay in user equipment-initiated beam management (UEIBM), leading to potential delays and outdated reports, which can impact beam switching efficiency and network performance.

Method used

Implement a timer-based mechanism for event instance detection, where a first timer is started upon meeting a reporting condition, and a message is transmitted after a certain number of event instances are reached, defining the delay requirement as the time between the condition being met and the message transmission.

Benefits of technology

This approach provides consistent and accurate measurement reporting delays, ensuring timely and reliable beam reporting, thereby enhancing network performance and reducing latency in UEIBM.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026053999_19112026_PF_FP_ABST
    Figure IB2026053999_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Example embodiments of the present disclosure are directed to measurement reporting delay. A method comprises in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, start a first timer for the event instance detection of the reference signal of the beam; in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and causing a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.
Need to check novelty before this filing date? Find Prior Art

Description

MEASUREMENT REPORTING DELAYCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from, and the benefit of, India Patent Application No.202541047395, filed May 16, 2025, the contents of which are hereby incorporated by reference in their entirety.FIELD

[0002] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for measurement reporting delay.BACKGROUND

[0003] Some use cases where UE may benefit from initiating the user equipment-initiated beam management (UEIBM) reporting are being identified, e.g., to facilitate beam switch. The UEIBM feature may refer to the case where the UE may be configured with at least one event / condition and then the UE may start beam reporting if this at least one event / condition occurs or is satisfied.SUMMARY

[0004] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, start a first timer for the event instance detection of the reference signal of the beam; in accordance with a certain number of event instances being reached, transmit, to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and cause a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0005] In a second aspect of the present disclosure, there is provided a method. The method comprises: in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, starting a first timer for the event instance detection of the reference signal of the beam; in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and causing a time period, between a time point at which the reporting condition is met and a further time point at which themessage is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0006] In a third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, starting a first timer for the event instance detection of the reference signal of the beam; means for in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and means for causing a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0007] In a fourth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the second aspect.

[0008] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Some example embodiments will now be described with reference to the accompanying drawings, where:

[0010] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

[0011] FIGS. 2A-2D illustrates different scenarios of a measurement reporting delay;

[0012] FIG. 3 illustrates an example process of event-triggering reporting in accordance with some example embodiments of the present disclosure;

[0013] FIG. 4 illustrates an example process of event-triggering reporting in accordance with some example embodiments of the present disclosure;

[0014] FIG. 5 illustrates an example process of event-triggering reporting in accordance with some example embodiments of the present disclosure;

[0015] FIG. 6 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0016] FIG. 7 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0017] FIG. 8 illustrates a flowchart of a method implemented at a first apparatus in accordance withsome example embodiments of the present disclosure;

[0018] FIG. 9 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

[0019] FIG. 10 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0020] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION

[0021] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

[0022] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0023] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0024] It shall be understood that although the terms “first,” “second,”..., etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0025] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0026] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.

[0027] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0028] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) and(b) combinations of hardware circuit(s) and software, such as (as applicable):(i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and (ii) any or all portions of hardware processor(s) (including digital and / or quantum signal processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions) and(c) any or all portions of hardware circuit(s), such as a microprocessor(s), processor(s), and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0029] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0030] As used herein, the term “network device” refers to a node in a communication network viawhich a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (I AB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

[0031] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0032] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmissionresource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0033] FIG. 1 illustrates an example communication network 100 in which example embodiments of the present disclosure can be implemented. As shown in FIG. 1 , the communication network 100 may comprise a first apparatus 110 which may also be, for example, referred to as a terminal device or a UE.

[0034] The communication network 100 may further comprise a second apparatus 120, which may be, for example, considered as being a network device or being included in a network device. In some example embodiments, the network device may be discussed as a BS, a gNB, or an eNB.

[0035] A serving area provided by the second apparatus 120 is called a cell. The second apparatus 120 may provide one or more cells serving the first apparatus. For example, the first apparatus 110 may communicate with the second apparatus 120 within the cell 102. In some scenarios, the cell 102 may be considered as a cell that is serving the first apparatus 110.

[0036] In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 110 operating as a terminal device and the second apparatus 120 operating as a network device. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.

[0037] In some example embodiments, if the first apparatus 110 is a terminal device and second apparatus 120 is a network device, a link from the second apparatus 120 to first apparatus 110 is referred to as a downlink (DL), while a link from the first apparatus 110 to second apparatus 120 is referred to as an UL. In DL, the second apparatus 120 is a transmitting (TX) apparatus (or a transmitter) and the first apparatus 110 is a receiving (RX) apparatus (or a receiver). In UL, the first apparatus 110 is a TX apparatus (or a transmitter) and the second apparatus 120 is an RX apparatus (or a receiver).

[0038] It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the second apparatus 120 may be another device than a network device. Although illustrated as a terminal device, the first apparatus 110 may be another device than a terminal device.

[0039] In the following, for the purpose of illustration, some example embodiments are describedwith the first apparatus 110 operating as a UE and the second apparatus 120 operating as a base station. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.

[0040] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0041] Enhancement to facilitate UE-initiated / event-driven beam management is specified for reducing overhead and / or latency, assuming the unified transmission configuration indicator (TCI) while leveraging (as much as possible) channel state information (CSI) measurement and reporting configuration frameworks, targeting frequency range 2 (FR2) and s-transmission reception point (TRP) with intra- and inter-cell beam management, which may include UL signaling content(s) (and procedure(s) as required) for UE-initiated / event-driven beam reporting facilitating fast beam switching and UL signaling medium / container considering the UE-initiated / event-driven nature of the UL transmission, designed primarily for the purpose of beam reporting.

[0042] Some events, which may cause a UE to initiate a beam report, have been agreed, for example, which may include Event 2, Event 1 and Event 7. Event 2 may refer to the quality of at least one new beam, such as layer 1 -reference signal received power (L1-RSRP), becoming a threshold value better than the current beam. Event 1 may refer to the quality of the current beam being worse than a certain threshold. Event 7 may refer to the quality of at least one new beam, such as L1-RSRP, becoming a threshold value better than the reference signal (RS) derived from the activated TCI state with the Q-th best quality.

[0043] For the triggering event determination, two options have been defined. Regarding the basic functionality, as soon as there is an event instance, for example with Event-2 once the L1-RSRP of the new beam becomes a threshold value better than the current beam, UE initiated beam report occurs.

[0044] Regarding UE capability, if within a measurement window (which is configurable), the number of event instance(s) for at least one same new beam is greater than or equal to a configurable numberM, UE initiated beam report occurs.

[0045] Two variants, i.e., mode A and mode B, have been defined for the actual beam report procedure.o Mode A (dynamically scheduling uplink control information (UCI) by gNB):■ Step 1 : UE transmits a first physical uplink control channel (PUCCH) (one-bit / multi- bit) to request a resource for a second UL channel to carry beam report■ Step 2: UE detects the downlink control information (DCI) format to indicate a resource for a second UL channel to carry beam report.■ Step 3: Beam report is transmitted in second UL channel.■ This mode is basic UE capability (i.e., all UE supporting UE-initiated / event-driven beam reporting should support this feature).o Mode B (UCI in pre-configured resource(s) for second UL channel):■ Step 1 : UE transmits a first PUCCH (one-bit / m u Iti- bit) notifying a second UL channel to carry beam report■ Step 2: UE transmits the beam report in the second UL channel.■ The notification in Step 1 is in a separate reporting instance from the beam report in Step 2.

[0046] In both these modes, when the event condition is met, the UE transmits a first PUCCH.

[0047] In case of mode A, at the gNB, reception of the first PUCCH implies that the UE is asking for resources on the uplink to transmit the beam report.

[0048] In case of mode B, at the gNB, reception of the first PUCCH implies that the UE shall be transmitting the beam report on the uplink resources reserved for the beam report.

[0049] In the context of what to report, i.e., the UL signal content of the UEIBM report with Event-2 with L1-RSRP as quality metric, it has been agreed that the UE reports N beams, for example the top N beams, with N> 1 configured by the network via radio resource control (RRC), and at least one of those N beams satisfies the triggering event. Then, in addition to those N beams, the network may configure via RRC the UE to also report the current beam, where the current beam is associated to the indicated TCI state. It has not been finalized yet how the UEIBM report will be with Event-1 and Event-7, but the current assumption is that Event-2 design is going to be reused as much as possible, and probably just few modifications will be introduced, for example:• For Event-1 , the current beam is always reported.• For Event-7, instead of reporting the current beam the UE reports the beam associated to the activated TCI state with the Q-th best quality.

[0050] In the context of the window based approach, having a semi-sliding window has been agreed. Regarding triggering event determination for Event 2, on the measurement window for initiating the UE-initiated / event-driven beam reporting procedure, support Option-4.• Option-4: If an Event-2 instance for a new beam is obtained at the time t and the timer for the new beam is not running, UE starts the timer for the new beam, where the expiry time of the timer is equal to the NW-configured length of the time window (T_window)o Note: Timer is new beam specific.• Note: T_window is the agreed time window parameter for measurement.• Introduce separate UE capability to limit the number of timers. There is only 1 timer per new beam.

[0051] Reporting delay for the event-triggered UEIBM reporting without the window approach has been discussed. The delay within which the UE may be able to send the report after the reporting condition becomes met may need to be defined.

[0052] Summarized, the reporting delay when window / timer is not configured is the time from when the reporting condition becomes met over the air (i.e., signal level(s) of serving or candidate cell change so that the condition becomes met), until the UE sends the first PUCCH to request or inform about reporting. The delay consists of:• T_L1_measurement_period, which is the time from when the reporting condition becomes met over the air until the UE realizes the condition is met based on measurements (i.e. time until the first measurement occasion based on which the UE realizes report has to be triggered).• T_first_UL_channel, which is the time from UE realizing the reporting condition is met until the UE sends the first PUCCH.

[0053] Discussions are ongoing on how to define the measurement reporting delay in the case of UEIBM. For example, there were discussions on whether to define measurement reporting delay requirements only for the one-shot measurement case or to cover the window based UEI beam reporting scenario as well.

[0054] In the case of defining measurement reporting delay for a window-based event triggering determination, there can be different variants to this reporting delay as illustrated in FIG. 2A and FIG.2B. (Here the number of event instances is assumed to be L=3 for the event triggering condition to be satisfied and the same definition of measurement reporting delay as currently defined for non-window based UEI beam reporting is assumed). As an example, as shown in FIG. 2A, 3 event instances occur before the first PUCCH (at TO), in this situation, the measurement reporting delay may be considered as being from the time that the event is met over the air to the point when the UE transmits a first PUCCH. As another example, as shown in FIG. 2A, the number of event instances (e.g., 3) are not reached before the first PUCCH (at TO), in this situation, the measurement reporting delay may be considered as being from the time that the event is met over the air to the point when the UE transmits a first PUCCH (at T1) after the number of event instances (e.g., 3) are reached.

[0055] This measurement reporting delay in turn has multiple components such as the evaluation delay, the time to determine that L number of event instances have occurred within a time window to satisfy the event triggering condition and the time the UE transmits the 1stPUCCH. As shown in FIG.2C, T_evaluation_delay may be defined as time between the event that will trigger the report becoming met + the measurement that defines that condition is met and starts the window timer.T_time_until_L_samples may represent the delay until L measurement occasions have fulfilled reporting condition. T_UL_delay may represent the time from the time instant where L measurements have fulfilled reporting criteria until the UE sends the first PUCCH. L may represent the number of event instances that need to occur for the same new beam for the event triggering condition to be satisfied.

[0056] In addition to the scenarios shown in FIGS. 2A and 2B, there is also a scenario shown in FIG.2D. Here the UE has started a timer (TO) at time instance ti for a beam but the event triggering condition is not satisfied till the timer expiry. Instead, while the timer TO is running, the event condition is again met over the air at t2. Since only one timer per beam can be running at a given instance of time, the UE needs to wait till the expiry of timer TO before it can start another timer T1 for a new window when an event instance occurs at ts. In such a case, from when the measurement reporting delay starts is still unclear.

[0057] In accordance with some example embodiments of the present disclosure, there is provided a solution for measurement reporting delay. In this solution, if a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met and no timer being running for an event instance detection of the reference signal of the beam, the first apparatus 110 starts a first timer for the event instance detection of the reference signal of the beam. If a certain number of event instances are reached, the first apparatus 110 transmits, to a second apparatus 120, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached. Then the first apparatus 110 causes a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0058] As a further alternative, if a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, the first apparatus 110 starts a first timer for an event instance detection of the reference signal of the beam. If a certain number of event instances are reached before an expiry of the first timer, the first apparatus 110 transmits, to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached. Then the first apparatus 110 causes a time period, between a time point at which the first timer starts and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0059] As another alternative, if a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met for the first time, the first apparatus 110 starts a first timer for an event instance detection of the reference signal of the beam. If a certain number of event instances are not reached before an expiry of the first timer, the first apparatus 110 starts a second timer for the event instance detection of the reference signal of the beam. If the certain number ofevent instances are reached before an expiry of the second timer, the first apparatus 110 transmits, to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached. Then the first apparatus 110 causes a time period, between a time point at which the first timer expires, or the reporting condition associated with the event-triggered reporting for the beam is met again and a time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0060] In this way, the maximum delay, that can be expected by the network for a UE to realize that an event has occurred and indicate the occurrence of the event to the network, can be defined. These minimum requirements may be used for UE conformance testing. Without such requirements, a poor UE implementation may result in extremely outdated reports being sent to the network.

[0061] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0062] FIGS. 3-5 illustrate different scenarios of event-triggering reporting process in accordance with some example embodiments of the present disclosure. With reference to FIGS. 3-5, different options of measurement reporting delay will be described in detail.

[0063] In some embodiments, the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met for the first time, may be considered as being the starting point of the measurement reporting delay. Hereinafter, a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met may be considered as the event condition being met over the air.

[0064] As an example shown in FIG. 3, after the event condition for a beam is met over the air, the first timer may start. The first apparatus 110 may detect the event instance for a reference signal of the beam within the time window 301 of the first timer, to determine whether a certain number (e.g., L=3) of event instances occur within this time window 301.

[0065] If the certain number (e.g., L=3) of event instances are not reached within this time window 301, for example, as shown in FIG. 3, only 2 event instances 311 and 312 occur within this time window 301.

[0066] At the end of the time window 301 , the first timer expires. The second timer may start, e.g., for detecting the event instance for a reference signal of the same beam. As shown in FIG. 3, 3 event instances 321 , 322 and 323 occur within this time window 302. Upon detecting the event instance 323, the first apparatus 110 may determine that the certain number (e.g., L=3) of event instances are reached and the event-triggered reporting may be triggered. Then the first apparatus 110 may send a message 331 associated with the event-triggered reporting in the first PUCCH after the certain number of event instances are reached. The content of message may depend on whether the Mode A or Mode B of the event-triggered reporting is applied.

[0067] As described above, the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, may be considered as being the starting point of the measurement reporting delay. In this case, the time period 340 between the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, and the further time point, when the message 331 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0068] As another example shown in FIG. 4, after the event condition for a beam is met over the air, the first timer may start. The first apparatus 110 may detect the event instance for a reference signal of the beam within the time window 401 of the first timer, to determine whether a certain number (e.g., L=3) of event instances occur within this time window 401.

[0069] If the certain number (e.g., L=3) of event instances 411, 412 and 413 are reached within this time window 401, for example, as shown in FIG. 4, upon detecting the event instance 413, the first apparatus 110 may determine that the certain number (e.g., L=3) of event instances are reached and the event-triggered reporting may be triggered. Then the first apparatus 110 may send a message 421 associated with the event-triggered reporting in the first PUCCH after the certain number of event instances are reached.

[0070] In this case, the time period 430 between the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, and the further time point, when the message 412 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0071] The solution described above may be considered as the simplest way of defining the measurement reporting delay requirements options if the same baseline for measurement reporting delay as that of the non-window based approach is used but may in effect reflect a really long delay when the delay includes also timers / windows within which the certain number of event instances are not fulfilled.

[0072] In some other embodiments, the measurement reporting delay may be defined as the time from starting the timer within which the certain number (e.g., L=3) of event instances occur until the first apparatus 110 sends the first PUCCH. That is, the delay only takes into account the timer / window based on which the reporting is triggered.

[0073] In this case, as shown in FIG. 3, as described above, the certain number (e.g., L=3) of event instances 321, 322 and 323 are reached within the time window 302 of the second timer. Therefore, the time period between the time point, when the second timer starts and the further time point, when the message 331 associated with the event-triggered reporting is transmitted in the first PUCCH, maybe considered as being a measurement reporting delay for the event-triggered reporting.

[0074] As shown in FIG. 4, as described above, the certain number (e.g., L=3) of event instances 411, 412 and 413 are reached within the time window 401 of the first timer. Therefore, the time period between the time point, when the first timer starts and the further time point, when the message 421 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0075] This solution described above may be considered as a new way of defining the measurement reporting delay and is not affected by when the event condition is met over the air. Using the start of the timer as the start of the delay requirement where the delay only takes into account the timer / window based on which the reporting is triggered is an accurate way of defining and testing the UE behavior in a window based approach.

[0076] In some other embodiments, the measurement reporting delay may be defined as the time from a reporting condition becoming met if a timer is not already running, or an expiration of a (previous) timer if a timer is already running, until the UE sends the first PUCCH based on the certain number (e.g., L=3) of event instances occurring within a timer.

[0077] In this situation, for a case where the starting point of measurement reporting delay relates to the reporting condition becoming met if a timer is not already running. As shown in FIG. 3, when the event condition is met over the air, there is no timer running. Therefore, the time period 340 between the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, and the further time point, when the message 331 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0078] As shown in FIG. 4, when the event condition is met over the air, there is no timer running. Therefore, the time period 430 between the time point, when a reporting condition associated with an event-triggered reporting for a reference signal of a beam is met, and the further time point, when the message 412 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0079] For a case where the starting point of measurement reporting delay relates to an expiration of a (previous) timer, as shown in FIG. 3, the first timer expires and the certain number of event instances are reached within the time window 302 of the second timer which starts after the expiration of the first timer. In this case, the time period 350 between the time point, when the first timer expries, and the further time point, when the message 412 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0080] The measurement reporting delay may vary depending on whether the timer is running ornot. If the timer is not running when the event condition is met over the air, the reporting delay is same as embodiments described as above. But this option is advantageous when a timer is running and the event condition is met as the resulting measurement reporting delay is shorter. Furthermore, this option takes into account a UE implementation where the UE would re-evaluate whether the condition is still met after the first timer expires (i.e., UE does not consider previous measurements to define whether to restart the timer).

[0081] In yet other embodiments, if a reporting condition is again met while a timer (e.g., the first timer) is running, the measurement reporting delay may be defined as the time from the 2ndreporting condition until the first apparatus 110 sends the first PUCCH based on the certain number (e.g., L=3) of event instances occurring within a timer (e.g., the second timer) which is started after the expiry of the first timer. This measurement reporting delay is valid if the triggering condition is not met when the first timer was running and the reporting condition was met the first time.

[0082] As an example shown in FIG. 5, after the event condition for a beam is met over the air, e.g., for the first time, the first timer may start. The first apparatus 110 may detect the event instance for a reference signal of the beam within the time window 501 of the first timer, to determine whether a certain number (e.g., L=3) of event instances occur within this time window 501.

[0083] If the certain number (e.g., L=3) of event instances are not reached within this time window 501, for example, as shown in FIG. 5, only 2 event instances 511 and 512 occur within this time window 501.

[0084] When the first timer is running, the event condition for the beam is met over the air, e.g., for the second time, the second timer may start only after an expiry of the first timer.

[0085] At the end of the time window 501, the first timer expires and the certain number of event instances do not occur. The second timer may start, e.g., for detecting the event instance for a reference signal of the same beam.

[0086] As shown in FIG. 5, 3 event instances 521, 522 and 523 occur within this time window 502. Upon detecting the event instance 523, the first apparatus 110 may determine that the certain number (e.g., L=3) of event instances are reached and the event-triggered reporting may be triggered. Then the first apparatus 110 may send a message 531 associated with the event-triggered reporting in the first PUCCH after the certain number of event instances are reached. The content of message may depend on whether the Mode A or Mode B of the event-triggered reporting is applied.

[0087] In this case, the time period 540 between the time point, when a reporting condition associated with an event-triggered reporting for the reference signal of the beam is met again (i.e., not for the first time), and the further time point, when the message 531 associated with the event-triggered reporting is transmitted in the first PUCCH, may be considered as being a measurement reporting delay for the event-triggered reporting.

[0088] This solution may provide the most accurate reporting delay if the same baseline for measurement reporting delay as that of the non-window based approach is used.

[0089] FIG. 6 shows a flowchart of an example method 600 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0090] At block 610, in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, at block 620, the first apparatus 110 starts a first timer for the event instance detection of the reference signal of the beam.

[0091] At block 630, in accordance with a certain number of event instances being reached, at block 640, the first apparatus 110 transmits to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached.

[0092] At block 650, the first apparatus 110 causes a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0093] In some example embodiments, the reporting condition associated with the event-triggered reporting is met for the first time.

[0094] In some example embodiments, the certain number of event instances are reached before an expiry of the first timer.

[0095] In some example embodiments, the method 600 further comprises: in accordance with the certain number of event instances being not reached before an expiry of the first timer, starting a second timer for the event instance detection of the reference signal of the beam after the expiry of the first timer.

[0096] In some example embodiments, the certain number of event instances are reached before an expiry of the second timer.

[0097] In some example embodiments, the second timer starts when the reporting condition associated with the event-triggered reporting for the beam is met again.

[0098] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0099] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0100] FIG. 7 shows a flowchart of an example method 700 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0101] At block 710, in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met, at block 720, the first apparatus 110 starts a first timer for an event instance detection of the reference signal of the beam.

[0102] At block 730, in accordance with a certain number of event instances being reached before an expiry of the first timer, at block 740, the first apparatus 110 transmits to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached.

[0103] At block 750, the first apparatus 110 causes a time period, between a time point at which the first timer starts and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0104] In some example embodiments, the reporting condition associated with the event-triggered reporting is met for the first time.

[0105] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam was met before.

[0106] In some example embodiments, the method 700 further comprises: in accordance with a determination that the reporting condition associated with the event-triggered reporting for the beam was met, starting a second timer for the event instance detection of the reference signal of the beam; and in accordance with a determination that the certain number of event instances were not reached before an expiry of the second timer and the reporting condition associated with the event-triggered reporting for the beam is met, starting the first timer for the event instance detection of the reference signal of the beam after the second time expires.

[0107] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam is met before or after the expiry of the second timer.

[0108] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0109] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0110] FIG. 8 shows a flowchart of an example method 800 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0111] At block 810, in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met for the first time, at block 820, the first apparatus 110 starts a first timer for an event instance detection of the reference signal of the beam.

[0112] At block 830, in accordance with a certain number of event instances being not reached before an expiry of the first timer, at block 840, the first apparatus 110 starts a second timer for theevent instance detection of the reference signal of the beam.

[0113] At block 850, in accordance with the certain number of event instances being reached before an expiry of the second timer, at block 860, the first apparatus 110 transmits to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached.

[0114] At block 870, the first apparatus 110 causes a time period, between a time point at which the first timer expires, or the reporting condition associated with the event-triggered reporting for the beam is met again and a time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0115] In some example embodiments, the method 800 further comprises: in accordance with a certain number of event instances being not reached before an expiry of the first timer and the reporting condition associated with the event-triggered reporting for the beam is met again, starting the second timer.

[0116] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam is met again before the expiry of the first timer.

[0117] In some example embodiments, the method 800 further comprises: suspending a start of the second timer until the expiry of the first timer.

[0118] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0119] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0120] In some example embodiments, a first apparatus capable of performing any of the method 600 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0121] In some example embodiments, the first apparatus comprises in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, starting a first timer for the event instance detection of the reference signal of the beam; means for in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and means for causing a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0122] In some example embodiments, the reporting condition associated with the event-triggered reporting is met for the first time.

[0123] In some example embodiments, the certain number of event instances are reached before an expiry of the first timer.

[0124] In some example embodiments, the first apparatus further comprises: means for in accordance with the certain number of event instances being not reached before an expiry of the first timer, starting a second timer for the event instance detection of the reference signal of the beam after the expiry of the first timer.

[0125] In some example embodiments, the certain number of event instances are reached before an expiry of the second timer.

[0126] In some example embodiments, the second timer starts when the reporting condition associated with the event-triggered reporting for the beam is met again.

[0127] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0128] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0129] In some example embodiments, a first apparatus capable of performing any of the method 700 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0130] In some example embodiments, the first apparatus comprises means for in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met, starting a first timer for an event instance detection of the reference signal of the beam; means for in accordance with a certain number of event instances being reached before an expiry of the first timer, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and means for causing a time period, between a time point at which the first timer starts and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0131] In some example embodiments, the reporting condition associated with the event-triggered reporting is met for the first time.

[0132] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam was met before.

[0133] In some example embodiments, the first apparatus further comprises: means for inaccordance with a determination that the reporting condition associated with the event-triggered reporting for the beam was met, starting a second timer for the event instance detection of the reference signal of the beam; and means for in accordance with a determination that the certain number of event instances were not reached before an expiry of the second timer and the reporting condition associated with the event-triggered reporting for the beam is met, starting the first timer for the event instance detection of the reference signal of the beam after the second time expires.

[0134] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam is met before or after the expiry of the second timer.

[0135] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0136] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0137] In some example embodiments, a first apparatus capable of performing any of the method 800 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0138] In some example embodiments, the first apparatus comprises means for in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met for the first time, starting a first timer for an event instance detection of the reference signal of the beam; means for in accordance with a certain number of event instances being not reached before an expiry of the first timer, starting a second timer for the event instance detection of the reference signal of the beam; means for in accordance with the certain number of event instances being reached before an expiry of the second timer, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; and means for causing a time period, between a time point at which the first timer expires, or the reporting condition associated with the event-triggered reporting for the beam is met again and a time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

[0139] In some example embodiments, the first apparatus further comprises: means for in accordance with a certain number of event instances being not reached before an expiry of the first timer and the reporting condition associated with the event-triggered reporting for the beam is met again, starting the second timer.

[0140] In some example embodiments, the reporting condition associated with the event-triggered reporting for the beam is met again before the expiry of the first timer.

[0141] In some example embodiments, the first apparatus further comprises: means for suspending a start of the second timer until the expiry of the first timer.

[0142] In some example embodiments, the event-triggered reporting is a user equipment initiated beam management, UEIBM, reporting.

[0143] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0144] FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing example embodiments of the present disclosure. The device 900 may be provided to implement a communication device, for example, the first apparatus 110 as shown in FIG. 1. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 940 coupled to the processor 910.

[0145] The communication module 940 is for bidirectional communications. The communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 940 may include at least one antenna.

[0146] The processor 910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0147] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 924, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 922 and other volatile memories that will not last in the power-down duration.

[0148] A computer program 930 includes computer executable instructions that are executed by the associated processor 910. The instructions of the program 930 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 930 may be stored in the memory, e.g., the ROM 924. The processor 910 may perform any suitable actions and processing by loading the program 930 into the RAM 922.

[0149] The example embodiments of the present disclosure may be implemented by means of theprogram 930 so that the device 900 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 8. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0150] In some example embodiments, the program 930 may be tangibly contained in a computer readable medium which may be included in the device 900 (such as in the memory 920) or other storage devices that are accessible by the device 900. The device 900 may load the program 930 from the computer readable medium to the RAM 922 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e. , tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0151] FIG. 10 shows an example of the computer readable medium 1000 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1000 has the program 930 stored thereon.

[0152] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0153] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machineexecutable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0154] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to aprocessor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0155] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0156] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0157] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable subcombination.

[0158] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, start a first timer for the event instance detection of the reference signal of the beam;in accordance with a certain number of event instances being reached, transmit, to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; andcause a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

2. The first apparatus of claim 1, wherein the reporting condition associated with the event-triggered reporting is met for the first time.

3. The first apparatus of claim 1 or 2, wherein the certain number of event instances are reached before an expiry of the first timer.

4. The first apparatus of claim 1 or 2, wherein the first apparatus is caused to:in accordance with the certain number of event instances being not reached before an expiry of the first timer, start a second timer for the event instance detection of the reference signal of the beam after the expiry of the first timer.

5. The first apparatus of claim 4, wherein the certain number of event instances are reached before an expiry of the second timer.

6. The first apparatus of claim 4 or 5, wherein the second timer starts when the reporting condition associated with the event-triggered reporting for the beam is met again.

7. The first apparatus of any of claims 1-6, wherein the event-triggered reporting is a userequipment initiated beam management, UEIBM, reporting.

8. The first apparatus of any of claims 1-7, wherein the first apparatus comprises a terminal device and the second apparatus comprises a network device.

9. A method comprising:in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, starting a first timer for the event instance detection of the reference signal of the beam;in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; andcausing a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

10. A first apparatus comprising:in accordance with a reporting condition associated with an event-triggered reporting for a reference signal of a beam being met and no timer being running for an event instance detection of the reference signal of the beam, start a first timer for the event instance detection of the reference signal of the beam;means for in accordance with a certain number of event instances being reached, transmitting to a second apparatus, a message associated with the event-triggered reporting on the first uplink control channel after the certain number of event instances are reached; andmeans for causing a time period, between a time point at which the reporting condition is met and a further time point at which the message is transmitted, to be considered for a delay requirement of the event-triggered reporting.

11. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 4 or the method of claim 5 or the method of claim 9.