Service migration methods, apparatus, equipment and readable storage media

Abstract

This application provides a service migration method, apparatus, device, and readable storage medium. The method includes: acquiring first information, which is used by the core network element to select a destination node from candidate edge nodes; wherein the destination node is used to start a first application during the service migration process, and as a subordinate node and a source node as a master node, obtain the status information of the first application from a cloud server, and both the source node and the destination node provide the service of the first application to a terminal; the destination node is further used to acquire control authority after receiving an instruction from the terminal, and as a master node, provide the service of the first application to the terminal; wherein the master node can receive control signals of the first application from the terminal, and the subordinate node does not receive control signals of the first application sent by the terminal.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a service migration method, apparatus, device, and readable storage medium. Background Technology

[0002] The introduction of cognitive service architecture has transformed the 6th generation (6G) core network from a single communication network control center into a joint scheduling hub for network and computing resources. However, in new application scenarios, the 6G core network will face severe service continuity challenges. On the one hand, distributed edge computing power and a massive number of user devices bring more frequent service migration needs; on the other hand, with the development and popularization of the metaverse, highly interactive applications, represented by cloud-based virtual reality (cloud VR), will push the requirements for latency and bandwidth to new heights.

[0003] Ensuring service continuity during service instance migration and maintaining high service quality on the endpoint side has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a service migration method, apparatus, device, and readable storage medium to address the problem of ensuring service continuity when service instances are migrated and maintaining high service quality on the terminal side.

[0005] Firstly, a service migration method is provided, applied to core network elements, including:

[0006] Obtain first information, which is used by the core network element to select a destination node from candidate edge nodes;

[0007] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0008] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0009] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0010] Optionally, the first information carries one or more of the following: location information of the edge node, and information of the first application supporting service migration.

[0011] Optionally, obtaining the first information includes:

[0012] The first information is obtained through the service registration agent of the edge node.

[0013] Optionally, the method further includes:

[0014] A first request is received, which is used to request the migration of the services of the first application from the source node to the destination node.

[0015] Optionally, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0016] Optionally, the method further includes:

[0017] Based on the first information, select the target node from the candidate edge nodes;

[0018] Send a second message to the destination node, the second message being used to instruct the destination node to launch the first application; and / or, the second message being used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal.

[0019] Optionally, after the destination node starts the first application, and / or after the new channel is established, the method further includes:

[0020] Send a third message to the source node, the third message being used to instruct the source node to notify the terminal to migrate the service of the first application from the source node to the destination node.

[0021] Secondly, a service migration method is provided, applied to a first node, which is an edge node, including:

[0022] Send first information, which is used by the core network element to select the destination node from the candidate edge nodes;

[0023] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0024] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0025] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0026] Optionally, the first information carries one or more of the following: location information of the edge node, and information of the first application supporting service migration.

[0027] Optionally, the method further includes:

[0028] The second information is received from the core network element, which instructs the destination node to start the first application; and / or, the second information instructs the establishment of a new channel between the terminal and the destination node, which is used by the destination node to provide the data stream of the first application to the terminal.

[0029] Optionally, the method further includes:

[0030] The terminal receives a fourth piece of information, which instructs the destination node to act as the master node and provide the terminal with the services of the first application.

[0031] Thirdly, a service migration method is provided, applied to a second node, which is the source node, including:

[0032] Send a first request, the first request being used to request that the services of the first application be migrated from the source node to the destination node;

[0033] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0034] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0035] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0036] Optionally, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0037] Optionally, the method further includes:

[0038] The third information is received from the core network element, which is used to instruct the source node to notify the terminal to migrate the service of the first application.

[0039] Optionally, the method further includes:

[0040] A fifth message is sent to the terminal, which instructs the terminal to switch the service of the first application from the source node to the destination node.

[0041] Optionally, the method further includes:

[0042] The terminal receives a sixth message, which instructs the source node to release the channel with the terminal.

[0043] Fourthly, a service migration method is provided, applied to a terminal, including:

[0044] The terminal receives fifth information from the source node, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node;

[0045] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0046] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0047] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0048] Optionally, the method further includes:

[0049] A fourth message is sent to the destination node, the fourth message being used to instruct the destination node to provide the service of the first application to the terminal as a master node.

[0050] Optionally, the method further includes:

[0051] The data stream of the first application provided by the destination node is obtained through a new channel established between the terminal and the destination node.

[0052] Fifthly, a service migration device is provided, applied to core network elements, comprising:

[0053] The first acquisition module is used to acquire first information, which is used by the core network element to select a destination node from candidate edge nodes.

[0054] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0055] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0056] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0057] Sixthly, a service migration apparatus is provided, applied to a first node, wherein the first node is an edge node, comprising:

[0058] The second sending module is used to send first information, which is used by the core network element to select the destination node from the candidate edge nodes.

[0059] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0060] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0061] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0062] In a seventh aspect, a service migration apparatus is provided, applied to a second node, the second node being the source node, comprising:

[0063] The fourth sending module is used to send a first request, which requests that the service of the first application be migrated from the source node to the destination node;

[0064] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0065] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0066] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0067] Eighthly, a service migration apparatus is provided, applied to a terminal, comprising:

[0068] The sixth receiving module is used to receive fifth information from the source node, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node;

[0069] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0070] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0071] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0072] A ninth aspect provides a communication device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the first, second, third, or fourth aspect.

[0073] A tenth aspect provides a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first, second, third, or fourth aspect.

[0074] In this embodiment, service continuity during migration is ensured through the overall scheduling of network and computing resources by core network elements. Unlike existing methods based on virtual machine or container migration, where computing state migration and network switching are performed independently, this embodiment fully utilizes data from the cloud server to restore the process at the destination node and keep it synchronized with the source node, avoiding memory copying and reducing downtime during service migration. This embodiment can significantly reduce the downtime of the first application, maintaining it between 8ms and 14ms, effectively reducing the amount of data transmitted from the source node to the destination node, even reducing it to zero. Attached Figure Description

[0075] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0076] Figure 1 This is a diagram illustrating the network handover during service migration;

[0077] Figure 2 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0078] Figure 3 This is one of the flowcharts of the service migration method provided in the embodiments of this application;

[0079] Figure 4 This is the second flowchart of the service migration method provided in the embodiments of this application;

[0080] Figure 5 This is the third flowchart of the service migration method provided in the embodiments of this application;

[0081] Figure 6 This is the fourth flowchart of the service migration method provided in the embodiments of this application;

[0082] Figure 7 This is the fifth flowchart of the service migration method provided in the embodiments of this application;

[0083] Figure 8 This is one of the schematic diagrams of the service migration device provided in the embodiments of this application;

[0084] Figure 9 This is a second schematic diagram of the service migration device provided in the embodiments of this application;

[0085] Figure 10 This is the third schematic diagram of the service migration device provided in the embodiments of this application;

[0086] Figure 11 This is the fourth schematic diagram of the service migration device provided in the embodiments of this application;

[0087] Figure 12 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0088] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0089] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0090] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0091] To facilitate understanding of the embodiments of this application, the following technical points are introduced first:

[0092] Intrinsic service continuity assurance is one of the key capabilities that distinguishes 6G core networks from previous generations, and it is a crucial enabling technology for the successful implementation of the 6G core network cognitive service architecture. Therefore, it has significant research value.

[0093] Current service migrations primarily occur within cloud data centers, and their main technical methods include virtual machine migration and container migration. Their main uses include:

[0094] (1) Hardware maintenance. During hardware updates, virtual machines are migrated to another server in real time to prevent services from going offline (service downtime).

[0095] (2) Load balancing. Some servers may become overloaded due to improper scheduling. Migrating virtual machines to other servers can alleviate this problem.

[0096] (3) Switching providers. Virtual machine migration is a powerful tool to streamline the process if users wish to migrate their services from their on-premises environment to the public cloud or change cloud providers.

[0097] Most mainstream commercial virtualization platforms currently support virtual machine migration, including VMware vSphere, Microsoft Hyper-V, KVM, and Google Compute Engine.

[0098] Commonly used migration techniques for containers are Checkpoint and Restore, which involves saving the process's memory state to a file and restoring the process from the file on the destination host. This process mainly relies on the Checkpoint / Restore In Userspace (CRIU) project, and mainstream container engines such as Docker, Podman, and OpenVZ have begun to support CRIU-based hot container migration.

[0099] The main difference between virtual machine migration and container migration lies in their different virtualization implementations. Virtual machines are implemented using hardware virtualization, with each virtual machine containing a fully virtualized system from virtual hardware and operating system to service applications. Containers, on the other hand, are implemented using operating system virtualization, with containers on the same host sharing the underlying operating system kernel. Therefore, virtual machine migration doesn't require much concern about dependencies; once migrated to a new physical node, virtual machines are essentially ready to use out of the box, requiring no additional maintenance of application dependencies. The main drawback is its lack of agility and the significant data transfer involved. In contrast, container migration is more lightweight, migrating applications at the process level—a fine-grained state migration method. However, container migration requires additional maintenance of environmental dependencies; the destination host must provide the necessary dependency libraries for the migrated containers.

[0100] However, existing migration technologies cannot meet the service migration requirements at the network edge caused by typical terminal mobility (user movement, high-speed rail movement, satellite movement, etc.) in 6G scenarios. The main reasons are as follows:

[0101] First, existing service migration methods primarily occur within a local area network (LAN). LAN migration has the following characteristics:

[0102] 1) Data centers use shared storage systems such as Storage Area Network (SAN) and Network Attached Storage (NAS).

[0103] 2) The source and destination servers are in the same subnet. Therefore, migration within a LAN only requires addressing the challenge of migrating in-memory data. Migration across edge nodes, however, falls under the category of WAN migration. In WAN migration, there is no shared storage system, different data centers have different network configurations, and the network conditions (such as bandwidth and latency) between data centers are much worse than in a LAN.

[0104] Secondly, while existing migration technologies offer good versatility, with no tight coupling between the migration vehicle (virtual machines and containers) and the application, their performance cannot meet the demands of highly interactive applications like Cloud VR. As shown in Table 1, highly interactive VR applications require latency below 8ms, meaning the brief downtime during migration should also be around 8ms. However, current migration technologies generally fail to meet this requirement. Currently, virtual machine migration within cloud data centers typically takes minutes. Although methods like pre-copy and post-copy can reduce downtime to tens to hundreds of milliseconds while keeping the total migration time essentially unchanged, this still falls short of Cloud VR's latency requirements. If migration occurs between edge data centers, considering the lack of shared storage and relatively poor WAN network conditions, the migration process must simultaneously address three challenges: memory data migration, storage data migration, and network connectivity continuity, further degrading performance. Furthermore, the CRIU-based checkpoint mechanism does not support saving graphics card state, making graphics application migration impossible; therefore, Cloud VR application migration is not currently supported.

[0105] Table 1: Network Latency Requirements for the Ideal Stage of Cloud VR

[0106]

[0107] Finally, current migration methods only apply to the data center and do not consider the core network system processes. The downtime that may occur during core network session establishment and other processes is also significant. In cloud VR scenarios, terminals access edge servers through the core network. Each time a service migration is triggered, the Packet Data Unit (PDU) session should be adjusted to redirect user data flow to the new edge server.

[0108] like Figure 1As shown, the terminal offloads the task to the edge server by establishing a PDU session to PDU session anchor point 1 (PSA1). Then, the user moves to gNB2. If the latency between gNB2 and PSA1 cannot meet the requirements, a service migration will be triggered between edge node 1 and edge node 2. During this process, not only does the service instance need to be migrated to edge node 2, but the PDU session anchor point also needs to be switched to PSA2. If the session switching process is not properly planned, the user side will also be in a state of service unreachability. However, the impact of core network session switching on the migration process is currently poorly studied.

[0109] See Figure 2 The figure shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 21 and a network-side device 22. Terminal 21 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 21 is not limited in this application embodiment.

[0110] Network-side equipment 22 may include base station access network equipment or core network elements. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 22 may include base stations, WLAN access points, or WiFi nodes, etc. A base station may be referred to as a node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that this application embodiment only uses a base station in an NR system as an example for description, but does not limit the specific type of base station.

[0111] Core network elements may include, but are not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Core network elements (BSF), application functions (AF), etc. It should be noted that this application embodiment only uses core network elements (such as NEF) in the NR system as an example for introduction, and does not limit the specific type of core network elements.

[0112] Downtime is unavoidable in container-based and virtual machine-based migration methods. This is because the source node must stop the containers or virtual machines to transfer state and files to the destination node to ensure data consistency. While these methods are highly versatile, their inherent limitations inevitably lead to a degradation in service quality.

[0113] It is understandable that applications with service migration requirements mainly have the following characteristics:

[0114] (1) It is latency sensitive and requires extremely low network latency. It must be deployed at the network edge rather than in the cloud data center.

[0115] (2) It is computationally intensive and cannot be run by a mobile terminal alone;

[0116] (3) High interactivity, unable to reduce the impact of changes in the network environment through local caching;

[0117] (4) Streaming computing requires the user terminal to continuously receive the latest service data instead of waiting for the results of batch processing.

[0118] Therefore, traditional web and video services do not have an urgent need for service migration. In comparison, highly interactive applications, represented by Cloud VR, face significant service migration challenges. These applications primarily rely on a three-layer cloud-edge-device collaboration mechanism: the cloud acts as a logic server, storing global state information; the edge is mainly a rendering server, responsible for real-time rendering of the image based on the state information obtained from the cloud and user input, and streaming the image to the terminal; the terminal is mostly a lightweight wearable device, only responsible for audio and video presentation and collecting user interaction information. To address these characteristics, this embodiment no longer relies on state migration from the source node, but instead uses data from the cloud logic server to restore the state at the destination node, thereby achieving state synchronization between the source and destination nodes. This embodiment also introduces a master-slave node mechanism, a session lock conversion mechanism, and a delayed release mechanism to ensure the smooth operation of highly interactive applications.

[0119] 1) Master-slave node mechanism

[0120] When service migration is triggered, the core network first selects a suitable edge node as the destination node. Then, the destination node starts a Cloud VR instance using the same user authentication information. It's important to note that the instance on the destination node can only reproduce the virtual environment. Therefore, during the migration preparation phase, two edge nodes will be rendering the same VR image. The difference is that the source node can receive control signals from the UE, but the destination node can only display the same image. Since there is an identical rendering instance on both the source and destination nodes, the node with control permissions can be called the master node, and the other the slave node. After the destination node starts the slave process and successfully synchronizes, the core network establishes a PDU session between the UE and the destination node. The UE then begins receiving Real-Time Streaming Protocol (RTSP) streams of the image from the destination node. It's important to note that to prevent display conflicts, the image from the slave node (or described as a slave device) is only received and not displayed. The key advantage of the master-slave node mechanism is that it replaces the migration process of virtual machines and containers with synchronous state replication, preventing the increase in data volume caused by frequent memory write operations.

[0121] 2) Session lock conversion mechanism

[0122] In most cases, to ensure data consistency, Cloud VR applications do not allow the same user to access the platform repeatedly. However, the master-slave mechanism does not conform to this property, and master-slave node switching also leads to master-slave session switching. During this process, session switching and control flow may become chaotic. To solve this problem, a lock translation mechanism is introduced.

[0123] During the migration process, both the master and slave nodes can read state information from the cloud server. However, the UE only sends control signals to the master node, and only the master node holds the session lock and can write data to the cloud server. When the slave node is fully prepared and transmitting state stably, the UE sends a "join" command to the slave node to trigger the transfer of the session lock. Upon receiving the command, the destination node becomes the master node (or described as the master device), while the previous source node becomes a slave node.

[0124] By combining master-slave node mechanisms and lock transition mechanisms, the originally sequential service migration process is replaced with asynchronous state synchronization and control session lock transitions. All switching operations are triggered only after the state has reached synchronization, thus avoiding additional time caused by data transmission during downtime.

[0125] 3) Delayed release mechanism

[0126] The ping-pong effect poses a significant challenge when it comes to handover issues. In service migration scenarios, the ping-pong effect refers to the repeated service migrations triggered when a user (UE) is at the boundary between the source and destination nodes due to UE movement or network instability. Because of the ping-pong effect, migrations based on virtual machines or containers can repeatedly fall into downtime migrations, rendering the service unavailable and consuming significant computing and network resources. To address the ping-pong effect, a delayed release mechanism is introduced. After the source node becomes a slave node, it maintains its slave node state and continues running for a period of time. If the user returns to the coverage area of ​​the previous node, the system only needs to switch the roles of the two edge nodes. This keeps the handover cost very low. When the migration ends after a certain period or the user moves away from the edge coverage boundary, the slave node is released.

[0127] 4) Overall Workflow

[0128] The implementation of the master-slave mechanism, lock conversion, and delayed release is handled by Network Open Functions (NEF). The entire service migration process follows a network-centric scheduling approach, with NEF handling joint scheduling of the network and computing domains. This includes not only network-side UPF selection and session establishment but also resource awareness and task scheduling for edge nodes. To support NEF's control over edge nodes, each edge node runs a service registration agent. Applications requiring service migration support need to register their services with this agent, providing registration information such as the application's name and instance deployment location.

[0129] See Figure 3 This application provides a service migration method, the execution subject of which can be a core network element, such as NEF, and the specific steps include:

[0130] Step 301: Obtain first information, which is used by the core network element to select the destination node from the candidate edge nodes;

[0131] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server (e.g., a cloud game server). Both the source node and the destination node provide the service of the first application to the terminal.

[0132] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0133] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0134] It is understandable that edge nodes complete their registration with core network elements through first information (equivalent to registration information), enabling core network elements to obtain relevant information about the edge node, such as the location of the edge node and whether the edge node can provide the first application service to the terminal.

[0135] Optionally, the first application is a highly interactive application, such as Cloud VR applications, digital twins, or applications in metaverse scenarios.

[0136] Optionally, both the source node and the destination node are computing power nodes (or can be described as computing nodes).

[0137] In one embodiment of this application, the first information carries one or more of the following: location information of the edge node, and information of the first application supporting service migration.

[0138] In one embodiment of this application, obtaining the first information includes:

[0139] The first information is obtained through the service registration agent of the edge node.

[0140] In one embodiment of this application, the method further includes:

[0141] Receive a first request from the source node, the first request being used to request the migration of the services of the first application from the source node to the destination node.

[0142] In one embodiment of this application, the first request carries one or more of the following: information about the first application, quality of service (QoS) requirements, user token, and terminal location information.

[0143] In one embodiment of this application, the method further includes:

[0144] Based on the first information, select the target node from the candidate edge nodes;

[0145] Send a second message to the destination node, the second message being used to instruct the destination node to launch the first application; and / or, the second message being used to instruct the establishment of a new channel (e.g., a PDU session) between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal.

[0146] For example, after the source node submits a migration request to NEF, NEF selects a suitable edge node as the target node from the already registered information, controls the selected target node to start relevant service instances through the service registration agent of the edge, and uses the session establishment process to establish a PDU session between the UE and the target node.

[0147] In one embodiment of this application, after the destination node starts the first application or after the new channel is established, the method further includes:

[0148] Send a third message (equivalent to a migration notification) to the source node, the third message being used to instruct the source node to notify the terminal to migrate the services of the first application from the source node to the destination node.

[0149] In this embodiment, service continuity during migration is ensured through the overall scheduling of network and computing resources by core network elements. Unlike previous methods based on virtual machine or container migration, where compute state migration and network switching are performed independently, this embodiment fully utilizes data from the cloud server to restore the process at the destination node and keep it synchronized with the source node, avoiding memory copying and reducing downtime during service migration. This embodiment can significantly reduce the downtime of the first application, maintaining it between 8ms and 14ms, and even reducing the amount of data transmitted from the source node to the destination node to zero.

[0150] See Figure 4 This application provides a service migration method, in which the execution subject can be a first node, which is an edge node (i.e., the first node is the destination node among the edge nodes). Specific steps include:

[0151] Step 401: Send first information, which is used by the core network element to select the destination node from the candidate edge nodes;

[0152] The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0153] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0154] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0155] In one embodiment of this application, the first information carries one or more of the following: location information of the edge node, and information of the first application supporting service migration.

[0156] In one embodiment of this application, the method further includes:

[0157] The second information is received from the core network element, which instructs the destination node to start the first application; and / or, the second information instructs the establishment of a new channel between the terminal and the destination node, which is used by the destination node to provide the data stream of the first application to the terminal.

[0158] In one embodiment of this application, the method further includes:

[0159] The terminal receives a fourth message (equivalent to a notification to change the master / slave node), which instructs the destination node to act as the master node and provide the services of the first application to the terminal.

[0160] In this embodiment, service continuity during migration is ensured through the overall scheduling of network and computing resources by core network elements. Unlike previous methods based on virtual machine or container migration, where compute state migration and network switching are performed independently, this embodiment fully utilizes data from the cloud server to restore the process at the destination node and keep it synchronized with the source node, avoiding memory copying and reducing downtime during service migration. This embodiment can significantly reduce the downtime of the first application, maintaining it between 8ms and 14ms, and even reducing the amount of data transmitted from the source node to the destination node to zero.

[0161] See Figure 5 This application provides a service migration method, in which the execution subject can be a second node, which is a source node (i.e., the second node is a source node among edge nodes). Specific steps include:

[0162] Step 501: Send a first request to the core network element, the first request being used to request the migration of the service of the first application from the source node to the destination node;

[0163] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0164] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0165] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0166] In one embodiment of this application, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0167] In one embodiment of this application, the method further includes:

[0168] The third information is received from the core network element, and the third information is used to instruct the source node to notify the terminal to migrate the service of the first application.

[0169] In one embodiment of this application, the method further includes:

[0170] Send a fifth message (equivalent to a notification to prepare for migration) to the terminal, the fifth message being used to instruct the terminal to switch the service of the first application from the source node to the destination node.

[0171] In one embodiment of this application, the method further includes:

[0172] The terminal receives a sixth message (equivalent to a notification to delay the release of the PDU session), which instructs the source node to release the channel with the terminal.

[0173] In this embodiment, service continuity during migration is ensured through the overall scheduling of network and computing resources by core network elements. Unlike previous methods based on virtual machine or container migration, where compute state migration and network switching are performed independently, this embodiment fully utilizes data from the cloud server to restore the process at the destination node and keep it synchronized with the source node, avoiding memory copying and reducing downtime during service migration. This embodiment can significantly reduce the downtime of the first application, maintaining it between 8ms and 14ms, and even reducing the amount of data transmitted from the source node to the destination node to zero.

[0174] See Figure 6 This application provides a service migration method, the execution subject of which can be a terminal, and the specific steps include:

[0175] Step 601: Receive fifth information from the source node, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node;

[0176] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0177] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0178] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0179] In one embodiment of this application, the method further includes:

[0180] A fourth message is sent to the destination node, the fourth message being used to instruct the destination node to provide the service of the first application to the terminal as a master node.

[0181] In one embodiment of this application, the method further includes:

[0182] The data stream of the first application provided by the destination node is obtained through a new channel established between the terminal and the destination node.

[0183] This application embodiment ensures service continuity during migration by using core network elements to comprehensively schedule network and computing resources. Unlike previous methods based on virtual machine or container migration, where compute state migration and network switching are performed independently, this application embodiment fully utilizes data from the cloud logic server to restore processes and maintain synchronization at the destination node, avoiding memory copying and reducing downtime during service migration. This application embodiment can significantly reduce the downtime of the first application, maintaining it between 8ms and 14ms, and even reducing the amount of data transmitted from the source node to the destination node to zero.

[0184] See Figure 7 The specific steps are as follows:

[0185] Step 1: The source node sends a service migration request to NEF (equivalent to the first request);

[0186] Optionally, the service migration request may include one or more of the following: app type, QoS requirements, user token, and user location information.

[0187] Since the highly interactive service screen of Cloud VR is generated in real time by the edge, the latency has a direct impact on the screen refresh quality and user interaction. When the UE finds that the latency is lower than acceptable, in order to ensure that the user can have a smooth user experience, the UE will report to the source node to perform service migration, and the source node will send a service migration request to NEF.

[0188] Step 2a: NEF notifies the destination node to start Cloud VR (equivalent to the second message);

[0189] Optionally, NEF selects an edge node as the destination node for the service migration request, and notifies the destination node to start the corresponding Cloud VR based on the received app type and user token.

[0190] For example, NEF selects edge nodes as destination nodes based on user location information.

[0191] Step 2b: Establish a new PDU session.

[0192] Optionally, NEF establishes a new PDU session between the UE and the destination node through control plane functions, and the rendering results on the destination node can be sent to the UE.

[0193] Step 3: The destination node logs into the cloud server using user authentication.

[0194] Optionally, the destination node logs into the cloud server using a user authentication method via a user token.

[0195] When the rendering instance starts running on the destination node in step 2b, the destination node needs to log in to the cloud server and enter slave mode, that is, the destination node becomes a slave node. At this time, the destination node can only reproduce the virtual environment screen (the same as the source node).

[0196] Step 4: If user authentication is successful, the cloud server returns a login success message to the destination node.

[0197] Step 5: NEF sends a migration-ready notification (equivalent to third-party information) to the source node.

[0198] Optionally, once the PDU session and Cloud VR instance on the destination node are ready, NEF will send a "confirmed" signal to the source node, which will then notify the UE that it is ready to migrate. Simultaneously, information such as the destination node's IP address will be sent to the source node to prepare for the subsequent migration.

[0199] Step 6: The source node sends a migration preparation notification to the UE (equivalent to the fifth message).

[0200] Optionally, the source node sends migration preparation information to the UE, which may include the destination node's IP address.

[0201] Step 7: The destination node transmits the Cloud VR video stream to the UE.

[0202] Optionally, the UE starts acquiring the video stream from the destination node, but the reception is not displayed on the screen, and the control signals from Cloud VR are still sent to the source node.

[0203] Step 8: The UE notifies the destination node to change the master / slave node (equivalent to the fourth piece of information).

[0204] Optionally, when the destination node is fully prepared and transmitting data stably, the UE sends a "join" signal to the destination node's slave node to trigger the lock transition mechanism and transfers the session lock to the destination node, thereby switching control permissions. Upon receiving the command, the destination node becomes the master node, while the previous source node becomes a slave node. The UE then begins sending CloudVR control signals to the destination node, allowing the destination node to write data to the cloud server.

[0205] Step 9: The UE notifies the source node to delay the release of the PDU session (equivalent to the sixth message).

[0206] To prevent the ping-pong effect from repeatedly triggering service migration, after the source node becomes a slave node, it will continue to maintain the slave node state and run for a period of time, and will be released after the time threshold is reached or the UE moves away from the source node.

[0207] See Figure 8 This application provides a service migration apparatus applied to core network elements, such as NEF, etc. The apparatus 800 includes:

[0208] The first acquisition module 801 is used to acquire first information, which is used by the core network element to select a destination node from candidate edge nodes.

[0209] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0210] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0211] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0212] In one embodiment of this application, the first information carries one or more of the following: location information of the edge node, and information of the first application supporting service migration.

[0213] In one embodiment of this application, the first acquisition module 801 is further configured to: acquire the first information through the service registration agent of the edge node.

[0214] In one embodiment of this application, the apparatus further includes:

[0215] The first receiving module is used to receive a first request, which requests the migration of the services of the first application from the source node to the destination node.

[0216] In one embodiment of this application, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0217] In one embodiment of this application, the apparatus further includes:

[0218] The first selection module is used to select the target node from the candidate edge nodes based on the first information;

[0219] A first processing module is configured to send second information to the destination node, the second information being used to instruct the destination node to launch the first application; and / or, the second information being used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal.

[0220] In one embodiment of this application, after the first application is launched at the destination node, and / or after the new channel is established, the apparatus further includes:

[0221] The first sending module is used to send third information to the source node, the third information being used to instruct the source node to notify the terminal to migrate the service of the first application from the source node to the destination node.

[0222] The apparatus provided in this application embodiment can achieve... Figure 3 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0223] See Figure 9 This application provides a service migration device applied to a first node, which is an edge node. The device 900 includes:

[0224] The second sending module 901 is used to send first information, which is used by the core network element to select the destination node from the candidate edge nodes.

[0225] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0226] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0227] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0228] In one embodiment of this application, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0229] In one embodiment of this application, the apparatus further includes:

[0230] The second receiving module is configured to receive second information from a core network element, the second information being used to instruct the destination node to launch the first application; and / or, the second information being used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal.

[0231] In one embodiment of this application, the apparatus further includes:

[0232] The third receiving module is used to receive fourth information from the terminal, the fourth information being used to instruct the destination node to provide the service of the first application to the terminal as a master node.

[0233] The apparatus provided in this application embodiment can achieve... Figure 4 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0234] See Figure 10 This application provides a service migration apparatus applied to a second node, which is the source node. The apparatus 1000 includes:

[0235] The fourth sending module 1001 is used to send a first request, the first request being used to request the migration of the service of the first application from the source node to the destination node;

[0236] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0237] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0238] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0239] In one embodiment of this application, the first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

[0240] In one embodiment of this application, the apparatus further includes:

[0241] The fourth receiving module is used to receive third information from the core network element, the third information being used to instruct the source node to notify the terminal to migrate the service of the first application.

[0242] In one embodiment of this application, the apparatus further includes:

[0243] The fifth sending module is used to send fifth information to the terminal, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node.

[0244] In one embodiment of this application, the apparatus further includes:

[0245] The fifth receiving module is used to receive sixth information from the terminal, the sixth information being used to instruct the source node to release the channel between itself and the terminal.

[0246] The apparatus provided in this application embodiment can achieve... Figure 5 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0247] See Figure 11 This application provides a service migration device applied to a terminal. The device 1100 includes:

[0248] The sixth receiving module 1101 is used to receive fifth information from the source node, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node;

[0249] The destination node is used to start the first application during the service migration process, and as a subordinate node, it and the source node, as the master node, obtain the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal.

[0250] The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal.

[0251] The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

[0252] In one embodiment of this application, the apparatus further includes:

[0253] The sixth sending module is used to send fourth information to the destination node, the fourth information being used to instruct the destination node to provide the service of the first application to the terminal as a master node.

[0254] In one embodiment of this application, the apparatus further includes:

[0255] The seventh receiving module is used to obtain the data stream of the first application provided by the destination node through a new channel established between the terminal and the destination node.

[0256] The apparatus provided in this application embodiment can achieve... Figure 6 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0257] like Figure 12 As shown, this application embodiment also provides a communication device 1200, including a processor 1201, a memory 1202, and a program or instructions stored in the memory 1202 and executable on the processor 1201. When the program or instructions are executed by the processor 1201, they implement the above-mentioned... Figure 3 or Figure 4 or Figure 5 or Figure 6 The various processes in the method embodiments can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0258] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 3 or Figure 4 or Figure 5 or Figure 6 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0259] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0260] The steps of the methods or algorithms described in this application can be implemented in hardware or by executing software instructions on a processor. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, portable hard disk, read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can be housed in an ASIC. Alternatively, the ASIC can be housed in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0261] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0262] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

[0263] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0264] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0265] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0266] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0267] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A service migration method, applied to core network elements, characterized in that, include: Obtain first information, which is used by the core network element to select a destination node from candidate edge nodes; Based on the first information, select the target node from the candidate edge nodes; Send a second message to the destination node, the second message being used to instruct the destination node to start the first application; Furthermore, the second information is used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal; After the first application is started at the destination node, and / or after the new channel is established, a third message is sent to the source node. The third message is used to instruct the source node to notify the terminal to migrate the service of the first application from the source node to the destination node. The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

2. The method according to claim 1, characterized in that, The first information carries one or more of the following: the location information of the edge node, and information of the first application that supports service migration.

3. The method according to claim 1, characterized in that, The acquisition of the first information includes: The first information is obtained through the service registration agent of the edge node.

4. The method according to claim 1, characterized in that, The method further includes: A first request is received, which is used to request the migration of the service of the first application from the source node to the destination node.

5. The method according to claim 4, characterized in that, The first request carries one or more of the following: information about the first application, QoS requirements, user token, and terminal location information.

6. A service migration method applied to a first node, wherein the first node is an edge node, characterized in that, include: Send first information, which is used by the core network element to select the destination node from the candidate edge nodes; Receive second information from the core network element, the second information being used to instruct the destination node to start the first application; Furthermore, the second information is used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal; The terminal receives fourth information, which instructs the destination node to act as the master node and provide the service of the first application to the terminal. The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

7. The method according to claim 6, characterized in that, The first information carries one or more of the following: the location information of the edge node, and information of the first application that supports service migration.

8. A service migration method applied to a second node, wherein the second node is the source node, characterized in that, include: Send a first request, the first request being used to request that the services of the first application be migrated from the source node to the destination node; The third information is received from the core network element, and the third information is used to instruct the source node to notify the terminal to migrate the service of the first application. A fifth message is sent to the terminal, the fifth message being used to instruct the terminal to migrate the service of the first application from the source node to the destination node; The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

9. The method according to claim 8, characterized in that, The first request carries one or more of the following: information about the first application, quality of service (QoS) requirements, user token, and location information of the terminal.

10. The method according to claim 8, characterized in that, The method further includes: The terminal receives a sixth message, which instructs the source node to release the channel with the terminal.

11. A service migration method applied to a terminal, characterized in that, include: The terminal receives fifth information from the source node, the fifth information being used to instruct the terminal to migrate the services of the first application from the source node to the destination node; Send a fourth message to the destination node, the fourth message being used to instruct the destination node to provide the service of the first application to the terminal as a master node; The data stream of the first application provided by the destination node is obtained through the new channel established between the terminal and the destination node; The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

12. A service migration device, applied to a core network element, characterized in that, include: The first acquisition module is used to acquire first information, which is used by the core network element to select a destination node from candidate edge nodes. The first selection module is used to select the target node from the candidate edge nodes based on the first information; A first processing module is configured to send second information to the destination node, the second information being used to instruct the destination node to launch a first application; Furthermore, the second information is used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal; The first sending module is configured to send third information to the source node after the first application is started at the destination node, and / or after the new channel is established. The third information is used to instruct the source node to notify the terminal to migrate the service of the first application from the source node to the destination node. The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

13. A service migration device applied to a first node, wherein the first node is an edge node, characterized in that, include: The second sending module is used to send first information, which is used by the core network element to select the destination node from the candidate edge nodes. The second receiving module is used to receive second information from the core network element, the second information being used to instruct the destination node to start the first application; Furthermore, the second information is used to instruct the establishment of a new channel between the terminal and the destination node, the new channel being used by the destination node to provide the data stream of the first application to the terminal; The third receiving module is used to receive fourth information from the terminal, the fourth information being used to instruct the destination node to provide the service of the first application to the terminal as a master node; The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

14. A service migration apparatus, applied to a second node, the second node being a source node, characterized in that, include: The fourth sending module is used to send a first request, which requests that the service of the first application be migrated from the source node to the destination node; The fourth receiving module is used to receive third information from core network elements, the third information being used to instruct the source node to notify the terminal to migrate the service of the first application; The fifth sending module is used to send fifth information to the terminal, the fifth information being used to instruct the terminal to migrate the service of the first application from the source node to the destination node; The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

15. A service migration device applied to a terminal, characterized in that, include: The sixth receiving module is used to receive fifth information from the source node, the fifth information being used to instruct the terminal to switch the service of the first application from the source node to the destination node; The sixth sending module is used to send fourth information to the destination node, the fourth information being used to instruct the destination node to provide the service of the first application to the terminal as a master node; The seventh receiving module is used to obtain the data stream of the first application provided by the destination node through a new channel established between the terminal and the destination node; The destination node is used to start the first application during the service migration process, and as a subordinate node, together with the source node as the master node, obtains the status information of the first application from the cloud server. Both the source node and the destination node provide the service of the first application to the terminal. The destination node is also used to obtain control permissions after receiving instructions from the terminal and act as a master node to provide the services of the first application to the terminal. The master node is able to receive control signals from the terminal for the first application, while the slave node does not receive control signals from the terminal for the first application.

16. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in any one of claims 1 to 11.

17. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 11.

Images