# US 2022/0035770 A1 · Asynchronous method for provisioning a service using file distribution technology

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0035770 A1
- Document ID: US20220035770A1
- Status: Published application
- Kind: A1
- Application number: 17/080,163
- Filed: 2020-10-26
- Published: 2022-02-03
- Earliest claimed: 2020-07-29
- Assignees: ZixCorp Systems, Inc.
- Applicants: ZixCorp Systems, Inc.
- Inventors: Dustin Stewart Silverman; Patrick Stephen Trantham; Robert Jamison White; Philippe-Jacques Thomas Green; Bryan Adam Joyner; Cara Joy Drye; Michael Patrick Bower
- Web page: https://patentgrep.com/patent/US20220035770A1

## CPC

- G06F 16/178: Techniques for file synchronisation in file systems
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- G06F 9/5072: {Grid computing}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 41/0843: {based on generic templates}
- H04L 41/0889: {Techniques to speed-up the configuration process}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/125: involving control of end-device applications over a network
- G06F 2209/548: Queue
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/14: {for detecting or protecting against malicious traffic}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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

### Claim 1

A system, comprising:
a provisioning manager, the provisioning manager comprising an interface and processing circuitry, the interface configured to obtain provisioning data from a provisioning database, and the processing circuitry configured to:
prepare one or more configuration files based on the provisioning data, the one or more configuration files indicating how to provision one or more service instances;
commit the one or more configuration files to one or more repositories, each of the one or more repositories configured to make at least one of the one or more configuration files available to at least one of the one or more service instances; and
wherein the one or more service instances include electronic mail and wherein the configuration files include encryption policies regarding the encryption of electronic mail messages.

### Claim 2 (depends on 21)

The system of claim 21, wherein the processing circuitry is configured to send one or more of the notification(s) according to a publisher/subscriber model.

### Claim 3 (depends on 2)

The system of claim 2, wherein a first notification of the one or more notifications is sent according to the publisher/subscriber model and the processing circuitry is further configured to:
indicate one or more topics associated with the first notification, the one or more topics indicating that each of the one or more service instances that subscribes to one or more of the topic(s) associated with the first notification is to receive and process the first notification.

### Claim 4

(canceled)

### Claim 5 (depends on 21)

The system of claim 21, wherein the processing circuitry is configured to send the one or more notifications according to a message queue model wherein each of the one or more service instances is associated with a corresponding message queue.

### Claim 6 (depends on 5)

The system of claim 5, wherein a first notification indicates that a first configuration file has been committed to the one or more repositories and, prior to sending the first notification, the processing circuitry is configured to determine a subset of the one or more service instances to which the first configuration file applies such that the first notification is sent to the message queue(s) corresponding to the subset of the one or more service instances to which the first configuration file applies without sending the first notification to the message queue(s) corresponding to the other service instance(s) to which the first configuration file does not apply.

### Claim 7 (depends on 21)

The system of claim 21, wherein the processing circuitry is further configured to initiate obtaining the provisioning data via the interface in response to receiving a notification indicating that the provisioning data has been added, modified, or removed in the provisioning database.

### Claim 8 (depends on 21)

The system of claim 21, wherein the processing circuitry is further configured to prepare a first configuration file of the one or more configuration files, wherein to prepare the first configuration file, the processing circuitry is configured to:
determine the provisioning data to include in the first configuration file;
determine whether to include any additional data in the first configuration file to assist the one or more service instances in applying the provisioning data; and
format the first configuration file according to a format that the one or more service instances are able to use for provisioning.

### Claim 9 (depends on 21)

The system of claim 21, wherein at least one of the one or more configuration files indicates at least one of the following types of data used in sending or receiving electronic messages:
an identification of one or more domains;
domain mapping information;
an identification of one or more clients;
mail relay configuration data; and
mail transport configuration data.

### Claim 10 (depends on 21)

The system of claim 21, wherein:
a first of the one or more repositories comprises a source code control repository, a version control repository, or an object store; and
the processing circuitry is further configured to use a file distribution technology to commit the one or more configuration files to the first repository.

### Claim 11 (depends on 10)

The system of claim 10, wherein the file distribution technology comprises at least one of Git, J/Git, Concurrent Version System (CVS), Subversion (SVN), Mercurial, Team Foundation Server (TFS), Clearcase, SourceSafe, Ceph, or Simple Storage Service (S3) technology.

### Claim 12 (depends on 21)

The system of claim 21, wherein the system further comprises:
a first service instance of the one or more service instances, the first service instance configured to:
receive a first of the one or more notifications indicating that a first of the one or more configuration files has been committed to a first of the one or more repositories;
retrieve the first configuration file from the first repository based at least in part on receiving the first notification; and
apply the configuration of the first configuration file.

### Claim 13

One or more non-transitory computer readable media storing logic that, when executed by processing circuitry of a provisioning manager, is operable to cause the provisioning manager to perform actions comprising:
obtaining provisioning data from a provisioning database;
preparing one or more configuration files based on the provisioning data, the one or more configuration files indicating how to provision one or more service instances;
committing the one or more configuration files to one or more repositories, each of the one or more repositories configured to make at least one of the one or more configuration files available to at least one of the one or more service instances;
wherein the one or more service instances include electronic mail and wherein the configuration files include encryption policies regarding the encryption of electronic mail messages; and
sending one or more notifications, the one or more notifications indicating to one or more of the service instances that the one or more configuration files have been committed to the one or more repositories.

### Claim 14 (depends on 13)

The one or more non-transitory computer readable media of claim 13, wherein a first notification of the one or more notifications is sent according to a publisher/subscriber model and the actions further comprise:
indicating one or more topics associated with the first notification, the one or more topics indicating that each of the one or more service instances that subscribes to one or more of the topic(s) associated with the first notification is to receive and process the first notification.

### Claim 15 (depends on 14)

The one or more non-transitory computer readable media of claim 14, wherein the one or more topics associated with the first notification relate to at least one of the following policies for handling electronic messages: encryption policy, quarantine policy, antivirus filter policy, anti-spam filter policy, archiving policy, and branding policy.

### Claim 16 (depends on 13)

The one or more non-transitory computer readable media of claim 13, wherein a first notification indicates that a first configuration file has been committed to the one or more repositories, the first notification sent according to a message queue model that associates each of the one or more service instances with a corresponding message queue wherein the actions further comprise, prior to sending the first notification, determining a subset of the one or more service instances to which the first configuration file applies such that the first notification is sent to the message queue(s) corresponding to the subset of the one or more service instances to which the first configuration file applies without sending the first notification to the message queue(s) corresponding to the other service instance(s) to which the first configuration file does not apply.

### Claim 17 (depends on 13)

The one or more non-transitory computer readable media of claim 13, wherein the actions further comprise preparing a first configuration file of the one or more configuration files, wherein preparing the first configuration file comprises:
determining the provisioning data to include in the first configuration file;
determining whether to include any additional data in the first configuration file to assist the one or more service instances in applying the provisioning data; and
formatting the first configuration file according to a format that the one or more service instances are able to use for provisioning.

### Claim 18

A method, comprising:
obtaining provisioning data from a provisioning database;
preparing one or more configuration files based on the provisioning data, the one or more configuration files indicating how to provision one or more service instances;
committing the one or more configuration files to one or more repositories, each of the one or more repositories configured to make at least one of the one or more configuration files available to at least one of the one or more service instances;
wherein the one or more service instances include electronic mail and wherein the configuration files include encryption policies regarding the encryption of electronic mail messages; and
sending one or more notifications, the one or more notifications indicating to one or more of the service instances that the one or more configuration files have been committed to the one or more repositories.

### Claim 19 (depends on 18)

The method of claim 18, wherein a first notification of the one or more notifications is sent according to a publisher/subscriber model and the method further comprises:
indicating one or more topics associated with the first notification, the one or more topics indicating that each of the one or more service instances that subscribes to one or more of the topic(s) associated with the first notification is to receive and process the first notification.

### Claim 20 (depends on 18)

The method of claim 18, wherein a first notification indicates that a first configuration file has been committed to the one or more repositories, the first notification sent according to a message queue model that associates each of the one or more service instances with a corresponding message queue wherein the method further comprises, prior to sending the first notification, determining a subset of the one or more service instances to which the first configuration file applies such that the first notification is sent to the message queue(s) corresponding to the subset of the one or more service instances to which the first configuration file applies without sending the first notification to the message queue(s) corresponding to the other service instance(s) to which the first configuration file does not apply.

### Claim 21 (depends on 1)

The system of claim 1, wherein the processing circuitry is configured to send one or more notifications, the one or more notifications indicating to one or more of the service instances that the one or more configuration files have been committed to the one or more repositories.
