IP Library Granted Patent US 12,670,041
Granted Patent B2
US 12,670,041 · App. 18/295,289 · Granted Jun 30, 2026

Realtime contextual event notification system

Inventors: Chris Schnurr (Londonderry, GB); Brendan Killen (Londonderry, GB); Marc Calahan (Milton, GA); Duane Wright (Guildford, GB)
Assignee: Verint Americas Inc.
G06F9/542G06F9/546
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,670,041
App. No.
18/295,289
Filed
Apr 4, 2023
Granted
Jun 30, 2026
Kind
B2
Examiner
HO, ANDY
Art Unit
2194
USPC
719/318
Abstract

A realtime contextual event notification system that ingests events as streams from any authorized entity applies rules to the event streams, determines a context of an end-user who is a recipient of a targeted notification, and provides notifications to the end-user in accordance with the context. The event streams may come from multiple sources and rules may be applied to provide realtime contextual information associated with the end-user.

Claims (44)

1 . A method of providing realtime contextual event notifications, comprising:

receiving, at an API gateway component, event messages from a source over a socket connection;

receiving, at a recorder management system, call event messages from the source, wherein the call event messages comprise application events and linguistic events;

forwarding, by the recorder management system, the event messages and the call event messages to a notification application programming interface (API) that provides a RESTful API to connect the event messages and the call event messages to a managed streaming component;

processing, at the managed streaming component, the event messages and the call event messages to determine a context including a condition of a user and a circumstance of a customer interaction to generate event notifications; and

communicating event notifications to a client management service that determines a target client to receive the event notifications.

2 . The method of claim 1 , wherein the event messages comprise linguistic events and application events.

3 . The method of claim 1 , further comprising authenticating the event messages and the call event messages using a token that is contained within a header.

4 . The method of claim 1 , the processing further comprising:

determining a current state of a call associated with the event messages using the call event messages;

updating a cache with a most current event of the call; and

adding the event notifications for consumption by the client management service for delivery to the target client.

5 . The method of claim 1 , further comprising receiving feedback on the event notifications from the target client.

6 . The method of claim 1 , further comprising:

receiving a connection from the target client; and

sending scripting language code to the target client that defines a user interface.

7 . The method of claim 1 , further comprising:

receiving the event messages as parallel streams;

processing the parallel streams by topic; and

determining the context in realtime as the parallel streams are received.

8 . A computer system, comprising: a memory comprising computer-executable instructions; and a processor configured to execute the computer-executable instructions and cause the computer system to perform a method of providing realtime contextual event notifications, the computer system executing instructions to:

receive, at an API gateway component, event messages from a source over a socket connection;

receive, at a recorder management system, call event messages from the source, wherein the call event messages comprise application events and linguistic events;

forward, by the recorder management system, the event messages and the call event messages to a notification application programming interface (API) that provides a RESTful API to connect the event messages and the call event messages to a managed streaming component;

process, at the managed streaming component, the event messages and the call event messages to determine a context to generate event notifications; and

communicate the event notifications to a client management service that determines a target client to receive the event notifications.

9 . The computer system of claim 8 , wherein the event messages comprise linguistic events and application events.

10 . The computer system of claim 8 , wherein the event messages and the call event messages are authenticated using a token that is contained within a header.

11 . The computer system of claim 8 , wherein a current state of a call associated with the event messages is determined using the call event messages, wherein a cache is updated with a most current event of the call, and wherein the event notifications are processed for consumption by the client management service for delivery to the target client.

12 . The computer system of claim 8 , wherein feedback on the event notifications is received from the target client.

13 . The computer system of claim 8 , wherein a connection is received from the target client, and wherein scripting language code that defines a user interface is sent to the target client.

14 . The computer system of claim 8 , wherein the event messages are received as parallel streams, wherein the parallel streams are processed by topic, and wherein the context is determined in realtime as the parallel streams are received.

15 . A non-transitory computer readable medium comprising instructions that, when executed by a processor of a processing system, cause the processing system to perform a method of providing realtime contextual event notifications, comprising instructions to:

receive, at an API gateway component, event messages from a source over a socket connection;

receive, at a recorder management system, call event messages from the source, wherein the call event messages comprise application events and linguistic events;

forward, by the recorder management system, the event messages and the call event messages to a notification application programming interface (API) that provides a RESTful API to connect the event messages and the call event messages to a managed streaming component;

process, at the managed streaming component, the event messages and the call event messages to determine a context; and

communicate event notifications to a client management service that determines a target client to receive the event notifications.

16 . The non-transitory computer readable medium of claim 15 , wherein the event messages comprise linguistic events and application events.

17 . The non-transitory computer readable medium of claim 15 , further comprising instructions to authenticate the event messages and the call event messages using a token that is contained within a header.

18 . The non-transitory computer readable medium of claim 15 , further comprising instructions to:

determine a current state of a call associated with the event messages using the call event messages;

update a cache with a most current event of the call; and

add the event notifications for consumption by the client management service (CMS) for delivery to the target client.

Assignments (2)
SECURITY INTEREST Recorded Dec 23, 2025
From: VERINT AMERICAS INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 074034/0292 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 4, 2023
From: SCHNURR, CHRIS; KILLEN, BRENDAN; CALAHAN, MARC; WRIGHT, DUANE
To: VERINT AMERICAS INC.
Reel/Frame 063213/0091 →
Continuity (2)
Provisional Application 63328308 · Apr 7, 2022
Related Publication 20230325261A1 · Oct 12, 2023
References Cited (52)
US 8549629B1 · McCreesh et al. · 2013 [cited by applicant]
US 8782668B1 · McCreesh et al. · 2014 [cited by applicant]
US 8787532B1 · Adam · 2014 [cited by applicant]
US 9779760B1 · Ouimette · 2017 [cited by examiner]
US 9922649B1 · Lore et al. · 2018 [cited by applicant]
US 9936066B1 · Mammen et al. · 2018 [cited by applicant]
US 10147427B1 · Johnson et al. · 2018 [cited by applicant]
US 10193992B2 · Wagenknecht · 2019 [cited by examiner]
US 10397740B2 · Lalka et al. · 2019 [cited by applicant]
US 10579742B1 · Fernandez · 2020 [cited by applicant]
US 11064072B1 · Sawala · 2021 [cited by applicant]
US 11178282B1 · Ramachandran et al. · 2021 [cited by applicant]
US 11196862B1 · Krebs et al. · 2021 [cited by applicant]
US 11509611B2 · Edamadaka · 2022 [cited by examiner]
US 11765270B1 · Langley · 2023 [cited by applicant]
US 20040054791A1 · Chakraborty et al. · 2004 [cited by applicant]
US 20040128359A1 · Horvitz et al. · 2004 [cited by applicant]
US 20040194110A1 · McKee et al. · 2004 [cited by applicant]
US 20040194116A1 · McKee et al. · 2004 [cited by applicant]
US 20100158237A1 · McCormack · 2010 [cited by examiner]
US 20100169067A1 · Basel et al. · 2010 [cited by applicant]
US 20110173620A1 · Dyer et al. · 2011 [cited by applicant]
US 20130091192A1 · Shafi et al. · 2013 [cited by applicant]
US 20130136253A1 · Liberman Ben-Ami et al. · 2013 [cited by applicant]
US 20140208172A1 · Schnurr et al. · 2014 [cited by applicant]
US 20140372544A1 · Wen · 2014 [cited by applicant]
US 20160021171A1 · Zourzouvillys · 2016 [cited by examiner]
US 20160191709A1 · Pullamplavil et al. · 2016 [cited by applicant]
US 20170288943A1 · Plumb et al. · 2017 [cited by applicant]
US 20180070152A1 · Yang et al. · 2018 [cited by applicant]
US 20180097768A1 · Ragsdale et al. · 2018 [cited by applicant]
US 20190057079A1 · Raanani et al. · 2019 [cited by applicant]
US 20190258825A1 · Krishnamurthy · 2019 [cited by applicant]
US 20190265865A1 · Yaseen et al. · 2019 [cited by applicant]
US 20190266611A1 · De Sousa Moura et al. · 2019 [cited by applicant]
US 20200065848A1 · Gupta et al. · 2020 [cited by applicant]
US 20200259948A1 · Keohane et al. · 2020 [cited by applicant]
US 20200358898A1 · Singer et al. · 2020 [cited by applicant]
US 20210044547A1 · Bradley et al. · 2021 [cited by applicant]
US 20210306457A1 · Krishnan · 2021 [cited by applicant]
US 20210350385A1 · Ellison et al. · 2021 [cited by applicant]
US 20220182492A1 · Skinner et al. · 2022 [cited by applicant]
US 20220270020A1 · Matula et al. · 2022 [cited by applicant]
US 20220366277A1 · DeFilippo et al. · 2022 [cited by applicant]
US 20240004729A1 · Workman et al. · 2024 [cited by applicant]
US 20250219863A1 · Ploegert et al. · 2025 [cited by applicant]
WO 2015184359A2 · 2015 [cited by applicant]
Extended European Search Report issued for Application No. 23167059.7, dated Aug. 25, 2023. [cited by applicant]
Advisory Action for U.S. Appl. No. 18/215,319, dated May 29, 2025, 03 Pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/339,402, dated Sep. 3, 2025, 13 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 18/215,319, mailed Jan. 3, 2025, 17 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/217,161, dated Aug. 27, 2025, 7 Pages. [cited by applicant]