System and method for controlling multidirectional operation of an elevator
US-2024425322-A1 · Dec 26, 2024 · US
US10127149B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10127149-B2 |
| Application number | US-201414257927-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 21, 2014 |
| Priority date | Mar 31, 2009 |
| Publication date | Nov 13, 2018 |
| Grant date | Nov 13, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Aspects of a data environment, such as the creation, provisioning, and management of data stores and instances, are managed using a separate control environment. A user can call into an externally-facing interface of the control environment, the call being analyzed to determine actions to be performed in the data environment. A monitoring component of the control plane also can periodically communicate with the data environment to determine any necessary actions to be performed, such as to recover from faults or events in the data environment. A workflow can be instantiated that includes tasks necessary to perform the action. For each task, state information can be passed to a component in the data environment operable to perform the task, until all tasks for an action are completed. Data in the data environment can be accessed directly using an externally-facing interface of the data environment, without accessing the control plane.
Opening claim text (preview).
What is claimed is: 1. A data management system, comprising: one or more processors; memory including instructions that, upon being executed by the one or more processors, cause the one or more processors to: send a first request, to a control interface of a data store provisioning service, to provision a data store instance, wherein the first request specifies a database engine type for the data store instance selected from a plurality of different database engine types supported by the data store provisioning service; receive, from the control interface, information to access via a data interface of the data store provisioning service a provisioned data store instance provisioned in response to the first request; load, using the information, data to the provisioned data store instance via the data interface; configure, via the control interface, replication of the provisioned data store instance; and configure, via the control interface, the provisioned data store instance to automatically scale. 2. The data management system of claim 1 , wherein the instructions, upon being executed, further cause the one or more processors to: send a second request, via the control interface, for at least one of upgrading the database engine of the provisioned data store instance, downgrading the database engine, converting the provisioned data store instance to a replicated instance, backing up data of the provisioned data store instance, restoring the provisioned data store instance, rebooting the provisioned data store instance, hibernating the provisioned data store instance, resuming the provisioned data store instance from hibernation, or deleting the provisioned data store instance. 3. The data management system of claim 1 , wherein the information to access the provisioned data instance includes at least one of a Domain Name System (DNS) name or network address information. 4. A computer-implemented method for integrating a provisioned data store instance with a data management system, comprising: under control of one or more computer systems configured with executable instructions, sending a first request, to a control interface of a data store provisioning service, to provision a data store instance as the provisioned data store instance, wherein the first request specifies a database engine type for the data store instance selected from a plurality of different database engine types supported by the data store provisioning service; receiving, from the control interface, information to access the provisioned data store instance via a data interface of the data store provisioning service in response to the first request; loading, using the information, data to the provisioned data store instance via the data instance; configuring, via the control interface, replication of the provisioned data store instance; and configuring, via the control interface, the provisioned data store instance to automatically scale. 5. The computer-implemented method of claim 4 , wherein the control interface corresponds to a control environment, the provisioned data store instance corresponds to a data environment, and the control environment is separate from the data environment. 6. The computer-implemented method of claim 4 , wherein the loading comprises: transferring data from a non-provisioned data store instance of the data management system to the provisioned data store instance via the data interface. 7. The computer-implemented method of claim 4 , further comprising: sending a second request, via the control interface, for at least one of upgrading the database engine of the provisioned data store instance, downgrading the database engine, converting the provisioned data store instance to a replicated instance, backing up data of the provisioned data store instance, restoring the provisioned data store instance, rebooting the provisioned data store instance, hibernating the provisioned data store instance, resuming the provisioned data store instance from hibernation, or deleting the provisioned data store instance. 8. The computer-implemented method of claim 4 , further comprising: configuring, via the control interface, a compute and storage capacity for the provisioned data store instance. 9. The computer-implemented method of claim 4 , wherein said configuring the provisioned data store instance to automatically scale comprises: subscribing the provisioned data store instance to an auto-scaling plan of the data store provisioning service. 10. The computer-implemented method of claim 4 , wherein the information to access the provisioned data store instance includes at least one of a DNS name or network address information. 11. The computer-implemented method of claim 4 , further comprising: selecting a version of the database engine type for the provisioned data store instance via the control interface. 12. The computer-implemented method of claim 4 , further comprising: managing user credentials via the control interface. 13. The computer-implemented method of claim 4 , further comprising: pointing an application server to the provisioned data store instance. 14. A non-transitory computer-readable storage medium for integrating a provisioned data store instance with a data store management system including instructions that, upon being executed by a processor, cause the processor to: send a first request, to a control interface of a data store provisioning service, to provision a data store instance as the provisioned data store instance, wherein the first request specifies a database engine type for the data store instance selected from a plurality of different database engine types supported by the data store provisioning service; receive, from the control interface, information to access the provisioned data store instance via a data interface of the data store provisioning service in response to the first request; load, using the information, data to the provisioned data store instance via the data interface; configure, via the control interface, replication of the provisioned data store instance; and configure, via the control interface, the provisioned data store instance to automatically scale. 15. The non-transitory computer-readable storage medium of claim 14 , wherein the control interface corresponds to a control environment, the provisioned data store instance corresponds to a data environment, and the control environment is separate from the data environment. 16. The non-transitory computer-readable storage medium of claim 14 , wherein the instructions, upon being executed, further cause the processor to: configure, via the control interface, a compute and storage capacity for the provisioned data store instance. 17. The non-transitory computer-readable storage medium of claim 14 , wherein to configure the provisioned data store instance to automatically scale, the instructions, upon being executed, further cause the processor to: subscribe the provisioned data store instance to an auto-scaling plan of the data store provisioning service. 18. The non-transitory computer-readable storage medium of claim 14 , wherein the instructions, upon being executed, further cause the processor to: select a version of the database engine type for the provisioned data store instance via the control interface. 19. The non-transitory computer-readable storage medium of claim 14 , wherein the instructions, upon being executed, further cause the processor to: manage user credentials via the control interface.
Database migration support · CPC title
Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Addressing or allocation; Relocation (program address sequencing G06F9/00; arrangements for selecting an address in a digital store G11C8/00) · CPC title
for performance assessment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.