WO2021093535A1

WO2021093535A1 - Mobile edge computing application data migration method, device, and core network node

Info

Publication number: WO2021093535A1
Application number: PCT/CN2020/122657
Authority: WO
Inventors: 王晔; 匡尚超; 李凤; 刘玮
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团有限公司
Priority date: 2019-11-11
Filing date: 2020-10-22
Publication date: 2021-05-20
Also published as: CN112788086A; CN112788086B

Abstract

The present disclosure provides a mobile edge computing application data migration method, a device, and a core network node. The mobile edge computing application data migration method is applied to a mobile edge computing (MEC) device and comprises: receiving vehicle position change information sent by a core network node; and migrating application data of a vehicle from a source MEC node to a target MEC node according to the vehicle position change information.

Description

Mobile edge computing application data migration method, device and core network node

Cross-references to related applications

This application claims the priority of Chinese Patent Application No. 201911095826.X filed in China on November 11, 2019, the entire content of which is incorporated herein by reference.

Technical field

The present disclosure relates to the technical field of Internet of Vehicles, and in particular to a method, device and core network node for data migration of mobile edge computing applications.

Background technique

In the vehicle-to-everything (Vehicle-to-Everything, V2X) mobile edge computing (Mobile Edge Computing, MEC) application scenario, the vehicle user equipment (UE, also called terminal) has high mobility, which is the overall architecture and Application services have brought great technical challenges.

On the basis of the fifth-generation (5Generation, 5G) network domain business continuity solution, the N9 channel between the source user plane function (UPF) and the destination UPF is established to provide application data migration and service redirection. The time buffer window has come to ensure that the source edge node V2X application can continue to provide services for a period of time for vehicles leaving.

However, the related technology does not have a corresponding implementation scheme for the migration of UE application data across MEC due to the MEC service area switch of the mobile entity under the MEC application service, and cannot guarantee the efficient and highly reliable application data migration of the network.

Summary of the invention

The embodiments of the present disclosure provide a mobile edge computing application data migration method, device, and core network node to solve the problem that the UE cannot perform efficient and highly reliable application data migration when the UE applies services across different MECs during the movement.

In order to solve the above technical problems, embodiments of the present disclosure provide a mobile edge computing application data migration method, which is applied to a mobile edge computing MEC device, including:

Receive vehicle position change information sent by core network nodes;

According to the vehicle position change information, the application data of the vehicle is migrated from the source MEC node to the target MEC node.

Optionally, the migrating the application data of the vehicle from the source MEC node to the target MEC node includes:

The MEC orchestrator in the MEC device sends the application data migration task of the vehicle to the source MEC node in the MEC device;

The MEC application data synchronization server of the source MEC node obtains the application data of the vehicle according to the application data migration task, and synchronizes the application data of the vehicle to the target MEC node.

Further, the MEC orchestrator communicates with the source MEC node through the MEC platform manager in the MEC device.

Further, the acquiring the application data of the vehicle and synchronizing the application data of the vehicle to the target MEC node includes:

The agent module of the MEC application data synchronization server obtains the application data of the vehicle;

The message queue agent module generates a queue according to the application data;

The transmission module sends the queue in the message queue agent module to the MEC application data synchronization server of the target MEC node in the form of a queue message.

Specifically, the agent module of the MEC application data synchronization server obtains the application data of the vehicle, including at least one of the following:

Query the application program interface API of MEC application related data from the MEC application data open server, and use the API to obtain vehicle application data from the MEC application;

Obtain vehicle application data from the MEC application data open server.

Further, after the obtaining the application data of the vehicle and synchronizing the application data of the vehicle to the target MEC node, the method further includes:

The target MEC node sends a migration complete message to the MEC arranger of the MEC device.

Optionally, after migrating the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information, the method further includes:

The target address of the application data of the vehicle is sent to the core network node.

The embodiment of the present disclosure also provides a mobile edge computing application data migration method, which is applied to a core network node, and includes:

Send vehicle position change information to the mobile edge computing MEC device.

Optionally, before sending the vehicle position change information to the mobile edge computing MEC device, the method further includes:

When determining that the location of the vehicle changes, the session management function SMF is used to establish the N9 forwarding channel from the source user plane function UPF to the target UPF for the vehicle, and configure the forwarding rules of the target UPF so that the vehicle can communicate with the source MEC node in the MEC device Interactive.

Optionally, after the sending the vehicle position change information to the mobile edge computing MEC device, the method further includes:

Receive the target address of the vehicle's application data sent by the MEC device;

According to the target address, the forwarding rule of the user plane function UPF is updated.

The embodiment of the present disclosure also provides a mobile edge computing MEC device, including:

The first receiving module is configured to receive the vehicle position change information sent by the core network node;

The migration module is used to migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information.

Optionally, the migration module includes:

A sending unit, used for the MEC orchestrator in the MEC device to send the application data migration task of the vehicle to the source MEC node in the MEC device;

The source MEC node MEC application data synchronization server is used to obtain the application data of the vehicle according to the application data migration task, and synchronize the application data of the vehicle to the target MEC node.

Further, the source MEC node MEC application data synchronization server includes:

An agent module, used for the agent module of the MEC application data synchronization server to obtain the application data of the vehicle;

The message queue agent module is used for the message queue agent module to generate a queue according to the application data;

The transmission module is used to send the queue in the message queue agent module to the MEC application data synchronization server of the target MEC node in the form of a queue message.

Specifically, the agent module is used to implement at least one of the following:

Obtain vehicle application data from the MEC application data open server.

Further, after the source MEC node MEC application data synchronization server obtains the application data of the vehicle according to the application data migration task, and synchronizes the application data of the vehicle to the target MEC node, the method further includes:

The feedback module is used for the target MEC node to send a migration completion message to the MEC orchestrator of the MEC device.

Optionally, after the migration module migrates the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle location change information, the method further includes:

The first sending module is used to send the target address of the application data of the vehicle to the core network node.

The embodiment of the present disclosure also provides a mobile edge computing MEC device, including a transceiver and a processor;

The transceiver is used to receive vehicle position change information sent by a core network node;

The processor is configured to migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information.

The embodiment of the present disclosure also provides a mobile edge computing MEC device, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the processor implements the foregoing when the program is executed. Mobile edge computing application data migration method.

The embodiment of the present disclosure also provides a core network node, including:

The second sending module is used to send vehicle position change information to the mobile edge computing MEC device.

Optionally, before the second sending module sends the vehicle position change information to the mobile edge computing MEC device, the method further includes:

The configuration module is used to establish the N9 forwarding channel from the source user plane function UPF to the target UPF for the vehicle through the session management function SMF when the position of the vehicle is determined to change, and configure the forwarding rules of the target UPF so that the vehicle can communicate with the MEC device To interact with the source MEC node.

Optionally, after the second sending module sends the vehicle position change information to the mobile edge computing MEC device, the method further includes:

The second receiving module is used to receive the target address of the vehicle application data sent by the MEC device;

The update module is used to update the forwarding rule of the user plane function UPF according to the target address.

The embodiment of the present disclosure also provides a core network node, including a transceiver and a processor;

The transceiver is used to send vehicle position change information to the mobile edge computing MEC device.

The embodiments of the present disclosure also provide a core network node, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the aforementioned movement when the program is executed. Edge computing application data migration method.

The embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps in the above-mentioned mobile edge computing application data migration method are realized.

The beneficial effects of the present disclosure are:

The above solution realizes the migration of the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle location change information, thereby solving the problem that the UE cannot perform efficient and highly reliable application data when applying services across different MECs during the movement. The problem of migration, this method ensures the accuracy and efficiency of application data migration.

Description of the drawings

FIG. 1 shows one of the schematic flowcharts of the mobile edge computing application data migration method according to an embodiment of the present disclosure;

Figure 2 shows a schematic diagram of the MEC application data migration framework;

Figure 3 shows a schematic diagram of the main components of MASS;

Figure 4 shows a sequence diagram of a sub-process of application data migration based on MASS;

Figure 5 shows a schematic diagram of the relationship between other modules in the MAOS and MEC application data migration framework;

Figure 6 shows a schematic diagram of the MEC application data migration and application redirection process based on 5G service continuity and 5G network capability opening;

Figure 7 shows a schematic diagram of the main flow of MEC application data migration;

FIG. 8 shows the second schematic flowchart of the mobile edge computing application data migration method according to an embodiment of the present disclosure;

FIG. 9 shows a schematic diagram of modules of an MEC device according to an embodiment of the present disclosure;

FIG. 10 shows a schematic diagram of modules of a core network node according to an embodiment of the present disclosure.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present disclosure clearer, the present disclosure will be described in detail below with reference to the accompanying drawings and specific embodiments.

The present disclosure aims at the problem that the UE cannot perform efficient and highly reliable application data migration when applying services across different MECs in a moving process, and provides a mobile edge computing application data migration method, device and core network node.

As shown in FIG. 1, the mobile edge computing application data migration method of the embodiment of the present disclosure, applied to a mobile edge computing (MEC) device, includes:

Step 11: Receive the vehicle position change information sent by the core network node;

It should be noted that the vehicle location change information is mainly obtained by the core network node according to the change of the access network accessed by the vehicle. The core network node mentioned in the embodiment of the present disclosure mainly refers to the 5G core network. node.

It should also be noted that the location of the vehicle is embodied by the on-board terminal equipment in the vehicle.

Step 12: Migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information;

It should be noted that when the vehicle is not moving, it obtains application data from the source MEC node. When it moves to a new access network node, the vehicle that provides application data will become the target MEC node (or called the destination MEC). Node), in order to ensure that the target MEC node can provide the vehicle with the application data it needs, the application data of the vehicle needs to be migrated from the source MEC node to the target MEC node.

It should be noted that the MEC device mentioned in the embodiments of the present disclosure is a functional entity of the application layer. The MEC device mainly includes the following functional entities: MEC Orchestrator (MEC) as a communication interface, MEC platform manager ( MEC Platform Manager (MEPM) realizes the management of MEC node (MEC Node, MEN) and MEC node (MEC Node, MEN). It should be noted that the MEC orchestrator realizes the communication with the MEC node through the MEC platform manager, and the MEC The orchestrator realizes the information interaction with the core network node through the core network node capability opening.

Among them, the MEC node also includes: MEC platform (MEC Platform, MEP), MEC application (MEC Platform Application, MEA), and further, MEC platform includes: MEC Application Data Synchronization Services (MEC Application Data Synchronization Services, MASS, this disclosure) In the embodiments, it is also called MEC Application Data Synchronization Server) and MEC Application Data Open Services (MAOS, also called MEC Application Data Open Server in the embodiments of the present disclosure). Specifically, the MEC application data migration framework is shown in the figure 2 shown.

It should be noted that MASS is a basic MEC Services provided by MEP. MASS is mainly responsible for providing cross-MEP application data migration and synchronization services for distributed MEAs. MASS mainly adopts the P2P (Point2Point) architecture and uses the Mp3 channel between MEPs to provide high-speed data transmission. With the help of MASS proxy module, MASS MQ module, MASS transmission module and MASS task management module, it can realize high-availability and high-real-time data migration synchronization services. . It should be noted that MASS considers priority strategies and provides differentiated migration and synchronization services to ensure service quality while also improving economy.

Further, MASS is mainly composed of modules, as shown in Figure 3, which mainly include:

A11, MASS task management module

Its main responsibilities are:

The task receives and receives the data migration task sent by MAPM, and triggers the MASS agent module to perform data acquisition;

Task monitoring, based on the acknowledgement (ACK) message mechanism, monitor the status of migration tasks in both directions, provide task rollback, and ensure reliability and consistency;

Task synchronization, data migration task status synchronization between source MASS and destination MASS;

The task is closed, the target MASS agent module completes the data update, the source MASS task manager feeds back to MEPM, and closes the task.

A12, MASS agent module

It mainly includes:

A121, MEA proxy (Proxy):

Get process: query the MEA related data query API from the MAOS service, use the API to obtain UE application data from the MEA; or directly obtain the data from the MAOS service;

Update process: query the MEA related data update API from the MAOS service, use the API to update the UE application data to the MEA, or directly update the data to the MAOS service.

A122. MQ Proxy:

As a producer, produce data to the MASS message queue according to the data obtained in the MEA Proxy Get process;

As a consumer, consume data from the MASS message queue and call the MEA Proxy Update process;

It should also be noted that MQ Proxy will produce and consume messages according to the task priority strategy.

A13, MASS message queue module

Priority-based multi-message queues: such as high-priority message queues (hight_priority_mq), medium-priority message queues (medium_priority_mq), and low-priority message queues (low_priority_mq), providing high-quality differentiated services;

Define message direction based on Topic: Use Topic={send,receive} to quickly distinguish data sent by MASS from data sent by other MASS;

It should be noted that the MASS message queue module is a distributed MQ architecture with high availability and high real-time.

A14, MASS transmission module

Sending process: As a consumer, consume the relevant message data that needs to be sent from the MASS message queue and send it to the destination MASS;

Receiving process: As a producer, it receives message data from other MASS and produces data to the MASS message queue.

It should be noted that, based on the above-mentioned MASS composition structure, the sequence of the application data migration sub-process based on MASS is shown in Figure 4:

S401, the source MASS (S-MASS) task management module, the source MASS agent module, and the source MASS MQ module receive the data migration task sent by MAPM;

It should be noted that the target MASS of the source MEC platform and the target MEC platform is based on the ACK message mechanism to monitor the entire life cycle of the data migration task.

S402: The source MASS task management module triggers execution data acquisition;

S403. The source MASS proxy module queries the MEA related data query API from MAOS;

S404: The source MASS proxy module uses API to obtain vehicle application data (also referred to as UE application data) from the source MEA;

S405. The source MEA feeds back the application data of the vehicle to the source MASS agent module;

S406. The source MASS agent module produces the migration data that needs to be sent to the source MASS MQ module;

S407. The source MASS MQ module consumes the migration data that needs to be sent from the MASS message queue;

S408: The source MASS transmission module sends the migration data to the target MASS;

It should be noted that the target MASS receives the data sent by the source MASS, and then migrates and updates the data to the target application through the corresponding transmission module, MQ module, and proxy module.

S409: The task management module of the target MASS feeds back the migration task completion status ACK message to the source MASS agent task management module;

It should also be noted that the target MASS agent module completes the data update, and the source MASS task management module feeds back to MEPM and closes the task.

Further, the main functions of MAOS are introduced as follows:

MAOS is also a basic MEC Services provided by MEP. MAOS is mainly responsible for providing MEA with open access services for application data. Based on different permissions, MEC Services, MEA, etc. on MEP can access application data.

MAOS hopes that MEA itself agrees and supports the unified management of application data through MAOS. MAOS will uniformly store application data through the allocated virtual infrastructure (Virtualization Infrastructure, VI), and open data reading to other MEC Services and MEA based on access rights. Write operation. For example, MASS can query and update the migration data of MEA applications that support the application data synchronization service from MAOS. Specifically, the relationship between MAOS and other modules in the MEC application data migration framework is shown in FIG. 5.

Application migration data types mainly include UE access authentication information, UE application session state information, UE-related application history data, etc.

Based on the foregoing description, it can be known that the specific implementation of the foregoing step 12 is as follows:

S11. The MEC orchestrator in the MEC device sends the application data migration task of the vehicle to the source MEC node in the MEC device;

S12. The MEC application data synchronization server of the source MEC node obtains the application data of the vehicle according to the application data migration task, and synchronizes the application data of the vehicle to the target MEC node.

It should be noted that the MEC orchestrator communicates with the source MEC node through the MEC platform manager in the MEC device.

Further, the specific implementation of S12 is:

Further, the agent module of the MEC application data synchronization server obtains the application data of the vehicle, including at least one of the following:

Obtain vehicle application data from the MEC application data open server.

Further, after S12, it also includes:

It should also be noted that after step 12, the MEC device also needs to send the target address of the vehicle's application data to the core network node, the target address mainly refers to the identification information of the target MEC node where the application data is located; the core network node is based on The target address updates the forwarding rule of the user plane function (UPF). Further, before the core network node sends the vehicle location change information to the mobile edge computing MEC device, it is first necessary to determine that the location of the vehicle has changed. When the location of the vehicle changes, the session management function (SMF) is used to establish a secondary user for the vehicle. The N9 forwarding channel of the UPF to the target UPF is configured to configure the forwarding rules of the target UPF so that the vehicle can interact with the source MEC node in the MEC device.

The MEC application data migration and application redirection process based on 5G service continuity and 5G network capability opening is shown in Figure 6, where the dotted arrow in Figure 6 indicates the path maintained by the application service before the migration, and the black solid arrow indicates the migration process. The communication process, the dotted arrow indicates the application service change process after migration.

Specifically, the main process of MEC application data migration is summarized as follows, which mainly includes three stages:

Stage one, before migration (mainly used to achieve business continuity guarantee)

1.1. The vehicle moves from the source access network node (S-NG-RAN) to the target access network node (T-NG-RAN);

1.2. The access and mobility management function (AMF) entity of the core network node (5GC) discovers the movement changes of the vehicle, and establishes the vehicle from the source user plane function (S-UPF) to the target user plane through the session management function (SMF) entity Function (T-UPF) N9 forwarding channel, configure T-UPF forwarding rules;

1.3. The vehicle can continue to interact with the source MEA (S-MEA), and the links are T-NG-RAN, T-UPF, S-UPF, source PDU session anchor (S-PSA), and S-MEA.

Phase two, migration (application data migration)

2.1, 5GC (AMF through the policy control function (Network Exposure Function, PCF), network opening function (Network Exposure Function, NEF) notification of MEO vehicle location changes;

2.2. MEO triggers the task of data migration of the vehicle S-MEA application;

2.3. The source MEC platform (S-MEP) obtains the data to be migrated by the S-MEA, and sends it to the target MEA (T-MEA) of the target MEC platform (S-MEP) to complete the migration.

Phase three, after migration (application service redirection)

3.1. MEO sends the vehicle’s new T-MEA routing rules to 5GC (NEF, PCF, SMF), and updates the UPF forwarding rules;

3.2. The vehicle switches to T-MEA interaction.

Specifically, as shown in FIG. 7, the main flow of MEC application data migration in which the UE moves under the access network node is described in detail as follows.

The UE moves to the T-NG-RAN and establishes the N9 channel. Before the application data migration is completed, the S-MEA continues to provide services to the UE through the N9 channel.

S701 and 5GC send UE location changes to MEO through network capability opening (AMF, PCF, NEF), such as (S-NG-RAN, T-NG-RAN);

S702. The MEO obtains the UE migration information (S-MEP, S-MEA, T-MEP, T-MEA) according to the UE location change and the system-level topology, and triggers the UE application data migration task;

It should be noted that MEO determines the UE target environment T-MEN according to UE location changes and system-level MEN topology; MEO queries whether T-MEA has T-MEA application instances running, and MEPM feeds back the status of T-MEA application instances (in normal operation) , Run without instance, etc.); MEO decides to trigger data migration or application instantiation based on the feedback results. It should be noted that the application instantiation is triggered here: according to the MEO application deployment management function, query the deployment resource requirements of the T-MEA application, the deployment mirror location, and the deployment script, etc., and MEO allocates deployment resources (calculations) for T-MEA through VIM , Storage, network), and copy the T-MEA deployment image through VIM; MEO, MEPM, VIM and T-MEA execute T-MEA deployment scripts to complete application instantiation, MEO informs MEPM T-MEA instantiation is complete, MEPM responds to T -MEA performs full life cycle status monitoring, MEO, MEPM, VIM and T-MEA complete the T-MEA application instantiation process, and MEO triggers the migration of S-MEA application data.

S703. The MEO sends a UE application data migration task to the MEPM;

S704. The MEPM forwards the UE application data migration task to the S-MEP;

S705, S-MEP queries the application migration data of UE in S-MEA through MASS and MAOS services;

S706. The S-MEA returns the data to be migrated, including UE access authentication information, UE application session state information, UE-related application history data, etc.;

S707. Through the MASS synchronization service, the S-MEP synchronizes the UE application migration data to the T-MEP;

S708, T-MEP updates the application data of UE in T-MEA through MASS and MAOS services;

S709. Complete the UE application data migration task, and gradually feedback information to T-MEP, S-MEP, MEPM and MEO;

S710. The MEO sends the new routing rule of the UE to the 5GC;

S711, 5GC (NEF, PCF, SMF) issue a new offloading strategy to UPF and take effect;

S712. T-MEA provides services for the UE.

It should be noted that the embodiments of the present disclosure are technically oriented towards the integration of 5G technology and MEC technology, and propose a 5G network-based MEC application data migration method. This method is oriented to the mobility of the UE and takes into account the continuity of services based on 5G MEC. The openness of 5G network capabilities to the MEC top-level architecture, and proposes a P2P-based efficient application data migration framework, the main process of MEC application data migration and the MASS sub-process; from a business perspective, facing the group’s 5G+AICDE strategy, the proposed method is in 5G Core network, MEC edge computing architecture, C-V2X Internet of Vehicles applications and other fields have clear application value. They are the technical prerequisites for assisted driving and high real-time and high safety guarantees for autonomous driving under the 5G MEC architecture in the future, and are expected to pass standardization. Organize for output.

As shown in FIG. 8, the mobile edge computing application data migration method of the embodiment of the present disclosure, applied to a core network node, includes:

Step 81: Send vehicle position change information to the mobile edge computing MEC device.

It should be noted that all the descriptions about core network nodes in the foregoing embodiments are applicable to the embodiments of the mobile edge computing application data migration method, and the same technical effects can also be achieved.

As shown in FIG. 9, the MEC device 90 of the embodiment of the present disclosure includes:

The first receiving module 91 is configured to receive vehicle position change information sent by a core network node;

The migration module 92 is configured to migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information.

Optionally, the migration module 92 includes:

Obtain vehicle application data from the MEC application data open server.

Optionally, after the migration module 92 migrates the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information, the method further includes:

It should be noted that the device provided by the embodiment of the present disclosure is a device capable of executing the above-mentioned mobile edge computing application data migration method, and all the implementation methods in the above-mentioned mobile edge computing application data migration method embodiment are applicable to the device, and all Can achieve the same or similar beneficial effects.

Optionally, the processor realizes the migration of the application data of the vehicle from the source MEC node to the target MEC node, which specifically includes:

Obtain vehicle application data from the MEC application data open server.

The embodiment of the present disclosure also provides a mobile edge computing MEC device, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the processor implements the foregoing when the program is executed. Each process in the embodiment of the mobile edge computing application data migration method can achieve the same technical effect. To avoid repetition, details are not repeated here.

The embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the above-mentioned mobile edge computing application data migration method embodiment applied to the MEC device side is implemented Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here. Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.

As shown in FIG. 10, the core network node 100 of the embodiment of the present disclosure includes:

The second sending module 101 is used to send vehicle position change information to the mobile edge computing MEC device.

Optionally, before the second sending module 101 sends the vehicle position change information to the mobile edge computing MEC device, the method further includes:

Optionally, after the second sending module 101 sends the vehicle position change information to the mobile edge computing MEC device, the method further includes:

It should be noted that the core network node provided by the embodiment of the present disclosure is a core network node that can execute the above-mentioned mobile edge computing application data migration method, and all the implementation methods in the above-mentioned mobile edge computing application data migration method embodiment are applicable to this Core network nodes can achieve the same or similar beneficial effects.

Optionally, before the sending the vehicle position change information to the mobile edge computing MEC device to the mobile edge computing MEC device, the processor is further configured to:

Optionally, after the vehicle location change information is sent to the mobile edge computing MEC device, the transceiver is also used to receive the vehicle application data sent by the MEC device. address;

The processor is further configured to update the forwarding rule of the user plane function UPF according to the target address.

The embodiments of the present disclosure also provide a core network node, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the aforementioned movement when the program is executed. Each process in the embodiment of the edge computing application data migration method can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.

The embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the above-mentioned mobile edge computing application data migration method embodiment applied to the core network node side is implemented Each process can achieve the same technical effect. In order to avoid repetition, I will not repeat it here. Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.

Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems) and computer program products according to the embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated for use. It is a device that realizes the functions specified in one process or multiple processes and/or one block or multiple blocks in the flowchart.

These computer program instructions can also be stored in a computer-readable storage medium that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable storage medium produce paper products that include the instruction device, The instruction device realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that the computer or other programmable equipment executes a series of operation steps to produce computer-implemented processing, thereby executing instructions on the computer or other scientific programming equipment Provides steps for realizing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

It can be understood that the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, units, modules, sub-units and sub-modules can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), and digital signal processing equipment (DSP Device). , DSPD), Programmable Logic Device (PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, Disclosure of the described functions in other electronic units or combinations thereof.

For software implementation, the technology described in the embodiments of the present disclosure can be implemented through modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure. The software codes can be stored in the memory and executed by the processor. The memory can be implemented in the processor or external to the processor.

The above are optional implementations of the present disclosure. It should be pointed out that for those of ordinary skill in the art, several improvements and modifications can be made without departing from the principles described in the present disclosure, and these improvements and modifications are also Within the protection scope of the present disclosure.

Claims

A mobile edge computing application data migration method, applied to a mobile edge computing MEC device, includes:

Receive vehicle position change information sent by core network nodes;

According to the vehicle position change information, the application data of the vehicle is migrated from the source MEC node to the target MEC node.
The mobile edge computing application data migration method according to claim 1, wherein the migration of the application data of the vehicle from the source MEC node to the target MEC node comprises:

The MEC orchestrator in the MEC device sends the application data migration task of the vehicle to the source MEC node in the MEC device;

The MEC application data synchronization server of the source MEC node obtains the application data of the vehicle according to the application data migration task, and synchronizes the application data of the vehicle to the target MEC node.
The mobile edge computing application data migration method according to claim 2, wherein the MEC orchestrator communicates with the source MEC node through the MEC platform manager in the MEC device.
The mobile edge computing application data migration method according to claim 2, wherein said acquiring the application data of the vehicle and synchronizing the application data of the vehicle to the target MEC node comprises:

The agent module of the MEC application data synchronization server obtains the application data of the vehicle;

The message queue agent module generates a queue according to the application data;

The transmission module sends the queue in the message queue agent module to the MEC application data synchronization server of the target MEC node in the form of a queue message.
The mobile edge computing application data migration method according to claim 4, wherein the acquisition of vehicle application data by the proxy module of the MEC application data synchronization server includes at least one of the following:

Query the application program interface API of MEC application related data from the MEC application data open server, and use the API to obtain vehicle application data from the MEC application;

Obtain vehicle application data from the MEC application data open server.
The mobile edge computing application data migration method according to claim 2, wherein after said acquiring the application data of the vehicle and synchronizing the application data of the vehicle to the target MEC node, the method further comprises:

The target MEC node sends a migration complete message to the MEC arranger of the MEC device.
The mobile edge computing application data migration method according to claim 1, wherein after said migrating the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information, the method further comprises:

The target address of the application data of the vehicle is sent to the core network node.
A data migration method for mobile edge computing applications, applied to core network nodes, includes:

Send vehicle position change information to the mobile edge computing MEC device.
The mobile edge computing application data migration method according to claim 8, wherein before said sending vehicle position change information to the mobile edge computing MEC device, the method further comprises:

When determining that the location of the vehicle changes, the session management function SMF is used to establish the N9 forwarding channel from the source user plane function UPF to the target UPF for the vehicle, and configure the forwarding rules of the target UPF so that the vehicle can communicate with the source MEC node in the MEC device Interactive.
The mobile edge computing application data migration method according to claim 8, wherein after said sending vehicle position change information to the mobile edge computing MEC device, the method further comprises:

Receive the target address of the vehicle's application data sent by the MEC device;

According to the target address, the forwarding rule of the user plane function UPF is updated.
A mobile edge computing MEC device, including:

The first receiving module is configured to receive the vehicle position change information sent by the core network node;

The migration module is used to migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information.
The mobile edge computing MEC device according to claim 11, wherein the migration module comprises:

A sending unit, used for the MEC orchestrator in the MEC device to send the application data migration task of the vehicle to the source MEC node in the MEC device;

The source MEC node MEC application data synchronization server is used to obtain the application data of the vehicle according to the application data migration task, and synchronize the application data of the vehicle to the target MEC node.
The mobile edge computing MEC device according to claim 12, wherein the MEC orchestrator communicates with the source MEC node through an MEC platform manager in the MEC device.
The mobile edge computing MEC device according to claim 12, wherein the source MEC node MEC application data synchronization server comprises:

An agent module, used for the agent module of the MEC application data synchronization server to obtain the application data of the vehicle;

The message queue agent module is used for the message queue agent module to generate a queue according to the application data;

The transmission module is used to send the queue in the message queue agent module to the MEC application data synchronization server of the target MEC node in the form of a queue message.
The mobile edge computing MEC device according to claim 14, wherein the proxy module is configured to implement at least one of the following:

Query the application program interface API of MEC application related data from the MEC application data open server, and use the API to obtain vehicle application data from the MEC application;

Obtain vehicle application data from the MEC application data open server.
The mobile edge computing MEC device according to claim 12, wherein the MEC application data synchronization server at the source MEC node obtains the application data of the vehicle according to the application data migration task, and synchronizes the application data of the vehicle to the target MEC After the node, it also includes:

The feedback module is used for the target MEC node to send a migration completion message to the MEC orchestrator of the MEC device.
The mobile edge computing MEC device according to claim 11, wherein after the migration module migrates the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information, further comprising:

The first sending module is used to send the target address of the application data of the vehicle to the core network node.
A mobile edge computing MEC device, including a transceiver and a processor;

The transceiver is used to receive vehicle position change information sent by a core network node;

The processor is configured to migrate the application data of the vehicle from the source MEC node to the target MEC node according to the vehicle position change information.
A mobile edge computing MEC device, including a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the processor executes the program as claimed in claim 1- 7. Any one of the mobile edge computing application data migration method.
A core network node, including:

The second sending module is used to send vehicle position change information to the mobile edge computing MEC device.
The core network node according to claim 20, wherein before the second sending module sends the vehicle position change information to the mobile edge computing MEC device, the method further comprises:

The configuration module is used to establish the N9 forwarding channel from the source user plane function UPF to the target UPF for the vehicle through the session management function SMF when the position of the vehicle is determined to change, and configure the forwarding rules of the target UPF so that the vehicle can communicate with the MEC device To interact with the source MEC node.
The core network node according to claim 20, wherein after the second sending module sends the vehicle position change information to the mobile edge computing MEC device, the method further comprises:

The second receiving module is used to receive the target address of the vehicle application data sent by the MEC device;

The update module is used to update the forwarding rule of the user plane function UPF according to the target address.
A core network node, including a transceiver and a processor;

The transceiver is used to send vehicle position change information to the mobile edge computing MEC device.
A core network node, comprising a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the processor executes the program as claimed in any of claims 8-10. A method for data migration of mobile edge computing applications.
A computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the steps in the mobile edge computing application data migration method according to any one of claims 1-10.