IP Library Granted Patent US 12,192,054
Granted Patent B1
US 12,192,054 · App. 18/333,913 · Granted Jan 7, 2025

Automated provisioning of temporary communication systems

Inventor: Justin Blackburn (Litchfield Park, AZ)
Assignee: Wells Fargo Bank, N.A.
H04L41/0886H04L63/0823H04L67/34
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,192,054
App. No.
18/333,913
Granted
Jan 7, 2025
Kind
B1
Abstract

An example computer system for providing a communication system can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: receive a command to create the communication system based upon an event; automatically install and provision the communication system in a cloud computing environment; provide an event management microservice programmed to track issues associated with the computer system, including provisioning the event management microservice with one or more tickets based upon a type of the event; and provide a communication microservice programmed to facilitate communications between users of the communication system, including provisioning the event management microservice with one or more contacts based upon the type of the event.

Claims (42)

1. A computer system for providing a communication system, comprising:

one or more processors; and

non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to:

receive a command to create the communication system based upon a cyber security event for an impacted system;

automatically install and provision the communication system in a cloud computing environment that is unassociated with the impacted system;

provide an event management microservice programmed to track issues associated with the impacted system, including provisioning the event management microservice with one or more tickets based upon a type of the cyber security event;

provide a communication microservice programmed to facilitate communications between users of the communication system, including provisioning the event management microservice with one or more contacts based upon the type of the cyber security event;

identify the type of the cyber security event; and

select the type of the cyber security event from a hierarchical list of different cyber security events, wherein the hierarchical list of different cyber security events provides provisioning information for the communication system based upon the type of the cyber security event.

2. The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to:

receive a single second command to remove the communication system; and

automatically remove the communication system from the cloud computing environment.

3. The computer system of claim 1 , wherein the provisioning information includes the one or more tickets to be added to the event management microservice and the one or more contacts to be added to the communication microservice.

4. The computer system of claim 3 , wherein the provisioning information identifies a subset of the one or more contacts to be assigned to the one or more tickets.

5. The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to provide both a chat microservice and a mail microservice.

6. The computer system of claim 1 , wherein the cloud computing environment is non-attributable to an entity associated with the computer system.

7. The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to log events associated with the communication system.

8. The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to create a directory programmed to provide directory information services for the communication system.

9. The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to create a provisioning engine programmed to:

setup a proxy to allow clients to connect with the event management microservice and the communication microservice;

generate digital certificates to secure the communications within the communication system; and

register users of the communication system within a directory.

10. A method for providing communication services, the method comprising:

receiving a command to create a communication system based upon a cyber security event for an impacted system;

automatically installing and provisioning the communication system in a cloud computing environment that is unassociated with the impacted system;

providing an event management microservice programmed to track issues associated with the impacted system, including provisioning the event management microservice with one or more tickets based upon a type of the cyber security event;

providing a communication microservice programmed to facilitate communications between users of the communication system, including provisioning the event management microservice with one or more contacts based upon the type of the cyber security event;

identifying the type of the cyber security event; and

selecting the type of the cyber security event from a hierarchical list of different cyber security events, wherein the hierarchical list of different cyber security events provides provisioning information for the communication system based upon the type of the cyber security event.

11. The method of claim 10 , further comprising:

receiving a single second command to remove the communication system; and

automatically removing the communication system from the cloud computing environment.

12. The method of claim 10 , wherein the provisioning information includes the one or more tickets to be added to the event management microservice and the one or more contacts to be added to the communication microservice.

13. The method of claim 12 , wherein the provisioning information identifies a subset of the one or more contacts to be assigned to the one or more tickets.

14. The method of claim 10 , further comprising providing both a chat microservice and a mail microservice.

15. The method of claim 10 , wherein the cloud computing environment is non-attributable to an entity associated with the method.

16. The method of claim 10 , further comprising logging events associated with the communication system.

17. The method of claim 10 , further comprising creating a directory programmed to provide directory information services for the communication system.

18. The method of claim 10 , further comprising:

setting up a proxy to allow clients to connect with the event management microservice and the communication microservice;

generating digital certificates to secure the communications within the communication system; and

registering users of the communication system within a directory.

Assignments (2)
STATEMENT OF CHANGE OF ADDRESS OF ASSIGNEE Recorded Jun 17, 2025
From: WELLS FARGO BANK, N.A.
To: WELLS FARGO BANK, N.A.
Reel/Frame 071679/0784 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 15, 2023
From: BLACKBURN, JUSTIN
To: WELLS FARGO BANK, N.A.
Reel/Frame 063968/0071 →
References Cited (39)
US 7817982B1 · Chu · 2010 [cited by examiner]
US 8069471B2 · Boren · 2011 [cited by applicant]
US 8572735B2 · Ghosh et al. · 2013 [cited by applicant]
US 8635490B2 · Narayanaswamy et al. · 2014 [cited by applicant]
US 9426834B2 · Greene et al. · 2016 [cited by applicant]
US 9454592B2 · Mills et al. · 2016 [cited by applicant]
US 9501541B2 · Doering et al. · 2016 [cited by applicant]
US 9906500B2 · O'Hare et al. · 2018 [cited by applicant]
US 10225269B2 · Yi · 2019 [cited by applicant]
US 10637994B2 · Amin et al. · 2020 [cited by applicant]
US 10762204B2 · Yuen et al. · 2020 [cited by applicant]
US 10904288B2 · Robertson · 2021 [cited by applicant]
US 20060149842A1 · Dawson et al. · 2006 [cited by applicant]
US 20070210909A1 · Addy · 2007 [cited by applicant]
US 20100306772A1 · Arnold et al. · 2010 [cited by applicant]
US 20120131226A1 · Stevens et al. · 2012 [cited by applicant]
US 20130189944A1 · McCoy · 2013 [cited by applicant]
US 20130295891A1 · Moon et al. · 2013 [cited by applicant]
US 20140125759A1 · Chalasani et al. · 2014 [cited by applicant]
US 20140372805A1 · Rijnders · 2014 [cited by examiner]
US 20160080248A1 · Rijnders · 2016 [cited by examiner]
US 20160219154A1 · Veron et al. · 2016 [cited by applicant]
US 20170118092A1 · Dixon · 2017 [cited by examiner]
US 20170279826A1 · Mohanty et al. · 2017 [cited by applicant]
US 20170353978A1 · Ulinskas · 2017 [cited by applicant]
US 20180054427A1 · Revell · 2018 [cited by applicant]
US 20180060153A1 · Innes · 2018 [cited by examiner]
US 20190147089A1 · Megahed et al. · 2019 [cited by applicant]
US 20200358617A1 · Baierlein et al. · 2020 [cited by applicant]
US 20220239568A1 · Celozzi et al. · 2022 [cited by applicant]
US 20220353177A1 · Mohammad · 2022 [cited by examiner]
US 20230116748A1 · Rowe · 2023 [cited by examiner]
US 20230140789A1 · Wenzel · 2023 [cited by examiner]
US 20230308460A1 · Thomas · 2023 [cited by examiner]
U.S. Appl. No. 18/347,789, filed Jul. 6, 2023. [cited by applicant]
U.S. Appl. No. 18/523,566, filed Nov. 29, 2023. [cited by applicant]
U.S. Appl. No. 18/587,487, filed Feb. 26, 2024. [cited by applicant]
Noel Burton-Krahn, HotSwap Network Solutions, pp. 205-212 of the Proceedings of LISA '02: Sixteenth Systems Administration Conference, (Berkeley, CA: USENIX Association, 2002), 8 pages. [cited by applicant]
U.S. Appl. No. 17/930,207, filed Sep. 7, 2022. [cited by applicant]