Intra-code communication in a localized device coordinator

• US 10,417,049 B2
• Filed: 11/28/2016
• Issued: 09/17/2019
• Est. Priority Date: 11/28/2016
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Pan, Cheng, Kuo, Calvin Yue-Ren, Turow, Jonathan I., Brooker, Marc John, Sorenson, III, James Christopher, McClenahan, Weili Zhong
• Primary Examiner(s): Dao, Tuan C
• Assistant Examiner(s): Wood, William C
• Application Number:
  US15/362,708
• Publication Number:
  US 20180150339A1
• Time in Patent Office: 1,023 Days
• Field of Search: None
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals

Abstract

Systems and methods are described for implementing a coordinator within a coordinated environment, which environment includes set of coordinated devices managed by the coordinator. The coordinator can be provisioned with a set of tasks, each task corresponding to a segment of code that can be executed by the coordinator, such as to manage the coordinated devices. To assist in execution of the tasks, the coordinator can include a communications manager that enables communications between tasks. The communications manager can provide a language-independent interface to call for execution of tasks, pass information to a task, and obtain outputs of a task. In some embodiments, the communication manager may utilize a language-independent protocol, such as the hypertext transport protocol, and be configured to respond to requests addressed to uniform resource identifiers associated with the communications manager.

Claims

1. A coordinator computing device implementing a communication manager enabling communications between executions of tasks on the coordinator computing device, wherein the coordinator computing device is configured to manage one or more coordinated devices within a coordinated environment, the system comprising:

a non-transitory data store including computer executable instructions corresponding to the communication manager that, when executed, enables communication between tasks executions on the coordinator computing device, wherein individual tasks correspond to code executable by the coordinator computing device to manage operation of the one or more coordinated devices;

a processor in communication with the non-transitory data store and configured to execute the communication manager, wherein execution of the communication manager causes the processor to;

obtain a call message from an execution of a first task on the coordinator computing device, wherein the call message is addressed to a resource identifier associated with a second task, and wherein the call message includes parameters to be passed to an execution of the second task;

identify the second task from at least the resource identifier to which the call message is addressed;

cause execution of the second task on the coordinator computing device;

transmit an execution identifier to the execution of the second task, wherein the execution identifier identifies the execution of the second task, as distinct from other executions of the second task;

obtain a return message from the execution of the second task, wherein the return message specifies the execution identifier;

obtain a return request message from the execution of the first task, wherein the return request message requests an output of the execution of the second task and specifies the execution identifier;

identify the return message as the output of the execution of the second task requested in the return request message based at least in part on matching the execution identifier, as included within the return message, with the execution identifier as included within the return request message; and

return the output of the execution of the second task to the execution of the first task.

2. The coordinator computing device of claim 1, wherein at least one of the call message or the return message are a hypertext transport protocol (HTTP) message.

3. The coordinator computing device of claim 1, wherein the processor is further configured to generate execution environments for the respective executions of the first task and of the second task, and wherein the execution environments are isolated from one another.

4. The coordinator computing device of claim 1, wherein execution of the communication manager further causes the processor to validate security information within the call message.

5. The coordinator computing device of claim 1, wherein the return message specifies the execution identifier by including the execution identifier in at least one of an address to which the return message is transmitted or a header field of the return message.

6. Non-transitory computer readable media including instructions executable by a coordinator computing device to implement a communication manager enabling communications between executions of tasks on the coordinator computing device, wherein individual tasks of correspond to code executable by the coordinator computing device to manage operation of the one or more coordinated devices, and wherein execution of the instructions causes the coordinator computing device to:

obtain a call message from an execution of a first task on the coordinator computing device, wherein the call message is addressed to a resource identifier associated with a second task;

identify the second task from at least the resource identifier to which the call message is addressed;

cause execution of the second task on the coordinator computing device;

obtain a return message from the execution of the second task, wherein the return message includes an execution identifier associated with the execution of the second task and wherein the execution identifier identifies the execution of the second task, as distinct from other executions of the second task;

obtain a return request message from the execution of the first task, wherein the return request message requests an output of the execution of the second task and specifies the execution identifier;

identify the return message as the output of the execution of the second task requested in the return request message based at least in part on matching the execution identifier, as included within the return message, with the execution identifier as included within the return request message; and

return the output of the execution of the second task to the execution of the first task.

7. The non-transitory computer readable media of claim 6, wherein the return request message is obtained prior to obtaining the return message.

8. The non-transitory computer readable media of claim 6, wherein the call message includes a priority to be assigned to the execution of the second task.

9. The non-transitory computer readable media of claim 6, wherein the resource identifier associated with the second task includes a domain name associated with the coordinator computing device, a port associated with the communication manager, and a path associated with the second task.

10. The non-transitory computer readable media of claim 6, wherein the resource identifier associated with the second task is a uniform resource identifier.

11. The non-transitory computer readable media of claim 6, wherein the first task and the second task are the same task.

12. A computer-implemented method to enable communication between executions of tasks on the coordinator computing device, wherein individual tasks of correspond to code executable by the coordinator computing device, the computer-implemented method comprising:

obtaining a call message from an execution of a first task on the coordinator computing device, wherein the call message is addressed to a resource identifier associated with a second task;

identifying the second task from at least the resource identifier to which the call message is addressed;

causing execution of the second task on the coordinator computing device;

obtaining a return message from the execution of the second task, wherein the return message includes an execution identifier associated with the execution of the second task, and wherein the execution identifier identifies the execution of the second task, as distinct from other executions of the second task;

obtaining a return request message from the execution of the first task, wherein the return request message requests an output of the execution of the second task and specifies the execution identifier;

identifying the return message as the output of the execution of the second task requested in the return request message based at least in part on matching the execution identifier, as included within the return message, with the execution identifier as included within the return request message; and

returning the output of the execution of the second task to the execution of the first task.

13. The computer-implemented method of claim 12 further comprising at least one of assigning the execution identifier to the execution of the second task or identifying, within the call message, the execution identifier.

14. The computer-implemented method of claim 12 further comprising passing the execution identifier to the execution of the second task.

15. The computer-implemented method of claim 12, wherein causing execution of the second task on the coordinator computing device comprises generating an execution environment for the execution of the second task on the coordinator computing device.

16. The computer-implemented method of claim 12, wherein returning the output of the execution of the second task to the execution of the first task comprises returning the output as a push message to the first task.

17. The computer-implemented method of claim 12, wherein the first task corresponds to code of a first programming language and the second task corresponds to code of a second programming language.

18. The computer-implemented method of claim 12, wherein the return request message is obtained prior to obtaining the return message.