WO2019015669A1 - Service migration method and apparatus - Google Patents

Service migration method and apparatus Download PDF

Info

Publication number
WO2019015669A1
WO2019015669A1 PCT/CN2018/096441 CN2018096441W WO2019015669A1 WO 2019015669 A1 WO2019015669 A1 WO 2019015669A1 CN 2018096441 W CN2018096441 W CN 2018096441W WO 2019015669 A1 WO2019015669 A1 WO 2019015669A1
Authority
WO
WIPO (PCT)
Prior art keywords
fog
migration
fog node
service
node
Prior art date
Application number
PCT/CN2018/096441
Other languages
French (fr)
Chinese (zh)
Inventor
刘芙蕾
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019015669A1 publication Critical patent/WO2019015669A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions

Definitions

  • the present disclosure relates to, but is not limited to, the field of edge computing techniques.
  • OpenFog The Open Fog Alliance (OpenFog) aims to accelerate the deployment of fog technology by developing core technologies such as open architecture, distributed computing, networking and storage. The goal is to promote industrial and academic institutions in fog computing architecture, test development, and interoperability. The study of assembleable lines enables seamless connectivity from edge to cloud architecture, making end-to-end Internet of Things (IOT) scenarios a reality.
  • OpenFog's reference architecture is a vertical, system-level architecture that distributes compute, storage, communication, control, and networking functions closer to users. The reference architecture represents a shift from a traditional closed system and a cloud-dependent model to a new computing model that moves computing from the cloud to the edge, even to IoT sensors and actuators.
  • the computation, network, storage, and acceleration units in the new model can all be fog nodes.
  • Each layer in the layered architecture consisting of fog nodes provides additional processing, storage, and networking capabilities for vertical application at that layer.
  • the fog node can form a multi-layer fog network architecture, but OpenFog has not yet given a solution for how the application (APP) migrates from one fog node to another in the fog network.
  • An embodiment of the present disclosure provides a service migration method, including: when a source edge fog node determines that its service needs to be migrated, a migration request including a migration service is initiated to a target edge fog node via a fog network; and the target edge fog node receives After the migration request, the resource corresponding to the migration service is activated by configuring the resource of the migration service, and the migration response is sent to the source edge fog node via the fog network; and the source edge fog node receives After the migration response, resources corresponding to the migration service are released.
  • the embodiment of the present disclosure further provides a service migration apparatus, including a source edge fog node and a target edge fog node.
  • a service migration apparatus including a source edge fog node and a target edge fog node.
  • the migration request including the migration service is initiated to the target edge fog node via the fog network, and after receiving the migration response for the migration request, releasing the migration service corresponding to the migration service H.
  • the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node via the fog network.
  • Embodiments of the present disclosure also provide a computer storage medium having stored thereon a computer program that, when executed by a processor, executes a service migration method according to the present disclosure.
  • FIG. 1 is a flowchart of a service migration method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a service migration apparatus according to an embodiment of the present disclosure
  • FIG. 3 is an architectural diagram of a centralized fog network in accordance with an embodiment of the present disclosure
  • FIG. 4 is a flow diagram of mobility within a high-level fog node initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure
  • FIG. 5 is a flow diagram of mobility within a high-level fog node initiated by a fog node in a centralized fog network, in accordance with an embodiment of the present disclosure
  • FIG. 6 is a flow diagram of mobility between high-level fog nodes initiated by a terminal in a centralized fog network, in accordance with an embodiment of the present disclosure
  • FIG. 7 is a flow diagram of mobility between high-level fog nodes initiated by a fog node in a centralized fog network, in accordance with an embodiment of the present disclosure
  • FIG. 8 is an architectural diagram of a distributed fog network in accordance with an embodiment of the present disclosure.
  • FIG. 9 is a flow diagram of mobility initiated by a distributed terminal in accordance with an embodiment of the present disclosure.
  • FIG. 10 is a flow diagram of mobility initiated by a distributed fog node, in accordance with an embodiment of the disclosure.
  • the services described in the embodiments of the present disclosure include services or applications, such as an APP.
  • FIG. 1 is a flow chart of a method of business migration in accordance with an embodiment of the present disclosure.
  • the service migration method may include steps S101 to S103.
  • step S101 the source edge fog node initiates a migration request including the migration service to the target edge fog node via the fog network when determining that its service needs to be migrated.
  • the target edge fog node After receiving the migration request, the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node via the fog network.
  • step S103 after receiving the migration response, the source edge fog node releases the resource corresponding to the migration service.
  • the fog network may comprise a centralized fog network or a distributed fog network.
  • the centralized fog network may include a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node.
  • the distributed fog network can include multiple edge fog nodes.
  • the source edge fog node When the source edge fog node is located in the centralized fog network, if the source edge fog node and the target edge fog node are managed by the same high-level fog node, the source edge fog node initiates the migration service including the migration service to the target edge fog node via the high-level fog node. a migration request; if the source edge fog node and the target edge fog node are managed by different high-level fog nodes, the source edge fog node passes the source high-level fog node managing the source edge fog node and the target high-level fog node managing the target edge fog node to the target The edge fog node initiates a migration request that includes the migration service.
  • the source edge fog node When the source edge fog node is located in the distributed fog network, the source edge fog node directly initiates a migration request including the migration service to the target edge fog node.
  • FIG. 2 is a schematic diagram of a service migration device in accordance with an embodiment of the present disclosure.
  • the service migration apparatus includes a source edge fog node 201 and a target edge fog node 202.
  • the source edge fog node 201 initiates a migration request including the migration service to the target edge fog node 202 via the fog network when determining that its service needs to be migrated, and releases the migration service after receiving the migration response for the migration request.
  • the target edge fog node 202 activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node 201 via the fog network.
  • the fog network may comprise a centralized fog network or a distributed fog network.
  • the centralized fog network may include a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node.
  • the distributed fog network can include multiple edge fog nodes.
  • the source edge fog node 201 When the source edge fog node 201 is located in the centralized fog network, if the source edge fog node 201 and the target edge fog node 202 are managed by the same high-level fog node, the source edge fog node 201 passes the high-level fog node to the target edge fog node 202. Initiating a migration request including a migration service; if the source edge fog node 201 and the target edge fog node 202 are managed by different high-level fog nodes, the source edge fog node 201 manages the source high-level fog node and the management target edge via the source edge fog node 201 The target high-level fog node of the fog node 202 initiates a migration request containing the migration service to the target edge fog node 202.
  • the source edge fog node 201 When the source edge fog node 201 is located in the distributed fog network, the source edge fog node 201 directly initiates a migration request including the migration service to the target edge fog node 202.
  • the fog network can be divided into two types: centralized fog network and distributed fog network.
  • FIG. 3 is an architectural diagram of a centralized multi-layer fog network in accordance with an embodiment of the present disclosure.
  • a fog node having centralized control management in the fog network is called a high-level fog node, and the high-level fog node can manage the edge fog node of the bottom layer.
  • the edge fog node can provide multiple access modes for various devices, and can provide functions such as data acquisition, data format conversion, data reporting, and APP deployment.
  • the high-level fog node can provide functions such as management, data analysis, data processing, and command generation for the edge fog nodes under its jurisdiction.
  • mobility in a fog network can be divided into two layers, namely, seamless mobility at the bearer level and mobility at the fog node level.
  • the seamless mobility at the bearer level is guaranteed by the access network, which guarantees seamless mobility between communication pipes.
  • the mobility at the fog node level ie, the mobility of the APP in the fog network
  • the mobility at the fog node level is performed after the mobility at the bearer level is completed, or can be performed simultaneously with the mobility at the bearer level to reduce the delay.
  • the mobility at the bearer level has been defined by protocols such as the 3rd Generation Partnership Project (3GPP)/Institute of Electrical and Electronics Engineers (IEEE), so the mobility in the fog network is mainly discussed. It is the mobility of the fog node level.
  • 3GPP 3rd Generation Partnership Project
  • IEEE Institute of Electrical and Electronics Engineers
  • the mobility of the APP may include the following three scenarios.
  • Scenario 1 The edge fog node where the APP is located has not changed, but the access network has changed.
  • the access network is changed from Long Term Evolution (LTE) to 5G (edge fog nodes can support multiple access networks).
  • LTE Long Term Evolution
  • 5G edge fog nodes can support multiple access networks.
  • This mobility is guaranteed by an access protocol such as 3GPP/IEEE, and is not within the scope of the present disclosure.
  • Scenario 2 The APP moves from one edge fog node (ie, the source edge fog node) under the jurisdiction of the same High-Tier Fog Node (H-FN) to another edge fog node (ie, the target edge fog node) ). This can be referred to as mobility within the high-level fog node (Intra-HFN). This mobility information interaction is mainly coordinated by the HFN.
  • H-FN High-Tier Fog Node
  • Intra-HFN High-level fog node
  • Scenario 3 The APP moves from one high-level fog node (ie, the source high-level fog node) to another high-level fog node (ie, the target high-level fog node). This can be referred to as the mobility between high-level fog nodes (Inter-HFN).
  • the mobility information interaction is mainly coordinated by the Source-High-Tier Fog Node (S-H-FN) and the Target-High-Tier Fog Node (T-H-FN).
  • Intra-HFN mobility can be divided into the following terminal-initiated mobility and fog-initiated mobility according to different methods initiated.
  • FIG. 4 is a flow diagram of mobility within a high-level fog node initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure.
  • the flow of mobility within the high-level fog node initiated by the terminal in the centralized fog network may include steps S401 to S414.
  • step S401 when the bearer network (access network) of the terminal changes, the APP migration of the terminal is triggered.
  • step S402 the terminal APP instance initiates an APP instance migration request to the H-FN through the APP instance/platform of the Source-Edge Fog Node (S-EFN).
  • S-EFN Source-Edge Fog Node
  • step S403 the H-FN initiates an APP instance migration request to the Target-Edge Fog Node (T-EFN) platform.
  • T-EFN Target-Edge Fog Node
  • the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
  • step S405 the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
  • the T-EFN platform initiates a configuration request to the T-EFN APP instance.
  • step S407 the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
  • step S408 the T-EFN platform replies to the H-FN with an APP instance migration response.
  • step S409 the H-FN replies to the S-EFN with an APP instance migration response.
  • step S410 the APP instance performs state synchronization between S-EFN and T-EFN.
  • FIG. 4 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S410 may be omitted.
  • step S411 the H-FN initiates a termination APP instance request to the S-EFN platform.
  • step S412 a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
  • step S413 a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
  • step S414 the S-EFN platform initiates a termination APP instance response to the H-FN.
  • FIG. 5 is a flow diagram of mobility within a high-level fog node initiated by a fog node in a centralized fog network, in accordance with an embodiment of the disclosure.
  • the flow of mobility within the high-level fog node initiated by the fog node in the centralized fog network may include steps S501 through S515.
  • step S501 when the bearer (access network) of the terminal changes, for example, from LTE to a cellular-based Narrow Band Internet of Things (NB-IOT), the fog node does not support NB-IOT. Access, the fog node triggers the APP migration of the terminal.
  • NB-IOT Narrow Band Internet of Things
  • step S502 the S-EFN APP instance and the S-EFN platform perform a bearer update process.
  • step S503 the S-EFN platform initiates an APP instance migration request to the H-FN.
  • step S504 the H-FN initiates an APP instance migration request to the T-EFN platform.
  • the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
  • step S506 the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
  • step S507 the T-EFN platform initiates a configuration request to the T-EFN APP instance
  • step S508 the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
  • step S509 the T-EFN platform replies to the H-FN with an APP instance migration response.
  • step S510 the H-FN replies to the S-EFN with an APP instance migration response.
  • step S511 the APP instance performs state synchronization between S-EFN and T-EFN.
  • FIG. 5 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S511 can be omitted.
  • step S512 the H-FN initiates a termination APP instance request to the S-EFN platform.
  • step S513 a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
  • a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
  • step S515 the S-EFN platform initiates a termination APP instance response to the H-FN.
  • Inter-HFN mobility can be divided into terminal-initiated mobility and fog-initiated mobility according to different methods initiated.
  • FIG. 6 is a flow diagram of mobility between high-level fog nodes initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure.
  • the flow of mobility between high-level fog nodes initiated by the terminal in the centralized fog network may include steps S601 to S616.
  • step S601 when the bearer (access network) of the terminal changes, the APP migration of the terminal is triggered.
  • step S602 the terminal APP instance initiates an APP instance migration request to the S-H-FN through the APP instance/platform of the S-EFN.
  • step S603 the S-H-FN initiates an APP instance migration request to the T-H-FN.
  • step S604 the T-H-FN initiates an APP instance migration request to the T-EFN platform.
  • the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
  • step S606 the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
  • step S607 the T-EFN platform initiates a configuration request to the T-EFN APP instance.
  • step S608 the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
  • step S609 the T-EFN platform replies to the T-H-FN with an APP instance migration response.
  • the T-H-FN replies to the S-H-FN with an APP instance migration response.
  • step S611 the S-H-FN replies to the S-EFN with an APP instance migration response.
  • step S612 the APP instance performs state synchronization between S-EFN and T-EFN.
  • FIG. 6 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S612 may be omitted.
  • step S613 the S-H-FN initiates a termination APP instance request to the S-EFN platform.
  • step S614 a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
  • a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
  • step S616 the S-EFN platform initiates a termination APP instance response to the S-H-FN.
  • FIG. 7 is a flow diagram of mobility between high-level fog nodes initiated by a fog node in a centralized fog network, in accordance with an embodiment of the disclosure.
  • the flow of mobility between high-level fog nodes initiated by the fog node in the centralized fog network may include steps S701 to S717.
  • step S701 when the bearer (access network) of the terminal changes, for example, from LTE to NB-IOT, and the fog node does not support NB-IOT access, the fog node triggers APP migration of the terminal.
  • step S702 the S-EFN APP instance and the S-EFN platform perform a bearer update process.
  • step S703 the S-EFN platform initiates an APP instance migration request to the S-H-FN.
  • step S704 the S-H-FN initiates an APP instance migration request to the T-H-FN.
  • step S705 the T-H-FN initiates an APP instance migration request to the T-EFN platform.
  • the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
  • step S707 the infrastructure of the T-EFN allocates resources and then replies to the resource allocation response to the T-EFN platform.
  • the T-EFN platform initiates a configuration request to the T-EFN APP instance.
  • step S709 the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
  • step S710 the T-EFN platform replies to the T-H-FN with an APP instance migration response.
  • step S711 the T-H-FN replies to the S-H-FN with an APP instance migration response.
  • step S712 the S-H-FN replies to the S-EFN with an APP instance migration response.
  • step S713 the APP instance performs state synchronization between the S-EFN and the T-EFN.
  • FIG. 7 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, there is no need to perform APP state synchronization, that is, step S713 may be omitted.
  • step S714 the S-H-FN initiates a termination APP instance request to the S-EFN platform.
  • step S715 a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
  • a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
  • step S717 the S-EFN platform initiates a termination APP instance response to the S-H-FN.
  • the APP mobility discussed above is not limited to a centralized fog network composed of two layers of fog nodes, but can also be applied to a multi-layer centralized fog network architecture composed of multi-layer fog nodes.
  • FIG. 8 is an architectural diagram of a distributed fog network in accordance with an embodiment of the present disclosure.
  • each fog node performs an independent function in a distributed fog network.
  • the fog node can provide multiple access modes for various devices, and can provide functions such as data collection, data format conversion, data analysis and processing, command generation, reporting data to the cloud, and APP deployment.
  • mobility in a fog network can be divided into two layers, namely, seamless mobility at the bearer level and mobility at the fog node level.
  • the seamless mobility at the bearer level is guaranteed by the access network, which guarantees seamless mobility between communication pipes.
  • the mobility at the fog node level ie, the mobility of the APP in the fog network
  • the mobility at the fog node level is performed after the mobility at the bearer level is completed, or can be performed simultaneously with the mobility at the bearer level to reduce the delay.
  • the mobility at the bearer level has been defined by protocols such as 3GPP/IEEE. Therefore, the mobility in the fog network mainly discusses the mobility at the fog node level.
  • the mobility of the APP may include the following two scenarios.
  • Scenario 1 The fog node where the APP is located has not changed, but the access network has changed.
  • the access network is changed from LTE to 5G (the fog node can support multiple access networks).
  • the fog node can support multiple access networks.
  • This mobility is guaranteed by an access protocol such as 3GPP/IEEE, and is not within the scope of the present disclosure.
  • Scenario 2 The APP moves from one fog node to another.
  • the information interaction of the mobility is mainly coordinated by the source fog node and the target fog node.
  • the mobility between the fog nodes is divided into two types: mobility initiated by the terminal and mobility initiated by the fog node.
  • FIG. 9 is a flow diagram of mobility initiated by a distributed terminal in accordance with an embodiment of the disclosure.
  • the flow of mobility initiated by the distributed terminal may include steps S901 to S906.
  • step S901 when the bearer (access network) of the terminal changes, the terminal triggers APP migration.
  • step S902 the terminal APP initiates an APP instance migration request to the source-fog node (S-FN).
  • step S903 the S-FN initiates an APP instance migration request to the target-fog node (T-FN).
  • step S904 after the T-FN allocates the resources and completes the corresponding configuration, the T-FN replies with the configuration response to the S-FN.
  • step S905 the APP instance performs state synchronization between the S-FN and the T-FN.
  • FIG. 9 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, APP state synchronization is not required, that is, step S905 may be omitted.
  • step S906 the S-FN completes the release of the corresponding resource of the migrated APP.
  • the following shows the flow shown in FIG. 9 by taking the car search positioning as an example.
  • Scene setting The user parks the car in the underground garage of the commercial area A and goes shopping in the business district B. After the meal is over, the user sends a picture of the vehicle to the car search app to help the user locate the vehicle and navigate the route to the vehicle.
  • the underground garage of the commercial area A is covered by LoRa
  • the commercial area B is covered by LTE
  • the commercial area A and the commercial area B respectively deploy a fog node.
  • the user initiates an application request at the source fog node S-FN of the business area B and moves to the business area A, so the target fog node T-FN of the business area A is required to complete the application task.
  • the search for the car also needs to be transferred from the S-FN of the commercial area B to the T-FN of the commercial area A due to the handover of the LoRa to the LTE bearer, triggering APP migration of the terminal.
  • the terminal APP instance initiates an APP instance migration request to the S-FN platform
  • the S-FN platform initiates an APP instance migration request to the T-FN platform.
  • the T-FN platform initiates a resource allocation request to the T-FN infrastructure, and the T-FN infrastructure allocates resources and then replies to the T-FN platform with a resource allocation response.
  • the T-FN platform initiates a configuration request to the T-FN APP instance, and the T-FN APP instance returns the configuration response to the T-FN platform after completing the resource configuration.
  • the T-FN platform replies to the S-FN platform with an APP instance migration response, and the S-FN platform replies to the S-FN APP instance with an APP instance migration response, and the APP instance performs state synchronization between the S-FN and the T-FN.
  • the process of terminating the APP instance is performed between the S-FN platform and the S-FN APP instance, and the resource deletion process is performed between the S-FN platform and the S-FN infrastructure.
  • FIG. 10 is a flow diagram of mobility initiated by a distributed fog node, in accordance with an embodiment of the disclosure.
  • the flow of mobility initiated by the distributed fog node may include steps S1001 through S1006.
  • step S1001 when the bearer (access network) of the terminal changes, the fog node can trigger the APP migration of the terminal (for example, the fog node does not support some access mode).
  • step S1002 the S-FN completes the bearer update process.
  • step S1003 the S-FN initiates an APP instance migration request to the T-FN.
  • step S1004 after the T-FN allocates the resources and completes the corresponding configuration, the T-FN replies with the configuration response to the S-FN.
  • step S1005 the APP instance performs state synchronization between the S-FN and the T-FN.
  • FIG. 10 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, there is no need to perform APP state synchronization, that is, step S1005 may be omitted.
  • step S1006 the S-FN completes the release of the corresponding resource of the migrated APP.
  • the APP mobility discussed above is not limited to a distributed fog network composed of a layer of fog nodes, but also applicable to a multi-layer distributed fog network architecture composed of multi-layer fog nodes.
  • a multi-layer distributed fog network when the migration of the fog node occurs in the APP, the interaction between the source fog node and the target fog node is directly performed without passing through the other third fog node.
  • the fog node of Building A is S-FN
  • the fog node of Building B is T-FN.
  • the fog nodes deployed in Buildings A and B complete the video surveillance of the working status of the power equipment in the building. When the equipment has an abnormality, it can generate an early warning, and the information about the working condition of the building's power equipment is periodically transmitted to the power maintenance provider. Cloud platform for data backup and analysis.
  • the fog node load of Building A is overloaded and part of the work needs to be diverted to the fog section of Building B
  • the fog node S-FN migrates part of the ongoing video image analysis to the fog node T-FN.
  • the T-FN platform initiates a resource allocation request to the T-FN infrastructure, and the T-FN infrastructure allocates resources and then replies to the T-FN platform with a resource allocation response.
  • the T-FN platform initiates a configuration request to the T-FN APP instance, and the T-FN APP instance returns the configuration response to the T-FN platform after completing the resource configuration.
  • the T-FN platform of Building B initiates an APP migration response to the S-FN of Building A, and the S-FN platform of Building A informs the S-FN APP instance that the state synchronization of the migration APP is ready.
  • the resource release is completed between the S-FN platform and the S-FN APP instance of the building A, and the S-FN platform and the S-FN of the building A are completed.
  • the resources are released between the infrastructures and the process ends.
  • the neighbor relationship between each fog node has been configured, and the service or application moves from the source edge fog node to the target edge fog node.
  • the service or application movement can be completed by each edge fog node between the source edge fog node and the target edge fog node. . That is to say, the service or application always moves from the source edge fog node to the adjacent edge fog node in the fog network, and then moves the adjacent edge fog node as a new source edge fog node to the target edge fog node.
  • a computer readable storage medium such as a floppy disk, an optical disk, a hard disk, a flash memory, a USB flash drive, a CF card, an SD card, an MMC card, etc.
  • the implementation is stored according to the computer readable storage medium
  • the one or more programs may be read and executed by a processor to implement the service migration method according to the above embodiments.
  • each module or step of the above disclosure may be implemented by a general-purpose computing device, and each module or step may be centralized on a single computing device or distributed among multiple computing devices. online.
  • each module or step may be implemented by a program code executable by a computing device, such that the program code may be stored in a computer storage medium (ROM/RAM, disk, optical disk) by a computing device, and
  • the steps shown or described may be performed in a different order than the ones described herein, or each module or step may be separately fabricated into individual integrated circuit modules, or multiple modules or steps in each module or step. It is made into a single integrated circuit module. Therefore, the present disclosure is not limited to any specific combination of hardware and software.
  • the mobility of a service or an application moving from one fog node to another is solved, and the user experience is improved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The present invention relates to the technical field of edge computing. Disclosed are a service migration method and apparatus. The method comprises: a source edge fog node initiates a migration request containing a migration service to a target edge fog node by means of a fog network when determining that a service of the source edge fog node needs to be migrated; after receiving the migration request, the target edge fog node activates a service corresponding to the migration service by configuring a resource for the migration service, and sends a migration response to the source edge fog node by means of the fog network; and the source edge fog node release the resource corresponding to the migration service after receiving the migration response.

Description

业务迁移方法及装置Business migration method and device 技术领域Technical field
本公开涉及(但不限于)边缘计算技术领域。The present disclosure relates to, but is not limited to, the field of edge computing techniques.
背景技术Background technique
开放雾联网联盟(OpenFog)旨在通过开发开放式架构、分布式计算、联网和存储等核心技术加快雾技术的部署，其目标在于促进工业和学术机构在雾计算架构、测试开发、交互性操作、可组装线的研究，使得从边缘到云的架构无缝连接，从而使端到端的物联网(Internet of Things，IOT)场景变成现实。OpenFog的参考架构是一个垂直的、***级别的架构，将计算、存储、通讯、控制、网络功能分布到更靠近用户的地方。该参考架构代表了从传统封闭***和依赖于云计算的模型转变为一个新的计算模型，即，将计算从云端移动到靠近边缘的地方，甚至是物联网传感器和执行器上。新模型中的计算、网络、存储和加速单元都可以成为雾节点。雾节点组成的分层架构中的每一层都会提供垂直应用在该层的附加处理、存储、网络能力。雾节点可以组成多层雾网络架构，但是对于应用(APP)如何在雾网络中从一个雾节点迁移到另一个雾节点，OpenFog目前还没有给出解决方案。The Open Fog Alliance (OpenFog) aims to accelerate the deployment of fog technology by developing core technologies such as open architecture, distributed computing, networking and storage. The goal is to promote industrial and academic institutions in fog computing architecture, test development, and interoperability. The study of assembleable lines enables seamless connectivity from edge to cloud architecture, making end-to-end Internet of Things (IOT) scenarios a reality. OpenFog's reference architecture is a vertical, system-level architecture that distributes compute, storage, communication, control, and networking functions closer to users. The reference architecture represents a shift from a traditional closed system and a cloud-dependent model to a new computing model that moves computing from the cloud to the edge, even to IoT sensors and actuators. The computation, network, storage, and acceleration units in the new model can all be fog nodes. Each layer in the layered architecture consisting of fog nodes provides additional processing, storage, and networking capabilities for vertical application at that layer. The fog node can form a multi-layer fog network architecture, but OpenFog has not yet given a solution for how the application (APP) migrates from one fog node to another in the fog network.
发明内容Summary of the invention
本公开实施例提供了一种业务迁移方法，包括：源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求；所述目标边缘雾节点收到所述迁移请求后，通过对所述迁移业务的资源进行配置，激活与所述迁移业务对应的业务，并经由雾网络向源边缘雾节点发送迁移响应；以及所述源边缘雾节点收到所述迁移响应后，释放与所述迁移业务相应的资源。An embodiment of the present disclosure provides a service migration method, including: when a source edge fog node determines that its service needs to be migrated, a migration request including a migration service is initiated to a target edge fog node via a fog network; and the target edge fog node receives After the migration request, the resource corresponding to the migration service is activated by configuring the resource of the migration service, and the migration response is sent to the source edge fog node via the fog network; and the source edge fog node receives After the migration response, resources corresponding to the migration service are released.
本公开实施例还提供了一种业务迁移装置，包括源边缘雾节点和目标边缘雾节点。源边缘雾节点在确定其业务需要进行迁移时，经 由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求，并且在收到针对所述迁移请求的迁移响应后，释放与所述迁移业务相应的资源。目标边缘雾节点收到所述迁移请求后，通过对所述迁移业务的资源进行配置，激活与所述迁移业务对应的业务，并经由雾网络向源边缘雾节点发送所述迁移响应。The embodiment of the present disclosure further provides a service migration apparatus, including a source edge fog node and a target edge fog node. When the source edge fog node determines that its service needs to be migrated, the migration request including the migration service is initiated to the target edge fog node via the fog network, and after receiving the migration response for the migration request, releasing the migration service corresponding to the migration service H. After receiving the migration request, the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node via the fog network.
本公开实施例还提供了一种计算机存储介质，其上存储有计算机程序，当处理器执行所述计算机程序是，所述处理器执行根据本公开的业务迁移方法。Embodiments of the present disclosure also provide a computer storage medium having stored thereon a computer program that, when executed by a processor, executes a service migration method according to the present disclosure.
附图说明DRAWINGS
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：The drawings described herein are provided to provide a further understanding of the present disclosure, and are intended to be a part of the present disclosure. In the drawing:
图1是根据本公开实施例的业务迁移方法的流程图；FIG. 1 is a flowchart of a service migration method according to an embodiment of the present disclosure;
图2是根据本公开实施例的业务迁移装置的示意图；2 is a schematic diagram of a service migration apparatus according to an embodiment of the present disclosure;
图3是根据本公开实施例的集中式雾网络的架构图；3 is an architectural diagram of a centralized fog network in accordance with an embodiment of the present disclosure;
图4是根据本公开实施例的在集中式雾网络中由终端发起的高层雾节点内的移动性的流程图；4 is a flow diagram of mobility within a high-level fog node initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure;
图5是根据本公开实施例的在集中式雾网络中由雾节点发起的高层雾节点内的移动性的流程图；5 is a flow diagram of mobility within a high-level fog node initiated by a fog node in a centralized fog network, in accordance with an embodiment of the present disclosure;
图6是根据本公开实施例的在集中式雾网络中由终端发起的高层雾节点间的移动性的流程图；6 is a flow diagram of mobility between high-level fog nodes initiated by a terminal in a centralized fog network, in accordance with an embodiment of the present disclosure;
图7是根据本公开实施例的在集中式雾网络中由雾节点发起的高层雾节点间的移动性的流程图；7 is a flow diagram of mobility between high-level fog nodes initiated by a fog node in a centralized fog network, in accordance with an embodiment of the present disclosure;
图8是根据本公开实施例的分布式雾网络的架构图；8 is an architectural diagram of a distributed fog network in accordance with an embodiment of the present disclosure;
图9是根据本公开实施例的由分布式终端发起的移动性的流程图；以及9 is a flow diagram of mobility initiated by a distributed terminal in accordance with an embodiment of the present disclosure;
图10是根据本公开实施例的由分布式雾节点发起的移动性的流程图。10 is a flow diagram of mobility initiated by a distributed fog node, in accordance with an embodiment of the disclosure.
具体实施方式Detailed ways
以下结合附图对本公开的实施例进行详细说明，应当理解，以下所说明的实施例仅用于说明和解释本公开，并不用于限定本公开。The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
本公开实施例中所述的业务包括业务或应用，比如APP。The services described in the embodiments of the present disclosure include services or applications, such as an APP.
图1是根据本公开实施例的业务迁移方法的流程图。1 is a flow chart of a method of business migration in accordance with an embodiment of the present disclosure.
如图1所示，根据本公开实施例的业务迁移方法可以包括步骤S101至S103。As shown in FIG. 1, the service migration method according to an embodiment of the present disclosure may include steps S101 to S103.
在步骤S101，源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求。In step S101, the source edge fog node initiates a migration request including the migration service to the target edge fog node via the fog network when determining that its service needs to be migrated.
在步骤S102，目标边缘雾节点收到迁移请求后，通过对迁移业务的资源进行配置，激活与迁移业务对应的业务，并经由雾网络向源边缘雾节点发送迁移响应。After receiving the migration request, the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node via the fog network.
在步骤S103，源边缘雾节点收到迁移响应后，释放与迁移业务相应的资源。In step S103, after receiving the migration response, the source edge fog node releases the resource corresponding to the migration service.
雾网络可以包括集中式雾网络或分布式雾网络。集中式雾网络可以包括多个高层雾节点和每个高层雾节点管理的多个边缘雾节点。分布式雾网络可以包括多个边缘雾节点。The fog network may comprise a centralized fog network or a distributed fog network. The centralized fog network may include a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node. The distributed fog network can include multiple edge fog nodes.
源边缘雾节点位于集中式雾网络中时，如果源边缘雾节点与目标边缘雾节点由相同的高层雾节点管理，则源边缘雾节点经由该高层雾节点向目标边缘雾节点发起包含迁移业务的迁移请求；如果源边缘雾节点与目标边缘雾节点由不同的高层雾节点管理，则源边缘雾节点经由管理源边缘雾节点的源高层雾节点和管理目标边缘雾节点的目标高层雾节点向目标边缘雾节点发起包含迁移业务的迁移请求。When the source edge fog node is located in the centralized fog network, if the source edge fog node and the target edge fog node are managed by the same high-level fog node, the source edge fog node initiates the migration service including the migration service to the target edge fog node via the high-level fog node. a migration request; if the source edge fog node and the target edge fog node are managed by different high-level fog nodes, the source edge fog node passes the source high-level fog node managing the source edge fog node and the target high-level fog node managing the target edge fog node to the target The edge fog node initiates a migration request that includes the migration service.
源边缘雾节点位于分布式雾网络中时，源边缘雾节点直接向目标边缘雾节点发起包含迁移业务的迁移请求。When the source edge fog node is located in the distributed fog network, the source edge fog node directly initiates a migration request including the migration service to the target edge fog node.
图2是根据本公开实施例的业务迁移装置的示意图。2 is a schematic diagram of a service migration device in accordance with an embodiment of the present disclosure.
如图2所示，根据本公开实施例的业务迁移装置包括源边缘雾节点201和目标边缘雾节点202。源边缘雾节点201在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点202发起包含迁移业务的迁移请求，并且在收到针对所述迁移请求的迁移响应后，释放与迁 移业务相应的资源。目标边缘雾节点202收到所述迁移请求后，通过对迁移业务的资源进行配置，激活与迁移业务对应的业务，并经由雾网络向源边缘雾节点201发送迁移响应。As shown in FIG. 2, the service migration apparatus according to an embodiment of the present disclosure includes a source edge fog node 201 and a target edge fog node 202. The source edge fog node 201 initiates a migration request including the migration service to the target edge fog node 202 via the fog network when determining that its service needs to be migrated, and releases the migration service after receiving the migration response for the migration request. H. After receiving the migration request, the target edge fog node 202 activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration response to the source edge fog node 201 via the fog network.
雾网络可以包括集中式雾网络或分布式雾网络。集中式雾网络可以包括多个高层雾节点和每个高层雾节点管理的多个边缘雾节点。分布式雾网络可以包括多个边缘雾节点。The fog network may comprise a centralized fog network or a distributed fog network. The centralized fog network may include a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node. The distributed fog network can include multiple edge fog nodes.
源边缘雾节点201位于集中式雾网络中时，如果源边缘雾节点201与目标边缘雾节点202由相同的高层雾节点管理，则源边缘雾节点201经由该高层雾节点向目标边缘雾节点202发起包含迁移业务的迁移请求；如果源边缘雾节点201与目标边缘雾节点202由不同的高层雾节点管理，则源边缘雾节点201经由管理源边缘雾节点201的源高层雾节点和管理目标边缘雾节点202的目标高层雾节点向目标边缘雾节点202发起包含迁移业务的迁移请求。When the source edge fog node 201 is located in the centralized fog network, if the source edge fog node 201 and the target edge fog node 202 are managed by the same high-level fog node, the source edge fog node 201 passes the high-level fog node to the target edge fog node 202. Initiating a migration request including a migration service; if the source edge fog node 201 and the target edge fog node 202 are managed by different high-level fog nodes, the source edge fog node 201 manages the source high-level fog node and the management target edge via the source edge fog node 201 The target high-level fog node of the fog node 202 initiates a migration request containing the migration service to the target edge fog node 202.
源边缘雾节点201位于分布式雾网络中时，源边缘雾节点201直接向目标边缘雾节点202发起包含迁移业务的迁移请求。When the source edge fog node 201 is located in the distributed fog network, the source edge fog node 201 directly initiates a migration request including the migration service to the target edge fog node 202.
根据组网架构不同，雾网络可以分为集中式雾网络和分布式雾网络两种型式。According to different networking architectures, the fog network can be divided into two types: centralized fog network and distributed fog network.
图3是根据本公开实施例的集中式多层雾网络的架构图。3 is an architectural diagram of a centralized multi-layer fog network in accordance with an embodiment of the present disclosure.
如图3所示，在该雾网络中存在一个集中控制管理的雾节点称为高层雾节点，该高层雾节点可以对底层的边缘雾节点进行管理。As shown in FIG. 3, a fog node having centralized control management in the fog network is called a high-level fog node, and the high-level fog node can manage the edge fog node of the bottom layer.
在图3所示的集中式雾网络架构中，各种设备(传感器等)通过接入网络(无线或有线方式)加入到雾网络中。边缘雾节点可以提供各种设备的多种接入方式，并且可以提供数据采集、数据格式转换、数据上报、APP部署等功能。高层雾节点可以提供对所辖边缘雾节点的管理、数据分析和数据处理、命令生成等功能。In the centralized fog network architecture shown in FIG. 3, various devices (sensors, etc.) are added to the fog network through an access network (wireless or wired). The edge fog node can provide multiple access modes for various devices, and can provide functions such as data acquisition, data format conversion, data reporting, and APP deployment. The high-level fog node can provide functions such as management, data analysis, data processing, and command generation for the edge fog nodes under its jurisdiction.
在图3所示的场景中，雾网络中移动性可分为两个层面，即，承载层面的无缝移动性和雾节点层面的移动性。承载层面的无缝移动性由接入网络保证，即保证通信管道间的无缝移动性。雾节点层面的移动性(即，雾网络中APP的移动性)是在承载层面的移动性完成之后进行的，或者可以和承载层面的移动性同时进行，以减少时延。In the scenario shown in Figure 3, mobility in a fog network can be divided into two layers, namely, seamless mobility at the bearer level and mobility at the fog node level. The seamless mobility at the bearer level is guaranteed by the access network, which guarantees seamless mobility between communication pipes. The mobility at the fog node level (ie, the mobility of the APP in the fog network) is performed after the mobility at the bearer level is completed, or can be performed simultaneously with the mobility at the bearer level to reduce the delay.
承载层面的移动性已经由第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)/电气和电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)等协议定义清楚，因此雾网络中移动性主要讨论的是雾节点层面的移动性。The mobility at the bearer level has been defined by protocols such as the 3rd Generation Partnership Project (3GPP)/Institute of Electrical and Electronics Engineers (IEEE), so the mobility in the fog network is mainly discussed. It is the mobility of the fog node level.
在图3所示的场景中，APP的移动性可以包括以下三种场景。In the scenario shown in FIG. 3, the mobility of the APP may include the following three scenarios.
场景1：APP所在的边缘雾节点没有变更，只是接入网络发生变更，例如，接入网络从长期演进(Long Term Evolution，LTE)变更到5G(边缘雾节点可支持多种接入网络)。这种场景中不存在不同边缘雾节点之间的信息交互，只是接入网络发生变更，这种移动性由3GPP/IEEE等接入协议保证，不在本公开讨论范围内。Scenario 1: The edge fog node where the APP is located has not changed, but the access network has changed. For example, the access network is changed from Long Term Evolution (LTE) to 5G (edge fog nodes can support multiple access networks). In this scenario, there is no information interaction between different edge fog nodes, but the access network is changed. This mobility is guaranteed by an access protocol such as 3GPP/IEEE, and is not within the scope of the present disclosure.
场景2：APP从同一个高层雾节点(High-Tier Fog Node，H-FN)管辖下的一个边缘雾节点(即，源边缘雾节点)移动到另一个边缘雾节点(即，目标边缘雾节点)。这可称之为高层雾节点内(Intra-HFN)的移动性。该移动性的信息交互主要由HFN协调完成。Scenario 2: The APP moves from one edge fog node (ie, the source edge fog node) under the jurisdiction of the same High-Tier Fog Node (H-FN) to another edge fog node (ie, the target edge fog node) ). This can be referred to as mobility within the high-level fog node (Intra-HFN). This mobility information interaction is mainly coordinated by the HFN.
场景3：APP从一个高层雾节点(即，源高层雾节点)移动到另外一个高层雾节点(即，目标高层雾节点)。这可称之为高层雾节点间(Inter-HFN)的移动性。该移动性的信息交互主要由源高层雾节点(Source-High-Tier Fog Node，S-H-FN)和目标高层雾节点(Target-High-Tier Fog Node，T-H-FN)之间协调完成。Scenario 3: The APP moves from one high-level fog node (ie, the source high-level fog node) to another high-level fog node (ie, the target high-level fog node). This can be referred to as the mobility between high-level fog nodes (Inter-HFN). The mobility information interaction is mainly coordinated by the Source-High-Tier Fog Node (S-H-FN) and the Target-High-Tier Fog Node (T-H-FN).
下面针对场景2和场景3的移动性进行具体描述。The mobility of scene 2 and scene 3 will be specifically described below.
Intra-HFN移动性Intra-HFN mobility
Intra-HFN移动性根据发起的不同方式，可以分为以下终端发起的移动性和雾节点发起的移动性两种。Intra-HFN mobility can be divided into the following terminal-initiated mobility and fog-initiated mobility according to different methods initiated.
图4是根据本公开实施例的在集中式雾网络中由终端发起的高层雾节点内的移动性的流程图。4 is a flow diagram of mobility within a high-level fog node initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure.
如图4所示，在集中式雾网络中由终端发起的高层雾节点内的移动性的流程可以包括步骤S401至S414。As shown in FIG. 4, the flow of mobility within the high-level fog node initiated by the terminal in the centralized fog network may include steps S401 to S414.
在步骤S401，终端的承载网络(接入网络)发生变化时，触发终端的APP迁移。In step S401, when the bearer network (access network) of the terminal changes, the APP migration of the terminal is triggered.
在步骤S402，终端APP实例通过源边缘雾节点(Source-Edge Fog  Node，S-EFN)的APP实例/平台向H-FN发起APP实例迁移请求。In step S402, the terminal APP instance initiates an APP instance migration request to the H-FN through the APP instance/platform of the Source-Edge Fog Node (S-EFN).
在步骤S403，H-FN向目标边缘雾节点(Target-Edge Fog Node，T-EFN)平台发起APP实例迁移请求。In step S403, the H-FN initiates an APP instance migration request to the Target-Edge Fog Node (T-EFN) platform.
在步骤S404，T-EFN平台向T-EFN的基础设施发起资源分配请求。At step S404, the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
在步骤S405，T-EFN的基础设施分配好资源后向T-EFN平台回复资源分配响应。In step S405, the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
在步骤S406，T-EFN平台向T-EFN APP实例发起配置请求。At step S406, the T-EFN platform initiates a configuration request to the T-EFN APP instance.
在步骤S407，T-EFN APP实例完成资源配置后向T-EFN平台回复配置响应。In step S407, the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
在步骤S408，T-EFN平台给H-FN回复APP实例迁移响应。In step S408, the T-EFN platform replies to the H-FN with an APP instance migration response.
在步骤S409，H-FN向S-EFN回复APP实例迁移响应。In step S409, the H-FN replies to the S-EFN with an APP instance migration response.
在步骤S410，APP实例在S-EFN和T-EFN间进行状态同步。图4示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S410。In step S410, the APP instance performs state synchronization between S-EFN and T-EFN. FIG. 4 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S410 may be omitted.
在步骤S411，H-FN向S-EFN平台发起终止APP实例请求。In step S411, the H-FN initiates a termination APP instance request to the S-EFN platform.
在步骤S412，在S-EFN平台和S-EFN APP实例间进行终止APP实例的过程。In step S412, a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
在步骤S413，在S-EFN平台和S-EFN基础设施间进行资源删除过程。In step S413, a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
在步骤S414，S-EFN平台向H-FN发起终止APP实例响应。In step S414, the S-EFN platform initiates a termination APP instance response to the H-FN.
图5是根据本公开实施例的在集中式雾网络中由雾节点发起的高层雾节点内的移动性的流程图。5 is a flow diagram of mobility within a high-level fog node initiated by a fog node in a centralized fog network, in accordance with an embodiment of the disclosure.
如图5所示，在集中式雾网络中由雾节点发起的高层雾节点内的移动性的流程可以包括步骤S501至S515。As shown in FIG. 5, the flow of mobility within the high-level fog node initiated by the fog node in the centralized fog network may include steps S501 through S515.
在步骤S501，当终端的承载(接入网络)发生变化时，例如，从LTE变化为基于蜂窝的窄带物联网(Narrow Band Internet of Things，NB-IOT)，而该雾节点不支持NB-IOT接入，雾节点触发终端的APP迁移。In step S501, when the bearer (access network) of the terminal changes, for example, from LTE to a cellular-based Narrow Band Internet of Things (NB-IOT), the fog node does not support NB-IOT. Access, the fog node triggers the APP migration of the terminal.
在步骤S502，S-EFN APP实例和S-EFN平台进行承载更新过程。In step S502, the S-EFN APP instance and the S-EFN platform perform a bearer update process.
在步骤S503，S-EFN平台向H-FN发起APP实例迁移请求。In step S503, the S-EFN platform initiates an APP instance migration request to the H-FN.
在步骤S504，H-FN向T-EFN平台发起APP实例迁移请求。In step S504, the H-FN initiates an APP instance migration request to the T-EFN platform.
在步骤S505，T-EFN平台向T-EFN的基础设施发起资源分配请求。At step S505, the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
在步骤S506，T-EFN的基础设施分配好资源后向T-EFN平台回复资源分配响应。In step S506, the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
在步骤S507，T-EFN平台向T-EFN APP实例发起配置请求；In step S507, the T-EFN platform initiates a configuration request to the T-EFN APP instance;
在步骤S508，T-EFN APP实例完成资源配置后向T-EFN平台回复配置响应。In step S508, the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
在步骤S509，T-EFN平台给H-FN回复APP实例迁移响应。In step S509, the T-EFN platform replies to the H-FN with an APP instance migration response.
在步骤S510，H-FN向S-EFN回复APP实例迁移响应。In step S510, the H-FN replies to the S-EFN with an APP instance migration response.
在步骤S511，APP实例在S-EFN和T-EFN间进行状态同步。图5示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S511。In step S511, the APP instance performs state synchronization between S-EFN and T-EFN. FIG. 5 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S511 can be omitted.
在步骤S512，H-FN向S-EFN平台发起终止APP实例请求。In step S512, the H-FN initiates a termination APP instance request to the S-EFN platform.
在步骤S513，在S-EFN平台和S-EFN APP实例间进行终止APP实例的过程。In step S513, a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
在步骤S514，在S-EFN平台和S-EFN基础设施间进行资源删除过程。At step S514, a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
在步骤S515，S-EFN平台向H-FN发起终止APP实例响应。In step S515, the S-EFN platform initiates a termination APP instance response to the H-FN.
Inter-HFN移动性Inter-HFN mobility
Inter-HFN移动性根据发起的不同方式，可以分为终端发起的移动性和雾节点发起的移动性两种。Inter-HFN mobility can be divided into terminal-initiated mobility and fog-initiated mobility according to different methods initiated.
图6是根据本公开实施例的在集中式雾网络中由终端发起的高层雾节点间的移动性的流程图。6 is a flow diagram of mobility between high-level fog nodes initiated by a terminal in a centralized fog network, in accordance with an embodiment of the disclosure.
如图6所示，在集中式雾网络中由终端发起的高层雾节点间的移动性的流程可以包括步骤S601至S616。As shown in FIG. 6, the flow of mobility between high-level fog nodes initiated by the terminal in the centralized fog network may include steps S601 to S616.
在步骤S601，终端的承载(接入网络)发生变化时，触发终端的APP迁移。In step S601, when the bearer (access network) of the terminal changes, the APP migration of the terminal is triggered.
在步骤S602，终端APP实例通过S-EFN的APP实例/平台向 S-H-FN发起APP实例迁移请求。In step S602, the terminal APP instance initiates an APP instance migration request to the S-H-FN through the APP instance/platform of the S-EFN.
在步骤S603，S-H-FN向T-H-FN发起APP实例迁移请求。In step S603, the S-H-FN initiates an APP instance migration request to the T-H-FN.
在步骤S604，T-H-FN向T-EFN平台发起APP实例迁移请求。In step S604, the T-H-FN initiates an APP instance migration request to the T-EFN platform.
在步骤S605，T-EFN平台向T-EFN的基础设施发起资源分配请求。At step S605, the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
在步骤S606，T-EFN的基础设施分配好资源后向T-EFN平台回复资源分配响应。In step S606, the T-EFN infrastructure allocates resources and then replies to the T-EFN platform with a resource allocation response.
在步骤S607，T-EFN平台向T-EFN APP实例发起配置请求。In step S607, the T-EFN platform initiates a configuration request to the T-EFN APP instance.
在步骤S608，T-EFN APP实例完成资源配置后向T-EFN平台回复配置响应。In step S608, the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
在步骤S609，T-EFN平台给T-H-FN回复APP实例迁移响应。In step S609, the T-EFN platform replies to the T-H-FN with an APP instance migration response.
在步骤S610，T-H-FN向S-H-FN回复APP实例迁移响应。At step S610, the T-H-FN replies to the S-H-FN with an APP instance migration response.
在步骤S611，S-H-FN向S-EFN回复APP实例迁移响应。In step S611, the S-H-FN replies to the S-EFN with an APP instance migration response.
在步骤S612，APP实例在S-EFN和T-EFN间进行状态同步。图6示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S612。In step S612, the APP instance performs state synchronization between S-EFN and T-EFN. FIG. 6 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, no APP state synchronization is required, that is, step S612 may be omitted.
在步骤S613，S-H-FN向S-EFN平台发起终止APP实例请求。In step S613, the S-H-FN initiates a termination APP instance request to the S-EFN platform.
在步骤S614，在S-EFN平台和S-EFN APP实例间进行终止APP实例的过程。In step S614, a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
在步骤S615，在S-EFN平台和S-EFN基础设施间进行资源删除过程。At step S615, a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
在步骤S616，S-EFN平台向S-H-FN发起终止APP实例响应。In step S616, the S-EFN platform initiates a termination APP instance response to the S-H-FN.
图7是根据本公开实施例的在集中式雾网络中由雾节点发起的高层雾节点间的移动性的流程图。7 is a flow diagram of mobility between high-level fog nodes initiated by a fog node in a centralized fog network, in accordance with an embodiment of the disclosure.
如图7所示，在集中式雾网络中由雾节点发起的高层雾节点间的移动性的流程可以包括步骤S701至S717。As shown in FIG. 7, the flow of mobility between high-level fog nodes initiated by the fog node in the centralized fog network may include steps S701 to S717.
在步骤S701，当终端的承载(接入网络)发生变化时，例如，从LTE变化为NB-IOT，而该雾节点不支持NB-IOT接入，雾节点触发终端的APP迁移。In step S701, when the bearer (access network) of the terminal changes, for example, from LTE to NB-IOT, and the fog node does not support NB-IOT access, the fog node triggers APP migration of the terminal.
在步骤S702，S-EFN APP实例和S-EFN平台进行承载更新过程。In step S702, the S-EFN APP instance and the S-EFN platform perform a bearer update process.
在步骤S703，S-EFN平台向S-H-FN发起APP实例迁移请求。In step S703, the S-EFN platform initiates an APP instance migration request to the S-H-FN.
在步骤S704，S-H-FN向T-H-FN发起APP实例迁移请求。In step S704, the S-H-FN initiates an APP instance migration request to the T-H-FN.
在步骤S705，T-H-FN向T-EFN平台发起APP实例迁移请求。In step S705, the T-H-FN initiates an APP instance migration request to the T-EFN platform.
在步骤S706，T-EFN平台向T-EFN的基础设施发起资源分配请求。At step S706, the T-EFN platform initiates a resource allocation request to the infrastructure of the T-EFN.
在步骤S707，T-EFN的基础设施分配好资源后向T-EFN平台回复资源分配响应。In step S707, the infrastructure of the T-EFN allocates resources and then replies to the resource allocation response to the T-EFN platform.
在步骤S708，T-EFN平台向T-EFN APP实例发起配置请求。At step S708, the T-EFN platform initiates a configuration request to the T-EFN APP instance.
在步骤S709，T-EFN APP实例完成资源配置后向T-EFN平台回复配置响应。In step S709, the T-EFN APP instance returns the configuration response to the T-EFN platform after completing the resource configuration.
在步骤S710，T-EFN平台给T-H-FN回复APP实例迁移响应。In step S710, the T-EFN platform replies to the T-H-FN with an APP instance migration response.
在步骤S711，T-H-FN向S-H-FN回复APP实例迁移响应。In step S711, the T-H-FN replies to the S-H-FN with an APP instance migration response.
在步骤S712，S-H-FN向S-EFN回复APP实例迁移响应。In step S712, the S-H-FN replies to the S-EFN with an APP instance migration response.
在步骤S713，APP实例在S-EFN和T-EFN间进行状态同步。图7示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S713。In step S713, the APP instance performs state synchronization between the S-EFN and the T-EFN. FIG. 7 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, there is no need to perform APP state synchronization, that is, step S713 may be omitted.
在步骤S714，S-H-FN向S-EFN平台发起终止APP实例请求。In step S714, the S-H-FN initiates a termination APP instance request to the S-EFN platform.
在步骤S715，在S-EFN平台和S-EFN APP实例间进行终止APP实例的过程。In step S715, a process of terminating the APP instance is performed between the S-EFN platform and the S-EFN APP instance.
在步骤S716，在S-EFN平台和S-EFN基础设施间进行资源删除过程。At step S716, a resource deletion process is performed between the S-EFN platform and the S-EFN infrastructure.
在步骤S717，S-EFN平台向S-H-FN发起终止APP实例响应。In step S717, the S-EFN platform initiates a termination APP instance response to the S-H-FN.
上述讨论的APP移动性不仅仅局限于两层雾节点组成的集中式雾网络，也可以适用于多层雾节点组成的多层集中式雾网络架构。The APP mobility discussed above is not limited to a centralized fog network composed of two layers of fog nodes, but can also be applied to a multi-layer centralized fog network architecture composed of multi-layer fog nodes.
图8是根据本公开实施例的分布式雾网络的架构图。8 is an architectural diagram of a distributed fog network in accordance with an embodiment of the present disclosure.
如图8所示，在分布式雾网络中每个雾节点完成独立的功能。As shown in Figure 8, each fog node performs an independent function in a distributed fog network.
在图8所示的分布式雾网络架构中，各种设备(传感器等)通过接入网络(无线或有线方式)加入到雾网络中。雾节点可以提供各种设备的多种接入方式，并且可以提供数据采集、数据格式转换、数据分析和处理、命令生成、向云端上报数据、APP部署等功能。In the distributed fog network architecture shown in FIG. 8, various devices (sensors, etc.) are added to the fog network through an access network (wireless or wired). The fog node can provide multiple access modes for various devices, and can provide functions such as data collection, data format conversion, data analysis and processing, command generation, reporting data to the cloud, and APP deployment.
在图8所示的场景中，雾网络中移动性可分为两个层面，即，承载层面的无缝移动性和雾节点层面的移动性。承载层面的无缝移动性由接入网络保证，即保证通信管道间的无缝移动性。雾节点层面的移动性(即，雾网络中APP的移动性)是在承载层面的移动性完成之后进行的，或者可以和承载层面的移动性同时进行，以减少时延。In the scenario shown in Figure 8, mobility in a fog network can be divided into two layers, namely, seamless mobility at the bearer level and mobility at the fog node level. The seamless mobility at the bearer level is guaranteed by the access network, which guarantees seamless mobility between communication pipes. The mobility at the fog node level (ie, the mobility of the APP in the fog network) is performed after the mobility at the bearer level is completed, or can be performed simultaneously with the mobility at the bearer level to reduce the delay.
承载层面的移动性已经由3GPP/IEEE等协议定义清楚，因此雾网络中移动性主要讨论的是雾节点层面的移动性。The mobility at the bearer level has been defined by protocols such as 3GPP/IEEE. Therefore, the mobility in the fog network mainly discusses the mobility at the fog node level.
在图8所示的场景中，APP的移动性可以包括以下两种场景。In the scenario shown in FIG. 8, the mobility of the APP may include the following two scenarios.
场景1：APP所在的雾节点没有变更，只是接入网络发生变更，例如，接入网络从LTE变更到5G(雾节点可支持多种接入网络)。这种场景中不存在不同雾节点之间的信息交互，只是接入网络发生变更，这种移动性由3GPP/IEEE等接入协议保证，不在本公开讨论范围内。Scenario 1: The fog node where the APP is located has not changed, but the access network has changed. For example, the access network is changed from LTE to 5G (the fog node can support multiple access networks). In this scenario, there is no information interaction between different fog nodes, but the access network changes. This mobility is guaranteed by an access protocol such as 3GPP/IEEE, and is not within the scope of the present disclosure.
场景2：APP从一个雾节点移动到另一个雾节点。该移动性的信息交互主要由源雾节点和目标雾节点协调完成。Scenario 2: The APP moves from one fog node to another. The information interaction of the mobility is mainly coordinated by the source fog node and the target fog node.
下面针对场景2的移动性进行具体描述。The mobility of scenario 2 will be specifically described below.
根据发起的不同方式，雾节点间的移动性分为终端发起的移动性和雾节点发起的移动性两种。According to different ways of initiation, the mobility between the fog nodes is divided into two types: mobility initiated by the terminal and mobility initiated by the fog node.
图9是根据本公开实施例的由分布式终端发起的移动性的流程图。9 is a flow diagram of mobility initiated by a distributed terminal in accordance with an embodiment of the disclosure.
如图9所示，由分布式终端发起的移动性的流程可以包括步骤S901至S906。As shown in FIG. 9, the flow of mobility initiated by the distributed terminal may include steps S901 to S906.
在步骤S901，终端的承载(接入网络)发生变化时，终端触发APP迁移。In step S901, when the bearer (access network) of the terminal changes, the terminal triggers APP migration.
在步骤S902，终端APP向源雾节点(Source-Fog Node，S-FN)发起APP实例迁移请求。In step S902, the terminal APP initiates an APP instance migration request to the source-fog node (S-FN).
在步骤S903，S-FN向目标雾节点(Target-Fog Node，T-FN)发起APP实例迁移请求。In step S903, the S-FN initiates an APP instance migration request to the target-fog node (T-FN).
在步骤S904，T-FN分配好资源以及完成相应的配置后，向S-FN回复配置响应。In step S904, after the T-FN allocates the resources and completes the corresponding configuration, the T-FN replies with the configuration response to the S-FN.
在步骤S905，APP实例在S-FN和T-FN间进行状态同步。图9示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S905。In step S905, the APP instance performs state synchronization between the S-FN and the T-FN. FIG. 9 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, APP state synchronization is not required, that is, step S905 may be omitted.
在步骤S906，S-FN完成已迁移APP的相应资源释放。In step S906, the S-FN completes the release of the corresponding resource of the migrated APP.
下面以寻车定位为例，对图9所示的流程进行说明。The following shows the flow shown in FIG. 9 by taking the car search positioning as an example.
场景设置：用户把车停在商业区A的地下车库，到商业区B购物用餐。用餐结束后，用户将车辆的图片发送给寻车APP，以帮助用户定位车辆并导航到达车辆的路线。商业区A的地下车库采用LoRa覆盖，商业区B采用LTE覆盖，并且商业区A和商业区B分别部署了一个雾节点。用户在商业区B的源雾节点S-FN发起应用请求，并移动到商业区A，因此需要商业区A的目标雾节点T-FN完成应用任务。Scene setting: The user parks the car in the underground garage of the commercial area A and goes shopping in the business district B. After the meal is over, the user sends a picture of the vehicle to the car search app to help the user locate the vehicle and navigate the route to the vehicle. The underground garage of the commercial area A is covered by LoRa, the commercial area B is covered by LTE, and the commercial area A and the commercial area B respectively deploy a fog node. The user initiates an application request at the source fog node S-FN of the business area B and moves to the business area A, so the target fog node T-FN of the business area A is required to complete the application task.
在用户从商业区B移动到商业区A的地下车库过程中，由于发生LoRa到LTE承载的切换，寻车APP也需要从商业区B的S-FN迁移到商业区A的T-FN，触发终端的APP迁移。终端APP实例向S-FN平台发起APP实例迁移请求，并且S-FN平台向T-FN平台发起APP实例迁移请求。T-FN平台向T-FN的基础设施发起资源分配请求，并且T-FN的基础设施分配好资源后向T-FN平台回复资源分配响应。T-FN平台向T-FN APP实例发起配置请求，并且T-FN APP实例完成资源配置后向T-FN平台回复配置响应。T-FN平台向S-FN平台回复APP实例迁移响应，S-FN平台向S-FN APP实例回复APP实例迁移响应，并且APP实例在S-FN和T-FN间进行状态同步。S-FN平台和S-FN APP实例间进行终止APP实例的过程，并且S-FN平台和S-FN基础设施间进行资源删除过程。During the process of the user moving from the commercial area B to the underground garage of the commercial area A, the search for the car also needs to be transferred from the S-FN of the commercial area B to the T-FN of the commercial area A due to the handover of the LoRa to the LTE bearer, triggering APP migration of the terminal. The terminal APP instance initiates an APP instance migration request to the S-FN platform, and the S-FN platform initiates an APP instance migration request to the T-FN platform. The T-FN platform initiates a resource allocation request to the T-FN infrastructure, and the T-FN infrastructure allocates resources and then replies to the T-FN platform with a resource allocation response. The T-FN platform initiates a configuration request to the T-FN APP instance, and the T-FN APP instance returns the configuration response to the T-FN platform after completing the resource configuration. The T-FN platform replies to the S-FN platform with an APP instance migration response, and the S-FN platform replies to the S-FN APP instance with an APP instance migration response, and the APP instance performs state synchronization between the S-FN and the T-FN. The process of terminating the APP instance is performed between the S-FN platform and the S-FN APP instance, and the resource deletion process is performed between the S-FN platform and the S-FN infrastructure.
图10是根据本公开实施例的由分布式雾节点发起的移动性的流程图。10 is a flow diagram of mobility initiated by a distributed fog node, in accordance with an embodiment of the disclosure.
如图10所示，由分布式雾节点发起的移动性的流程可以包括步骤S1001至S1006。As shown in FIG. 10, the flow of mobility initiated by the distributed fog node may include steps S1001 through S1006.
在步骤S1001，当终端的承载(接入网络)发生变化时，雾节点能会触发终端的APP迁移(例如，某雾节点不支持某种接入方式)。In step S1001, when the bearer (access network) of the terminal changes, the fog node can trigger the APP migration of the terminal (for example, the fog node does not support some access mode).
在步骤S1002，S-FN完成承载更新过程。In step S1002, the S-FN completes the bearer update process.
在步骤S1003，S-FN向T-FN发起APP实例迁移请求。In step S1003, the S-FN initiates an APP instance migration request to the T-FN.
在步骤S1004，T-FN分配好资源以及完成相应的配置后，向S-FN回复配置响应。In step S1004, after the T-FN allocates the resources and completes the corresponding configuration, the T-FN replies with the configuration response to the S-FN.
在步骤S1005，APP实例在S-FN和T-FN间进行状态同步。图10示出了APP处于激活状态时的流程，如果APP处于睡眠/空闲状态，则不需要进行APP状态同步，即，可省略步骤S1005。In step S1005, the APP instance performs state synchronization between the S-FN and the T-FN. FIG. 10 shows the flow when the APP is in an active state. If the APP is in the sleep/idle state, there is no need to perform APP state synchronization, that is, step S1005 may be omitted.
在步骤S1006，S-FN完成已迁移APP的相应资源释放。In step S1006, the S-FN completes the release of the corresponding resource of the migrated APP.
上述讨论的APP移动性不仅仅局限于一层雾节点组成的分布式雾网络，也可以适用于多层雾节点组成的多层分布式雾网络架构。在多层分布式雾网络中，当APP发生雾节点的迁移时，也是直接由源雾节点和目标雾节点间完成交互，不用通过其他第三个雾节点。The APP mobility discussed above is not limited to a distributed fog network composed of a layer of fog nodes, but also applicable to a multi-layer distributed fog network architecture composed of multi-layer fog nodes. In the multi-layer distributed fog network, when the migration of the fog node occurs in the APP, the interaction between the source fog node and the target fog node is directly performed without passing through the other third fog node.
下面以设备监控为例，对图10所示的流程进行说明。The process shown in FIG. 10 will be described below by taking device monitoring as an example.
场景设置：大楼A和大楼B分别部署一个雾节点，两个雾节点可互为备份进行工作，大楼A的雾节点为S-FN，大楼B的雾节点为T-FN。大楼A和B部署的雾节点完成大楼内电力设备工作状态的视频监控，当设备有异常发生时，能够产生预警，同时将该大楼电力设备的工作情况等信息周期性传递到电力维护提供商的云平台，进行数据备份和分析。当大楼A的雾节点负荷过载，需要将部分工作分流到大楼B的雾节时，雾节点S-FN将正在进行的部分视频图像分析迁移到雾节点T-FN上。Scene setting: Building A and Building B respectively deploy a fog node, and the two fog nodes can work together for backup. The fog node of Building A is S-FN, and the fog node of Building B is T-FN. The fog nodes deployed in Buildings A and B complete the video surveillance of the working status of the power equipment in the building. When the equipment has an abnormality, it can generate an early warning, and the information about the working condition of the building's power equipment is periodically transmitted to the power maintenance provider. Cloud platform for data backup and analysis. When the fog node load of Building A is overloaded and part of the work needs to be diverted to the fog section of Building B, the fog node S-FN migrates part of the ongoing video image analysis to the fog node T-FN.
大楼A的S-FN平台向大楼B的T-FN平台进行APP迁移请求。T-FN平台向T-FN的基础设施发起资源分配请求，并且T-FN的基础设施分配好资源后向T-FN平台回复资源分配响应。T-FN平台向T-FN APP实例发起配置请求，并且T-FN APP实例完成资源配置后向T-FN平台回复配置响应。大楼B的T-FN平台向大楼A的S-FN发起APP迁移响应，并且大楼A的S-FN平台向S-FN APP实例告知准备进行迁移APP的状态同步。在S-FN和T-FN之间完成迁移APP的镜像和状态同步后，大楼A的S-FN平台和S-FN APP实例间完成资源释放，并且大楼A的S-FN平台和S-FN基础设施间完成资源释放，过程结束。Building A's S-FN platform makes an APP migration request to Building B's T-FN platform. The T-FN platform initiates a resource allocation request to the T-FN infrastructure, and the T-FN infrastructure allocates resources and then replies to the T-FN platform with a resource allocation response. The T-FN platform initiates a configuration request to the T-FN APP instance, and the T-FN APP instance returns the configuration response to the T-FN platform after completing the resource configuration. The T-FN platform of Building B initiates an APP migration response to the S-FN of Building A, and the S-FN platform of Building A informs the S-FN APP instance that the state synchronization of the migration APP is ready. After the mirroring and state synchronization of the migration APP is completed between the S-FN and the T-FN, the resource release is completed between the S-FN platform and the S-FN APP instance of the building A, and the S-FN platform and the S-FN of the building A are completed. The resources are released between the infrastructures and the process ends.
综上所述，本公开实施例在构建集中式雾网络或分布式雾网络 时，各雾节点之间的相邻关系已配置，业务或应用在源边缘雾节点到目标边缘雾节点的移动过程中，若雾网络中源边缘雾节点到目标边缘雾节点之间有多个边缘雾节点，则可以通过在源边缘雾节点到目标边缘雾节点之间的各个边缘雾节点完成业务或应用的移动。也就是说，业务或应用总是从源边缘雾节点先移动到达雾网络中相邻的边缘雾节点，再以该相邻的边缘雾节点作为新的源边缘雾节点向目标边缘雾节点移动。In summary, when constructing a centralized fog network or a distributed fog network, the neighbor relationship between each fog node has been configured, and the service or application moves from the source edge fog node to the target edge fog node. In the fog network, if there are multiple edge fog nodes between the source edge fog node and the target edge fog node, the service or application movement can be completed by each edge fog node between the source edge fog node and the target edge fog node. . That is to say, the service or application always moves from the source edge fog node to the adjacent edge fog node in the fog network, and then moves the adjacent edge fog node as a new source edge fog node to the target edge fog node.
根据本公开实施例，还提供一种计算机可读存储介质，如软盘、光盘、硬盘、闪存、U盘、CF卡、SD卡、MMC卡等，在该计算机可读存储介质中存储有实现根据上述各实施例的业务迁移方法的一个或多个程序。所述一个或多个程序可以由处理器读取并执行，从而实现根据上述各实施例的业务迁移方法。According to an embodiment of the present disclosure, there is also provided a computer readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash memory, a USB flash drive, a CF card, an SD card, an MMC card, etc., in which the implementation is stored according to the computer readable storage medium One or more programs of the business migration method of each of the above embodiments. The one or more programs may be read and executed by a processor to implement the service migration method according to the above embodiments.
本领域的技术人员应该明白，上述本公开的各模块或各步骤可以用通用的计算装置来实现，各模块或各步骤可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上。此外，各模块或各步骤可以用计算装置可执行的程序代码来实现，从而，可以将程序代码存储在计算机存储介质(ROM/RAM、磁碟、光盘)中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将各模块或各步骤分别制作成各个集成电路模块，或者将各模块或各步骤中的多个模块或步骤制作成单个集成电路模块来实现。所以，本公开不限制于任何特定的硬件和软件结合。It should be understood by those skilled in the art that the various modules or steps of the above disclosure may be implemented by a general-purpose computing device, and each module or step may be centralized on a single computing device or distributed among multiple computing devices. online. In addition, each module or step may be implemented by a program code executable by a computing device, such that the program code may be stored in a computer storage medium (ROM/RAM, disk, optical disk) by a computing device, and In some cases, the steps shown or described may be performed in a different order than the ones described herein, or each module or step may be separately fabricated into individual integrated circuit modules, or multiple modules or steps in each module or step. It is made into a single integrated circuit module. Therefore, the present disclosure is not limited to any specific combination of hardware and software.
根据本公开实施例提供的方案，在集中式雾网络或分布式雾网络中，业务或应用从一个雾节点移动到另一个雾节点的移动性达到了解决，提高了用户体验。According to the solution provided by the embodiment of the present disclosure, in a centralized fog network or a distributed fog network, the mobility of a service or an application moving from one fog node to another is solved, and the user experience is improved.
尽管上文对本公开进行了详细说明，但是本公开不限于此，本技术领域技术人员可以根据本公开的原理进行各种修改。因此，凡按照本公开原理所作的修改，都应当理解为落入本公开的范围。Although the present disclosure has been described in detail above, the present disclosure is not limited thereto, and various modifications may be made by those skilled in the art in accordance with the principles of the present disclosure. Therefore, modifications made in accordance with the principles of the present disclosure are to be understood as falling within the scope of the present disclosure.

Claims (13)

  1. 一种业务迁移方法，包括：A method of business migration, including:
    源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求；The source edge fog node initiates a migration request including the migration service to the target edge fog node via the fog network when determining that its service needs to be migrated;
    所述目标边缘雾节点收到所述迁移请求后，通过对所述迁移业务的资源进行配置，激活与所述迁移业务对应的业务，并经由所述雾网络向所述源边缘雾节点发送迁移响应；以及After receiving the migration request, the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the migration to the source edge fog node via the fog network. Respond;
    所述源边缘雾节点收到所述迁移响应后，释放与所述迁移业务相应的资源。After receiving the migration response, the source edge fog node releases resources corresponding to the migration service.
  2. 根据权利要求1所述的业务迁移方法，其中，所述雾网络包括集中式雾网络，并且所述集中式雾网络包括多个高层雾节点和每个高层雾节点管理的多个边缘雾节点。The service migration method of claim 1, wherein the fog network comprises a centralized fog network, and the centralized fog network comprises a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node.
  3. 根据权利要求2所述的业务迁移方法，其中，所述源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求的步骤包括：The service migration method according to claim 2, wherein the step of the source edge fog node initiating a migration request including the migration service to the target edge fog node via the fog network when determining that the service needs to be migrated comprises:
    在所述集中式雾网络中，如果所述源边缘雾节点与所述目标边缘雾节点由相同的高层雾节点管理，则所述源边缘雾节点经由所述高层雾节点向所述目标边缘雾节点发起包含迁移业务的迁移请求。In the centralized fog network, if the source edge fog node and the target edge fog node are managed by the same high-level fog node, the source edge fog node is fogged to the target edge via the high-rise fog node The node initiates a migration request that includes the migration service.
  4. 根据权利要求2所述的业务迁移方法，其中，所述源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求的步骤包括：The service migration method according to claim 2, wherein the step of the source edge fog node initiating a migration request including the migration service to the target edge fog node via the fog network when determining that the service needs to be migrated comprises:
    在所述集中式雾网络中，如果所述源边缘雾节点与所述目标边缘雾节点由不同的高层雾节点管理，则所述源边缘雾节点经由源高层雾节点和目标高层雾节点向所述目标边缘雾节点发起包含迁移业务的迁移请求，In the centralized fog network, if the source edge fog node and the target edge fog node are managed by different high-level fog nodes, the source edge fog node passes through the source high-level fog node and the target high-level fog node The target edge fog node initiates a migration request including the migration service,
    其中，所述源边缘雾节点由所述源高层雾节点管理，并且所述 目标边缘雾节点由所述目标高层雾节点管理。Wherein the source edge fog node is managed by the source high level fog node, and the target edge fog node is managed by the target high level fog node.
  5. 根据权利要求1所述的业务迁移方法，其中，所述雾网络包括分布式雾网络，并且所述分布式雾网络包括多个边缘雾节点。The service migration method of claim 1, wherein the fog network comprises a distributed fog network, and the distributed fog network comprises a plurality of edge fog nodes.
  6. 根据权利要求6所述的业务迁移方法，其中，所述源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向目标边缘雾节点发起包含迁移业务的迁移请求的步骤包括：The service migration method according to claim 6, wherein the step of the source edge fog node initiating a migration request including the migration service to the target edge fog node via the fog network when determining that the service needs to be migrated comprises:
    在所述分布式雾网络中，所述源边缘雾节点直接向所述目标边缘雾节点发起包含迁移业务的迁移请求。In the distributed fog network, the source edge fog node directly initiates a migration request including a migration service to the target edge fog node.
  7. 一种业务迁移装置，包括源边缘雾节点和目标边缘雾节点，A service migration device includes a source edge fog node and a target edge fog node,
    所述源边缘雾节点在确定其业务需要进行迁移时，经由雾网络向所述目标边缘雾节点发起包含迁移业务的迁移请求，并且在收到针对所述迁移请求的迁移响应后，释放与所述迁移业务相应的资源，The source edge fog node initiates a migration request including the migration service to the target edge fog node via the fog network when determining that its service needs to be migrated, and releases the migration response after receiving the migration response for the migration request. Relating the resources corresponding to the migration business,
    所述目标边缘雾节点收到所述迁移请求后，通过对所述迁移业务的资源进行配置，激活与所述迁移业务对应的业务，并经由所述雾网络向所述源边缘雾节点发送所述迁移响应。After receiving the migration request, the target edge fog node activates the service corresponding to the migration service by configuring the resource of the migration service, and sends the service to the source edge fog node via the fog network. The migration response.
  8. 根据权利要求7所述的业务迁移装置，其中，所述雾网络包括集中式雾网络，并且所述集中式雾网络包括多个高层雾节点和每个高层雾节点管理的多个边缘雾节点。The service migrating device of claim 7, wherein the fog network comprises a centralized fog network, and the centralized fog network comprises a plurality of high-level fog nodes and a plurality of edge fog nodes managed by each high-level fog node.
  9. 根据权利要求8所述的业务迁移装置，其中，所述源边缘雾节点位于所述集中式雾网络中，如果所述源边缘雾节点与所述目标边缘雾节点由相同的高层雾节点管理，则所述源边缘雾节点经由所述高层雾节点向所述目标边缘雾节点发起包含迁移业务的迁移请求。The service migration apparatus according to claim 8, wherein said source edge fog node is located in said centralized fog network, and if said source edge fog node and said target edge fog node are managed by the same high-level fog node, And the source edge fog node initiates a migration request including the migration service to the target edge fog node via the high-level fog node.
  10. 根据权利要求8所述的业务迁移装置，其中，所述源边缘雾节点位于所述集中式雾网络中，如果所述源边缘雾节点与所述目标 边缘雾节点由不同的高层雾节点管理，则所述源边缘雾节点经由源高层雾节点和目标高层雾节点向所述目标边缘雾节点发起包含迁移业务的迁移请求，The service migration apparatus according to claim 8, wherein said source edge fog node is located in said centralized fog network, and if said source edge fog node and said target edge fog node are managed by different high-level fog nodes, And the source edge fog node initiates a migration request including the migration service to the target edge fog node via the source high-level fog node and the target high-level fog node,
    其中，所述源边缘雾节点由所述源高层雾节点管理，并且所述目标边缘雾节点由所述目标高层雾节点管理。The source edge fog node is managed by the source high-level fog node, and the target edge fog node is managed by the target high-level fog node.
  11. 根据权利要求7所述的业务迁移装置，其中，所述雾网络包括分布式雾网络，并且所述分布式雾网络包括多个边缘雾节点。The service migrating device of claim 7, wherein the fog network comprises a distributed fog network and the distributed fog network comprises a plurality of edge fog nodes.
  12. 根据权利要求11所述的业务迁移装置，其中，所述源边缘雾节点位于所述分布式雾网络中，并且所述源边缘雾节点直接向所述目标边缘雾节点发起包含迁移业务的迁移请求。The service migration apparatus according to claim 11, wherein said source edge fog node is located in said distributed fog network, and said source edge fog node directly initiates a migration request including a migration service to said target edge fog node .
  13. 一种计算机存储介质，其上存储有计算机程序，当处理器执行所述计算机程序是，所述处理器执行根据权利要求1至6中任一项所述的业务迁移方法。A computer storage medium having stored thereon a computer program, the processor executing the business migration method according to any one of claims 1 to 6 when the processor executes the computer program.
PCT/CN2018/096441 2017-07-21 2018-07-20 Service migration method and apparatus WO2019015669A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710601352.6A CN109286645A (en) 2017-07-21 2017-07-21 A kind of moving method and device of business
CN201710601352.6 2017-07-21

Publications (1)

Publication Number Publication Date
WO2019015669A1 true WO2019015669A1 (en) 2019-01-24

Family

ID=65015813

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096441 WO2019015669A1 (en) 2017-07-21 2018-07-20 Service migration method and apparatus

Country Status (2)

Country Link
CN (1) CN109286645A (en)
WO (1) WO2019015669A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852693A (en) * 2021-09-26 2021-12-28 北京邮电大学 Migration method of edge computing service

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111800442B (en) * 2019-04-08 2022-10-28 阿里巴巴集团控股有限公司 Network system, mirror image management method, device and storage medium
CN110290506B (en) * 2019-04-17 2020-08-14 中国联合网络通信集团有限公司 Edge cloud mobility management method and device
CN112748992B (en) * 2019-10-31 2024-03-01 中国电信股份有限公司 Electronic device, method and storage medium for migrating tasks
CN113453286B (en) * 2020-03-24 2023-05-12 上海诺基亚贝尔股份有限公司 Service migration in response to access device handoff

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212810A (en) * 2006-12-27 2008-07-02 华为技术有限公司 Customer premise equipment switching method and system in radio network
CN103873534A (en) * 2012-12-18 2014-06-18 ***通信集团公司 Method and device for application cluster migration
CN104468759A (en) * 2014-11-27 2015-03-25 中国联合网络通信集团有限公司 Method and device for achieving application migration in PaaS platform
US20150212756A1 (en) * 2014-01-28 2015-07-30 International Business Machines Corporation Management of extent migration on tiered storage
CN105897375A (en) * 2015-01-26 2016-08-24 中兴通讯股份有限公司 Service migration method and device

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101977242A (en) * 2010-11-16 2011-02-16 西安电子科技大学 Layered distributed cloud computing architecture and service delivery method
US20170048308A1 (en) * 2015-08-13 2017-02-16 Saad Bin Qaisar System and Apparatus for Network Conscious Edge to Cloud Sensing, Analytics, Actuation and Virtualization
CN106357743B (en) * 2016-08-29 2019-06-07 北京邮电大学 A kind of mist calculating business transmitting method of the network based on hierarchical cache
CN106792739B (en) * 2016-11-17 2020-01-21 北京邮电大学 Network slicing method, device and equipment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212810A (en) * 2006-12-27 2008-07-02 华为技术有限公司 Customer premise equipment switching method and system in radio network
CN103873534A (en) * 2012-12-18 2014-06-18 ***通信集团公司 Method and device for application cluster migration
US20150212756A1 (en) * 2014-01-28 2015-07-30 International Business Machines Corporation Management of extent migration on tiered storage
CN104468759A (en) * 2014-11-27 2015-03-25 中国联合网络通信集团有限公司 Method and device for achieving application migration in PaaS platform
CN105897375A (en) * 2015-01-26 2016-08-24 中兴通讯股份有限公司 Service migration method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OSANAIYE, O. ET AL.: "From Cloud to Fog Computing: A Review and a Conceptual Live VM Migration Framework", IEEE ACCESS: SPECIAL SECTION ON RECENT ADVANCES IN CLO UD RADIO ACCESS NETWORKS, vol. 5, 11 April 2017 (2017-04-11), XP011651412, Retrieved from the Internet <URL:DOI:10.1109/ACCESS.2017.2692960> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852693A (en) * 2021-09-26 2021-12-28 北京邮电大学 Migration method of edge computing service

Also Published As

Publication number Publication date
CN109286645A (en) 2019-01-29

Similar Documents

Publication Publication Date Title
WO2019015669A1 (en) Service migration method and apparatus
Yi et al. Fog computing: Platform and applications
Yi et al. Lavea: Latency-aware video analytics on edge computing platform
Giang et al. Developing iot applications in the fog: A distributed dataflow approach
KR102435503B1 (en) COMPUTING SYSTEM AND METHOD FOR INTELLIGENT IoE INFORMATION FRAMEWORK
US11368409B2 (en) Method for customized, situation-aware orchestration of decentralized network resources
EP3567921A1 (en) Network switching method and related equipment
WO2017041525A1 (en) Virtual network function reconstruction method and device
TWI745557B (en) Method, apparatus, and computer-readable medium for wireless communication
US20210243105A1 (en) Systems and methods for automatically packaging and deploying virtual network functions based on network interface dependencies and compatibilities
US20190098104A1 (en) Network infrastructure system and method for data processing and data sharing using the same
Alioua et al. dSDiVN: a distributed software-defined networking architecture for infrastructure-less vehicular networks
US20210286655A1 (en) Dynamic fog service deployment and management
CN113778615B (en) Rapid and stable network shooting range virtual machine construction system
JP2020150533A (en) Digital representation of physical intelligent moving object
da Silva Barbosa et al. A platform for cloudification of network and applications in the Internet of Vehicles
CN112527493A (en) Method, device, system and medium for creating edge computing service
JP2022077504A (en) Computer-implemented method, computer system, and computer program, for predictively deploying microservices on edge devices in network
WO2019105129A1 (en) Method and apparatus for implementing fog node communication service, fog node, and storage medium
EP3456086B1 (en) System and method for managing mobile virtual machine type communication devices
WO2018214815A1 (en) Network slice control method, device and system
EP3633919A1 (en) Control method, related device, and system
Pritchard et al. Mobile edge computing: Architecture, use-cases, applications
CN111480322A (en) Pervasive computing
KR20230014747A (en) Method and system for interaction between 5G and multiple TSC/TSN domains

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18834415

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18834415

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/05/2020)