Communications Interface for Simulation Systems and Methods

• US 20180060462A1
• Filed: 11/28/2016
• Published: 03/01/2018
• Est. Priority Date: 08/24/2016
• Status: Active Grant

• Current Assignee: Improbable Worlds Ltd.
• Original Assignee: Improbable Worlds Ltd.
• Inventors: Whitehead, Robert James Frederick, Tang, Hanying, Lewis, Matthew John Reveley, Lipka, Peter Richard
• Granted Patent: US 10,289,767 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 30/20 Design optimisation, verification or simulation optimisation, verification or simulation of circuit designs G06F30/30
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Methods, systems, computer-readable media, and apparatuses for performing, providing, managing, executing, and/or running a spatially-optimized simulation are presented. In one or more embodiments, the spatially-optimized simulation may comprise a plurality of worker modules performing the simulation, a plurality of entities being simulated among the plurality of worker modules, a plurality of bridge modules facilitating communication between workers and an administrative layer including a plurality of chunk modules, at least one receptionist module, and at least one oracle module. The spatially-optimized simulation may be configured to provide a distributed, persistent, fault-tolerate and spatially-optimized simulation environment. In some embodiments, load balancing and fault tolerance may be performed using transfer scores and/or tensile energies determined among the candidates for transferring simulation entities among workers. In some embodiments, the plurality of bridge modules may expose an application programming interface (API) for communicating with the plurality of worker modules.

Claims

1. A method for communicating with a worker module in a spatially-optimized simulation, said method comprising:

exposing a first Application Programming Interface (API) for adding an entity to the simulation;

exposing a second API for removing the entity from the simulation;

exposing a third API for notifying the worker module of a change in a state of a component;

exposing a fourth API for delegating authority of the component;

exposing a fifth API for removing delegation authority of the component;

exposing a sixth API for setting delegation authority of the component; and

exposing a seventh API for updating the state of a component that has delegated authority to the worker module.

2. The method of claim 1, wherein the first API comprises a first parameter indicating the entity to be added and a second parameter indicating an initial state of the entity, and wherein the first API triggers addition of the entity to a spatial region assigned to the worker module.

3. The method of claim 2, wherein the second API comprises a third parameter indicating the entity to be removed, and wherein the second API triggers removal of the entity from the spatial region assigned to the worker module.

4. The method of claim 3, wherein the third API comprises a fourth parameter indicating the entity comprising the component to be modified and a fifth parameter indicating the state of the component, and wherein the third API triggers modification of the state of the entity in the simulation.

5. The method of claim 4, wherein the fourth API comprises a sixth parameter indicating the entity comprising the component to be delegated and a seventh parameter indicating the component to be delegated, and wherein the fourth API triggers the component to delegate authority to the worker module.

6. The method of claim 5, wherein the fifth API comprises an eighth parameter indicating the entity comprising the component to be undelegated and a ninth parameter indicating the component to be undelegated, and wherein the fifth API triggers the component to remove delegation authority from the worker module.

7. The method of claim 6, wherein the sixth API comprises a tenth parameter indicating the entity comprising the component, an eleventh parameter indicating the component, and a twelfth parameter indicating to set delegation authority on the component, and where the sixth API triggers the component to delegate authority to the worker module.

8. The method of claim 6, wherein the sixth API comprises a tenth parameter indicating the entity comprising the component, an eleventh parameter indicating the component, and a twelfth parameter indicating to unset delegation authority on the component, and where the sixth API triggers the component to remove delegation authority from the worker module.

9. The method of claim 7, wherein the seventh API comprises a thirteenth parameter indicating the entity comprising the component to be updated and a fourteenth parameter indicating the state of the component, and wherein the seventh API triggers update of the state of the entity.

10. The method of claim 8, wherein the seventh API comprises a thirteenth parameter indicating the entity comprising the component to be updated and a fourteenth parameter indicating the state of the component, and wherein the seventh API triggers notification of a change in the state of the component.

11. A method for communicating with a worker module in a spatially-optimized simulation, said method comprising:

adding an entity to the simulation responsive to receiving a message in accordance with a format of a first Application Programming Interface (API);

removing the entity from the simulation responsive to receiving a message in accordance with a format of a second API;

modifying a state of a component of an entity being simulated responsive to receiving a message in accordance with a format of a third API;

delegating authority of the component responsive to receiving a message in accordance with a format of a fourth API;

removing delegation authority of the component responsive to receiving a message in accordance with a format of a fifth API;

setting delegation authority of the component responsive to receiving a message in accordance with a format of a sixth API; and

transmitting a message in accordance with a format of a seventh API responsive to updating the state of the component.

12. The method of claim 11, wherein the first API comprises a first parameter indicating the entity to be added and a second parameter indicating an initial state of the entity, and wherein the first API triggers addition of the entity to a spatial region assigned to the worker module.

13. The method of claim 12, wherein the second API comprises a third parameter indicating the entity to be removed, and wherein the second API triggers removal of the entity from the spatial region assigned to the worker module.

14. The method of claim 13, wherein the third API comprises a fourth parameter indicating the entity comprising the component to be modified and a fifth parameter indicating the state of the component, and wherein the third API triggers modification of the state of the entity in the worker module.

15. The method of claim 14, wherein the fourth API comprises a sixth parameter indicating the entity comprising the component to be delegated and a seventh parameter indicating the component to be delegated, and wherein the fourth API triggers the component to delegate authority to the worker module.

16. The method of claim 15, wherein the fifth API comprises an eighth parameter indicating the entity comprising the component to be undelegated and a ninth parameter indicating the component to be undelegated, and wherein the fifth API triggers the component to remove delegation authority from the worker module.

17. The method of claim 16, wherein the sixth API comprises a tenth parameter indicating the entity comprising the component, an eleventh parameter indicating the component, and a twelfth parameter indicating to set delegation authority on the component, and where the sixth API triggers the component to delegate authority to the worker module.

18. The method of claim 16, wherein the sixth API comprises a tenth parameter indicating the entity comprising the component, an eleventh parameter indicating the component, and a twelfth parameter indicating to unset delegation authority on the component, and where the sixth API triggers the component to remove delegation authority from the worker module.

19. The method of claim 17, wherein the seventh API comprises a thirteenth parameter indicating the entity comprising the component to be updated and a fourteenth parameter indicating the state of the component, and wherein the seventh API triggers update of the state of the entity.

20. The method of claim 18, wherein the seventh API comprises a thirteenth parameter indicating the entity comprising the component to be updated and a fourteenth parameter indicating the state of the component, and wherein the seventh API triggers modification of the state of the entity in the simulation.