# US 2021/0243263 A1 · Container and data mobility platform for edge networks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0243263 A1 - Document ID: US20210243263A1 - Status: Published application - Kind: A1 - Application number: 16/779,013 - Filed: 2020-01-31 - Published: 2021-08-05 - Earliest claimed: 2020-01-31 - Assignees: EMC IP Holding Company LLC - Applicants: EMC IP Holding Company LLC - Inventors: Victor Fong; Kenneth Durazzo; Robert A. Lincourt - Web page: https://patentgrep.com/patent/US20210243263A1 ## CPC - H04L 67/148: Migration or transfer of sessions - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57) - G06F 9/5072: {Grid computing} - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A software and/or data mobility platform. The mobility of software and data in an edge network is achieved by loading software and/or data on an edge node. The software and data are replicated or migrated to neighbor nodes and prepared for the device when the device switches nodes. As the device switched nodes, clean up or mobility operations are performed by replicating or migrating the software/data to new neighbor nodes and deleting or removing the software/data from nodes that are no longer considered to be neighbor nodes. The software is typically deployed to the mobility platform rather than directly to the nodes to allow developers to focus on their application rather than on the mobility of the application. ## Claims ### Claim 1 A method, comprising: loading a container using a mobility platform installed on an edge node of an edge network in response to a request from a device associated with an end user, wherein the mobility platform is independent of a service provider associated with the edge node and independent of the container; loading the container into mobility platforms of neighbor nodes of the edge node; warming up the container on the neighbor nodes; replicating user data to the neighbor nodes; determining that the device has moved from the edge node to a first neighbor node included in the neighbor nodes, wherein the device has disconnected from the edge node and connected with the first neighbor node; and running the container that has been loaded and warmed up on the first neighbor node with the device. ### Claim 2 (depends on 1) The method of claim 1, further comprising receiving the request from the device. ### Claim 3 (depends on 1) The method of claim 1, further comprising loading user data on the edge node and replicating the user data to the device. ### Claim 4 (depends on 1) The method of claim 1, further comprising deleting the container replicated to the neighbor nodes that are no longer neighbor nodes to the first neighbor node once the device has connected with the first neighbor node. ### Claim 5 (depends on 4) The method of claim 4, further comprising loading the container on at least one additional edge node that is determined to be a new neighbor node of the first neighbor node. ### Claim 6 (depends on 3) The method of claim 3, further comprising backing up the user data to a datacenter. ### Claim 7 (depends on 1) The method of claim 1, further comprising installing a mobility platform on the edge network, wherein instances of the mobility platform are installed on each of the edge nodes and on a datacenter associated with the edge nodes. ### Claim 8 (depends on 7) The method of claim 7, further comprising deploying the container to the mobility platform such that the mobility platform orchestrates movement of the container and user data in the edge network. ### Claim 9 (depends on 8) The method of claim 8, further comprising tracking each user connected to each of the edge nodes. ### Claim 10 (depends on 1) The method of claim 1, further comprising performing mobility operations after each migration of the container associated with movement of the device wherein the mobility operations include replicating the container and/or user data to edge nodes that become neighbor nodes and removing the container and/or user data from neighbor nodes that are no longer neighbor nodes. ### Claim 11 A non-transitory storage medium having stored therein instructions that are executable one or more hardware processors to perform operations comprising: loading a container using a mobility platform installed on an edge node of an edge network in response to a request from a device associated with an end user, wherein the mobility platform is independent of a service provider associated with the edge node and independent of the container; loading the container into mobility platforms of neighbor nodes of the edge node; warming up the container on the neighbor nodes; replicating user data to the neighbor nodes; determining that the device has moved from the edge node to a first neighbor node included in the neighbor nodes, wherein the device has disconnected from the edge node and connected with the first neighbor node; and running the container that has been loaded and warmed up on the first neighbor node with the device. ### Claim 12 (depends on 11) The non-transitory storage medium of claim 11, the operations further comprising receiving the request from the device. ### Claim 13 (depends on 11) The non-transitory storage medium of claim 11, the operations further comprising loading user data on the edge node and replicating the user data to the device. ### Claim 14 (depends on 11) The non-transitory storage medium of claim 11, the operations further comprising deleting the container replicated to the neighbor nodes that are no longer neighbor nodes to the first neighbor node once the device has connected with the first neighbor node. ### Claim 15 (depends on 14) The non-transitory storage medium of claim 14, the operations further comprising loading the container on at least one additional edge node that is determined to be a new neighbor node of the first neighbor node. ### Claim 16 (depends on 13) The non-transitory storage medium of claim 13, the operations further comprising backing up the user data to a datacenter. ### Claim 17 (depends on 11) The non-transitory storage medium of claim 11, the operations further comprising installing a mobility platform on the edge network, wherein instances of the mobility platform are installed on each of the edge nodes and on a datacenter associated with the edge nodes. ### Claim 18 (depends on 17) The non-transitory storage medium of claim 17, the operations further comprising deploying the container to the mobility platform such that the mobility platform orchestrates movement of the container and user data in the edge network. ### Claim 19 (depends on 18) The non-transitory storage medium of claim 18, the operations further comprising tracking each user connected to each of the edge nodes. ### Claim 20 (depends on 11) The non-transitory storage medium of claim 11, the operations further comprising performing mobility operations after each migration of the container associated with movement of the device wherein the mobility operations include replicating the container and/or user data to edge nodes that become neighbor nodes and removing the container and/or user data from neighbor nodes that are no longer neighbor nodes.