# US 2021/0176330 A1 · Automated platform provisioning system

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

- Number: US 2021/0176330 A1
- Document ID: US20210176330A1
- Status: Published application
- Kind: A1
- Application number: 17/181,678
- Filed: 2021-02-22
- Published: 2021-06-10
- Earliest claimed: 2016-12-21
- Assignees: Hartford Fire Insurance Company
- Applicants: Hartford Fire Insurance Company
- Inventors: Joseph Nicholas Nigro
- Web page: https://patentgrep.com/patent/US20210176330A1

## CPC

- H04L 67/303: Terminal profiles
- H04L 41/5051: Service on demand, e.g. definition and deployment of services in real time
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 41/5096: {wherein the managed service relates to distributed or central networked applications}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

According to some embodiments, a system to automate platform provisioning for an enterprise includes a platform resource computer store containing a set of electronic data records (each including a component identifier and a set of computing characteristic values). A profile engine may receive a platform request from a user associated with the enterprise and identify, based on data in the platform resource computer store, a resource bundle of components appropriate in view of the platform request. A platform generator may receive platform requirements based on the identified resource bundle of components and provide input data to a REST API service. Final platform definition information for the enterprise may be stored into a central repository. According to some embodiments, a platform provisioning system may process IaaS and PaaS automation components and utilize a return service to generate infrastructure binding data to couple components in the resource bundle to each other.

## Claims

### Claim 1

A system to automate platform provisioning for an enterprise, comprising:
(a) a platform resource computer store containing a set of electronic data records, each electronic data record including a component identifier and a set of computing characteristic values;
(b) a profile engine computer, coupled to the platform resource computer store, programmed to:
(i) receive a platform request from a user associated with the enterprise, wherein the platform request is associated with a base service level, a multiplier, and at least one service offering extension,
(ii) identify, based on the electronic data records in the platform resource computer store, a resource bundle of components appropriate in view of the platform request, and
(iii) output platform requirements based at least in part on the identified resource bundle of components;
(c) a platform generator system computer, coupled to the profile engine computer, programmed to:
(i) receive the platform requirements from the profile engine computer,
(ii) provide input data to an asynchronous representational state transfer application programming interface service, and
(iii) store final platform definition information for the enterprise into a central repository;
(d) a platform provisioning system computer, coupled to the platform generator system computer, programmed to:
(i) process Infrastructure-as-a-Service automation components,
(ii) process Platform-as-a-Service automation components,
(iii) utilize a return service to generate infrastructure binding data to couple components in the resource bundle to each other;
(e) the central repository to store the final platform definition information in response to the platform request received from the user; and
(f) an automated build platform de-creation computer, programmed to:
(i) receive a platform de-creation request from the user associated with the enterprise, the platform de-creation request indicating that components of a currently deployed platform are no longer needed by the enterprise,
(ii) responsive to the received platform de-creation request, arrange for computing resources associated with the platform to be released, and
(iii) store information about the released computing resources into a software version control system data store for later use by the platform provisioning system computer,
wherein the central repository is further to provide feedback data to the profile engine computer, the feedback data being used by the profile engine computer to improve responses to future platform requests from users, the feedback data including: (i) a component add, (ii) a component change, (iii) a component delete, and (iv) a capacity adjustment.

### Claim 2 (depends on 1)

The system of claim 1, further comprising:
(g) a communication port coupled to the profile engine computer to facilitate an exchange of electronic messages, via a distributed cloud-based communication network, to present an interactive graphical user interface at a remote user terminal associated with the user.

### Claim 3 (depends on 1)

The system of claim 1, wherein the identified resource bundle of components includes a web server, an application server, and a database server.

### Claim 4 (depends on 3)

The system of claim 3, wherein: (i) the web server is associated with a first virtual machine of a web hosting tier, (ii) the application server is associated with a second virtual machine of an application container tier, and (iii) the database server is associated with a third virtual machine of a database instance tier.

### Claim 5 (depends on 4)

The system of claim 4, wherein the resource bundle of components further includes at least one of: (i) a network component, (ii) a network balancer, and (iii) middleware services.

### Claim 6 (depends on 1)

The system of claim 1, wherein the binding of resources to each other is associated with at least one of: (i) a request proxy, (ii) a datasource, (iii) an internet protocol address, and (iv) a port range.

### Claim 7 (depends on 1)

The system of claim 1, wherein the platform request is associated with at least one of: (i) a standardized service template, (ii) a pre-defined profile, (iii) a customized profile, (iv) a set of individual micro infrastructure service definitions, (v) platform input data, (vi) a user defined filter, (vii) an application profile, (viii) a questionnaire, (ix) an enterprise web application interaction, (x) a bundles services input template, and (xi) a user selection of computing resource units.

### Claim 8 (depends on 7)

The system of claim 7, wherein the platform request is associated with at least one of: (i) a framework template, (ii) a runtime template, (iii) a middleware template, (iv) an operating system template, (v) a native service template, (vi) a load balanced, auto-scaled website, (vii) a relational database management system, (viii) a JBoss stack, layer, instances, and associated resources, (ix) website hosting with domain name services entry, and (x) identity and access management.

### Claim 9 (depends on 8)

The system of claim 8, wherein the platform request generates a platform as a service application programming interface reference including: (i) a data type, (ii) common parameters, (iii) common errors, and (iv) regions and endpoints.

### Claim 10 (depends on 1)

The system of claim 1, wherein the service offering extension includes at least one of: (i) availability, (ii) security, (iii) performance, (iv) agility, (v) workload, (vi) support, (vii) capabilities, (viii) cost, and (ix) monitoring ability.

### Claim 11 (depends on 1)

The system of claim 1, wherein the Infrastructure-as-a-Service automation components are associated with at least one of: (i) compute, (ii) network, and (iii) storage.

### Claim 12 (depends on 1)

The system of claim 1, wherein the Platform-as-a-Service automation components are associated with at least one of: (i) object storage, (ii) identity, (iii) runtime, (iv) queue, (v) database, (vi) cloud modeling framework, (vii) data types, (viii) common data types, (ix) common errors, and (x) regions and endpoints.

### Claim 13

A computerized method to automate platform provisioning for an enterprise, comprising:
receiving, at a profile engine computer, a platform request from a user associated with the enterprise, wherein the platform request is associated with a base service level, a multiplier, and at least one service offering extension;
identifying, based on electronic data records in a platform resource computer store, a resource bundle of components appropriate in view of the platform request;
outputting platform requirements based at least in part on the identified resource bundle of components;
receiving, by a platform generator system computer, the platform requirements from the profile engine computer;
providing input data to an asynchronous representational state transfer application programming interface service;
storing the final platform definition information for the enterprise into a central repository;
processing, by a platform provisioning system computer, Infrastructure-as-a-Service automation components;
processing, by the platform provisioning system computer, Platform-as-a-Service automation components;
utilizing a return service to generate infrastructure binding data to couple components in the resource bundle to each other;
receiving, at an automated build platform de-creation computer, a platform de-creation request from the user associated with the enterprise, the platform de-creation request indicating that components of a currently deployed platform are no longer needed by the enterprise;
responsive to the received platform de-creation request, arranging, by the automated build platform de-creation computer, for computing resources associated with the platform to be released;
storing, by the automated build platform de-creation computer, information about the released computing resources into a software version control system data store for later use by the platform provisioning system computer;
providing, by the central repository to the profile engine computer, feedback data; and
using, by the profile engine computer, the feedback data to improve responses to future platform requests from users, the feedback data including: (i) a component add, (ii) a component change, (iii) a component delete, (iv) a capacity adjustment, and (v) a data change.

### Claim 14 (depends on 13)

The method of claim 13, wherein the identified resource bundle of components includes a web server, an application server, and a database server.

### Claim 15 (depends on 13)

The method of claim 13, wherein the platform request is associated with at least one of: (i) a standardized service template, (ii) a pre-defined profile, (iii) a customized profile, (iv) a set of individual micro infrastructure service definitions, (v) platform input data, (vi) a user defined filter, (vii) an application profile, and (viii) a questionnaire.

### Claim 16

A system to automate platform provisioning for an enterprise, comprising:
(a) a platform resource computer store containing a set of electronic data records, each electronic data record including a component identifier and a set of computing characteristic values;
(b) a profile engine computer, coupled to the platform resource computer store, programmed to:
(i) receive a platform request from a user associated with the enterprise, wherein the platform request is associated with a base service level, a multiplier, and at least one service offering extension,
(ii) identify, based on the electronic data records in the platform resource computer store, a resource bundle of components appropriate in view of the platform request, the identified resource bundle of components including a web server, an application server, and a database server, and
(iii) output platform requirements based at least in part on the identified resource bundle of components;
(c) a platform generator system computer, coupled to the profile engine computer, programmed to:
(i) receive the platform requirements from the profile engine computer,
(ii) provide input data to an asynchronous representational state transfer application programming interface service, and
(iii) store final platform definition information for the enterprise into a central repository;
(d) a platform provisioning system computer, coupled to the platform generator system computer, programmed to:
(i) process Infrastructure-as-a-Service automation components,
(ii) process Platform-as-a-Service automation components, and
(iii) utilize a return service to generate infrastructure binding data to couple components in the resource bundle to each other;
(e) the central repository to store the final platform definition information in response to the platform request received from the user;
(f) a communication port coupled to the profile engine computer to facilitate an exchange of electronic messages, via a distributed cloud-based communication network, to present an interactive graphical user interface at a remote user terminal associated with the user; and
(g) an automated build platform de-creation computer, programmed to:
(i) receive a platform de-creation request from the user associated with the enterprise, the platform de-creation request indicating that components of a currently deployed platform are no longer needed by the enterprise,
(ii) responsive to the received platform de-creation request, arrange for computing resources associated with the platform to be released, and
(iii) store information about the released computing resources into a software version control system data store for later use by the platform provisioning system computer,
wherein the central repository is further to provide feedback data to the profile engine computer, the feedback data being used by the profile engine computer to improve responses to future platform requests from users, the feedback data including: (i) a component add, (ii) a component change, (iii) a component delete, and (iv) lifestyle event data.

### Claim 17 (depends on 16)

The system of claim 16, wherein: (i) the web server is associated with a first virtual machine of a web hosting tier, (ii) the application server is associated with a second virtual machine of an application container tier, and (iii) the database server is associated with a third virtual machine of a database instance tier.

### Claim 18 (depends on 16)

The system of claim 16, wherein the platform request is associated with at least one of: (i) a standardized service template, (ii) a pre-defined profile, (iii) a customized profile, (iv) a set of individual micro infrastructure service definitions, and (v) platform input data.
