Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L67/63—Routing a service request depending on the request content or context
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/22—Parsing or analysis of headers

Definitions

• the present disclosure generally relates to the field of communication systems. More particularly, the present disclosure relates to software architecture of a high scale distributed system.
• EM – Element Manager an entity which resides in all nodes of the cluster for managing the elements as required by the CM.
• RM Routing Manager. WB - White-box.
• Container – A container is an isolated execution environment that behaves much like a full-featured installation with its own users, file system, processes, libraries, codes, network stacks and the like. That ensures an identical behavior resulting from the software contained within such a container, irrespective of the system in which the container is being executed.
• Data Plane – A logical layer that encompasses all functions and processes related to the forwarding of data packets/frames from one interface to another through a system. This term encompasses among others, but not limited to, routing via physical ports as well as via intermediate backplane ports to enable data packets to reach physical ports which are not immediately reachable.
• BACKGROUND In the area of high scale distributed systems, one of the challenges in the software architecture domain, is, the ability to efficiently deliver messages to relevant system users.
• distributed messaging is based on the concept of reliable message queuing. Messages are queued asynchronously between client applications and messaging systems, and such a distributed messaging system provides the benefits of reliability, scalability, and persistence.
• each node typically forwards many messages to its cluster manager (CM).
• CM cluster manager
• CM cluster manager
• 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, wherein the method is characterized in that the messages comprise a data payload and a header that comprises a tuple of metadata of the data payload.
• the term “tuple” as used herein throughout the specification and claims is used to denote a finite sequence of terms, e.g., a single row in a relational database.
• metadata as used herein throughout the specification and claims, is used to denote data that provides information about other data but not the content of the data, such as the text of a message or an image itself.
• the metadata comprises at least one member of a group that consists of a target, a source, an event type (i.e., the classification of the event) and an event related data.
• the metadata comprises at least one member of a group that consists of a target; a source; an event type; and an event related data.
• each of the at least one member of the group has a binary value, thereby the header is suited to provide an indication regarding whether a message is an important message or not.
• each of the one or more clusters comprises a cluster manager configured to determine whether a message is an important message or not, based on value of one or more of the at least one member included in said group.
• the message will still be handled is such a case as an important message.
• the system operational definition may be such that the message will still be considered as an important message. Obviously. If all four members have the value of “1”, the message will be considered an important message.
• 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, and configured to deliver messages within said distributed system, wherein said distributed system is characterized in that said messages comprise a data payload and a header, and wherein said header comprises a tuple of metadata associated with said data payload.
• the metadata enables determining how a message associated therewith, will be handled.
• the metadata comprises at least one member of a group that consists of a target, a source, an event type and an event related data.
• each of the at least one member of said group has a binary value.
• each of the one or more clusters comprise a cluster manager configured to determine whether a message is an important message or not, based on value of one or more of the at least one member included in that group.
• the cluster manager is configured to determine whether a message is an important message or not based on the value of the event type member.
• FIG. 1 illustrates a partial view of a distributed system, wherein important messages are separated from regular messages, construed in accordance with an embodiment of the present invention
• FIG. 2 illustrates a flow chart, exemplifying a method for carrying out the present solution according to an embodiment construed in accordance with the present invention.
• the solution provided by the present invention is based on distinguishing between important messages vis. regular messages, and to enable handling (e.g., forwarding) the important messages faster than regular ones.
• a novel mechanism of structured binary tag messages that are being forwarded across the system is used.
• This prefix (tag) attached to the message comprises metadata of the message’s data payload, and comprises at least one member of a group that consists of a target to which the message needs to be forwarded, a source where the message was generated, type of an event associated with that message and related data of that event.
• each of the members discussed above which are comprised in the metadata simply indicate if the message is an important message or not. That may be done for example, per the system operator’s decision, if one of the members in the group is defined as a member that has a higher weight than any of other members, e.g., if the value of the event type in the message header is “1” whereas all other members of the group have the value “0”, the message will still be handled is such a case as an important message.
• the system operational definition may be such that the message will still be considered as an important message. Obviously. If all four members have the value of “1”, the message will be considered an important message.
• FIG. 1 illustrates a partial view of a distributed system 5, wherein important messages are separated from regular messages, construed in accordance with an embodiment of the present invention.
• the regular messages are forwarded along a “slowpath” for non-urgent events (associated with regular messages) as opposed to a path for handling messages associated with events marked for relay (forwarding without further processing).
• CM cluster manager 10
• Information that relates to these events is forwarded by using messages generated by an application, which then sends respective messages with their metadata-tagged events comprised in the messages’ headers.
• the messages are sent towards the local node’s element manager (EM) 25 that resides within a cluster leader 30 (CL), and element manager 25 then forwards them to the CM 10 connection.
• EM element manager
• the message is classified based on the information included in the respective message header. If the values included in the metadata indicates that the event is important and therefore the message has to be conveyed without further processing.
• FIG. 2 illustrates a flow chart, exemplifying a method for carrying out the present solution according to an embodiment construed in accordance with the present invention.
• a message is created to be conveyed via a distributed system operating in a communication network, wherein the message comprises a data payload, and a header comprises a tuple of its metadata – target, source, event type and event data.
• the message is conveyed via the distributed system and arrives at a cluster manager (step 210).
• the cluster manager and detects the values of the constituents included in header (step 220) and classifies, based on one or more of these values, depending on the system operator’s decision, the message as an important message or as a regular message (step 230). If the cluster manager determines that the message is an important message conveying the message without any further processing of the message, towards its destination without undue delay (step 240).
• the classification ability by the cluster manager side by inspecting the event type. Events, which are tagged as having a type that requires to be relayed immediately, will be forwarded without additional inspection and parsing.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=91587848

Family Applications (1)

Country Status (4)

Family Cites Families (3)

• 2022
  • 2022-12-18 EP EP22969089.6A patent/EP4635141A4/de active Pending
  • 2022-12-18 IL IL321169A patent/IL321169A/en unknown
  • 2022-12-18 JP JP2025535336A patent/JP2025540416A/ja active Pending
  • 2022-12-18 WO PCT/IL2022/051347 patent/WO2024134639A1/en not_active Ceased

Also Published As

Similar Documents

Legal Events