Network device for distributing computing operations by data communication in a network
US-12164880-B2 · Dec 10, 2024 · US
US10237145B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10237145-B2 |
| Application number | US-201614993673-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 12, 2016 |
| Priority date | Apr 20, 2012 |
| Publication date | Mar 19, 2019 |
| Grant date | Mar 19, 2019 |
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.
An application, interface, device and method for coordinating a parameter across cloud domains of various distributed data centers. The method includes using an infrastructure service for generating one or more values of the parameter so that the values are different from each other; and providing the values to the respective cloud domains.
Opening claim text (preview).
What is claimed is: 1. A method for coordinating a parameter across cloud domains of various data centers, the method comprising: generating, in an infrastructure service, a plurality of values for the parameter, wherein each of the plurality of values are different from each other; sending each of the plurality of values to each of the cloud domains of the various data centers; verifying at each of the cloud domains whether a corresponding value generates an internal conflict; and accepting the corresponding value if there is no internal conflict or sending back to the infrastructure service a conflict message if there is an internal conflict. 2. The method of claim 1 , wherein the infrastructure service is provided in a device that is not part of the cloud domains. 3. The method of claim 1 , wherein the infrastructure service is implemented in at least one cloud domain of the cloud domains. 4. The method of claim 3 , further comprising: generating various values of the parameter at the at least one cloud domain; and forwarding the various values of the parameter to remaining cloud domains of the various data centers. 5. The method of claim 1 , further comprising: providing a seed to a function of the infrastructure service for automatically generating the plurality of values, wherein the function is configured to generate unique values based on the seed. 6. The method of claim 1 , wherein the parameter is an address of an element of a cloud domain of the various data centers. 7. The method of claim 1 , further comprising: after receiving the conflict message for a given cloud domain indicative of the internal conflict, generating another value for the parameter for the given cloud domain; and sending the another value to the given cloud domain. 8. An infrastructure service application for coordinating a parameter across cloud domains of various data centers, the infrastructure service application being embedded into a computing device, the computing device comprising: a processor configured to generate a plurality of values for the parameter, wherein each of the plurality of values are different from each other; and an interface connected to the processor and configured to send each of the plurality of values to each of the cloud domains of the various data centers, wherein each of the cloud domains verify whether a corresponding value generates an internal conflict, and the cloud domains accept the corresponding value if there is no internal conflict or send back to the infrastructure service application a conflict message if there is an internal conflict. 9. The computing device of claim 8 , wherein the infrastructure service application is provided in a node that is not part of the various data centers. 10. The computing device of claim 8 , wherein the infrastructure service application is implemented in at least one cloud domain of the various data centers. 11. The computing device of claim 10 , wherein the processor is further configured to generate various values of the parameter at the at least one cloud domain; and the interface is further configured to forward the various values of the parameter to remaining cloud domains of the various data centers. 12. The computing device of claim 8 , wherein the processor is further configured to provide a seed to a function of the infrastructure service application for automatically generating the plurality of values, wherein the function is configured to generate unique values based on the seed. 13. The computing device of claim 8 , wherein the parameter is an address of an element of a cloud domain of the various data centers. 14. The computing device of claim 8 , wherein the processor is further configured to generate, after receiving the conflict message for a given cloud domain indicative of the internal conflict, another value for the parameter for the given cloud domain; and the interface is configured to send the another value to the given cloud domain. 15. A computer embedded infrastructure service interface for coordinating a parameter across cloud domains of various data centers, the computer embedded infrastructure service interface being configured to: generate a plurality of values for the parameter so that each of the plurality of values are different from each other; and send each of the plurality of values to each of the cloud domains of the various data centers, wherein each of the cloud domains verify whether a corresponding value generates an internal conflict; and accept the corresponding value if there is no internal conflict or send back to the computer embedded infrastructure service interface a conflict message if there is an internal conflict. 16. The computer embedded infrastructure service interface of claim 15 , being further configured to: provide a seed to a function for automatically generating the plurality of values, wherein the function is configured to generate unique values based on the seed. 17. The computer embedded infrastructure service interface of claim 15 , wherein the parameter is an address of an element of a cloud domain of the various data centers. 18. A method for coordinating a parameter across cloud domains of various data centers, the method comprising: distributing an infrastructure service as local infrastructure services to each of the cloud domains of the various data centers; generating at a first local infrastructure service a first value of the parameter based on a first seed; sending to a second local infrastructure service a seed list that includes the first seed; generating at the second local infrastructure service a second seed that is different from the first seed; generating at the second local infrastructure service a second value of the parameter based on the second seed; and sending to a third local infrastructure service the seed list that includes the first seed and the second seed. 19. The method of claim 18 , further comprising: generating at the third local infrastructure service a third seed and a third value of the parameter, based on the first to third seeds. 20. The method of claim 19 , further comprising: sending the seed list to a next local infrastructure service; generating a new seed and a new value of the parameter at the next local infrastructure service; and repeating the steps of sending and generating until all the local infrastructure services have generated corresponding values for the parameter. 21. An infrastructure service, embedded in a plurality of cloud domains of various data centers, for coordinating a parameter across the plurality of cloud domains of various data centers, the infrastructure service comprising: a first local infrastructure service configured to generate a first value of the parameter based on a first seed; a second local infrastructure service configured to receive from the first local infrastructure service a seed list that includes the first seed; the second local infrastructure service being configured to generate a second seed that is different from the first seed and to generate a second value of the parameter based on the second seed; and the second local infrastructure service being configured to send to a third local infrastructure service the seed list that includes the first seed and the second seed. 22. The infrastructure service of claim 21 , further comprising: the third local infrastructure service being configured to generate a third seed
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
characterised by the time relationship between creation and deployment of a service · CPC title
Testing arrangements · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.