A determination method, device, electronic device and storage medium

Abstract

The present invention discloses a determination method, device, electronic device and storage medium. The determination method is applied to an MEC system and includes: obtaining a handover message; determining an MEC application accessed by a terminal device based on the handover message; and determining a destination edge cloud gateway address based on the handover message and application attributes of the MEC application. Through the handover message obtained by the MEC system in the above technical solution, and by combining the application attributes of the MEC application to determine the destination edge cloud gateway address, when the terminal accesses the MEC application in the MEC system and a handover occurs, the target edge cloud gateway address can be determined, so that the terminal can access the switched MEC host through the determined destination edge cloud gateway address, ensuring the service continuity and service quality of the terminal and improving the user experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technologies, and in particular, to a determination method, apparatus, electronic device, and storage medium. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) defines three major scenarios for the application of 5th Generation Mobile Communication Technology (5G): enhanced mobile broadband, ultra-reliable low-latency communication, and massive machine-type communication. Among them, the enhanced mobile broadband scenario provides large-capacity mobile broadband services, such as high-speed downloads, high-definition videos, etc., which places a huge pressure on the wireless backhaul network. It is necessary to sink services to the network edge as much as possible to achieve local traffic splitting of services; scenarios such as ultra-reliable low-latency communication, such as driverless and industrial control, also require sinking services to the network edge to reduce the network latency brought by network transmission.

[0003] Facing the characteristic that 5G applications need to be sunk to the network edge, Multi-Access Edge Computing (MEC) emerges as the times require and has been incorporated into the 3GPP 5G standard as a key technology. The 5G core network separates the control plane (CP) from the user plane (UP). The user plane function (UPF) can be flexibly sunk and deployed to the network edge, while control plane functions such as the policy control function (PCF) and the session management function (SMF) can be centrally deployed. And MEC enables operators and third-party services to be hosted near the access point of the user equipment (UE), thereby achieving efficient service delivery by reducing the end-to-end delay and the load on the transmission network. The 5G core network selects a UPF close to the UE and performs traffic control from the UPF to the local data network through the N6 interface.

[0004] In the architecture of the existing technology for docking the MEC system in the 5G network, the user equipment accesses the MEC application service in the MEC system via the 5G access network. Due to the lack of a corresponding handover mechanism, when the UE makes a handover and the currently accessed MEC host can no longer provide edge services for it, the service of the UE cannot be guaranteed. Summary of the Invention

[0005] The present invention provides a determination method, apparatus, electronic device, and storage medium to ensure the service continuity and quality of service of a UE when the UE accesses a MEC application in a MEC system and undergoes a handover.

[0006] In a first aspect, an embodiment of the present invention provides a determination method applied to a MEC system, including:

[0007] Obtain a handover message;

[0008] Based on the handover message, determine the MEC application accessed by the terminal device;

[0009] Based on the handover message and the application attributes of the MEC application, determine the destination edge cloud gateway address.

[0010] In a second aspect, an embodiment of the present invention provides a determination method applied to a core network, including:

[0011] Receive a first handover request;

[0012] In response to the first handover request, send a handover message, where the handover message is used to determine the destination edge cloud gateway address.

[0013] In a third aspect, an embodiment of the present invention provides a determination apparatus, including:

[0014] An obtaining module, configured to obtain a handover message;

[0015] A first module, configured to determine the MEC application accessed by the terminal device based on the handover message;

[0016] A second module, configured to determine the destination edge cloud gateway address based on the handover message and the application attributes of the MEC application.

[0017] In a fourth aspect, an embodiment of the present invention provides a determination apparatus, including:

[0018] A receiving module, configured to receive a first handover request;

[0019] A sending module, configured to send a handover message in response to the first handover request, where the handover message is used to determine the destination edge cloud gateway address.

[0020] In a fifth aspect, an embodiment of the present invention provides an electronic device, including:

[0021] At least one processor; and

[0022] A memory communicatively connected to the at least one processor; wherein,

[0023] The memory stores a computer program executable by the at least one processor, and when the computer program is executed by the at least one processor, the at least one processor is enabled to execute the methods described in the first aspect and the second aspect.

[0024] In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer instructions for causing a processor to implement the methods described in the first aspect and the second aspect when executed.

[0025] In the technical solution of the embodiment of the present invention, a handover message obtained by an MEC system is combined with the application attributes of an MEC application to determine the destination edge cloud gateway address, so that when a terminal accesses an MEC application in the MEC system and a handover occurs, the target edge cloud gateway address can be determined, and then the handover can be performed through the determined destination edge cloud gateway address. The MEC host is accessed to ensure the service continuity and quality of service of the terminal and improve the user experience.

[0026] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0028] Figure 1 It is a schematic diagram of the basic architecture of a 5G network and an MEC system in the prior art;

[0029] Figure 2 It is a schematic diagram of the interaction architecture of a 5G network and an MEC system provided by an embodiment of the present invention;

[0030] Figure 3 It is a flowchart of a determination method provided by Embodiment 1 of the present invention;

[0031] Figure 4 It is a flowchart of a determination method provided by Embodiment 2 of the present invention;

[0032] Figure 5 It is a flowchart of edge cloud gateway handover based on the N2 interface in a 5G network provided by Embodiment 2 of the present invention;

[0033] Figure 6It is a flowchart of edge cloud gateway handover based on the Xn interface under a 5G network provided by Embodiment 2 of the present invention;

[0034] Figure 7 It is a schematic structural diagram of a determination device provided by Embodiment 3 of the present invention;

[0035] Figure 8 It is a schematic structural diagram of a determination device provided by Embodiment 4 of the present invention;

[0036] Figure 9 It is a schematic structural diagram of an electronic device for implementing the determination method of the embodiments of the present invention. Detailed implementation manners

[0037] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0038] It should be noted that the terms "first", "second", etc. in the present invention are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0039] It can be understood that before using the technical solutions disclosed in the embodiments of the present invention, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the users and the users' authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0040] The following is a unified description of the English terms involved in the embodiments of the present invention:

[0041] Network Slice Selection Function (NSSF);

[0042] Network Function Repository Function (NRF);

[0043] Unified Data Management (UDM);

[0044] Unified Data Repository (UDR);

[0045] Policy Control Function (PCF);

[0046] Network Exposure Function (NEF);

[0047] Authentication Server Function (AUSF);

[0048] Access and Mobility Management Function (AMF);

[0049] Session Management Function (SMF);

[0050] Session Management (SM);

[0051] User Plane Function (UPF);

[0052] Application Function (AF);

[0053] Control Plane (CP);

[0054] Data Network (DN);

[0055] Access Network (AN);

[0056] Next Generation - Radio Access Network (NG - RAN);

[0057] Source - Next Generation - Radio Access Network (S - NG - RAN);

[0058] Objective: Target-Next Generation-Radio Access Network (T-NG-RAN);

[0059] Centralized Unit (CU);

[0060] Distributed Unit (DU);

[0061] Active Antenna Unit (AAU);

[0062] Local Area Data Network (LADN);

[0063] Application (APP);

[0064] Network Functions (NFs);

[0065] User plane (UP);

[0066] User Equipment (UE);

[0067] Multi-Access Edge Computing (MEC);

[0068] 3rd Generation Partnership Project (3GPP);

[0069] 5th Generation Mobile Communication Technology (5G);

[0070] MEC Orchestrator (MEO);

[0071] MEC Platform Manager (MEPM);

[0072] MEC Platform (MEP);

[0073] Local Area / Data Network (LA / DN);

[0074] Protocol Data Unit (PDU);

[0075] Quality of Service (QoS).

[0076] Exemplarily, Figure 1 is a schematic diagram of the basic architecture of a 5G network and an MEC system in the prior art. As Figure 1 shown, the MEC system may include an MEC system level (System Level), an MEC distribution host level (Distribution Host Level), and a network level. The MEC system level is mainly responsible for managing the resources of the entire MEC system and receiving service requests from terminals and third parties; the MEC distribution host level is responsible for managing the resources of the MEC host and the configuration management of the MEC platform and applications; the network level ensures the connectivity between the MEC host and the external network. The system level may include MEO; the MEC distribution host level may include MEPM, MEP, Service, LA / DN, and UPF. LA / DN includes Virtualization Infrastructure and multiple application programs APP. NSSF, NRF, UDM, PCF, NEF, AUSF, AMF, and SMF are connected to the MEC system level through the Naf interface. AMF, UE, and AN are connected pairwise. AN is connected to UPF. SMF and UPF are connected through the N4 interface. UPF has an N9 interface.

[0077] The 5G core network can separate the control plane from the user plane. The user plane network elements can be deployed at the network edge, while the control plane functions can be deployed centrally. The 5G core network selects a user plane close to the UE and performs traffic control from UPF to LA / DN through the N6 interface. This can be based on the UE's subscribed data, UE location, information from the application function, policies, or other relevant traffic rules. In such application scenarios, the MEC system acts as the role of AF+DN (Data Network) relative to the 5G core network. The MEC orchestrator is a functional entity at the MEC system level. It acts as an AF and can interact with the NEF or, in some cases, directly with the target 5G NFs. For example, it can affect the user plane policy as a non-trusted AF through NEF->PCF->SMF or as a trusted AF through direct access to PCF->SMF.

[0078] The MEC sinks the hosting of applications near the access point of the UE, closer to the data generated by the applications, and provides the ability to compute at the network edge near the UE, thereby achieving efficient service delivery by reducing the end-to-end latency and the load on the transmission network.

[0079] However, in the prior art in the architecture of the 5G network docking with the MEC system, the UE accesses the MEC application service in the MEC system via the 5G access network. Due to the lack of a corresponding handover mechanism, when the UE makes a handover and the currently accessed MEC host can no longer provide edge services for it, the service of the UE cannot be guaranteed.

[0080] Based on this, the embodiments of the present invention propose a determination method, device, electronic device and storage medium to ensure the service continuity and quality of service of the UE when the UE accesses the MEC application in the MEC system and makes a handover.

[0081] Figure 2 It is a schematic diagram of the interaction architecture between the 5G network and the MEC system provided by the embodiments of the present invention. The determination method provided by the embodiments of the present invention can be implemented on the interaction architecture between the 5G network and the MEC system as shown in Figure 2 shown.

[0082] As Figure 2 shown, the 5G core network may include network elements such as UDR, SMF, AMF, PCF, and NEF. The 5G core network can be connected to the UPF through the N4 interface, to the 5G CU through the N2 interface, and to the MEC system level through the Naf interface. The MEC system level may include an MEC orchestrator. The MEC system level is connected to multiple MEC distribution host levels. The number of MEC distribution host levels is not limited in the present invention. Figure 2 Only 2 MEC distribution host levels are shown in the figure. The 2 MEC distribution host levels are connected in series and are respectively connected to the UPF through the N6 interface. Inside each MEC distribution host level, an edge cloud gateway and an MEC host can be included. The UPF can be connected to the edge cloud gateway through the N6 interface, and the edge cloud gateway can be connected to the MEC host. Among them, the MEC host may include LADN and an MEC platform. The edge cloud gateway is connected to the LADN, and the LADN includes virtualized infrastructure and multiple APPs. The number of APPs is not limited in the present invention. Figure 2 Only the case where 3 APPs are included in the LADN is shown in the figure. The UPF, 5G CU, 5G DU are sequentially connected to the ground AAU, and the AAU is communicatively connected to the UE.

[0083] In the case as shown in Figure 2In the schematic diagram of the interaction architecture between the 5G network and the MEC system shown, the N2 interface can be the interface connecting the 5G core network and the 5G CU; the N4 interface can be the interface connecting the 5G core network and the UPF; the Naf interface can be the interface connecting the 5G core network and the MEC system level; the N6 interface can be the interface connecting the UPF and the edge cloud gateway. The terminal UE can communicate with the AAU. The AAU is connected to the 5G DU, 5G CU, and UPF in sequence. The UPF can be connected to the edge cloud gateway through the N6 interface. The edge cloud gateway can be connected to the MEC host, so as to access the MEC host through the edge cloud gateway and then access the MEC applications (i.e., multiple APPs included in the LADN).

[0084] In practical applications, the European Telecommunications Standards Institute (ETSI) GS MEC specification defines the MEC reference architecture. The ETSI MEC system consists of the MEC host and the MEC management function. The MEC host includes the MEC platform, virtualization infrastructure, and various MEC applications and services running on it. The MEC management function includes the MEC system level management function and the host level management function. The MEC system level management function includes the user application lifecycle management agent, the operation support system, and the MEC orchestrator. The MEC host level management function includes the MEC platform manager and the virtualization infrastructure manager. MEC enables operators and third-party services to be hosted near the access point of the UE, thus achieving efficient service delivery by reducing the end-to-end latency and the load on the transmission network.

[0085] Embodiment 1

[0086] Figure 3 It is a flowchart of a determination method provided according to Embodiment 1 of the present invention. This embodiment is applicable to the situation where the MEC system controls the switching of MEC applications. This method can be executed by a determination device, which can be implemented in the form of software and / or hardware and integrated in an electronic device. Further, the electronic device includes but is not limited to: computers, laptops, smartphones, servers, etc. As Figure 3 shown, the method includes:

[0087] S110. Obtain a handover message.

[0088] The handover message may be a message indicating a handover of the edge cloud gateway. For example, when a terminal (i.e., UE) accesses the MEC application service in the MEC system via the 5G access network, it is a message indicating a handover from the source edge cloud gateway to the destination edge cloud gateway. There is a corresponding relationship between the edge cloud gateway and the MEC host. After the handover of the edge cloud gateway, the MEC host corresponding to the edge cloud gateway can be accessed. Among them, the terminal may refer to an input / output device, and the type of the terminal is not limited in the present invention. For example, it may be a notebook, a tablet computer, a laptop computer, a personal digital assistant, and other suitable computers; in addition, it may also be various forms of mobile terminals, such as personal digital processing, smart phones, wearable devices, and other similar devices.

[0089] The handover message is not limited. The handover message may include, but is not limited to, one or more of the source UPF address, the destination UPF address, and the terminal address. Through the handover message, the terminal that needs to perform the handover, the source UPF before the handover does not occur, and the destination UPF to which the handover will be performed can be determined.

[0090] Optionally, the handover message includes the source UPF address, the destination UPF address, and the terminal address.

[0091] Among them, the source UPF address may refer to the address of the UPF indirectly connected to the MEC host before the handover does not occur. The destination UPF address may refer to the address of the UPF indirectly connected to the MEC host to which the handover will be performed. The terminal address may refer to the address code of the terminal device. The source UPF may be connected to the edge cloud gateway corresponding to the MEC host before the handover does not occur through the N6 interface. The edge cloud gateway may be connected to the MEC host before the handover does not occur. Therefore, the source UPF may be indirectly connected to the MEC host before the handover does not occur; similarly, the destination UPF may be indirectly connected to the MEC host to which the handover will be performed.

[0092] The source UPF address, the destination UPF address, and the terminal address are not limited, as long as the source UPF, the destination UPF, and the terminal can be determined through the source UPF address, the destination UPF address, and the terminal address respectively. For example, by assigning a unique identifier to each UPF or terminal, when needed, the UPF corresponding to the unique identifier can be used to determine whether the UPF is the source UPF, the destination UPF, or other UPFs, and the terminal corresponding to the unique identifier can be used to determine the terminal that needs to perform the handover. The identifier is not limited, as long as different UPFs can be distinguished. For example, it may be different numbers; in addition, the source UPF address, the destination UPF address, and the terminal address may be Internet Protocol (IP) addresses. By assigning different IP addresses to each UPF and terminal, when needed, the UPF or terminal corresponding to the IP address can be queried through the IP address, and then the source UPF address, the destination UPF address, and the terminal address can be determined.

[0093] The source UPF, destination UPF, and terminal can be determined through the source UPF address, destination UPF address, and terminal address, enabling the MEC system to perform corresponding operations and thus complete the handover.

[0094] There is no limitation on the way to obtain the handover message, as long as the handover message can be obtained. For example, the terminal can initiate a handover request to the 5G core network via the source NG-RAN, and the SMF in the 5G core network sends the source UPF address, destination UPF address, and terminal address to the MEC system, enabling the MEC system to obtain the handover message. Another example is that the MEC system statistically analyzes the traffic of the MEC application accessed by the terminal device. When the value of the statistically analyzed traffic is less than the traffic threshold, the MEC system determines that a handover is required. The MEC system obtains the source UPF address, destination UPF address, and terminal address through the 5G core network, thereby obtaining the handover message. Herein, the traffic threshold can be a threshold set according to actual needs.

[0095] In one embodiment, when the terminal needs to perform a handover, the terminal initiates a handover request (such as a first handover request) to the 5G core network via the source NG-RAN. The SMF in the 5G core network sends the source UPF address, destination UPF address, and terminal address to the MEC system, enabling the MEC system to obtain the handover message. Furthermore, the terminal that needs to perform the handover, the source UPF indirectly connected to the MEC host before the handover, and the destination UPF indirectly connected to the MEC host to be switched can be determined based on the source UPF address, destination UPF address, and terminal address.

[0096] S120. Determine the MEC application accessed by the terminal device based on the handover message.

[0097] The MEC application can refer to the application (i.e., APP) in the MEC host, and the terminal device can access the application in the MEC host.

[0098] There is no limitation on the way the terminal device accesses the MEC application. For example, the terminal device is communicatively connected to the AAU, the AUU is sequentially connected to the 5G DU, 5G CU, and UPF. The UPF can be connected to the edge cloud gateway through the N6 interface, and the edge cloud gateway can be connected to the MEC host, thereby accessing the MEC host through the edge cloud gateway and then accessing the MEC application.

[0099] The method for determining the MEC application accessed by the terminal device based on the handover message is not limited, as long as the MEC application accessed by the terminal device can be determined based on the handover message. For example, the source UPF address and the terminal address can be obtained based on the handover message. The source UPF can support the routing and forwarding of terminal service data, data and service identification, action and policy execution, etc. The terminal can access the edge cloud gateway through the source UPF, and the edge cloud gateway can be connected to the MEC host, so as to access the MEC host through the edge cloud gateway and then access the MEC application. Therefore, the MEC application accessed by the terminal device can be determined through the source UPF address and the terminal address.

[0100] S130. Determine the destination edge cloud gateway address based on the handover message and the application attributes of the MEC application.

[0101] Among them, the application attributes can be a general term for the nature corresponding to the application and the relationship between applications. The destination edge cloud gateway address can refer to the address of the edge cloud gateway connected to the MEC host to be switched.

[0102] The type of application attributes is not limited. For example, it can be the application type of the application, the memory space occupied, the running duration, the traffic usage, the power consumption, the application name or the permissions, etc. Among them, the application type can characterize the type to which the application belongs, such as the high-definition video service; the memory space occupied can characterize the size of the terminal memory occupied by the application; the running duration can characterize the running time of the application. For example, the usage of different applications can be reflected by the running duration of different applications; the traffic usage can characterize the traffic usage of the application, such as the amount of traffic used and the frequency of traffic use; the power consumption can characterize the amount of power used by the application; the application name can facilitate the distinction between different applications; the permissions can reflect the restriction situation of the application, such as the permission to read or write files, access location permissions or connect to peripheral devices. The permissions can include, but are not limited to, prohibited, always allowed or only allowed during use. By setting the application permissions, the application can have different functions. Through application attributes such as the application type, memory space occupied, running duration, traffic usage, power consumption or permissions of the application, the running situation of the application can be reflected.

[0103] The method for determining the destination edge cloud gateway address based on the handover message and the application attributes of the MEC application is not limited, as long as the destination edge cloud gateway address can be determined based on the handover message and the application attributes of the MEC application. For example, based on the handover message, the source UPF address, the destination UPF address, and the terminal address can be determined. Through the source UPF address and the terminal address, the MEC application accessed by the terminal device can be determined. Through the destination UPF address, the destination UPF indirectly connected to the MEC host to be switched can be determined. Through the application attributes of the MEC application, the running status of the application can be obtained, and then the MEC host suitable for running the application can be determined through the application attributes. Then, through the destination UPF and the MEC host, the destination edge cloud gateway to which the destination UPF can access the MEC host can be determined, and thus the destination edge cloud gateway address can be determined based on the handover message and the application attributes of the MEC application.

[0104] In one embodiment, the destination edge cloud gateway is determined based on the handover message and the application attributes of the MEC application. Specifically, the MEC application accessed by the terminal device can be determined according to the source UPF address and the terminal address included in the handover message. The traffic required to run the MEC application can be judged according to the traffic usage of the MEC application, and then the MEC host that can ensure the traffic required for the operation of the MEC application can be determined. Then, the destination UPF indirectly connected to the MEC host to be switched can be determined through the destination UPF address, and further the destination edge cloud gateway address to which the destination UPF can access the MEC host can be determined through the destination UPF and the MEC host.

[0105] The technical solution of the embodiment of the present invention determines the destination edge cloud gateway address by combining the handover message obtained by the MEC system with the application attributes of the MEC application. When the terminal accesses the edge application (i.e., the MEC application) in the MEC system and a handover occurs, the terminal can access the switched MEC host through the determined destination edge cloud gateway address, ensuring the service continuity and quality of service of the terminal and improving the user experience.

[0106] Further, determining the MEC application accessed by the terminal device based on the handover message includes:

[0107] Determining the MEC application accessed by the terminal device according to the source UPF address and the terminal address.

[0108] The method for determining the MEC application accessed by the terminal device based on the source UPF address and the terminal address is not limited, as long as the MEC application accessed by the terminal device can be determined based on the source UPF address and the terminal address. For example, based on the source UPF address and the terminal address, the source UPF and the terminal connected to the source UPF are determined. The terminal can be communicatively connected to the AAU, and the AUU can be sequentially connected to the 5G DU, the 5G CU, and the source UPF. Furthermore, the terminal can perform routing and forwarding of service data, data and service identification, action and policy execution, etc. through the source UPF, and then connect to the MEC host through the N6 interface of the source UPF, thereby determining the MEC application accessed by the terminal device.

[0109] Determining the MEC application accessed by the terminal device through the handover message enables the MEC system to determine the MEC application accessed by the terminal, facilitating the MEC system to determine the MEC host that can be switched based on the application attributes of the MEC application.

[0110] Furthermore, based on the handover message and the application attributes of the MEC application, determining the destination edge cloud gateway address includes:

[0111] Determining the destination edge cloud gateway address based on the destination UPF address and the application attributes of the MEC application.

[0112] The method for determining the destination edge cloud gateway address based on the destination UPF address and the application attributes of the MEC application is not limited, as long as the destination edge cloud gateway address can be determined based on the destination UPF address and the application attributes of the MEC application. For example, the destination UPF indirectly connected to the MEC host to be switched can be determined through the destination UPF address, and the running status of the application can be obtained through the application attributes of the MEC application. Furthermore, the MEC host suitable for running this application can be determined through the application attributes, and then the destination edge cloud gateway through which the destination UPF can access this MEC host can be determined based on the destination UPF and the MEC host, thereby determining the destination edge cloud gateway address.

[0113] Determining the destination edge cloud gateway address through the handover message and the application attributes of the MEC application enables the terminal to access the MEC host to be switched through the destination UPF and the destination edge cloud gateway.

[0114] Furthermore, the determination method further includes:

[0115] Determining the source edge cloud gateway address according to the source UPF address and the terminal address included in the handover message;

[0116] Migrating the MEC application from the source MEC host to the destination MEC host according to the application attributes, the source edge cloud gateway address, and the destination edge cloud gateway address.

[0117] Among them, the source MEC host may refer to the MEC host before handover occurs. The destination MEC host may refer to the MEC host to which the handover will occur. The source edge cloud gateway address may refer to the address of the edge cloud gateway connected to the source MEC host.

[0118] The specific form of the source edge cloud gateway address is not limited, as long as the source edge cloud gateway can be determined through the source edge cloud gateway address. For example, different IP addresses are assigned to different source edge cloud gateways, and the unique source edge cloud gateway corresponding to the IP address can be determined through the IP address.

[0119] The method for determining the source edge cloud gateway address based on the source UPF address and the terminal address included in the handover message is not limited, as long as the source edge cloud gateway address can be determined based on the source UPF address and the terminal address. For example, the source UPF and the terminal connected to the source UPF can be determined through the source UPF address and the terminal address included in the handover message. The terminal accesses the source edge cloud gateway through the source UPF and the N6 interface and then accesses the source MEC host. Therefore, the source edge cloud gateway address can be determined based on the source UPF address and the terminal address.

[0120] Migrating the MEC application from the source MEC host to the destination MEC host according to the application attribute, the source edge cloud gateway address, and the destination edge cloud gateway address can be understood as follows: according to the application attribute, the running situation of the application can be determined; according to the source edge cloud gateway address, the source edge cloud gateway, the source UPF connected to the source edge cloud gateway, and the source MEC host can be determined; according to the destination edge cloud gateway address, the destination edge cloud gateway, the destination UPF connected to the destination edge cloud gateway, and the destination MEC host can be determined. The source MEC host and the destination MEC host are connected in series. Therefore, the MEC application accessed by the terminal through the source MEC host can be migrated to the destination MEC host.

[0121] Migrating the MEC application from the source MEC host to the destination MEC host according to the application attribute, the source edge cloud gateway address, and the destination edge cloud gateway address enables the terminal to access the MEC application migrated to the destination MEC host through the destination UPF, the N6 interface, and the destination edge cloud gateway.

[0122] Furthermore, the determination method further includes:

[0123] Transmitting a response message and the destination edge cloud gateway address, where the response message is used to indicate that the handover of the MEC application is ready.

[0124] The response message may be a message indicating that the switching of the MEC application is ready. The switching of the MEC application may be understood as the process of migrating the MEC application from the source MEC host to the destination MEC host. The form of the response message is not limited, as long as the switching readiness of the MEC application can be determined through the response message. For example, the response message may be in the form of a data message, which may refer to a data unit exchanged and transmitted in the network, including complete data information to be sent.

[0125] The MEC system transmits a response message and the address of the destination edge cloud gateway to the 5G core network, so that the 5G core network can determine that the switching of the MEC application is ready. The 5G core network can transmit the address of the destination edge cloud gateway to the destination UPF so that the destination UPF forwards the data from the user to the destination edge cloud gateway.

[0126] Embodiment 2

[0127] Figure 4 This is a flow chart of a determination method provided according to the second embodiment of the present invention. This embodiment is applicable to the case where the core network receives information sent by the MEC system to control application switching. The method can be executed by a determination device, which can be implemented in the form of software and / or hardware and integrated in an electronic device. Further, the electronic device includes but is not limited to: computers, laptops, smart phones, servers, etc. Figure 4 As shown, the method includes:

[0128] S210: Receive a first switching request.

[0129] The first switching request may refer to a request for edge cloud gateway switching. The form of the first switching request is not limited, as long as it can be determined through the first switching request that edge cloud gateway switching is required. For example, the first switching request may be in the form of a data message.

[0130] The receiving method of the first handover request is not limited, as long as the first handover request can be received. For example, the terminal initiates the first handover request to the core network via the source NG-RAN, so that the core network receives the first handover request.

[0131] By receiving the first switching request, it can be determined that the source MEC host currently accessed by the user can no longer provide edge services and an edge cloud gateway switch is required.

[0132] S220. In response to the first switching request, send a switching message, where the switching message is used to determine the address of the destination edge cloud gateway.

[0133] Among them, the handover message may include but is not limited to the source UPF address, the destination UPF address, and the terminal address. The destination edge cloud gateway address can be determined through the handover message.

[0134] In response to the first handover request, there is no limitation on the way of sending the handover message, as long as the handover message can be sent to the MEC system. For example, the SMF in the core network sends the handover message to the MEC system through the Naf interface, so that the MEC system can obtain the handover message and determine the destination edge cloud gateway address through the handover message.

[0135] The technical solution of the embodiment of the present invention enables the core network to determine that an edge cloud gateway handover is required by receiving the first handover request, and then switches from the source MEC host to the destination MEC host, and sends the handover message to the MEC system, so that the MEC system determines the destination edge cloud gateway address through the handover message, and finally switches the MEC application from the source MEC host to the destination MEC host, ensuring the service continuity and quality of service of the terminal.

[0136] Furthermore, the determination method further includes:

[0137] Receiving a response message and the destination edge cloud gateway address, where the response message is used to indicate that the handover of the MEC application is ready.

[0138] There is no limitation on the way of receiving the response message and the destination edge cloud gateway address, as long as the response message and the destination edge cloud gateway address can be received. For example, the core network receives the response message and the destination edge cloud gateway address sent by the MEC system through the Naf interface.

[0139] By receiving the response message, the core network can confirm that the handover of the MEC application is ready. By receiving the destination edge cloud gateway address, the core network can forward the destination edge cloud gateway address to the destination UPF, so that the destination UPF forwards the user data to the destination edge cloud gateway corresponding to the destination edge cloud gateway address.

[0140] Furthermore, the determination method further includes:

[0141] Transmitting a policy rule and the destination edge cloud gateway address to the destination UPF. The destination edge cloud gateway corresponding to the destination edge cloud gateway address is used to receive the terminal data transmitted by the destination UPF, and the policy rule is used for the destination UPF to perform corresponding operations based on the policy rule.

[0142] Among them, the policy rule can be a rule for the destination UPF to use. There is no limitation on the policy rule, and it can be a rule related to QoS, such as bandwidth, priority, etc. After receiving the policy rule, the destination UPF can execute the policy rule to complete the corresponding operation. The corresponding operation can be considered as an operation related to the policy rule, which is not limited here, and different policy rules correspond to different operations.

[0143] The terminal data can refer to the data used to confirm the terminal or the data generated during the use of the terminal. The terminal data includes, but is not limited to, the terminal address and the information of the MEC application accessed by the terminal, etc.

[0144] There is no limitation on the way of transmitting the policy rule and the destination edge cloud gateway address to the destination UPF, as long as the policy rule and the destination edge cloud gateway address can be transmitted to the destination UPF. For example, the core network transmits the policy rule and the destination edge cloud gateway address to the destination UPF through the N4 interface.

[0145] By transmitting the policy rule and the destination edge cloud gateway address to the destination UPF, the destination UPF can confirm the destination edge cloud gateway corresponding to the destination edge cloud gateway address and connect to the destination edge cloud gateway through the N6 interface. Then, the destination edge cloud gateway can receive the terminal data transmitted by the destination UPF, and the terminal can access the MEC application in the destination MEC host through the destination UPF and the destination edge cloud gateway.

[0146] The following is an exemplary description of the present invention:

[0147] The present invention provides a method for switching an edge cloud gateway in a 5G network, which can ensure the service continuity and quality of service of a mobile user (i.e., a terminal) when accessing an edge cloud application (i.e., an MEC application) in an MEC system and switching occurs.

[0148] In this embodiment, an edge cloud gateway is set in the MEC system to provide an entrance for accessing the MEC host externally. The edge cloud gateway receives data packets from the UPF of the 5G core network. The UPF receives the policy rule from the 5G core network and executes it. The UPF and the edge cloud gateway are connected through the N6 interface.

[0149] When a mobile user moves from one area to another area, the source NG-RAN sends a handover request (i.e., the first handover request) to the 5G core network;

[0150] The 5G core network sends a message (i.e., a handover message) to the MEC system, including an indication that the user has a handover, and at the same time carrying the source UPF address, the destination UPF address, and the user address (i.e., the terminal address);

[0151] The MEC system determines the MEC application that the user is accessing and the corresponding source edge cloud gateway address based on the source UPF address and the user address;

[0152] The MEC system determines the destination edge cloud gateway address based on the destination UPF address and the MEC application attributes;

[0153] Furthermore, the MEC system migrates the MEC application that the user is accessing from the source MEC host to the destination MEC host based on information such as the MEC application attributes, the source edge cloud gateway address, and the destination edge cloud gateway address;

[0154] Furthermore, the MEC system sends a response message to the 5G core network, indicating that the MEC application switch is ready, and at the same time carrying the destination edge cloud gateway address;

[0155] The 5G core network sends a handover request to the destination NG-RAN;

[0156] The 5G core network issues a policy rule to the destination UPF, carrying the destination edge cloud gateway address;

[0157] The destination UPF forwards the data report (i.e., terminal data) from this user to the destination edge cloud gateway.

[0158] Figure 5 It is a flowchart of edge cloud gateway handover based on the N2 interface in a 5G network provided by Embodiment 2 of the present invention, as Figure 5 shown, and specifically includes:

[0159] The UE has registered in the 5G network and established a PDU session to use services; and accesses the application services of the local data network in the MEC system through the source 5G radio access network S-NG-RAN;

[0160] At this time, the uplink data path of the UE is: UE to S-NG-RAN to source UPF to source edge cloud gateway; the downlink path is: source edge cloud gateway to source UPF to S-NG-RAN to UE;

[0161] 1. Handover request: The UE's location changes. Based on the new radio conditions or load balancing, the S-NG-RAN decides to initiate an N2-based handover;

[0162] 2. PDU session update request: The AMF sends a PDU session update request to the SMF, including N2SM information, UE location information (i.e., terminal address), etc.;

[0163] 3. Handover indication (i.e., handover message): The SMF sends a handover indication to the MEC orchestrator in the MEC system, including the PDU session ID, UE location information, source UPF address, destination UPF address, etc.;

[0164] 4. Policy Decision: The MEC system determines the MEC application that the UE is accessing and the corresponding source edge cloud gateway address based on the source UPF address and UE location information; the MEC system determines the destination edge cloud gateway address based on the destination UPF address and MEC application attributes; the MEC system migrates the MEC application that the user is accessing from the source MEC host to the destination MEC host based on information such as MEC application attributes, source edge cloud gateway address, and destination edge cloud gateway address;

[0165] 5. Handover Indication Response: The MEC system sends a response message to the SMF, indicating that the MEC application handover is ready, including the destination edge cloud gateway address;

[0166] 6. N4 Session Establishment: The SMF sends an N4 session establishment request to the destination UPF, including information such as the destination edge cloud gateway address and QoS list; the destination UPF replies with a response;

[0167] 7. PDU Session Update Response: The SMF sends a PDU session update response to the AMF;

[0168] 8. PDU Handover Response Supervision: The AMF performs PDU handover response supervision;

[0169] 9. Handover Request: The AMF sends a handover request to the T-NG-RAN;

[0170] 10. Handover Request Acknowledgment: The T-NG-RAN sends a handover request response to the AMF;

[0171] 11. PDU Session Update Request: The AMF sends a PDU session update request to the SMF;

[0172] 12. N4 Session Modification: The SMF sends an N4 session modification request to the destination UPF; the destination UPF replies with a response;

[0173] 13. N4 Session Modification: The SMF sends an N4 session modification request to the source UPF; the source UPF replies with a response;

[0174] 14. PDU Session Update Response: The SMF sends a PDU session update response to the AMF;

[0175] At this time, the uplink data path of the UE is: UE -> T-NG-RAN -> destination UPF -> destination edge cloud gateway; the downlink data path is: destination edge cloud gateway -> destination UPF -> T-NG-RAN -> UE.

[0176] Figure 6 It is a flowchart of edge cloud gateway handover based on the Xn interface in a 5G network provided by Embodiment 2 of the present invention, asFigure 6 As shown below, specifically including:

[0177] 1. Handover preparation: The UE has been registered in the 5G network and established a PDU session to use services; and accesses the application services of the local data network in the MEC system through the source 5G radio access network S-NG-RAN. The UE's location changes and it leaves the S-NG-RAN and is about to enter the new NG-RAN service area, i.e., T-NG-RAN. At this time, handover preparation is performed;

[0178] 2. Handover execution: When the handover preparation is completed, the handover operation is executed;

[0179] 3. Data forwarding: S-NG-RAN forwards data to T-NG-RAN;

[0180] At this time, the downlink data path of the UE is: T-NG-RAN to UE; the uplink path is: UE to T-NG-RAN to the source UPF to the source edge cloud gateway;

[0181] 4. N2 path handover request: T-NG-RAN sends an N2 path handover request to the AMF, including the list of PDU sessions to be handed over and the corresponding N2 SM information (PDU session ID, QoS list, etc.), UE location information, etc.;

[0182] 5. PDU session update request: The AMF sends a PDU session update request to the SMF, including N2SM information, UE location information, etc.;

[0183] 6. Handover indication: The SMF sends a handover indication to the MEC orchestrator in the MEC system, including the PDU session ID, UE location information, source UPF address, destination UPF address, etc.;

[0184] 7. Policy decision: The MEC system determines the MEC application accessed by the UE and the corresponding source edge cloud gateway address according to the source UPF address and UE location information; the MEC system determines the destination edge cloud gateway address according to the destination UPF address and MEC application attributes; the MEC system migrates the MEC application accessed by the user from the source MEC host to the destination MEC host based on information such as MEC application attributes, source edge cloud gateway address, and destination edge cloud gateway address;

[0185] 8. Handover indication response: The MEC system replies to the SMF with a response message indicating that the MEC application handover is ready, including the destination edge cloud gateway address;

[0186] 9. N4 session establishment: The SMF sends an N4 session establishment request to the destination UPF, including information such as the destination edge cloud gateway address and QoS list; the destination UPF replies with a response;

[0187] 10. N4 Session Modification: The SMF sends an N4 session modification request to the source UPF; the source UPF replies with a response;

[0188] 11. N3 End Marker: The source UPF sends an N3 end marker to the S-NG-RAN;

[0189] 12. N3 End Marker: After receiving it, the S-NG-RAN sends an N3 end marker to the T-NG-RAN;

[0190] At this time, the UE's downlink data path is: the destination edge cloud gateway to the destination UPF to the T-NG-RAN to the UE;

[0191] 13. PDU Session Update Response: The SMF replies with a PDU session update response to the AMF;

[0192] 14. N2 Path Switch Request Acknowledgment: The AMF sends an N2 path switch request acknowledgment to the T-NG-RAN;

[0193] At this time, the UE's uplink data path is: the UE to the T-NG-RAN to the destination UPF to the destination edge cloud gateway;

[0194] 15. Release Resources: The T-NG-RAN sends a resource release message to the S-NG-RAN to release the resources occupied by the UE before the handover.

[0195] Embodiment III

[0196] Figure 7 It is a schematic structural diagram of a determination device provided according to Embodiment III of the present invention. This embodiment is applicable to the situation where the MEC system controls the handover of MEC applications. As Figure 7 shown, the specific structure of the device includes:

[0197] An obtaining module 21, configured to obtain a handover message;

[0198] A first module 22, configured to determine the MEC application accessed by the terminal device based on the handover message;

[0199] A second module 23, configured to determine the destination edge cloud gateway address based on the handover message and the application attributes of the MEC application.

[0200] The determination device provided in this embodiment first obtains a handover message through the obtaining module 21; then determines the MEC application accessed by the terminal device through the first module 22 based on the handover message; and finally determines the destination edge cloud gateway address through the second module 23 based on the handover message and the application attributes of the MEC application.

[0201] Further, the switching message obtained by the obtaining module 21 includes the source UPF address, the destination UPF address, and the terminal address.

[0202] Further, the first module 22 is specifically configured to:

[0203] Determine the MEC application accessed by the terminal device according to the source UPF address and the terminal address.

[0204] Further, the second module 23 is specifically configured to:

[0205] Determine the destination edge cloud gateway address according to the destination UPF address and the application attributes of the MEC application.

[0206] Further, the device further includes:

[0207] An address determination module, configured to determine the source edge cloud gateway address according to the source UPF address and the terminal address included in the switching message;

[0208] A migration module, configured to migrate the MEC application from the source MEC host to the destination MEC host according to the application attributes, the source edge cloud gateway address, and the destination edge cloud gateway address.

[0209] Further, the device further includes:

[0210] A first transmission module, configured to transmit a response message and the destination edge cloud gateway address, where the response message is used to indicate that the switching of the MEC application is ready.

[0211] The determination device provided by the embodiment of the present invention can execute the determination method provided by the first embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method.

[0212] Embodiment 4

[0213] Figure 8 It is a schematic structural diagram of a determination device provided by the fourth embodiment of the present invention. This embodiment is applicable to the case where the core network receives information sent by the MEC system for application switching control. As Figure 8 shown, the specific structure of the device includes:

[0214] A receiving module 31, configured to receive a first switching request;

[0215] A sending module 32, configured to send a switching message in response to the first switching request, where the switching message is used to determine the destination edge cloud gateway address.

[0216] The determination device provided in this embodiment first receives a first switching request through the receiving module 31; and then sends a switching message in response to the first switching request through the sending module 32, where the switching message is used to determine the destination edge cloud gateway address.

[0217] Further, the device further includes:

[0218] A second receiving module, configured to receive a response message and a destination edge cloud gateway address, where the response message is used to indicate that the handover of the MEC application is ready.

[0219] Further, the device further includes:

[0220] A second transmission module, configured to transmit a policy rule and a destination edge cloud gateway address to a destination UPF, where the destination edge cloud gateway corresponding to the destination edge cloud gateway address is used to receive terminal data transmitted by the destination UPF, and the policy rule is used for the destination UPF to perform corresponding operations based on the policy rule.

[0221] The determination device provided by the embodiments of the present invention can execute the determination method provided by the second embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method.

[0222] Embodiment 5

[0223] Figure 9 It is a schematic structural diagram of an electronic device for implementing the determination method of the embodiments of the present invention. The electronic device is intended to represent various forms of digital computers, such as, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, a personal digital processor, a cellular phone, a smart phone, a wearable device (such as a helmet, glasses, a watch, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present invention described herein and / or claimed.

[0224] As Figure 9 shown, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc. Among them, the memory stores a computer program executable by at least one processor, and the processor 11 can execute various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. The input / output (I / O) interface 15 is also connected to the bus 14.

[0225] Multiple components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disc, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0226] The processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the processor 11 include but are not limited to a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the determination method.

[0227] In some embodiments, the determination method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the determination method described above can be executed. Alternatively, in other embodiments, the processor 11 can be configured to execute the determination method in any other suitable way (e.g., by means of firmware).

[0228] The various embodiments of the systems and technologies described above in this document can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs, which can be executed and / or interpreted on a programmable system including at least one programmable processor, and the programmable processor can be a dedicated or general-purpose programmable processor, receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0229] A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions / operations specified in the flowchart and / or block diagram to be implemented. The computer program may be executed entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0230] In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0231] In order to provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0232] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected with each other by digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

[0233] A computing system can include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The client-server relationship is created by computer programs running on respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system, and solves the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0234] It should be understood that various forms of the processes shown above can be used, with steps reordered, added, or deleted. For example, the steps recited in the present invention can be executed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved, and no limitation is made herein.

[0235] The above specific embodiments do not constitute a limitation on the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims

1. A determination method, characterized in that, Applied to the MEC system, the method includes: Obtain a handover message; the handover message includes a source UPF address, a destination UPF address, and a terminal address; Based on the handover message, determine the MEC application accessed by the terminal device; Based on the handover message and the application attributes of the MEC application, determine the destination edge cloud gateway address; Wherein, based on the handover message and the application attributes of the MEC application, determining the destination edge cloud gateway address includes: Determine the destination edge cloud gateway address according to the destination UPF address and the application attributes of the MEC application; The method further includes: Determine the source edge cloud gateway address according to the source UPF address and the terminal address included in the handover message; Migrate the MEC application from the source MEC host to the destination MEC host according to the application attributes, the source edge cloud gateway address, and the destination edge cloud gateway address.

2. The method according to claim 1, wherein The determining, based on the handover message, the MEC application accessed by the terminal device includes: Determine the MEC application accessed by the terminal device according to the source UPF address and the terminal address.

3. The method according to claim 1, wherein It further includes: Transmit a response message and the destination edge cloud gateway address, the response message being used to indicate that the handover of the MEC application is ready.

4. A determination method, characterized in that, Applied to the core network, the method includes: Receive a first handover request; In response to the first handover request, send a handover message, the handover message including a source UPF address, a destination UPF address, and a terminal address; The handover message is used to determine the MEC application accessed by the terminal device corresponding to the terminal address; The destination UPF address and the application attributes of the MEC application are used to determine the destination edge cloud gateway address; The source UPF address and the terminal address are used to determine the source edge cloud gateway address; The application attributes, the source edge cloud gateway address, and the destination edge cloud gateway address are used to migrate the MEC application from the source MEC host to the destination MEC host.

5. The method according to claim 4, characterized in that, It further includes: Receive a response message and the destination edge cloud gateway address, the response message being used to indicate that the handover of the MEC application is ready.

6. The method according to claim 5, wherein It further includes: Transmit a policy rule and the destination edge cloud gateway address to the destination UPF, the destination edge cloud gateway corresponding to the destination edge cloud gateway address being used to receive the terminal data transmitted by the destination UPF, and the policy rule being used for the destination UPF to perform corresponding operations based on the policy rule.

7. A determination device, characterized in that, It includes: An acquisition module, configured to acquire a handover message; The handover message includes a source UPF address, a destination UPF address, and a terminal address; A first module, configured to determine the MEC application accessed by the terminal device based on the handover message; A second module, configured to determine the destination edge cloud gateway address based on the handover message and the application attributes of the MEC application; Wherein, the second module is specifically configured to: Determine the destination edge cloud gateway address according to the destination UPF address and the application attributes of the MEC application; The apparatus further includes: An address determination module, configured to determine the source edge cloud gateway address according to the source UPF address and the terminal address included in the handover message; A migration module, configured to migrate the MEC application from the source MEC host to the destination MEC host according to the application attribute, the source edge cloud gateway address, and the destination edge cloud gateway address.

8. A determining device, characterized in that, It includes: A receiving module, configured to receive a first handover request; A sending module, configured to send a handover message in response to the first handover request, where the handover message includes a source UPF address, a destination UPF address, and a terminal address; The handover message is used to determine the MEC application accessed by the terminal device corresponding to the terminal address; The destination UPF address and the application attribute of the MEC application are used to determine the destination edge cloud gateway address; The source UPF address and the terminal address are used to determine the source edge cloud gateway address; The application attribute, the source edge cloud gateway address, and the destination edge cloud gateway address are used to migrate the MEC application from the source MEC host to the destination MEC host.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and when the computer program is executed by the at least one processor, the at least one processor is enabled to execute the method according to any one of claims 1-6.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1-6 is implemented.

Images