WO2025214632A1

WO2025214632A1 - Terminal capability consideration for terminal-initiated reporting

Info

Publication number: WO2025214632A1
Application number: PCT/EP2025/054088
Authority: WO
Inventors: Timo Koskela; Sami-Jukka Hakola; Juha Pekka Karjalainen
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2024-04-12
Filing date: 2025-02-14
Publication date: 2025-10-16
Anticipated expiration: 2026-10-12

Abstract

There are provided measures for terminal capability consideration for terminal-initiated reporting. Such measures exemplarily comprise indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, and determining at least one transmission related condition based on said time interval, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report.

Description

Title

TERMINAL CAPABILITY CONSIDERATION FOR TERMINAL-INITIATED REPORTING

Field

Various example embodiments relate to terminal capability consideration for terminal-initiated reporting. More specifically, various example embodiments exemplarily relate to measures (including methods, apparatuses and computer program products) for realizing terminal capability consideration for terminal-initiated reporting.

Background

The present specification generally relates to reporting related to radio conditions experienced by terminals, mobile stations, modems, or user equipments (UE), such as a smartphone, and the like.

Such reporting may for example be channel state information (CSI) reporting, layer 1 reporting, reporting of layer 1 measurements, beam reporting, and the like.

Such reporting may for example relate to multiple input multiple output (MIMO) / beam management (BM). Alternatively, or additionally, such reporting may relate to L1/L2 triggered mobility (LTM). LTM may refer to Layer 2 Mobility, Lower Layer Triggered Mobility, L1/L2 centric Mobility.

Such reporting may in general be periodic reporting, were a terminal (always) repeatedly measures a reference signal and periodically reports in predetermined periodic radio resources irrespective of whether reporting was actually necessary (i.e., irrespective of whether there are e.g. changes in a radio condition experienced), aperiodic reporting, where a terminal, once it is triggered to report, measures a reference signal and reports once, and semi- persistent reporting, where a terminal, once it is triggered to report, repeatedly measures a reference signal and periodically reports in predetermined periodic radio resources until it is released from reporting (i.e., semi-persistent reporting is a kind of mix of periodic and aperiodic reporting).

On the other hand, such reporting may be terminal-initiated, e.g. event- driven, where the event may be detection of a predetermined condition.

For such terminal-initiated reporting, the terminal must be provided/scheduled with resources enabling the terminal to actually transmit the data to be reported.

Such resource scheduling may be accompanied with resource waste and communication latency in case the terminal cannot for any reason keep up with the schedule, as scheduled resources are generally barred for other communication participants.

For the terminal-initiated reporting (UE event triggered transmission/reporting), the terminal could be configured with uplink (UL) resources to be used for requesting resources for event based reporting.

As an example, a terminal (e.g. UE) may be configured with a periodic UL resource allocation for reporting (e.g. for uplink control information (UCI) reporting), where the periodic UL resources can be used by the terminal upon providing an indication for resource usage (terminal indicates intention to use an occurrence of the periodic UL resources). The indication resource (i.e., the UL resource to be used for the terminal to provide an indication for resource usage (terminal indicates intention to use an occurrence of the periodic UL resources)) may be periodically available.

As another example, the terminal may be configured with a periodic UL resource for requesting resources for event based reporting (terminal- initiated reporting). The network may schedule UL resource for reporting upon receiving the indication/request from the terminal.

As another example, the terminal may be configured with a periodic UL resource for indicating that an event for reporting has been triggered.

In these options, the terminal may have specific computation time/processing capabilities associated with the reporting of an event triggered report in specific reporting configurations which may affect the network resource usage (in terms of configuration of resources) and terminal's capability to handle specific types of reporting and timelines. In this regard, it is noted that for an event triggered report to be actually reported, the event triggered report has to be generated/calculated/processed beforehand.

Hence, the problem arises that e.g. resource waste and communication latency are detrimental to operation of a mobile network both for the involved terminal itself but also for the overall network and affected other terminals.

Hence, there is a need to provide for terminal capability consideration for terminal-initiated reporting.

Various example embodiments aim at addressing at least part of the above issues and/or problems and drawbacks.

Various aspects of example embodiments are set out in the appended claims.

According to an exemplary aspect, there is provided an apparatus, comprising means for indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and means for determining at least one transmission related condition based on said time interval.

According to an exemplary aspect, there is provided an apparatus, comprising indicating circuitry configured to indicate a time interval required between a first terminal-initiated reporting related timing and a second terminal- initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining circuitry configured to determine at least one transmission related condition based on said time interval.

According to an exemplary aspect, there is provided an apparatus, comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining at least one transmission related condition based on said time interval.

According to an exemplary aspect, there is provided a method, comprising indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining at least one transmission related condition based on said time interval.

According to an exemplary aspect, there is provided a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method- related exemplary aspects of the present disclosure.

Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computerexecutable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.

Any one of the above aspects enables an efficient information derivation and/or exchange regarding the resources (to be) used by the terminal for the reporting to thereby solve at least part of the problems and drawbacks identified in relation to the prior art.

By way of example embodiments, there is provided terminal capability consideration for terminal-initiated reporting. More specifically, by way of example embodiments, there are provided measures and mechanisms for realizing terminal capability consideration for terminal-initiated reporting.

Thus, improvement is achieved by methods, apparatuses and computer program products enabling/realizing terminal capability consideration for terminal-initiated reporting. Brief description of the drawings

In the following, the present disclosure will be described in greater detail by way of non-limiting examples with reference to the accompanying drawings, in which

FIG. 1 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 2 is a block diagram illustrating an apparatus according to example embodiments,

FIG. 3 is a schematic diagram of a procedure according to example embodiments, and

FIG. 4 is a block diagram alternatively illustrating apparatuses according to example embodiments.

Detailed description

The present disclosure is described herein with reference to particular nonlimiting examples and to what are presently considered to be conceivable embodiments. A person skilled in the art will appreciate that the disclosure is by no means limited to these examples, and may be more broadly applied.

It is to be noted that the following description of the present disclosure and its embodiments mainly refers to specifications being used as non-limiting examples for certain exemplary network configurations and deployments. Namely, the present disclosure and its embodiments are mainly described in relation to 3GPP specifications being used as non-limiting examples for certain exemplary network configurations and deployments. As such, the description of example embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the disclosure in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized as long as compliant with the features described herein.

Hereinafter, various embodiments and implementations of the present disclosure and its aspects or embodiments are described using several variants and/or alternatives. It is generally noted that, according to certain needs and constraints, all of the described variants and/or alternatives may be provided alone or in any conceivable combination (also including combinations of individual features of the various variants and/or alternatives).

As used herein, "at least one of the following: <a list of two or more elements>" and "at least one of <a list of two or more elements>" 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.

According to example embodiments, in general terms, there are provided measures and mechanisms for (enabling/realizing) terminal capability consideration for terminal-initiated reporting.

Terminal-initiated reporting (or UE-initiated reporting or UE event driven reporting) provides advantages regarding resource utilization and configuration flexibility.

One example application of terminal-initiated reporting (or UE-initiated reporting or UE event driven reporting) is UE-initiated/event-driven beam management (MIMO/BM).

Advantageously, control thereof is facilitated leveraging (as much as possible) 3^rd Generation Partnership Project (3GPP) legacy CSI measurement and reporting configuration frameworks, targeting frequency range 1/2 (FR1/FR2) and single transmission/reception point (sTRP) with intra- and inter-cell beam management.

Furthermore, one of the objectives of 3GPP NR. Rel-release 19 mobility enhancements is to specify necessary components to support event triggered layer 1 (LI) measurement reporting (such as CSI reporting but not limited to it) for L1/L2 triggered mobility (LTM), which may be L1/L2 centric mobility, lower layer triggered mobility, L2 mobility.

Heretofore, uplink (UL) signaling content(s) (and procedure(s) as required) for UE-initiated/event-driven beam reporting facilitating fast beam switching and also UL signaling medium/container considering the UE-initiated/event- driven nature of the UL transmission, designed primarily for the purpose of beam reporting, are to be defined.

In this regard, in relation to MIMO/BM the following is conceivable:

For terminal-initiated reporting (or UE-initiated reporting or UE event driven reporting), a terminal/UE has to detect a trigger-event for beam reporting. In view thereof, the terminal/UE may monitor a reference signal (RS) (or a plurality of RSs) to assess if a beam-reporting trigger condition has been met.

Further, for terminal-initiated reporting (or UE-initiated reporting or UE event driven reporting), a terminal/UE has to transmit a beam-report, with the content of the beam report being indicative of the experienced radio condition, and with the signaling medium/container for beam report transmission being, for example, a medium access control control element (MAC-CE) or uplink control information (UCI).

UE-initiated/event-driven beam reporting may be implemented utilizing a concept according to which the UE requests UL resource(s) for the beam report (and the network grants/schedules such UL resource(s)), a concept according to which a UE notifies beforehand transmission of a beam report, a concept according to which a UE notifies that event has been triggered, and a concept where the network (e.g. a gNB) preconfigures UL resources for the UE's beam report.

As discussed above, reporting may be performed using periodic reporting, aperiodic reporting, and semi-persistent reporting.

These concepts are explained below with reference to layer 1 (LI) reference signal received power (RSRP) reporting according to a CSI framework.

As mentioned, such frameworks may be leveraged/utilized as much as possible also for terminal-initiated reporting (or UE-initiated reporting or UE event driven reporting). Leverage/utilization thereof as much as possible may be aimed for.

According to this framework, procedures on aperiodic CSI reporting assume that the CSI reporting is triggered by DCI format 0_l, but they equally apply to CSI reporting triggered by DCI format 0_2, by applying higher layer parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize. Procedures on aperiodic CSI reporting further assume that the CSI reporting is triggered by DCI format 0_l, but they equally apply to CSI reporting triggered by DCI format 0_3.

According to this framework, further, the time and frequency resources that can be used by the UE to report CSI are controlled by the gNB. CSI may consist of channel quality indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS/PBCH block resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), Ll-RSRP, Ll-SINR, Capabilityindex, or time-domain channel properties (TDCP).

According to this framework, further, each reporting setting CSI-ReportConfig is associated with a single downlink bandwidth part (BWP) (indicated by higher layer parameter BWP-Id) given in the associated CSI-ResourceConfig for channel measurement and contains the parameter(s) for one CSI reporting band: codebook configuration including codebook subset restriction, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configurations, and the CSI-related quantities to be reported by the UE such as the LI, Ll-RSRP, Ll-SINR, CRI, SSBRI, Capabilityindex, and TDCP.

According to this framework, further, the time domain behavior of the CSI- ReportConfig is indicated by the higher layer parameter reportConfigType and can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH'/'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset applies in the numerology of the UL BWP in which the CSI report is configured to be transmitted. The higher layer parameter reportQuantity indicates the CSI-related, Ll-RSRP-related, Ll- SINR-related, Capabilitylndex-related, or TDCP-related quantities to report.

According to this framework, further, each CSI resource setting CSI- ResourceConfig contains a configuration of a list of SSsl CSI resource sets (given by higher layer parameter csi-RS-ResourceSetList), where the list is comprised of references to either or both of NZP CSI-RS resource set(s) and SS/PBCH block set(s) or the list is comprised of references to CSI-IM resource set(s). Each CSI resource setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI resource settings linked to a CSI report setting have the same DL BWP.

As mentioned above, before an event triggered report can actually be reported, the event triggered report has to be generated/calculated/processed. As the terminal may have specific computation time/processing capabilities associated with the reporting of an event triggered report in specific reporting configurations, the terminal may potentially fail keeping up with a schedule not taking into account terminal's capabilities and restraints. This may result in resource waste and communication latency, as scheduled resources are generally barred for other communication participants, and only free/unscheduled/unused resources (resources that are known to be free/unscheduled/unused) may be scheduled by the network (e.g. gNB) for other purposes other than terminal-initiated reporting by the considered terminal.

Hence, in brief, according to example embodiments, a terminal (e.g. UE) may indicate (provide indication on) one or more capabilities.

According to example embodiments, the one or more capabilities include at least one of the following:

- a capability for a required time interval (e.g., a (substantially) minimum interval) between an UL signaling (a first UL signal) to request physical uplink resources and (a) correspondingly allocated resource(s) (second UL signal),

- a capability for a required time interval (e.g., a (substantially) minimum interval) between an UL signaling (first UL signal) to indicate/announce UL resource usage and (a) correspondingly allocated resource(s) (second UL signal), and

- a capability for a required time interval (e.g., a (substantially) minimum interval) between a downlink (DL) control message scheduling the second signal and the second signal (i.e., the correspondingly allocated resource(s)).

According to example embodiments, the indication and/or the network configuration comprises a signaling message including at least one of the following:

- a (required) time interval (e.g., a (substantially) minimum time interval) between the UL signal (first UL signal) requesting the UL resource for event based reporting, and the start of the reporting occasion (i.e., the UL resource (second UL signal)), and - a (required) time interval (e.g., a (substantially) minimum time interval) between the UL resource (first UL signal) indicating/announcing the use of (preconfigured) UL resource (second UL signal) for event based reporting associated with the request, and the start of the reporting occasion (i.e., the UL resource (second UL signal)), and

- a (required) time interval (e.g., a (substantially) minimum time interval) between the physical downlink control channel (PDCCH) allocating the UL resource (second UL signal) for event based reporting, and the start of the reporting occasion (i.e., the UL resource (second UL signal)).

According to example embodiments, each of the mentioned required time intervals may be a specific time interval associated with a specific reporting related parameter metric such as reference signal received power (R.SR.P) or a signal to interference plus noise ratio (SINR), to an event type, or to an amount of to be reported information (e.g. number of resource indicators).

According to further example embodiments, the UE (terminal) may receive a configuration of an actual (minimum) time interval (i.e., an actually configured time interval) between the first UL signal and the second UL signal that the UE can expect. The UE (terminal) may receive the configuration of an actual (minimum) time interval as a response to the indication. The configured time interval is at least the required time interval according to the terminal's indicated capability.

According to further example embodiments, the UE (terminal) may receive a configuration of a time interval between the first UL signal and the second UL signal that the UE can expect. The configured time interval may be at least the required time interval according to the terminal's indicated capability.

According to further example embodiments, the UE (terminal) may receive a configuration of a time interval between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing. In an example, the second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report. In an example the UE may determine at least one transmission related condition based on said time interval.

Example embodiments are specified below in more detail.

FIG. 1 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a terminal 10 such as a user equipment comprising means for indicating 11 and means for determining 12. The means for indicating 11 indicates a time interval required between a first terminal- initiated reporting related timing and a second terminal-initiated reporting related timing. Here, the second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report. Further, the first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report. The means for determining 12 determines at least one transmission related condition based on said time interval. FIG. 3 is a schematic diagram of a procedure according to example embodiments. The apparatus according to FIG. 1 may perform the method of FIG. 3 but is not limited to this method. The method of FIG. 3 may be performed by the apparatus of FIG. 1 but is not limited to being performed by this apparatus.

As shown in FIG. 3, a procedure according to example embodiments comprises an operation of indicating (S31) a time interval required between a first terminal-initiated reporting related timing and a second terminal- initiated reporting related timing (said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report), and an operation of determining (S32) at least one transmission related condition based on said time interval.

FIG. 2 is a block diagram illustrating an apparatus according to example embodiments. In particular, FIG. 2 illustrates a variation of the apparatus shown in FIG. 1. The apparatus according to FIG. 2 may thus further comprise means for receiving 21, means for transmitting 22, means for detecting 23, means for deciding 24, means for obtaining 25, means for conducting 26, and/or means for generating 27.

In an embodiment at least some of the functionalities of the apparatus shown in FIG. 1 (or 2) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

As an alternative to the operation of indicating (S31) a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, the procedure according to example embodiments may comprises an operation of receiving (for example, but not limited to, from a mobile network access entity (e.g. a base station, e.g. gNB)) a configuration indicative of a time interval between the first terminal-initiated reporting related timing and the second terminal-initiated reporting related timing. According to this alternative, the apparatus 10 may thus comprise, instead of or in addition to the means for indicating 11, means for receiving the configuration indicative of the time interval between the first terminal-initiated reporting related timing and the second terminal-initiated reporting related timing. Further, according to this alternative, the operation of determining (S32) the at least one transmission (e.g. reporting) related condition may be based on the time interval indicated by the received configuration. Further, according to this alternative, the procedure may additionally comprise performing at least one transmission based on the time interval indicated by the network. Further, according to this alternative, the procedure may additionally comprise performing at least one transmission based on the time interval configured by the network.

According to further example embodiments, said second terminal-initiated reporting related timing corresponds to uplink reporting resources to be used for said transmission of said radio condition report, and said first terminal- initiated reporting related timing precedes said uplink reporting resources to be used for transmission of said radio condition report and is associated with said uplink reporting resources to be used for transmission of said radio condition report.

According to further example embodiments, said second terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink reporting resources to be used for said transmission of said radio condition report or to a first or last symbol of a slot of said uplink reporting resources to be used for said transmission of said radio condition report.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a resource request for said transmission of said radio condition report.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said resource request.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink resources to be used for said resource request.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a transmission intention indication for said transmission of said radio condition report. According to further example embodiments, said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said transmission intention indication.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink resources to be used for said transmission intention indication.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a resource scheduling configuration for said transmission of said radio condition report.

According to further example embodiments, said resource scheduling configuration is a resource scheduling utilizing a physical downlink control channel.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to downlink resources to be used for said resource scheduling configuration.

According to further example embodiments, said first terminal-initiated reporting related timing corresponds to a first or last symbol of said downlink resources to be used for said resource scheduling configuration.

According to further example embodiments, said time interval is (substantially) equal to or larger than a required processing time interval required for generating said radio condition report.

According to further example embodiments, said time interval is specified in a number of symbols or slots or milliseconds.

According to a variation of the procedure shown in FIG. 3, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of receiving information indicative of a configured terminal-initiated reporting related time interval, wherein said configured terminal-initiated reporting related time interval is substantially equal to or larger than said time interval.

According to a variation of the procedure shown in FIG. 3, exemplary details of the indication operation (S31, indicating said time interval) are given, which are inherently independent from each other as such. Such exemplary indication operation (S31, indicating said time interval) according to example embodiments may comprise an operation of transmitting information indicative of said time interval. The operation of transmitting said information indicative of said time interval may transmit said information to a mobile network access entity (e.g. a base station, e.g. gNB). The operation of transmitting said information indicative of said time interval is, however, not limited to such transmission destination.

According to a variation of the procedure shown in FIG. 3, exemplary details of the determining operation (S32, determining said at least one transmission related condition) are given, which are inherently independent from each other as such. Such exemplary determining operation (S32, determining said at least one transmission related condition) according to example embodiments may comprise an operation of detecting a first occasion for terminal-initiated reporting, and an operation of deciding, if said time interval is not met with said first occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to withhold said transmission of said radio condition report.

According to a variation of the procedure shown in FIG. 3, exemplary details of the determining operation (S32, determining said at least one transmission related condition) are given, which are inherently independent from each other as such. Such exemplary determining operation (S32, determining said at least one transmission related condition) according to example embodiments may comprise an operation of detecting a second occasion for terminal-initiated reporting, and an operation of deciding, if said time interval is met with said second occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to perform said transmission of said radio condition report utilizing said second occasion for terminal-initiated reporting.

According to a variation of the procedure shown in FIG. 3, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of obtaining said time interval.

According to a variation of the procedure shown in FIG. 3, exemplary details of the obtaining operation (obtaining said time interval) are given, which are inherently independent from each other as such. Such exemplary obtaining operation according to example embodiments may comprise an operation of deciding said time interval based on at least one of the following: a configuration at said apparatus, or capabilities of said apparatus, or supported types of event based reporting supported by said apparatus, or processing capability of the apparatus.

According to a variation of the procedure shown in FIG. 3, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of receiving said configuration.

According to further example embodiments, said radio condition report is related to a first radio metric or to a second radio metric, and said time interval includes a first time interval valid for reporting related to said first radio metric, and a second time interval valid for reporting related to said second radio metric. According to further example embodiments, said radio condition report includes a first amount of information or a second amount of information, and said time interval includes a third time interval valid for said radio condition report including said first amount of information, and a fourth time interval valid for said radio condition report including said second amount of information.

According to a variation of the procedure shown in FIG. 3, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of determining an occasion for a terminal-initiated reporting, and an operation of conducting said terminal-initiated reporting according to a timeline which complies with said time interval.

According to a variation of the procedure shown in FIG. 3, exemplary details of the conducting operation (conducting said terminal-initiated reporting) are given, which are inherently independent from each other as such. Such exemplary conducting operation according to example embodiments may comprise an operation of generating said radio condition report between said first terminal-initiated reporting related timing associated with said terminal- initiated reporting and said second terminal-initiated reporting related timing associated with said terminal-initiated reporting, and an operation of transmitting said radio condition report.

Example embodiments outlined and specified above are explained below in more specific terms.

In detail, according to example embodiments, a terminal (e.g. UE) indicates a (minimum) time interval (i.e., a required time interval) between the UL signal used to request resources for reporting and the corresponding reporting occasion. For this case, according to example embodiments, the time interval is determined as time (period) between the UL signal requesting the resource and the reporting occasion.

For this case, further, according to example embodiments, the time interval is determined as time (period) between the first/last symbol used to transmit the UL signal requesting the resource and the first symbol of the reporting occasion or the first symbol of the slot where the reporting occasions is.

For this case, further, according to example embodiments, the time interval is indicated in terms of symbols or slots or milliseconds.

According to further example embodiments, the UE (terminal) indicates a (minimum) time interval (i.e., a required time interval) between the UL signal used to indicate/announce the resource usage for reporting and the corresponding reporting occasion.

For this case, according to example embodiments, the time interval is determined as time (period) between the transmission of the UL signal indicating/announcing the resource (usage) and the reporting occasion.

For this case, further, according to example embodiments, the time interval is determined as time (period) between the first/last symbol used to transmit the UL signal indicating/announcing the resource (usage) and the first symbol of the reporting occasion or the first symbol of the slot where the reporting occasions is.

For this case, further, according to example embodiments, the time interval is indicated in terms of symbols or slots or milliseconds. According to further example embodiments, the terminal (e.g. UE) indicates a (minimum) time interval (i.e., a required time interval) between the PDCCH used to schedule (an) UL resource(s) for reporting and the reporting occasion.

For this case, according to example embodiments, the time interval is determined as time duration (period) between reception of downlink control information (DCI) (on PDCCH) used to schedule the UL resource(s) for reporting and the scheduled reporting occasion. The reception of DCI may refer to the last symbol of the PDCCH on CORESET used to transmit DCI.

For this case, further, according to example embodiments, the time interval is determined as time (period) between the first/last symbol of the PDCCH used to schedule the UL resource(s) for reporting and the first symbol of the scheduled reporting occasion or the first symbol of the slot of the scheduled reporting occasion.

According to further example embodiments, the indicated time interval is associated with a reporting quantity or is specific for a reporting quantity.

As an example, the time interval (e.g. indicated by the UE capability value or configured by network) may be associated with the number of resource indicators (RI) to be reported, i.e. the time interval may be associated with a (substantially maximum) number of resource indicators and/or an associated reporting quantity.

According to further example embodiments, the UE indication is conveyed in a radio resource control (RRC) message. Example embodiments are not limited to such implementation. Instead, the indication may be conveyed by any other uplink control message. According to further example embodiments, if the time interval between the signal requesting (an) UL resource(s) for reporting and the first (or last symbol) of the provided reporting occasion is shorter than the capability value (i.e., the required time interval/period), the terminal is not required to report on the reporting occasion. The terminal may report on a subsequent reporting occasion which meets the terminal's capability (i.e. required time interval).

According to further example embodiments, if the time interval between the signal requesting (an) UL resource(s) for reporting and the first (or last symbol) of the provided reporting occasion is shorter (or less) than the configured time interval (i.e., the required time interval/period), the terminal is not required to report on the reporting occasion. The terminal may report on a subsequent reporting occasion which meets the required (configured) time interval time interval).

According to further example embodiments, a time interval between the physical downlink control channel (PDCCH) allocating the UL resource (second UL signal) for event-triggered reporting and the start of the reporting occasion (i.e., the UL resource (second UL signal)) may be configured to be within the same slot. In some example embodiments, the UE may indicate capability that it is able to provide event triggered report on the same slot that schedules the UL resource for the report. In some example embodiments, the UE may indicate restriction that it is not able to perform reporting which is scheduled on the same slot as the PDCCH scheduling the report.

According to further example embodiments, a time interval between the physical downlink control channel (PDCCH) allocating the UL resource (second UL signal) for event-triggered reporting and the start of the reporting occasion (i.e., the UL resource (second UL signal)) may be configured (by network) to be the N number of slots. In some example embodiments, the UE may indicate capability that it is able to provide event triggered report on the slot that is N slots later than PDCCH that schedules the UL resource for the report. N may be e.g. N=0,l,2,3,4,... or (N = l,2,3,...).

In some example embodiments, the UE may indicate capability that it supports same slot scheduling of the event triggered report.

In some example embodiments, the UE may indicate capability that it supports cross-slot scheduling of the event triggered report.

In some example embodiments, the UE may indicate capability that it does not support cross-slot scheduling of the event triggered report.

In some example embodiments, cross-slot scheduling may refer to that the event triggered report is not transmitted on the same slot in which the PDCCH triggers the UL resource and/or reporting occasion for event triggered reporting.

In some example embodiments, the UE may indicate preference for the time interval between PDCCH that schedules the UL resource for the report and the UL resource for provisioning the event triggered report. The preference may be expressed in slots.

In some example embodiments, the UE may receive a configuration of a time interval value for providing the event triggered report. In an example, the time interval value may be expressed in slots. In an example, the configuration may comprise a value of N slots (N= 0, 1,2,3, 4,...). The UE may be configured to transmit the event triggered report on the slot that is N slots later than the PDCCH that schedules the UL resource for the report. The value N may be configured in the reporting configuration. The value N may be indicated in the DCI carried by the PDCCH that schedules the UL resource for reporting. In some example embodiments, the UE may receive the PDCCH that schedules the transmission of the event triggered report, wherein the UE may transmit the report on the UL resource (UL slot / UL reporting occasion) that is the "time interval" later than the PDCCH that schedules/triggers the transmission of the report. The UE may transmit the event triggered report on the slot that is N slots later than the PDCCH that schedules the UL resource for the report.

According to example embodiments, the PDCCH that schedules the UL resource for the report may comprise the PDCCH indicating the reporting occasion/resource/slot for provisioning the report.

According to example embodiments, the PDCCH may carry DCI triggering the reporting on an UL resource.

According to example embodiments, the PDCCH may carry DCI indicating the UL resource for reporting.

According to example embodiments, the PDCCH allocating the UL resource may refer to DCI (carried by PDCCH) indicating the reporting information.

According to example embodiments, the PDCCH may carry DCI indicating the reporting information. The reporting information may comprise at least one of: time slot for the reporting, frequency resource, reporting configuration, identifier for the reporting configuration, identifier of the report for which the resource is scheduled, identifier of an event for which the reporting is configured.

As a consequence, according to example embodiments, advantageously, efficient resource allocation in the system based on the UE capability is enabled. In addition, according to example embodiments, advantageously, efficient resource allocation and configuration for event based reporting is enabled. The network may not have to consider a worst case terminal (lowest capability terminal) when scheduling resources for the terminal but is enabled to be geared to (and to potentially exhaust) the terminals capabilities.

The above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below.

In the foregoing exemplary description of the network entity, only the units that are relevant for understanding the principles of the disclosure have been described using functional blocks. The network entity may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification. The arrangement of the functional blocks of the devices is not construed to limit the disclosure, and the functions may be performed by one block or further split into sub-blocks.

When in the foregoing description it is stated that the apparatus, i.e. network entity (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to" is construed to be equivalent to an expression such as "means for").

In FIG. 4, an alternative illustration of apparatuses according to example embodiments is depicted. As indicated in FIG. 4, according to example embodiments, the apparatus (terminal) 10' (corresponding to the terminal 10) comprises a processor 41, a memory 42 and an interface 43, which are connected by a bus 44 or the like. The apparatus 10' may be connected via link 45 e.g. with another apparatus 400, e.g. with an (unshown) interface of the another apparatus 400.

The processor 41 and/or the interface 43 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface 43 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively. The interface 43 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.

The memory 42 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the example embodiments.

In general terms, the respective devices/apparatuses (and/or parts thereof) may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.

When in the subsequent description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing" is construed to be equivalent to an expression such as "means for xxx-ing"). Also, such function is to be construed to be equivalently implementable by specifically configured circuitry configured to perform the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing" is construed to be equivalent to an expression such as "xxx-ing circuitry configured to xxx").

According to example embodiments, an apparatus representing the terminal 10 comprises at least one processor 41, at least one memory 42 including computer program code, and at least one interface 43 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 41, with the at least one memory 42 and the computer program code) is configured to perform indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal- initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report (thus the apparatus comprising corresponding means for indicating or (indicating) circuitry configured to indicate), and to perform determining at least one transmission related condition based on said time interval (thus the apparatus comprising corresponding means for determining or (determining) circuitry configured to determine).

For further details regarding the operability/functionality of the individual apparatuses, reference is made to the above description in connection with any one of FIGs. 1 to 3, respectively.

For the purpose of the present disclosure as described herein above, it should be noted that

- method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples of devices, apparatuses and/or modules thereof, or as examples of entities including apparatuses and/or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;

- generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;

- method steps and/or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

- devices, units or means (e.g. the above-defined network entity or network register, or any one of their respective units/means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;

- an apparatus like the user equipment and the network entity /network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;

- a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.

Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.

Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

The present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable. In view of the above, there are provided measures for terminal capability consideration for terminal-initiated reporting. Such measures exemplarily comprise indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, and determining at least one transmission related condition based on said time interval, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report.

Even though the disclosure is described above with reference to the examples according to the accompanying drawings, it is to be understood that the disclosure is not restricted thereto. Rather, it is apparent to those skilled in the art that the present disclosure can be modified in many ways without departing from the scope of the inventive idea as disclosed herein.

Among others, the following Items are covered by the above disclosure:

Item 1. An apparatus, comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform : indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining at least one transmission related condition based on said time interval. Item 2. The apparatus according to Item 1, wherein said second terminal-initiated reporting related timing corresponds to uplink reporting resources to be used for said transmission of said radio condition report, and said first terminal-initiated reporting related timing precedes said uplink reporting resources to be used for transmission of said radio condition report and is associated with said uplink reporting resources to be used for transmission of said radio condition report.

Item 3. The apparatus according to Item 2, wherein said second terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink reporting resources to be used for said transmission of said radio condition report or to a first or last symbol of a slot of said uplink reporting resources to be used for said transmission of said radio condition report.

Item 4. The apparatus according to any of Items 1 to 3, wherein said first terminal-initiated reporting related timing corresponds to a resource request for said transmission of said radio condition report.

Item 5. The apparatus according to Item 4, wherein said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said resource request.

Item 6. The apparatus according to Item 5, wherein said first terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink resources to be used for said resource request.

Item 7. The apparatus according to any of Items 1 to 3, wherein said first terminal-initiated reporting related timing corresponds to a transmission intention indication for said transmission of said radio condition report.

Item 8. The apparatus according to Item 7, wherein said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said transmission intention indication.

Item 9. The apparatus according to Item 8, wherein said first terminal-initiated reporting related timing corresponds to a first or last symbol of said uplink resources to be used for said transmission intention indication.

Item 10. The apparatus according to any of Items 1 to 3, wherein said first terminal-initiated reporting related timing corresponds to a resource scheduling configuration for said transmission of said radio condition report.

Item 11. The apparatus according to Item 10, wherein said resource scheduling configuration is a resource scheduling utilizing a physical downlink control channel.

Item 12. The apparatus according to Item 10 or 11, wherein said first terminal-initiated reporting related timing corresponds to downlink resources to be used for said resource scheduling configuration.

Item 13. The apparatus according to Item 12, wherein said first terminal-initiated reporting related timing corresponds to a first or last symbol of said downlink resources to be used for said resource scheduling configuration.

Item 14. The apparatus according to any of Items 1 to 13, wherein said time interval is substantially equal to or larger than a required processing time interval required for generating said radio condition report.

Item 15. The apparatus according to any of Items 1 to 14, wherein said time interval is specified in a number of symbols or slots or milliseconds.

Item 16. The apparatus according to any of Items 1 to 15, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: receiving information indicative of a configured terminal-initiated reporting related time interval, wherein said configured terminal-initiated reporting related time interval is substantially equal to or larger than said time interval.

Item 17. The apparatus according to any of Items 1 to 16, wherein in relation to said indicating said time interval, the instructions, when executed by the at least one processor, cause the apparatus at least to perform : transmitting information indicative of said time interval to a mobile network access entity.

Item 18. The apparatus according to any of Items 1 to 17, wherein in relation to said determining said at least one transmission related condition, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: detecting a first occasion for terminal-initiated reporting, and deciding, if said time interval is not met with said first occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to withhold said transmission of said radio condition report.

Item 19. The apparatus according to any of Items 1 to 18, wherein in relation to said determining said at least one transmission related condition, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: detecting a second occasion for terminal-initiated reporting, and deciding, if said time interval is met with said second occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to perform said transmission of said radio condition report utilizing said second occasion for terminal-initiated reporting.

Item 20. The apparatus according to any of Items 1 to 19, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: obtaining said time interval.

Item 21. The apparatus according to Item 20, wherein in relation to said obtaining said time interval, the instructions, when executed by the at least one processor, cause the apparatus at least to perform : deciding said time interval based on at least one of the following a configuration at said apparatus, capabilities of said apparatus, supported types of event based reporting supported by said apparatus.

Item 22. The apparatus according to Item 21, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: receiving said configuration.

Item 23. The apparatus according to any of Items 1 to 22, wherein said radio condition report is related to a first radio metric or to a second radio metric, and said time interval includes a first time interval valid for reporting related to said first radio metric, and a second time interval valid for reporting related to said second radio metric.

Item 24. The apparatus according to any of Items 1 to 22, wherein said radio condition report includes a first amount of information or a second amount of information, and said time interval includes a third time interval valid for said radio condition report including said first amount of information, and a fourth time interval valid for said radio condition report including said second amount of information.

Item 25. The apparatus according to any of Items 1 to 24, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform: determining an occasion for a terminal-initiated reporting, and conducting said terminal-initiated reporting according to a timeline which complies with said time interval.

Item 26. The apparatus according to Item 25, wherein in relation to said conducting said terminal-initiated reporting, the instructions, when executed by the at least one processor, cause the apparatus at least to perform: generating said radio condition report between said first terminal-initiated reporting related timing associated with said terminal- initiated reporting and said second terminal-initiated reporting related timing associated with said terminal-initiated reporting, and transmitting said radio condition report.

Item 27. A method, comprising indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining at least one transmission related condition based on said time interval.

Item 28. A computer program product comprising instructions which, when the program is executed by a computer, cause the computer to carry out: indicating a time interval required between a first terminal-initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and determining at least one transmission related condition based on said time interval.

List of acronyms and abbreviations

3GPP 3rd Generation Partnership Project

BM beam management

BWP bandwidth part

CQI channel quality indicator

CRI CSI-R.S resource indicator

CSI channel state information

DCI downlink control information DL downlink

FR.2 frequency range 2

LI layer 1

LI layer indicator

LTM L1/L2 triggered mobility, Layer 2 Mobility

MAC-CE medium access control control element

MIMO multiple input multiple output

PDCCH physical downlink control channel

PMI precoding matrix indicator

R.I rank indicator

R.I resource indicator

R.R.C radio resource control

RS reference signal

RSRP reference signal received power

SINR signal to interference plus noise ratio

SSBRI SS/PBCH block resource indicator sTRP single transmission/reception point

TDCP time-domain channel properties

UCI uplink control information

UE user equipment

UL uplink

Claims

1. An apparatus, comprising means for indicating a time interval required between a first terminal- initiated reporting related timing and a second terminal-initiated reporting related timing, wherein said second terminal-initiated reporting related timing corresponds to a transmission of a radio condition report, and said first terminal-initiated reporting related timing precedes said transmission of said radio condition report and is associated with said transmission of said radio condition report, and means for determining at least one transmission related condition based on said time interval.

2. The apparatus according to claim 1, wherein said second terminal-initiated reporting related timing corresponds to uplink reporting resources to be used for said transmission of said radio condition report, and said first terminal-initiated reporting related timing precedes said uplink reporting resources to be used for transmission of said radio condition report and is associated with said uplink reporting resources to be used for transmission of said radio condition report.

3. The apparatus according to claim 1 or 2, wherein said first terminal-initiated reporting related timing corresponds to a resource request for said transmission of said radio condition report, and optionally said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said resource request.

4. The apparatus according to claim 1 or 2, wherein said first terminal-initiated reporting related timing corresponds to a transmission intention indication for said transmission of said radio condition report, and optionally said first terminal-initiated reporting related timing corresponds to uplink resources to be used for said transmission intention indication.

5. The apparatus according to claim 1 or 2, wherein said first terminal-initiated reporting related timing corresponds to a resource scheduling configuration for said transmission of said radio condition report, and optionally said first terminal-initiated reporting related timing corresponds to downlink resources to be used for said resource scheduling configuration.

6. The apparatus according to any of claims 1 to 5, wherein said time interval is substantially equal to or larger than a required processing time interval required for generating said radio condition report, and/or said time interval is specified in a number of symbols or slots or milliseconds.

7. The apparatus according to any of claims 1 to 6, wherein said means for indicating said time interval comprises means for transmitting information indicative of said time interval to a mobile network access entity.

8. The apparatus according to any of claims 1 to 7, wherein said means for determining said at least one transmission related condition comprises means for detecting a first occasion for terminal-initiated reporting, and means for deciding, if said time interval is not met with said first occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to withhold said transmission of said radio condition report.

9. The apparatus according to any of claims 1 to 8, wherein said means for determining said at least one transmission related condition comprises means for detecting a second occasion for terminal-initiated reporting, and means for deciding, if said time interval is met with said second occasion for terminal-initiated reporting as said second terminal-initiated reporting related timing, to perform said transmission of said radio condition report utilizing said second occasion for terminal-initiated reporting.

10. The apparatus according to any of claims 1 to 9, further comprising means for obtaining said time interval.

11. The apparatus according to claim 10, wherein said means for obtaining said time interval comprises means for deciding said time interval based on at least one of the following a configuration at said apparatus, capabilities of said apparatus, supported types of event based reporting supported by said apparatus.

12. The apparatus according to any of claims 1 to 11, wherein said radio condition report is related to a first radio metric or to a second radio metric, and said time interval includes a first time interval valid for reporting related to said first radio metric, and a second time interval valid for reporting related to said second radio metric.

13. The apparatus according to any of claims 1 to 11, wherein said radio condition report includes a first amount of information or a second amount of information, and said time interval includes a third time interval valid for said radio condition report including said first amount of information, and a fourth time interval valid for said radio condition report including said second amount of information.

14. The apparatus according to any of claims 1 to 13, further comprising means for determining an occasion for a terminal-initiated reporting, and means for conducting said terminal-initiated reporting according to a timeline which complies with said time interval.

15. The apparatus according to claim 14, wherein said means for conducting said terminal-initiated reporting comprises means for generating said radio condition report between said first terminal-initiated reporting related timing associated with said terminal- initiated reporting and said second terminal-initiated reporting related timing associated with said terminal-initiated reporting, and means for transmitting said radio condition report.