# US 2024/0205288 A1 · High Speed Event Handling Mechanism in a Distributed System > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2024/0205288 A1 - Document ID: US20240205288A1 - Status: Published application - Kind: A1 - Application number: 18/067,922 - Filed: 2022-12-19 - Published: 2024-06-20 - Earliest claimed: 2022-12-19 - Applicants: Drivenets Ltd. - Inventors: Alexander ZILBERMAN; Amir BARAK; Idan MATITYAHU - Web page: https://patentgrep.com/patent/US20240205288A1 ## CPC - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method and a distributed system for use in a distributed system configured to be implemented in one or more clusters of a communication network for delivering messages within the distributed system, wherein the method and the distributed system are characterized in that the messages comprise a data payload and a header that comprises a tuple of metadata of the data payload. ## Claims ### Claim 1 A method for use in a distributed system configured to be implemented in one or more clusters of a communication network for delivering messages within the distributed system, each of said one or more clusters comprises a plurality of nodes and a cluster manager, wherein the method is characterized in that each of the messages comprises a data payload and a header, wherein said header comprises a tuple of metadata derived from the respective message's data payload, wherein said method comprises steps of conveying at least one of said messages from a respective node comprised in the one or more clusters to the respective cluster manager associated with said respective node from which the at least one of said messages was conveyed, and determining by the respective cluster manager whether the at least one message received from the respective node, is a message having an important payload, based on said tuple of metadata that comprises an event type, or an event related data, or a combination thereof derived from the data payload of said message, and wherein upon determining that a message received is an important message that comprises an important payload, said important message will be conveyed towards at least one node from among the plurality of nodes without further processing via a first communication path, whereas if a message received is not determined to be an important message, the message will be forwarded via a second path. ### Claim 2 (depends on 1) The method of claim 1, wherein said tuple of metadata derived from the data payload of a message being conveyed by the respective node, is comprised in a prefix attached to said message. ### Claim 3 (canceled) ### Claim 4 (depends on 1) The method of claim 1, wherein at least one of the event type and the event related data, has a binary value. ### Claim 5 (canceled) ### Claim 6 (depends on 1) The method of claim 1, wherein said cluster manager is configured to determine whether a received message is a message comprising an important payload or not, based on the binary value associated with the event type. ### Claim 7 (canceled) ### Claim 8 A distributed system for use in a communication network, said distributed system comprises a plurality of nodes arranged in a form of a plurality of clusters, wherein each of said plurality of clusters comprises a cluster manager and a plurality of nodes, each of said plurality of nodes is configured to deliver messages to a respective cluster manager associated therewith, wherein said distributed system is characterized in that messages delivered from each of the plurality of nodes, comprise a data payload and a header, wherein said header comprises a tuple of metadata associated with said data payload, said metadata comprises an event type, or an event related data, or a combination thereof, wherein said cluster manager is configured to determine whether a message received thereat comprises an important payload or not, based on said tuple of metadata derived from the data payload of said message and wherein upon determining that a message received is an important message that comprises an important payload, said important message will be conveyed towards at least one node from among the plurality of nodes without further processing via a first communication path, whereas if a message received is not determined to be an important message, the message will be forwarded via a second path. ### Claim 9 (depends on 8) The distributed system of claim 8, wherein said tuple of metadata derived from the data payload of a message being conveyed by the respective node, is comprised in a prefix attached to said message. ### Claim 10 (canceled) ### Claim 11 (depends on 8) The distributed system of claim 8, wherein at least one of the event type and the event related data has a binary value. ### Claim 12 (canceled) ### Claim 13 (depends on 8) The distributed system of claim 8, wherein said cluster manager is configured to determine whether a message comprises an important payload or not, based on the binary value associated with the event type. ### Claim 14 (canceled)