# US 11,310,096 B2 · Notification system and method of monitoring a multi-component system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,310,096 B2 - Document ID: US11310096B2 - Status: Granted - Kind: B2 - Application number: 16/579,538 - Filed: 2019-09-23 - Published: 2021-03-25 - Granted: 2022-04-19 - Earliest claimed: 2019-09-23 - Assignees: Rohde & Schwarz GmbH & Co. KG - Applicants: Rohde & Schwarz GmbH & Co. KG - Inventors: Jonas Von Andrian; Balthasar Biedermann; Vittorio Curcio - Web page: https://patentgrep.com/patent/US11310096B2 ## CPC - H04L 41/064: {involving time analysis} - H04L 43/0817: by checking functioning - G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)} - G06N 5/04: Inference or reasoning models - G06N 5/047: Pattern matching networks; Rete networks - H04L 41/0622: {based on time} - H04L 41/0686: Additional information in the notification, e.g. enhancement of specific meta-data - H04L 43/106: using time related information in packets, e.g. by adding timestamps - H04L 51/224: providing notification on incoming messages, e.g. pushed notifications of received messages - H04L 67/55: Push-based network services - H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] - G06F 2201/835: Timestamp - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A notification system for monitoring a multi-component system is disclosed. The notification system comprises a notification processing module and an event processing module. The event processing module comprises an event input and an event classifier module. The event input is configured to receive an event signal that comprises at least one status parameter being indicative of at least one of a status and a status change of at least one component of the multi-component system. The event classifier module is configured to classify the event signal into at least one event class based on the at least one status parameter. The notification processing module is configured to generate no user notification or at least one user notification based on the at least one event class. Further, a method of monitoring a multi-component system is disclosed. ## Claims ### Claim 1 A notification system for monitoring a multi-component system, comprising: a notification processing circuit; a setting circuit comprising at least one setting parameter, wherein the at least one setting parameter comprises information on which event classes have to be considered, which event classes have to be temporarily ignored, and which event classes have to be permanently ignored for generating user notifications; and an event processing circuit comprising an event input and an event classifier circuit, wherein said event input is configured to receive an event signal that comprises at least one status parameter, said at least one status parameter being indicative of at least one of a status and a status change of at least one component of the multi-component system, wherein said event classifier circuit is configured to classify the event signal into at least one event class based on said at least one status parameter, wherein said notification processing circuit is configured to generate no user notification or at least one user notification based on said at least one event class, wherein said notification processing circuit is configured to aggregate several event signals coming from different individual components of the multi-component system and being classified into the same event class into a common user notification, and wherein said notification processing circuit is configured to save said at least one user notification based on said at least one setting parameter, wherein the saved user notification is not sent to the user immediately. ### Claim 2 (depends on 1) The notification system of claim 1, wherein the notification processing circuit is configured to at least one of approve or discard said at least one user notification based on said at least one setting parameter. ### Claim 3 (depends on 1) The notification system of claim 1, wherein said status parameter comprises a time stamp, said time stamp being a time of recording of the at least one of said status or said status change. ### Claim 4 (depends on 1) The notification system of claim 1, wherein said event signal comprises at least one attribute parameter, said at least one attribute parameter being indicative of at least one property of said at least one component. ### Claim 5 (depends on 4) The notification system of claim 4, wherein said event classifier circuit is configured to classify the event signal into said at least one event class based on said at least one attribute parameter. ### Claim 6 (depends on 4) The notification system of claim 4, wherein said notification processing circuit is configured to generate said at least one user notification based on said at least one attribute parameter. ### Claim 7 (depends on 1) The notification system of claim 1, wherein said notification system is configured to transmit said at least one user notification via at least one of email, text message, push message or web frontend. ### Claim 8 (depends on 1) The notification system of claim 1, wherein said notification processing circuit is configured to generate said at least one user notification based on at least one of a number of event signals, an event signal rate, a time development of said number of event signals or a time development of said event signal rate. ### Claim 9 A method of monitoring a multi-component system, the method comprising: receiving an event signal, said event signal comprising at least one status parameter, said at least one status parameter being indicative of at least one of a status or a status change of at least one component of the multi-component system; classifying the event signal into at least one event class based on said at least one status parameter; and generating no user notification or at least one user notification based on said at least one event class, wherein event signals coming from different individual components of the multi-component system and being classified into the same event class are aggregated into a common user notification, and saving the at least one user notification based on at least one setting parameter, wherein the saved user notification is not sent to the user immediately, the at least one setting parameter comprising information on which event classes have to be considered, which event classes have to be temporarily ignored, and which event classes have to be permanently ignored for generating user notifications. ### Claim 10 (depends on 9) The method of claim 9, wherein said at least one user notification is at least one of approved or discarded. ### Claim 11 (depends on 9) The method of claim 9, wherein said status parameter comprises a time stamp, said time stamp being a time of recording of the at least one of said status or said status change. ### Claim 12 (depends on 9) The method of claim 9, wherein said event signal comprises at least one attribute parameter, said at least one attribute parameter being indicative of at least one property of said at least one component. ### Claim 13 (depends on 12) The method of claim 12, wherein the event signal is classified into said at least one event class based on said at least one attribute parameter. ### Claim 14 (depends on 12) The method of claim 12, wherein said at least one user notification is generated based on said at least one attribute parameter. ### Claim 15 (depends on 9) The method of claim 9, wherein said at least one user notification is transmitted via at least one of email, text message, push message or web frontend. ### Claim 16 (depends on 9) The method of claim 9, wherein said at least one user notification is generated based on at least one of a number of event signals, an event signal rate, a time development of said number of event signals or a time development of said event signal rate.