Throttling events in entity lifecycle management

• US 10,437,635 B2
• Filed: 08/18/2016
• Issued: 10/08/2019
• Est. Priority Date: 02/10/2016
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Layman, Andrew, Bosworth, Adam, Mamut, Tatyana
• Primary Examiner(s): Cao, Diem K
• Application Number:
  US15/240,729
• Publication Number:
  US 20170228253A1
• Time in Patent Office: 1,146 Days
• Field of Search: None
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: 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
• CPC Class Codes: G06F 11/3013 where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems testing or monitoring of control systems or parts thereof G05B23/02
• CPC Class Codes: G06F 11/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G06F 11/328 Computer systems status display G06F11/327 takes precedence
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/4887 involving deadlines, e.g. rate based, periodic
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

The disclosed declarative framework implements a machine for multi-step progression of interaction with an entity. The framework is usable for a broad range of applications—providing a simple rule-based authoring tool for specifying elements and components of a complex state machine, including state definitions, state transition triggers, state transition conditions and state transition actions. Case-status states, a first filtering condition, and a count parameter that specifies a limit on a number of times within a time period in excess of which additional events with characteristics that match will be ignored or discarded are usable to determine whether to ignore or process an incoming event—throttling the rate at which certain actions occur. A workflow engine gets loaded with instructions derived from the states and event filtering conditions, for handling incoming machine-generated events. Once defined, the state machine is automatically generated and implemented based on the declarative input provided.

Claims

1. A method comprising:

presenting, by at least one processor, a user interface comprising a prompt for input, the prompt comprising a description of a device, at least one state transition condition, a first event-filtering condition, and a first state of the device after a first event;

selecting, by the at least one processor, instructions responsive to at least the first event-filtering condition and the first state of the device for a plurality of incoming machine-generated events;

setting, by the at least one processor, in a memory, according to an input via the user interface, a value of an integer count parameter, wherein the at least one processor is further configured to log additional events of the plurality of incoming machine-generated events, wherein to log the additional events, the at least one processor is further configured to ignore specified additional events that have matching characteristics satisfying the first event-filtering condition, when a count of the specified additional events exceeds the value of the integer count parameter; and

configuring, by the at least one processor, a workflow engine to execute the instructions that are selected by the at least one processor responsive to at least the first event-filtering condition, the integer count parameter, and the first state of the device for the plurality of incoming machine-generated events, omitting the ignored additional events.

2. The method of claim 1, further comprising:

skipping, by the at least one processor, a workflow action corresponding to at least one of the ignored additional events.

3. The method of claim 1, wherein the incoming machine-generated events and the additional events are received from a near real-time (NRT) event management framework that includes a message bus and a stream processing system.

4. The method of claim 1, wherein the first state of the device comprises online, offline, standby, power up, power down, level of network connectivity, or a combination thereof.

5. The method of claim 1, further comprising:

determining, by the at least one processor, that the device has transitioned from the first state of the device to a second state of the device.

6. The method of claim 5, further comprising:

performing, by the at least one processor, a specified action, upon determining that the state transition meets the at least one state transition condition.

7. The method of claim 1, wherein the at least one state transition condition corresponds to a time-based transition trigger and an event-based transition trigger.

8. A system comprising memory and at least one processor coupled thereto, the at least one processor being configured to perform operations comprising:

presenting a user interface comprising a prompt for input, the prompt comprising a description of a device, at least one state transition condition, a first event-filtering condition, and a first state of the device after a first event;

selecting instructions responsive to at least the first event-filtering condition and the first state of the device for a plurality of incoming machine-generated events;

setting, in the memory, according to an input via the user interface, a value of an integer count parameter, wherein the at least one processor is further configured to log additional events of the plurality of incoming machine-generated events, wherein to log the additional events, the at least one processor is further configured to ignore specified additional events that have matching characteristics satisfying the first event-filtering condition, when a count of the specified additional events exceeds the value of the integer count parameter; and

configuring a workflow engine to execute the instructions that are selected by the at least one processor responsive to at least the first event-filtering condition, the integer count parameter, and the first state of the device, for the plurality of incoming machine-generated events, omitting the ignored additional events.

9. The system of claim 8, the at least one processor configured to perform the operations further comprising:

skipping a workflow action corresponding to at least one of the ignored additional events.

10. The system of claim 8, wherein the incoming machine-generated events and the additional events are received from a near real-time (NRT) event management framework that includes a message bus and a stream processing system.

11. The system of claim 8, wherein the first state of the device comprises online, offline, standby, power up, power down, level of network connectivity, or a combination thereof.

12. The system of claim 8, the at least one processor configured to perform the operations further comprising:

determine that the device has transitioned from the first state of the device to a second state of the device.

13. The system of claim 12, the at least one processor being further configured to:

perform a specified action, upon determining that the state transition meets the at least one state transition condition.

14. A non-transitory computer-readable storage medium comprising code that, when executed by at least one processor, causes the at least one processor to perform operations comprising:

presenting a user interface comprising a prompt for input, the prompt comprising a description of a device, at least one state transition condition, a first event-filtering condition, and a first state of the device after a first event;

selecting instructions responsive to at least the first event-filtering condition and the first state of the device for a plurality of incoming machine-generated events;

setting, in a memory, according to an input via the user interface, a value of an integer count parameter, wherein the at least one processor is further configured to log additional events of the plurality of incoming machine-generated events, wherein to log the additional events, the at least one processor is further configured to ignore specified additional events that have matching characteristics satisfying the first event-filtering condition, when a count of the specified additional events exceeds the value of the integer count parameter; and

configuring a workflow engine to execute the instructions that are selected by the at least one processor responsive to at least the first event-filtering condition, the integer count parameter, and the first state of the device for the plurality of incoming machine-generated events, omitting the ignored additional events.

15. The non-transitory computer-readable storage medium of claim 14, the operations further comprising:

skipping a workflow action corresponding to at least one of the ignored additional events.

16. The non-transitory computer-readable storage medium of claim 14, wherein the incoming machine-generated events and the additional events are received from a near real-time (NRT) event management framework that includes a message bus and a stream processing system.

17. The non-transitory computer-readable storage medium of claim 14, wherein the first state of the device comprises online, offline, standby, power up, power down, level of network connectivity, or a combination thereof.

18. The non-transitory computer-readable storage medium of claim 14, the operations further comprising:

determining that the device has transitioned from the first state of the device to a second state of the device.

19. The non-transitory computer-readable storage medium of claim 18, the operations further comprising:

performing a specified action, upon determining that the state transition meets the at least one state transition condition.

20. The non-transitory computer-readable storage medium of claim 14, wherein the at least one state transition condition corresponds to a time-based transition trigger and an event-based transition trigger.