# US 12,602,268 B2 · Methods for event prioritization in network function virtualization using rule-based feedback > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,268 B2 - Document ID: US12602268B2 - Status: Granted - Kind: B2 - Application number: 17/422,685 - Filed: 2019-01-14 - Published: 2022-04-21 - Granted: 2026-04-14 - Earliest claimed: 2019-01-14 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Allan Vidal; Pedro Henrique Gomes Da Silva - Web page: https://patentgrep.com/patent/US12602268B2 ## CPC - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/4831: {with variable priority} - G06F 9/546: {Message passing systems or structures, e.g. queues} - G06F 2209/544: Remote - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method is implemented by an event collector to utilize feedback from an event handler to prioritize event forwarding to the event handler. The method includes receiving feedback from the event handler in response to a successful match-action in a rules engine, the feedback including a derived condition which is a generalized version of a condition stored in the match part of a rule, determining whether the derived condition is stored in an event prioritizer, and storing the derived condition in the event prioritizer with initial expiration timer and hit counter, in response to the derived condition not being present in the event prioritizer, and updating a hit counter and expiration timer of the derived condition in the event prioritizer, in response to the derived condition being present in the event prioritizer. ## Claims ### Claim 1 A method implemented by an event collector to utilize feedback from an event handler to prioritize event forwarding to the event handler in a network function virtualization, NFV, architecture, the method comprising: receiving feedback from the event handler in response to a successful match-action in a rules engine, the event handler being an NFV orchestrator, NFVO, the feedback including a derived condition which is a generalized version of a condition stored in a match part of a rule; determining whether the derived condition is stored in an event prioritizer; determining whether an incoming event matches a previously seen pattern based on: a configuration of the event prioritizer, the feedback from the event handler, and a configuration from the event handler, determining that the incoming event matches a previously seen pattern establishing that the derived condition is present in the event prioritizer; storing the derived condition in the event prioritizer with initial expiration timer and hit counter in response to the derived condition not being present in the event prioritizer, the expiration timer being set to a default value and the hit counter being set to one; updating the hit counter and expiration timer of the derived condition in the event prioritizer, in response to the derived condition being present in the event prioritizer, the expiration timer being reset and the hit counter being increased; and storing received events in one of a set of priority queues to be dispatched to the event handler, the event collector being a virtual network function manager, VNFM, the event collector determining which of the available set of priority queues to place an event in based on a pre-configured policy. ### Claim 2 (depends on 1) The method of claim 1, further comprising: resetting an expiration timer of a derived condition in response to receiving a subsequent occurrence of the derived condition. ### Claim 3 (depends on 2) The method of claim 2, further comprising: incrementing the hit counter in response to receiving the subsequent occurrence of the derived condition. ### Claim 4 (depends on 1) The method of claim 1, further comprising: prioritizing received events using a priority value based on matching derived conditions. ### Claim 5 (depends on 4) The method of claim 4, wherein the priority value is a sum, median, mean, or mode of the hit counter of the matching derived conditions. ### Claim 6 (depends on 1) The method of claim 1, further comprising: processing an event by a rules engine and executing actions matching the event. ### Claim 7 (depends on 6) The method of claim 6, further comprising: determining the derived condition for a matched rule. ### Claim 8 A computing device to implement a method of an event collector to utilize feedback from an event handler to prioritize event forwarding to the event handler in a network function virtualization, NFV, architecture, the computing device comprising: a non-transitory machine-readable medium having stored therein the event collector and the event handler, the event handler being an NFV orchestrator, NFVO, the event collector being a virtual network function manager, VNFM, the event handler being adapted to determine a priority queue to source a next event from using a pre-configured policy, and to forward the next event from the priority queue, the event handler processing an event by a rules engine and executing actions matching the event, the event handler further determining the derived condition for a matched rule; and a processor coupled to the non-transitory machine-readable medium, the processor configured to execute the event collector; the event collector configured to: receive feedback from the event handler in response to a successful match-action in a rules engine, the feedback including a derived condition that is a generalized version of a condition stored in a match part of a rule; determine whether the derived condition is stored in an event prioritizer; determine whether an incoming event matches a previously seen pattern based on: a configuration of the event prioritizer, the feedback from the event handler, and a configuration from the event handler, determining that the incoming event matches a previously seen pattern establishing that the derived condition is present in the event prioritizer; store the derived condition in the event prioritizer with initial expiration timer and hit counter in response to the derived condition not being present in the event prioritizer, the expiration timer being set to a default value and the hit counter being set to one; and update the hit counter and the expiration timer of the derived condition in the event prioritizer in response to the derived condition being present in the event prioritizer, the expiration timer being reset and the hit counter being increased, the event collector storing received events in one of a set of priority queues to be dispatched to the event handler, the event collector determining which of the available set of priority queues to place an event in based on a pre-configured policy. ### Claim 9 (depends on 8) The computing device of claim 8, wherein the event collector resets an expiration timer of a derived condition in response to receiving a subsequent occurrence of the derived condition. ### Claim 10 (depends on 9) The computing device of claim 9, wherein the event collector increments the hit counter in response to receiving the subsequent occurrence of the derived condition. ### Claim 11 (depends on 8) The computing device of claim 8, wherein the event collector prioritizes received events using a priority value based on matching derived conditions. ### Claim 12 (depends on 11) The computing device of claim 11, wherein the priority value is a sum, median, mean, or mode of the hit counter of the matching derived conditions.