View source for Dell products l.p. (20240095054). SELF-ADAPTIVE EVENT NOTIFICATION FREQUENCY FOR NODES IN A HYPER-CONVERGED INFRASTRUCTURE (HCI) CLUSTER simplified abstract

=SELF-ADAPTIVE EVENT NOTIFICATION FREQUENCY FOR NODES IN A HYPER-CONVERGED INFRASTRUCTURE (HCI) CLUSTER=


==Organization Name==

[[:Category:dell products l.p.|dell products l.p.]]


[[Category:dell products l.p.]]

==Inventor(s)==

[[:Category:Lixia Hu of Shanghai (CN)|Lixia Hu of Shanghai (CN)]][[Category:Lixia Hu of Shanghai (CN)]]

[[:Category:Joan Jun Xiong of Shanghai (CN)|Joan Jun Xiong of Shanghai (CN)]][[Category:Joan Jun Xiong of Shanghai (CN)]]

[[:Category:Tianhe Li of Shanghai (CN)|Tianhe Li of Shanghai (CN)]][[Category:Tianhe Li of Shanghai (CN)]]

[[:Category:Kai Chen of Shanghai (CN)|Kai Chen of Shanghai (CN)]][[Category:Kai Chen of Shanghai (CN)]]

==SELF-ADAPTIVE EVENT NOTIFICATION FREQUENCY FOR NODES IN A HYPER-CONVERGED INFRASTRUCTURE (HCI) CLUSTER - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240095054 titled 'SELF-ADAPTIVE EVENT NOTIFICATION FREQUENCY FOR NODES IN A HYPER-CONVERGED INFRASTRUCTURE (HCI) CLUSTER

==Simplified Explanation==

The disclosed event notification management method and service for use with a multi-node, hyper-converged infrastructure (HCI) cluster involves adjusting notification intervals based on monitored parameters such as the success of previous notifications and the severity of pending notifications. 

* The service runs on a node in the cluster to monitor parameters associated with event notifications.
* Parameters include a Last Event Notification Successful (LENS) parameter and a severity parameter based on the urgency of pending notifications.
* The service uses formulas to adjust notification intervals, decreasing them after successful notifications and increasing them after unsuccessful ones.
* The severity parameter influences the magnitude of adjustment, allowing for aggressive interval reduction in high urgency situations.

== Potential Applications ==
This technology can be applied in various industries where real-time monitoring and notification systems are crucial, such as:
* Data centers
* Network operations centers
* Industrial automation

== Problems Solved ==
This technology addresses the following issues:
* Efficient management of event notifications in a clustered environment
* Timely response to critical events
* Optimization of notification intervals based on severity and success rates

== Benefits ==
The benefits of this technology include:
* Improved system reliability and performance
* Enhanced response times to critical events
* Automated adjustment of notification intervals for optimal resource utilization

== Potential Commercial Applications ==
Potential commercial applications of this technology include:
* Software development for hyper-converged infrastructure management
* Integration with existing monitoring and notification systems
* Consulting services for implementing efficient event notification management solutions

== Possible Prior Art ==
One possible prior art for this technology could be existing event notification management systems that do not dynamically adjust notification intervals based on monitored parameters.

=== Unanswered Questions ===

=== How does this technology compare to traditional event notification management systems? ===
This article does not provide a direct comparison between this technology and traditional event notification management systems. 

=== What impact could this technology have on overall system performance and reliability? ===
The article does not delve into the potential impact of this technology on overall system performance and reliability.


==Original Abstract Submitted==

a disclosed event notification management method and service for use with a multi-node, hyper-converged infrastructure (hcl) cluster employs a service running on a corresponding node to monitor one or more parameters associated with event notifications sent to a cluster. the service may adjust a node's notification interval based on the monitored parameters. the parameters may include a last event notification successful (lens) parameter indicating whether a recent notification was successful and a severity parameter determined based on an urgency type of a plurality of pending notifications within an event queue. the service may employ a first formula to decrease the notification interval following a successful previous notification and a second formula to increase the notification interval following an unsuccessful notification. the magnitude by which the notification interval is adjusted may be influenced by the severity parameter, e.g., to aggressively reduce the notification interval following successful notifications when urgency is high.



[[Category:G06F9/455]]
[[Category:H04L41/06]]