IP Library › Granted Patent US 12,430,295
Granted Patent B2
US 12,430,295 · App. 18/652,023 · Granted Sep 30, 2025

Asynchronous method for provisioning a service using file distribution technology

Inventors: Dustin Stewart Silverman (Richardson, TX); Patrick Stephen Trantham (Sunnyvale, CA); Robert Jamison White (Pensacola, FL); Philippe-Jacques Thomas Green (Ann Arbor, MI); Bryan Adam Joyner (Sachse, TX); Cara Joy Drye (Pensacola, FL); Michael Patrick Bower (Milton, FL)
Assignee: ZixCorp Systems, Inc.
G06F16/178G06F9/542G06F16/2379
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,430,295
App. No.
18/652,023
Granted
Sep 30, 2025
Kind
B2
Abstract

According to certain embodiments, a provisioning manager comprises an interface and processing circuitry. The interface is configured to obtain provisioning data from a provisioning database. The processing circuitry is configured to prepare one or more configuration files based on the provisioning data. The configuration file(s) indicate how to provision one or more service instances. The processing circuitry is further configured to commit the configuration file(s) to one or more repositories in order to make the configuration file(s) available to at least one of the service instances. The processing circuitry is further configured to send one or more notifications indicating to one or more of the service instances that the configuration file(s) have been committed to the one or more repositories.

Claims (35)

1. A system, comprising:

a processor;

a non-transitory computer readable medium, comprising instructions to:

prepare a configuration file comprising provisioning data for a service instance based on provisioning data from a provisioning database;

commit the configuration file to a repository associated with one or more file distribution technologies;

identify, by a provisioning manager prior to providing a notification associated with the committed configuration file, the service instance as a target for the committed configuration file based on predefined criteria correlating the committed configuration file to the service instance; and

provide a first notification from the provisioning manager to the service instance, wherein the notification indicates that the committed configuration file is available for retrieval by the service instance using the one or more file distribution technologies.

2. The system of claim 1 , wherein providing the first notification comprises sending the first notification to a message queue associated with the service instance.

3. The system of claim 1 , wherein the configuration file is prepared and committed based on a second notification indicating the provisioning data in the provisioning database was altered.

4. The system of claim 1 , wherein committing the configuration comprises storing the file in a repository associated with a file distribution system.

5. The system of claim 4 , wherein the second notification was sent from the file distribution system.

6. The system of claim 1 , wherein the provisioning data of the committed configuration file is arranged in a format associated with the service instance such that the provisioning data of the committed configuration file can be applied by the service instance.

7. The system of claim 1 , wherein the first notification is provided to that service instance without providing the first notification to other service instances to which the committed configuration file does not apply.

8. A method, comprising:

preparing a configuration file comprising provisioning data for a service instance based on provisioning data from a provisioning database;

committing the configuration file to a repository associated with one or more file distribution technologies;

identifying, by a provisioning manager prior to providing a notification associated with the configuration file, the service instance as a target for the committed configuration file based on predefined criteria correlating the configuration file to the service instance; and

providing a first notification from the provisioning manager to the service instance, wherein the notification indicates that the configuration file is available for retrieval by the service instance using the one or more file distribution technologies.

9. The method of claim 8 , wherein providing the first notification comprises sending the first notification to a message queue associated with the service instance.

10. The method of claim 8 , wherein the configuration file is prepared and committed based on a second notification indicating the provisioning data in the provisioning database was altered.

11. The method of claim 8 , wherein committing the configuration comprises storing the file in a repository associated with a file distribution system.

12. The method of claim 11 , wherein the second notification was sent from the file distribution system.

13. The method of claim 8 , wherein the provisioning data of the committed configuration file is arranged in a format associated with the service instance such that the provisioning data of the committed configuration file can be applied by the service instance.

14. The method of claim 8 , wherein the first notification is provided to that service instance without providing the first notification to other service instances to which the committed configuration file does not apply.

15. A non-transitory computer readable medium, comprising instructions for:

preparing a configuration file comprising provisioning data for a service instance based on provisioning data from a provisioning database;

committing the configuration file to a repository associated with one or more file distribution technologies;

identifying, by a provisioning manager prior to providing a notification associated with the configuration file, the service instance as a target for the committed configuration file based on predefined criteria correlating the configuration file to the service instance; and

providing a first notification from the provisioning manager to the service instance, wherein the notification indicates that the configuration file is available for retrieval by the service instance using the one or more file distribution technologies.

16. The non-transitory computer readable medium of claim 15 , wherein providing the first notification comprises sending the first notification to a message queue associated with the service instance.

17. The non-transitory computer readable medium of claim 15 , wherein the configuration file is prepared and committed based on a second notification indicating the provisioning data in the provisioning database was altered.

18. The non-transitory computer readable medium of claim 15 , wherein committing the configuration comprises storing the file in a repository associated with a file distribution system.

19. The non-transitory computer readable medium of claim 18 , wherein the second notification was sent from the file distribution system.

20. The non-transitory computer readable medium of claim 15 , wherein the provisioning data of the committed configuration file is arranged in a format associated with the service instance such that the provisioning data of the committed configuration file can be applied by the service instance.

21. The non-transitory computer readable medium of claim 15 , wherein the first notification is provided to that service instance without providing the first notification to other service instances to which the committed configuration file does not apply.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2024
From: SILVERMAN, DUSTIN STEWART; TRANTHAM, PATRICK STEPHEN; WHITE, ROBERT JAMISON; GREEN, PHILIPPE-JACQUES THOMAS; JOYNER, BRYAN ADAM; DRYE, CARA JOY; BOWER, MICHAEL PATRICK
To: ZIXCORP SYSTEMS, INC.
Reel/Frame 067372/0585 →
Continuity (6)
Continuation 17874049 · Jul 26, 2022
Continuation 17080163 · Oct 26, 2020
Continuation In Part 16942202 · Jul 29, 2020
Continuation In Part 15896569 · Feb 14, 2018
Continuation In Part 14154755 · Jan 14, 2014
Related Publication 20240281412A1 · Aug 22, 2024
References Cited (18)
US 10567388B1 · Kruse · 2020 [cited by examiner]
US 11023218B1 · Lu · 2021 [cited by examiner]
US 12095611B2 · Joyner et al. · 2024 [cited by applicant]
US 20060036463A1 · Patrick · 2006 [cited by examiner]
US 20110093436A1 · Zha · 2011 [cited by examiner]
US 20140075031A1 · Doering · 2014 [cited by examiner]
US 20160070747A1 · Pottlapelli · 2016 [cited by examiner]
US 20160139033A1 · Zallat · 2016 [cited by examiner]
US 20160149761A1 · Liu · 2016 [cited by examiner]
US 20170048339A1 · Straub · 2017 [cited by examiner]
US 20180275902A1 · Monday · 2018 [cited by examiner]
US 20180322149A1 · Vermeulen · 2018 [cited by examiner]
US 20190098071A1 · Bitincka · 2019 [cited by examiner]
US 20190104116A1 · Nayshtut · 2019 [cited by examiner]
US 20190347178A1 · Velummylum · 2019 [cited by examiner]
US 20210133183A1 · Biswas · 2021 [cited by examiner]
US 20240406063A1 · Joyner et al. · 2024 [cited by applicant]
WO WO2015153671A1 · 2015 [cited by examiner]
Cited By (1)
US 12,627,725