Location based application migration for enhancing lightweight IoT device applications

Patent metadata

Field	Value
Publication number	US-11917724-B2
Application number	US-201916453647-A
Country	US
Kind code	B2
Filing date	Jun 26, 2019
Priority date	Jun 26, 2019
Publication date	Feb 27, 2024
Grant date	Feb 27, 2024

Abstract

One example method includes receiving input concerning a mobile IoT device, and the input includes information about a location of the mobile IoT device, information about whether the mobile IoT device is moving, and, when the mobile IoT device is moving, information about the range, speed, and bearing of the mobile IoT device. Next, the method includes generating a predicted location of the mobile IoT device based on the inputs received, using the predicted location of the mobile IoT device and a map of nodes in an environment where the mobile IoT device is located to make a migration decision concerning an application used by the mobile IoT device, and migrating the application from a present location to a node expected to be accessible by the mobile IoT device when the mobile IoT device reaches the predicted location, and the node and present location are physically separated by a distance.

First claim

What is claimed is:

1. A method, comprising:
receiving input concerning a mobile IoT device, and the input comprises: information about a location of the mobile IoT device; information about a direction and orientation of the mobile IoT device; resources available at a set of nodes; time required to migrate an application; information about whether the mobile IoT device is moving; and, when the mobile IoT device is moving, information about the range, speed, planned trajectory, and bearing of the mobile IoT device;
generating a predicted location at a given point in time of the mobile IoT device based on the input received;
using the predicted location at the given point in time of the mobile IoT device, a map of nodes in an environment containing the set of nodes where the mobile IoT device is located, and the input to make a decision as to whether to migrate part or all of the application, used by the mobile IoT device, from a first node at which the application is executable to a second node expected to be accessible by the mobile IoT device when the mobile IoT device reaches the predicted location;
migrating a portion of the application from the first node to the second node, wherein the portion of the application includes differences between a current application state and an instance of the application existing at the second node and the second node and the first node are physically separated by a distance;
in response to obtaining information indicating the predicted location, automatically pre-positioning a resource at the second node, and the resource comprises a resource that is needed to support operation of the application, and wherein pre-positioning the resource comprises replicating a virtual machine, and/or a replicating a container, at the second node; and
notifying the mobile IoT device that the resource is in process of being migrated, is expected to be available for use by the mobile IoT device at the second node, and when the resource is expected to be available based on an estimated time required to migrate the resource.

2. The method as recited in claim 1 , wherein the mobile IoT device lacks adequate on-board processing capability to run the application on the mobile IoT device.

3. The method as recited in claim 1 , further comprising initially deciding, prior to making the migration decision, to replicate the application to several candidate nodes in parallel.

4. The method as recited in claim 1 , wherein the second node is selected to receive the application from the first node based on an expected latency of communications between the second node and the mobile IoT device.

5. The method as recited in claim 1 , wherein the portion of the application is migrated automatically from the first node to the second node when the mobile IoT device reaches the predicted location.

6. The method as recited in claim 1 , wherein migration of the portion of the application begins prior to the mobile IoT device reaching the predicted location.

7. The method as recited in claim 1 , wherein the mobile IoT device is an unmanned vehicle, or an autonomous vehicle.

8. The method as recited in claim 1 , wherein the application is accessible to, and usable by, the mobile IoT device at the second node when the mobile IoT device arrives at the expected location.

9. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
receiving input concerning a mobile IoT device, and the input comprises: information about a location of the mobile IoT device; information about a direction and orientation of the mobile IoT device; resources available at a set of nodes; time required to migrate an application; information about whether the mobile IoT device is moving; and, when the mobile IoT device is moving, information about the range, speed, and bearing of the mobile IoT device;
generating a predicted location at a given point in time of the mobile IoT device based on the input received;
using the predicted location at the given point in time of the mobile IoT device, a map of nodes in an environment containing the set of nodes where the mobile IoT device is located, and the input to make a decision as to whether to migrate part or all of an application, used by the mobile IoT device, from a first node at which the application is executable to a second node expected to be accessible by the mobile IoT device when the mobile IoT device reaches the predicted location;
migrating a portion of the application from the first node to the second node, wherein the portion of the application includes differences between a current application state and an instance of the application existing at the second node and the second node and the first node are physically separated by a distance;
in response to obtaining information indicating the predicted location, automatically pre-positioning a resource at the second node, and the resource comprises a resource that is needed to support operation of the application, and wherein pre-positioning the resource comprises replicating a virtual machine, and/or a replicating a container, at the second node; and
notifying the mobile IoT device that the resource is in process of being migrated, is expected to be available for use by the mobile IoT device at the second node, and when the resource is expected to be available based on an estimated time required to migrate the resource.

10. The non-transitory storage medium as recited in claim 9 , wherein the mobile IoT device lacks adequate on-board processing capability to run the application on the mobile IoT device.

11. The non-transitory storage medium as recited in claim 9 , wherein the operations further comprise initially deciding, prior to making the migration decision, to replicate the application to several candidate nodes in parallel.

12. The non-transitory storage medium as recited in claim 9 , wherein the second node is selected to receive the application from the first node based on an expected latency of communications between the second node and the mobile IoT device.

13. The non-transitory storage medium as recited in claim 9 , wherein the portion of the application is migrated automatically from the first node to the second node when the mobile IoT device reaches the predicted location.

14. The non-transitory storage medium as recited in claim 9 , wherein migration of the portion of the application begins prior to the mobile IoT device reaching the predicted location.

15. The non-transitory storage medium as recited in claim 9 , wherein the mobile IoT device is an unmanned vehicle, or an autonomous vehicle.

16. The non-transitory storage medium as recited in claim 9 , wherein the application is accessible to, and usable by, the mobile IoT device at the node when the mobile IoT device arrives at the expected location.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Shemer Jehuda
• Wolfson Kfir
• Natanzon Assaf

Classifications

• B64U10/14

  with four distinct rotor axes, e.g. quadcopters · CPC title

• H04W80/10 Primary

  adapted for {application} session management, e.g. SIP [Session Initiation Protocol] {(connection management H04W76/00; arrangements for session management H04L67/14)} · CPC title

• B64C39/024

  of the remote controlled vehicle type, i.e. RPV · CPC title

• H04W4/027

  using movement velocity, acceleration information · CPC title

• H04W4/029

  Location-based management or tracking services · CPC title