UPF network element selection method and device

Abstract

The present application provides a UPF network element selection method and device. According to the UPF network element selection method provided in the present application, a PLMN management system determines a UPF network element deployed at an EAS position as a UPF network element corresponding to an EAS, which ensures that the EAS and the UPF network element corresponding to the EAS are co-deployed at the same position, thereby avoiding a transmission delay caused by different positions, and improving experience of a user in using application services provided by the EAS.

Description

UPF network element selection method and device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on November 28, 2023, with application number 202311614809.9 and application name “UPF network element selection method and device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a method and device for selecting a UPF network element. Background Art

[0003] In the multi-access edge computing (MEC) architecture, user equipment (UE) exchanges data with the edge application server (EAS) deployed on the edge data network (EDN) through the user plane function (UPF) network element, necessitating a UE-EAS connection. However, in the user plane path between the UPF network element and the EAS, the latency is relatively high. Summary of the Invention

[0004] The present application provides a UPF network element selection method and device, aiming to deploy EAS and its corresponding UPF network element at the same location, thereby reducing data interaction delay.

[0005] In the first aspect, the present application provides a user plane function network element selection method, which is applied to a public land mobile network PLMN management system, the method including: receiving a first request information from an edge computing service provider ECSP management system, the first request information requesting that a first edge application server EAS be connected to a user plane function UPF network element; determining the UPF network element corresponding to the first EAS, the deployment location of the UPF network element corresponding to the first EAS being the same as the deployment location of the first EAS.

[0006] When the PLMN management system selects a UPF network element for the first EAS, it selects a UPF network element with the same deployment location as the first EAS as the UPF network element corresponding to the first EAS, which can ensure that the first EAS and its corresponding UPF network element are deployed at the same location, thereby reducing the data transmission delay caused by different locations.

[0007] In some implementations, before receiving the first request information from the edge computing service provider (ECSP) management system, the method further includes:

[0008] The method further comprises: receiving first indication information from an ECSP management system, the first indication information indicating a desired location for deploying a first EAS; determining a first location based on at least one location corresponding to at least one UPF network element in the first indication information; and sending a second request information to the ECSP management system, the second request information requesting deployment of the first EAS at the first location.

[0009] In some implementations, the first position is the same position as the position where the first EAS is expected to be deployed among at least one position in a one-to-one correspondence between at least one UPF network element, or the first position is the position that is closest to the position where the first EAS is expected to be deployed among at least one position in a one-to-one correspondence between at least one UPF network element.

[0010] Deploying the first EAS at the first location can ensure that a UPF network element exists at the deployment location of the first EAS.

[0011] In some implementations, after sending the second request information to the ECSP management system, the method further includes:

[0012] Configure first access information, where the first access information indicates that the EES corresponding to the first UPF network element is the EES registered with the first EAS, and / or send a third request information to the ECSP management system, where the third request information requests creation of a connection relationship between the EES registered with the first EAS and the first UPF network element, where the first UPF network element is the UPF network element corresponding to the first position.

[0013] Creating a connection relationship between the first UPF network element and the EES registered with the first EAS can provide a prerequisite for subsequently creating an optimal user plane path between the UE and the first EAS based on the first EAS and the first UPF network element being deployed at the same location.

[0014] In some implementations, before receiving the first request information from the edge computing service provider (ECSP) management system, the method further includes:

[0015] Receive second indication information from the ECSP management system, where the second indication information indicates a second location, where the second location is the location where the first EAS is deployed; and send fourth request information to the network function virtualization orchestrator NFVO according to the second indication information, where the fourth request information requests deployment of a UPF network element at the second location.

[0016] Deploying the UPF network element at the second location can ensure that the UPF network element exists at the deployment location of the first EAS.

[0017] In some implementations, after sending fourth request information to the network function virtualization orchestrator NFVO according to the second indication information, the method further includes:

[0018] Configure second access information, where the second access information indicates that the EES corresponding to the second UPF network element is the EES registered with the first EAS, and / or send a fifth request message to the ECSP management system, where the fifth request message requests creation of a connection relationship between the EES registered with the first EAS and the second UPF network element, where the second UPF network element is the UPF network element corresponding to the second position.

[0019] Creating a connection relationship between the second UPF network element and the EES registered with the first EAS can provide a prerequisite for the subsequent creation of the optimal user plane path between the UE and the first EAS based on the first EAS and the second UPF network element being deployed at the same location.

[0020] In some implementations, the first request information includes first information, where the first information indicates a UPF network element corresponding to a first edge enabling server EES, and the first EES is an EES registered with the first EAS.

[0021] Determining the UPF network element corresponding to the first EAS includes:

[0022] The UPF network element indicated by the first information is determined as the UPF network element corresponding to the first EAS.

[0023] Determining the UPF network element corresponding to the first EES as the UPF network element corresponding to the first EAS can ensure that the user plane path between the UE and the first EAS is optimal on the basis that the first EAS and its corresponding UPF network element are deployed at the same location, avoid the occurrence of transit UPF network elements, and further reduce data transmission delay.

[0024] In the second aspect, the present application provides a user plane function network element selection method, which is applied to the PLMN management system, and the method includes: receiving a first request information from the ECSP management system, the first request information requesting to connect the first EAS to the UPF network element; determining the UPF network element corresponding to the first EAS, wherein the UPF network element corresponding to the first EAS is the same as the UPF network element corresponding to the EES registered with the first EAS.

[0025] In some implementations, the first request information includes first information, where the first information indicates a UPF network element corresponding to the first EES, and the first EES is the EES registered with the first EAS.

[0026] Determining the UPF network element corresponding to the first EAS includes:

[0027] The UPF network element indicated by the first information is determined as the UPF network element corresponding to the first EAS.

[0028] When the PLMN management system selects the UPF network element for the first EAS, the UPF network element corresponding to the first EES is used as the UPF network element corresponding to the first EAS, ensuring that the UPF network element corresponding to the first EAS and the associated first EES is the same UPF network element, thereby obtaining the optimal user plane path between the UE-EAS and reducing the communication delay during data interaction between the UE and the first EAS.

[0029] In some implementations, the first request information further includes second information, where the second information includes at least one of the following information: edge data network EDN information of the first EAS, service area information, or N6 traffic routing information.

[0030] When the distance between the UPF network element indicated by the first information and the first EAS is greater than a preset threshold, the method further includes:

[0031] Determine a first UPF network element based on the second information; determine the first UPF network element as the UPF network element corresponding to the first EAS; configure first access information, the first access information indicates that the EES corresponding to the first UPF network element is the first EES, and / or send a second request information to the ECSP management system, the second request information requesting to establish a connection relationship between the first EES and the first UPF network element.

[0032] When the UPF network element corresponding to the EES associated with the first EAS cannot match the service requirements of the first EAS, the PLMN management system selects a new UPF network element for the first EAS based on the second information to ensure that the user plane path between the UE and the first EAS is the optimal user plane path, thereby reducing the N6 delay.

[0033] In some implementations, the method further includes:

[0034] When the first UPF network element is not deployed, a third request message is sent to the NFVO, where the third request message requests the deployment of the first UPF network element.

[0035] In some implementations, when the service area of ​​the first UPF network element does not include the service area of ​​the first EES, the method further includes:

[0036] Determine the second EES based on the service area of ​​the first UPF network element, where the service area of ​​the second EES is included in the service area of ​​the first UPF network element; configure second access information, where the second access information indicates that the EES corresponding to the first UPF network element is the second EES, and / or send a fourth request message to the ECSP management system, where the fourth request message requests to establish a connection relationship between the second EES and the first UPF network element; send a fifth request message to the ECSP management system, where the fifth request message requests to update the EES registered with the first EAS to the second EES.

[0037] In some implementations, the method further includes:

[0038] When the second EES is not deployed, a sixth request message is sent to the ECSP management system, where the sixth request message requests deployment of the second EES.

[0039] When the service area of ​​the first EES cannot match the service area of ​​the first UPF network element selected by the PLMN management system, the EES associated with the first EAS is adaptively adjusted to ensure that the user plane path between the UE and the first EAS is the optimal user plane path.

[0040] In a third aspect, the present application provides a method for selecting a user plane function network element, which is applied to an ECSP management system. The method includes:

[0041] A first request message is sent to the PLMN management system, where the first request message requests that the first EAS be connected to the UPF network element.

[0042] In some implementations, before sending the first request information to the PLMN management system, the method further includes:

[0043] Receive a second request message from an application service provider ASP, the second request message requesting deployment of a first EAS, the second request message including second information, the second information indicating the location where the first EAS is expected to be deployed; send a first indication message to a PLMN management system, the first indication message indicating the location where the first EAS is expected to be deployed; receive a third request message from the PLMN management system, the third request message requesting deployment of the first EAS at a first location, the first location being the same location as the location where the first EAS is expected to be deployed in at least one location corresponding to at least one UPF network element, or the first location being the location that is closest to the location where the first EAS is expected to be deployed in at least one location corresponding to at least one UPF network element.

[0044] In some implementations, after receiving the third request information from the PLMN management system, the method further includes:

[0045] Receive a fourth request message from the PLMN management system, the fourth request message requests to create a connection relationship between the EES registered with the first EAS and the first UPF network element, the first UPF network element is the UPF network element corresponding to the first position; configure the first access information, the first access information indicates that the UPF network element corresponding to the EES registered with the first EAS is the first UPF network element.

[0046] In some implementations, before sending the first request information to the PLMN management system, the method further includes:

[0047] Send second indication information to the PLMN management system, where the second indication information indicates a second location, where the second location is the location where the first EAS is deployed.

[0048] In some implementations, after sending the second indication information to the PLMN management system, the method further includes:

[0049] Receive the fifth request information from the PLMN management system, the fifth request information requests to create a connection relationship between the EES registered with the first EAS and the second UPF network element, the second UPF network element is the UPF network element corresponding to the second position; configure the second access information, the second access information indicates that the UPF network element corresponding to the EES registered with the first EAS is the second UPF network element.

[0050] In some implementations, the first request information includes first information, the first information indicates a UPF network element corresponding to the first EES, and the first EES is an EES registered with the first EAS.

[0051] In some implementations, the method further includes:

[0052] Receive the sixth request information from the PLMN management system, the sixth request information requests to create a connection relationship between the first EES and the third UPF network element, the third UPF network element is the UPF network element corresponding to the first EAS; configure the third access information, the third access information indicates that the UPF network element corresponding to the first EES is the third UPF network element.

[0053] In some implementations, the method further includes:

[0054] Receive the seventh request information from the PLMN management system, the seventh request information requests to establish a connection relationship between the second EES and the third UPF network element, the third UPF network element is the UPF network element corresponding to the first EAS, and the second EES is the EES determined according to the service area of ​​the third UPF network element; configure the fourth access information, the fourth access information indicates the UPF network element corresponding to the second EES and the third UPF network element; receive the eighth request information from the PLMN management system, the eighth request information requests to update the EES registered with the first EAS to the second EES; send the ninth request information to the NFVO, the ninth request information requests to update the EES registered with the first EAS to the second EES.

[0055] In some implementations, before receiving the seventh request information from the PLMN management system, the method further includes:

[0056] A tenth request message is received from the PLMN management system, where the tenth request message requests deployment of a second EES; and an eleventh request message is sent to the NFVO, where the eleventh request message requests deployment of the second EES.

[0057] In a fourth aspect, the present application provides a user plane function network element selection device, which includes various functional modules for implementing any user plane function network element selection method mentioned in the above implementation manner. Optionally, each module can be implemented by software and / or hardware.

[0058] In a fifth aspect, the present application provides a user plane function network element selection device, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of any possible implementation of the first aspect, the second aspect, or the third aspect. Optionally, the device further comprises a memory. Optionally, the device further comprises a communication interface, the processor coupled to the communication interface.

[0059] In a fifth aspect, the present application provides a computer-readable medium storing a program code for execution by a device, wherein the program code includes a method for executing the method in the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

[0060] In a sixth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the method in the first aspect, the second aspect, the third aspect, or any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0062] FIG1 is a schematic diagram of the edge application architecture defined by the SA6 group of 3GPP;

[0063] FIG2 is a simplified schematic diagram of a network access architecture under an edge application architecture applicable to the present application;

[0064] FIG3 is a flow chart of a method for selecting a UPF network element according to an embodiment of the present application;

[0065] FIG4 is a schematic diagram of a process for creating a user plane path according to an embodiment of the present application;

[0066] FIG5 is a flow chart of a method for deploying a first EAS according to an embodiment of the present application;

[0067] FIG6 is a schematic diagram of a process for deploying a UPF network element according to an embodiment of the present application;

[0068] Figure 7 is a schematic diagram of the access of EES and EAS corresponding to different UPF network elements;

[0069] FIG8 is a flow chart of a method for selecting a UPF network element according to another embodiment of the present application;

[0070] FIG9 is a flow chart of a method for selecting a UPF network element according to another embodiment of the present application;

[0071] FIG10 is a schematic structural diagram of a device for selecting a user plane function network element according to an embodiment of the present application;

[0072] FIG11 is a schematic structural diagram of a user plane function network element selection device provided in another embodiment of the present application.

[0073] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0074] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0075] First, the relevant concepts involved in this application are introduced:

[0076] Terminal device: A device with wireless transceiver capabilities that can send signals to or receive signals from network devices. A terminal can also be called user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be various handheld devices with communication functions, vehicle-mounted devices, wearable devices, computers, and network devices. For example, a handheld device can be a smartphone. A vehicle-mounted device can be a car navigation system. A wearable device can be a smart bracelet. A computer can be a personal digital assistant (PDA), a tablet computer, or a laptop computer. Network devices can be a residential gateway (RG) and a switch.

[0077] Network equipment: It can be a base transceiver station (BTS) in a global system for mobile communications (GSM) system or a code division multiple access (CDMA) system, a base station (NodeB, NB) in a wideband CDMA (WCDMA) system, an evolutionary node B (eNB or eNodeB) in a long term evolution (LTE) system, or a wireless controller in a cloud radio access network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (PLMN), etc.

[0078] Currently, the SA6 group in the 3rd Generation Partnership Project (3GPP) organization is conducting MEC research on application enablement under the 5G network architecture. Figure 1 is a schematic diagram of the edge (EDGE) application architecture defined by the SA6 group of 3GPP. As shown in Figure 1, the application architecture includes a terminal device 110, an edge data network (EDN) 120, and an edge configuration server (ECS) 130. Among them, the EDN 120 includes an edge application server EAS121 and an edge enabler server (EES) 122. The terminal device includes an application client (AC) 111 and an edge enabler client (EEC) 112.

[0079] EDN 120 corresponds to a data network, a special local data network (local DN), which can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logical concept. In another understanding, EDN is the equivalent of the central cloud and can be understood as a local data center (i.e., a geographic location concept). It can also be identified using a DNAI and can include multiple local data networks (local DNs).

[0080] EAS 121, also known as an edge application, is an application deployed in EDN 120. This edge application can also be referred to as an "application instance." Specifically, it refers to an instance of a server application (e.g., social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN. An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered different EASs of the same application. They can share a domain name or use a different domain name from the application deployed in the cloud. The domain name can be a fully qualified domain name (FQDN), can use a single, freely playable Internet protocol (IP) address, or can use different IP addresses.

[0081] EES122 is deployed in EDN 120 and can provide some enabling capabilities for application instances deployed in EDN 120. It can better support the deployment of applications in MEC, support edge application registration, UE authentication and authorization, provide UE with application instance IP address information, etc., and further support obtaining application instance identification and IP address information, and further send the application instance identification and IP address information to the edge data network configuration server. Generally, an EAS is registered with an EES, or an EAS information is configured on an EES through a management system. This EES is called the EES associated with the EAS, and the EES controls / manages the EAS registered / configured on the EES.

[0082] AC 111 is the UE-side counterpart of EAS 121. AC 111 enables application users to obtain application services from application servers. Application clients are client programs running on the terminal side. Application clients can connect to application servers in the cloud or to EAS deployed and running in one or more EDNs to obtain application services.

[0083] EEC 112 is the UE-side counterpart of EES 122. EEC 112 is responsible for registering EEC information and application client information with EES 122, performing security authentication and authorization, obtaining EAS 121's IP address from EES 122, and providing edge computing capabilities to application clients. For example, the EAS 121 discovery server returns the EAS 121 IP address to the application client. EEC 112 can be a sub-functional module implemented within AC 111, a module integrated into the operating system, or a standalone application.

[0084] ECS 130 is responsible for configuring EDN 120, such as providing EES 122 information to the UE. ECS 130 can also directly provide application instance information to the UE and interact with the application's Domain Name System (DNS) to obtain application instance information. It can also obtain and store application instance and IP address information from other functional entities.

[0085] The MEC architecture is part of cloud computing services. Therefore, through network function virtualization (NFV) technology, software-defined network functions such as EES and EAS can be flexibly deployed within the network architecture. These software-defined network functions are called virtualized network functions (VNFs). In the NFV system proposed by the European Telecommunications Standards Institute (ETSI), the NFV orchestrator (NFVO) allocates and schedules the virtual resources required for the VNFs to be deployed. Deploying a VNF is equivalent to instantiating the VNF.

[0086] It is understandable that when a UE needs to use application services deployed in an EDN, it first needs to access the EDN. Figure 2 is a simplified schematic diagram of a network access architecture under an edge application architecture applicable to this application. As shown in Figure 2, the access architecture includes a UE, a radio access network (RAN), a UPF network element, and an EDN.

[0087] Among them, RAN is mainly used to implement wireless physical layer functions, resource scheduling and wireless resource management, wireless access control and mobility management functions; UPF network element is the network element in the 5G core network (5G core / new generation core, 5GC / NGC) responsible for external connection to DN and user plane data packet routing forwarding, message filtering, and execution of quality of service (QoS) control and other related functions. Therefore, in the edge application architecture, the UPF network element is responsible for external connection to EDN and realizing the interaction of user plane data with EDN through the N6 interface. It should be noted that Figure 2 is only an exemplary architecture diagram. In addition to the functional units shown in Figure 2, the architecture can also include other functional units, and the embodiments of the present invention are not limited to this.

[0088] It is understandable that when the UPF network element exchanges user plane data with the EDN through the N6 interface, it is actually interacting with the EES or EAS deployed on the EDN. Based on the EAS service area information provided by the application service provider (ASP), the edge computing service provider (ECSP) management system configures the EAS's EDN information, service area information, and N6 traffic routing information, and sends the above information to the PLMN management system. The PLMN management system selects a UPF network element that matches the EAS service requirements based on the above information. This UPF network element is the UPF network element corresponding to the EAS. It is understandable that the "corresponding" relationship between the EAS and the UPF network element means that when the UE uses the application service provided by the EAS, the user plane data interaction is realized through the UPF network element corresponding to the EAS.

[0089] However, the deployment location of the UPF network element selected by the PLMN management system for the EAS may be different from the deployment location of the EAS. Different deployment locations result in increased latency between the UPF network element and the EAS in the user plane path between the UE and the EAS. It should be noted that the deployment "location" mentioned in this application can be a geographical location, a logical topological location, a data center, or even a deployment room. These different deployment "locations" will all result in increased latency between the UPF network element and the EAS.

[0090] To solve the above problems, the present application provides a UPF network element selection method and device, which aims to deploy EAS and its corresponding UPF network element at the same location, thereby reducing data interaction delay.

[0091] The technical concept of this application is: when the PLMN management system selects the corresponding UPF network element for EAS, it selects the UPF network element deployed at the same location as the EAS as the UPF network element corresponding to the EAS, ensuring that the EAS and its corresponding UPF network element are deployed at the same location, thereby reducing the delay in the user plane path of the UE-EAS.

[0092] FIG3 is a flow chart of a method for selecting a UPF network element according to an embodiment of the present application. As shown in FIG3 , the method for selecting a UPF network element according to the present application includes the following steps:

[0093] S301: The ECSP management system sends a first request message to the PLMN management system, where the first request message is used to request that a first EAS be connected to a UPF network element.

[0094] If the UE needs to use the edge application service provided by the first EAS, it is necessary to establish a user plane path between the UE-EAS through the UPF network element. In this step, the ECSP management system requests the PLMN management system to select the corresponding UPF network element instance for the first EAS through the first request information. The first request information includes one or more of the deployment location of the first EAS, EAS EDN information and other information.

[0095] It should be noted that the connection of EAS to UPF network element mentioned in this application, the "connection" here means establishing a correspondence between EAS and UPF network element, that is, configuring the address information of its corresponding UPF network element for EAS, and configuring the address information of its corresponding EAS for UPF network element, so as to ensure that subsequent UPF network elements can achieve routing interoperability with EAS.

[0096] S302, the PLMN management system determines the UPF network element corresponding to the first EAS, and the deployment location of the UPF network element corresponding to the first EAS is the same as the deployment location of the first EAS.

[0097] According to step S301, the first request information includes the deployment location of the first EAS, and the PLMN management system can select the UPF network element deployed at the location as the UPF network element corresponding to the first EAS.

[0098] In some implementations, there are multiple optional UPF network elements at the deployment location of the first EAS, and the first request information also includes at least one of the following information: EDN information corresponding to the first EAS, service area information, or N6 traffic routing information. The PLMN management system can select the UPF network element with the highest degree of matching with the first EAS from multiple UPF network elements at the same deployment location based on the above information as the UPF network element corresponding to the first EAS.

[0099] In this embodiment, when the PLMN management system selects a UPF network element for the first EAS, it selects a UPF network element with the same deployment location as the first EAS as the UPF network element corresponding to the first EAS, which can ensure that the first EAS and its corresponding UPF network element are deployed at the same location, thereby reducing the data transmission delay caused by different locations.

[0100] It is understandable that in the embodiment shown in Figure 3, the PLMN management system only selects the UPF network element for the first EAS. To truly establish a user plane path between the UE and the EAS, further configuration and processing are required to establish a corresponding relationship between the EAS and the UPF network element. Figure 4 is a schematic diagram of the process of creating a user plane path according to an embodiment of the present application. As shown in S303 of Figure 4, the PLMN management system configures the association information of the first EAS for the UPF network element corresponding to the first EAS.

[0101] It should be noted that when the UE uses the edge application service provided by the EAS, the UPF network element can connect to the EAS corresponding to the address information through the EAS address information configured in the configuration file. That is, when the PLMN management system configures the EAS association information for the UPF network element, it is equivalent to creating a connection between the UPF and EAS. Therefore, in step S303, the PLMN management system creates a configuration file corresponding to the first EAS for the UPF network element corresponding to the first EAS, and associates the address information of the UPF network element corresponding to the first EAS with the address information of the first EAS in the configuration file. As an example, the IP address of the UPF network element corresponding to the first EAS can be associated with the IP address of the first EAS in the configuration file.

[0102] Considering that the data interaction between the UPF network element and the EAS is a bidirectional data transmission interaction process, it is also necessary to configure the association information of the UPF network element corresponding to the first EAS in the first EAS. After step S303, as shown in S304 in Figure 4, the PLMN management system sends the address information of the UPF network element corresponding to the first EAS to the ECSP management system. In this step, the address information of the UPF network element corresponding to the first EAS can be the IP address and / or ID of the UPF network element.

[0103] As shown in S305 of Figure 4 , the ECSP management system configures the association information of the UPF network element corresponding to the first EAS for the first EAS. Similar to step S303, in this step, the ECSP management system creates a corresponding configuration file for the first EAS, in which the address information of the first EAS is associated with the address information of the UPF network element corresponding to the first EAS, so that the first EAS can transmit data to the UPF network element corresponding to the first EAS during data exchange.

[0104] In the above embodiments, the deployment location of the UPF network element corresponding to the first EAS selected by the PLMN management system is the same as the deployment location of the first EAS, provided that an instantiated UPF network element exists at the deployment location of the first EAS. To ensure this, before the PLMN management system selects the corresponding UPF network element for the first EAS, this application proposes a method for deploying the EAS and a method for deploying the UPF network element.

[0105] FIG5 is a flow chart of a method for deploying a first EAS according to an embodiment of the present application. As shown in FIG5 , the process is executed before the PLMN management system selects a corresponding UPF network element for the first EAS, and specifically includes the following steps:

[0106] In step S501, the ASP sends a first deployment request message to the ECSP management system. The first deployment request message requests the deployment of a first EAS. The first deployment request message includes a desired deployment location of the first EAS.

[0107] The first EAS is an EAS that has not yet been instantiated. The location included in the first deployment request information can be a geographic location, a logical topological location, a data center, or even a computer room. For example, the first EAS's desired deployment location is Area A, where Area A can indicate a specific geographic address. Alternatively, the first deployment request information includes DNAI 1, where DNAI 1 indicates the first data center. Based on the first deployment request information, it can be determined that the first EAS's desired deployment location is the first data center.

[0108] S502: The ECSP management system sends first deployment response information to the ASP, where the first deployment response information is used to indicate that the first EAS is being deployed.

[0109] S503: The ECSP management system sends first deployment instruction information to the PLMN management system. The first deployment instruction information includes a desired deployment location of the first EAS.

[0110] In this step, the ECSP management system sends the desired deployment location of the first EAS to the PLMN management system, so that the PLMN management system selects a suitable deployment location for the first EAS from the candidate locations.

[0111] S504: The PLMN management system determines a first location according to the first deployment indication information and a deployment location of at least one instantiated UPF network element.

[0112] In this embodiment, before the ASP sends the first deployment request information to the ECSP management system, the PLMN management system has already deployed at least one UPF network element. That is, the PLMN management system can determine the deployment location corresponding to at least one instantiated UPF. Similar to the desired deployment location of the first EAS, the location corresponding to the instantiated UPF network element can be a geographical location, a logical topological location, a data center, or even a specific computer room. It will be understood that the "correspondence" relationship between the instantiated UPF network element and the location here means that the UPF network element is deployed at the location indicated in the first deployment instruction information.

[0113] In this step, the PLMN management system needs to determine a deployment location based on the desired deployment location of the first EAS and the location of at least one instantiated UPF network element. This location is the first location. The first location is the location where the first EAS will actually be deployed, and the UPF network element corresponding to the first location is the first UPF network element.

[0114] As an example, the first location can be the location that is closest to the location where the first EAS is expected to be deployed among at least one location that corresponds one-to-one with at least one instantiated UPF network element. If the location here is a geographic location, the geographic distance between at least one location that corresponds one-to-one with at least one instantiated UPF network element and the location where the first EAS is expected to be deployed is calculated respectively. If the location here is a logical topological location, the corresponding distance is calculated according to the meaning of "distance" between logical topological locations. It is understandable that the geographic distance can be calculated between different data centers or different computer rooms.

[0115] For example: the PLMN management system has deployed three UPF network elements, namely UPF 1, UPF 2 and UPF 3, among which UPF 1 is deployed in area A, UPF 2 is deployed in area B, and UPF 3 is deployed in area C. The expected deployment location of the first EAS contained in the first deployment indication information is area A. The PLMN management system calculates the geographical distances between the expected deployment location of the first EAS and area A, area B and area C respectively. It can be determined that area A corresponding to UPF 1 among UPF 1 to UPF 3 is closest to the expected deployment location of the first EAS. Therefore, it can be determined that area A is the first location, and area A is the location where the first EAS will actually be deployed.

[0116] It can be understood that, as shown in the above example, when at least one position corresponding to at least one instantiated UPF network element is the same as the position where the first EAS is expected to be deployed, it can be regarded as a special case with the shortest distance to the position where the first EAS is expected to be deployed, and this position can also be determined as the first position.

[0117] S505: The PLMN management system sends second deployment request information to the ECSP management system, where the second deployment request information requests deployment of a first EAS at a first location.

[0118] After the PLMN management system determines that the actual location corresponding to the first EAS is the first location, it sends the first location to the ECSP management system through the second deployment request information, requesting the deployment of the first EAS at the first location.

[0119] S506: The ECSP management system sends a third deployment request message to the NFVO, where the third deployment request message requests deployment of the first EAS at the first location.

[0120] In this step, the ECSP management system requests the NFVO to allocate and schedule the virtual resources required by the first EAS through the third deployment request information. The virtual resources are the unscheduled virtual resources at the first location, thereby deploying the first EAS at the first location.

[0121] Accordingly, the NFVO returns a second deployment response message to the ECSP management system. The second deployment response message is used to indicate whether the first EAS is successfully instantiated. The ECSP management system passes the second deployment response message to the ASP.

[0122] In the embodiment shown in Figure 5, the first EAS is deployed at the deployment location of the first UPF network element, which can ensure that the UPF network element is present at the deployment location of the first EAS. It is understandable that if the deployment location of the first EAS has been determined, deploying the UPF network element at that location in advance can achieve the same technical effect.

[0123] Figure 6 is a schematic diagram of a process for deploying a UPF network element according to an embodiment of the present application. As shown in Figure 6, the process is executed before the PLMN management system selects the corresponding UPF network element for the first EAS, and specifically includes the following steps:

[0124] S601: The ECSP management system sends second deployment indication information to the PLMN management system, where the second deployment indication information is used to indicate a second location.

[0125] In this step, the first EAS is an instantiated EAS, and the second location indicated in the second deployment indication information is the address where the first EAS is deployed. The location of the first EAS deployment can be a geographic location, a logical topological location, a data center, or even a specific computer room. The second location is communicated to the PLMN management system so that the PLMN management system can determine the deployment location for the second UPF network element.

[0126] S602: The PLMN management system determines to deploy the second UPF network element at the second location according to the second deployment indication information.

[0127] Among them, there is no second UPF network element at the expected deployment location. Therefore, in order to ensure that there is a co-deployed UPF network element at the deployment location of the first EAS, the PLMN management system can directly determine the deployment location of the first EAS as the location where the second UPF network element is to be deployed after receiving the second deployment indication information.

[0128] S603: The PLMN management system sends a fourth deployment request message to the NFVO, where the fourth deployment request message requests deployment of a second UPF network element at a second location.

[0129] In this step, the PLMN management system requests the NFVO to allocate and schedule the virtual resources required for the second UPF network element through the fourth deployment request information. The above virtual resources are the unscheduled virtual resources at the second location, thereby deploying the second UPF network element at the second location.

[0130] Accordingly, the NFVO returns a third deployment response message to the PLMN management system, where the third deployment response message is used to indicate whether the second UPF network element is successfully instantiated.

[0131] It can be understood that deploying the second UPF network element at the second position is actually reserving the second UPF network element as the UPF network element corresponding to the first EAS.

[0132] Through the method of deploying the first EAS according to the deployment location of the instantiated UPF network element in the above embodiments, or the method of deploying the UPF network element according to the deployment location of the first EAS, it is possible to ensure that the UPF network element exists at the deployment location of the first EAS before the PLMN management system selects the corresponding UPF network element for the first EAS.

[0133] It should be noted that the SA6 standard defines a two-level discovery mechanism. Before creating the user plane path between UE and EAS, the UE first needs to request its corresponding EES from ECS through EEC, that is, discover the EES platform from ECS. Since EAS is registered on EES, EES can match the information of the applications registered on it, thereby discovering the specific application that the UE needs to access through EES, that is, discovering EAS from the EES platform. Only through the above two-level discovery mechanism can the UE discover the EAS it expects to access. Once the EAS is registered with the EES platform, even if the EAS is not instantiated, the above discovery mechanism can still discover the EAS information that is not instantiated on the EES platform.

[0134] In the above discovery process, the UE realizes data interaction through the UPF network element corresponding to the EES. Therefore, after discovering the EAS to be accessed by the UE through the EES, when establishing the user plane path between the UE and the EAS, the user plane path must include the UPF network element corresponding to the EES. The "correspondence" relationship between the EES and the UPF network element here means that when the UE discovers the EAS service through the EES, a two-level discovery process is implemented through the UPF network element corresponding to the EES.

[0135] In the embodiment shown in Figure 3, when the PLMN management system selects a UPF network element for the first EAS, it only considers the deployment location of the UPF network element and does not consider the EES registered with the first EAS. This results in the UPF network element corresponding to the first EAS and the UPF network element corresponding to the EES registered with the first EAS possibly not being the same UPF network element. When the UE uses the application service provided by the first EAS, even if the first EAS and its corresponding UPF network element are deployed at the same location, there may still be transit transmission between different UPF network elements in the user plane path between the UE and the EAS. Different UPF network elements transmit data through the N6 interface, which increases the N6 latency between the UE and the EAS.

[0136] For example, Figure 7 is a schematic diagram of the access of different UPF network elements corresponding to EES and EAS. As shown in Figure 7, EES1 and EAS1 are both deployed in the data center identified as DNAI 1, and EAS1 corresponds to EES1. Among them, the UPF network element corresponding to EES1 is UPF 1, and the UPF network element corresponding to EAS1 is UPF 2. UPF 1 and UPF 2 are different UPF instances. Due to the two-level discovery mechanism, the UE first discovers EES1, and then discovers EAS1 registered on EES1 through EES1. Therefore, the user plane path between UE and EAS1 is UE-RAN-UPF1-UPF 2-EAS1. Obviously, the optimal user plane path between UE and EAS1 is UE-RAN-UPF 2-EAS1. However, the path shown in Figure 7 contains a transit path of UPF 1-UPF 2, which increases the N6 delay between UE and EAS1, affecting the user experience when UE accesses EAS1.

[0137] In a certain implementation, UPF 1 and EAS1 can be connected through at least one router. The UE is connected to EES1 through RAN and UPF 1. When the UE needs to connect to EAS1, the UE may need to connect to EAS through RAN, UPF 1 and at least one router. At this time, a delay of at least one router forwarding will be introduced between UPF and EAS.

[0138] To address this technical issue, the UPF network element selection method proposed in this application determines a common UPF network element for the first EAS and the EES with which the first EAS is registered. In the embodiment shown in Figure 5 , the first EAS is registered with the first EES, meaning that the first EAS is associated with the first EES. In this embodiment, deploying the first EAS at the first location effectively predestines the first UPF network element corresponding to the first location as the UPF network element corresponding to the first EAS.

[0139] Therefore, the PLMN management system needs to configure the first access information for the first UPF network element. Configuring the first access information is equivalent to creating a configuration file corresponding to the first EES for the first UPF network element. Associating the address information of the first UPF network element with the address information of the first EES in the configuration file is equivalent to indicating that the EES corresponding to the first UPF network element is the first EES. The address information of the first UPF network element and the address information of the first EES associated with each other in the configuration file indicate the connection relationship between the first UPF network element and the first EES.

[0140] In some implementations, the ECSP management system may create a configuration file corresponding to the first UPF network element for the first EES, and associate the address information of the first EES with the address information of the first UPF network element in the configuration file, thereby establishing a connection relationship between the first UPF network element and the first EES.

[0141] Through the above implementation, the UPF network element corresponding to the first EES can be determined as the first UPF network element, thereby ensuring that the UPF network element corresponding to the first EAS and the UPF network element corresponding to the EES associated with the first EAS are the same UPF network element. Based on the co-deployment of the first EAS and the first UPF network element at the same location, an optimal user plane path is created between the UE and the first EAS, avoiding the transit of the UPF network element, and further reducing the N6 delay between the EAS and the UPF network element.

[0142] Similarly, in the embodiment shown in FIG6 , the first EAS is associated with the first EES. In this embodiment, the second UPF network element is deployed at the second position, which actually means that the second UPF network element is reserved as the UPF network element corresponding to the first EAS.

[0143] Accordingly, considering that the second UPF network element may not be the UPF network element corresponding to the first EES, the PLMN management system configures second access information for the second UPF network element. Configuring the second access information is equivalent to creating a configuration file corresponding to the first EES for the second UPF network element. Associating the address information of the second UPF network element with the address information of the first EES in the configuration file is equivalent to indicating that the EES corresponding to the second UPF network element is the first EES. The address information of the second UPF network element and the address information of the first EES associated with each other in the configuration file indicate the connection relationship between the second UPF network element and the first EES.

[0144] In some implementations, the ECSP management system creates a configuration file corresponding to the second UPF network element for the first EES, and associates the address information of the first EES with the address information of the second UPF network element in the configuration file, thereby establishing a connection relationship between the second UPF network element and the first EES.

[0145] As a possible implementation method, on the premise that the UPF network element exists at the deployment location of the first EAS through the embodiment shown in Figure 5 or the embodiment shown in Figure 6, the first request information in the embodiment shown in Figure 3 can also include first information, and the first information is used to indicate the UPF network element corresponding to the first EES.

[0146] According to the above embodiments, the network management system configures the IP address of the UPF network element corresponding to the first EES and / or the ID of the UPF network element corresponding to the first EES when creating the connection between EES and UPF. That is, the IP address of the UPF network element corresponding to the first EES and / or the ID of the UPF network element corresponding to the first EES are associated with the address of the first EES. Therefore, the corresponding UPF network element can be determined through the address information of the first EES.

[0147] In some implementations, as an example, the first information may indicate the address information of the first EES. Since the address information of the first EES is associated with the IP address of its corresponding UPF network element and / or the ID of its corresponding UPF network element, the IP address of the UPF network element corresponding to the first EES and / or the ID of the UPF network element corresponding to the first EES can be determined based on the address information of the first EES. Each UPF network element has a unique IP address or ID, and a unique UPF network element can be determined based on the IP address and / or ID of the UPF network element corresponding to the first EES. In this implementation, the first information does not explicitly indicate the UPF network element corresponding to the first EES, but the UPF network element corresponding to the first EES can be determined based on the address information of the corresponding first EES. The first information implicitly indicates the UPF network element corresponding to the first EES to the PLMN management system.

[0148] In some implementations, the ECSP management system determines the corresponding UPF network element based on the address information of the first EES. The IP address and / or ID of the UPF network element can be directly indicated in the first information, thereby explicitly indicating the UPF network element corresponding to the first EES to the PLMN management system.

[0149] Since the deployment location of the UPF network element corresponding to the first EES is the same as the deployment location of the first EAS, the PLMN management system can directly determine the UPF network element indicated in the first information as the UPF network element corresponding to the first EAS based on the first information. In this implementation, the UPF network element corresponding to the first EAS and the UPF network element corresponding to the first EES are the same UPF network element, which can establish an optimal user plane path between the UE and the EAS. At the same time, it also ensures that the first EAS and its corresponding UPF network element are deployed in the same location, which can avoid transmission delays caused by different deployment locations.

[0150] It should be noted that, if the sole purpose is to ensure that the user plane path between the UE and the EAS is the optimal path, then upon receiving the first request from the ECSP management system, the PLMN management system only needs to ensure that the UPF network element corresponding to the first EAS is the same as the UPF network element corresponding to the EES registered with the first EAS. The UPF network element corresponding to the EES registered with the first EAS may not be deployed in the same location as the first EAS. The following describes a method for establishing a separate optimal user plane path between the UE and the EAS.

[0151] FIG8 is a flow chart of a method for selecting a UPF network element according to another embodiment of the present application. As shown in FIG8 , the method for selecting a UPF network element according to this embodiment includes the following steps:

[0152] S801: The ECSP management system sends a first request message to the PLMN management system, where the first request message is used to request that a first EAS be connected to a UPF network element.

[0153] In this step, the first request message includes first information indicating the UPF network element corresponding to the first EES. The first EES is the EES platform with which the first EAS is registered. It should be understood that prior to step S801, the ECSP management system had already requested the NFVO to deploy the first EES and, through the PLMN management system, selected the corresponding UPF network element for the first EES. Furthermore, the ECSP management system also requested the NFVO to deploy the first EAS and register the first EAS with the first EES.

[0154] Among them, the first information is used to indicate the first UPF. As a possible implementation method, the "indication" here can be an implicit indication, that is, the first information indicates the information of the first EES. As an example, the first information can indicate the first EES ID and / or the address information of the first EES. Since the first EES ID and / or the address information of the first EES are associated with the IP address of its corresponding UPF network element and / or the ID of its corresponding UPF network element, the PLMN management system can determine the IP address of the UPF network element corresponding to the first EES and / or the ID of the UPF network element corresponding to the first EES through this implicit indication.

[0155] In another possible implementation, the first information may explicitly indicate the UPF network element corresponding to the first EES, that is, the first information directly indicates the IP address and / or ID of a UPF network element. The above ID and / or IP address of the UPF network element is determined by the ECSP management system based on the information of the first EES, and the UPF network element is the UPF network element corresponding to the first EES.

[0156] S802: The PLMN management system determines the UPF network element indicated by the first information as the UPF network element corresponding to the first EAS.

[0157] According to step S801, the first information included in the first request information explicitly or implicitly indicates a UPF network element. When the first information implicitly indicates a UPF network element, the PLMN management system can determine a UPF network element based on the first EES ID and / or the address information of the first EES in the first information and use it as the UPF network element corresponding to the first EAS.

[0158] When the first information indicates the UPF network element in a displayed manner, the PLMN management system can directly determine a UPF network element based on the IP address of the UPF network element and / or the ID of the UPF network element in the first information, and use it as the UPF network element corresponding to the first EAS.

[0159] In this embodiment, no matter whether the first information indicates the UPF network element in an explicit or implicit manner, the UPF network element must be the UPF network element corresponding to the first EES.

[0160] S803, the PLMN management system configures the association information of the first EAS for the UPF network element corresponding to the first EES.

[0161] To connect the first EAS to the UPF network element corresponding to the first EES, it is necessary to establish a corresponding relationship between the first EAS and the UPF network element corresponding to the first EES. Therefore, in this step, the PLMN management system creates a configuration file corresponding to the first EAS for the UPF network element corresponding to the first EES, and associates the address information of the UPF network element corresponding to the first EES with the address information of the first EAS in the configuration file.

[0162] S804: The PLMN management system sends the address information of the UPF network element corresponding to the first EES to the ECSP management system.

[0163] S805: The ECSP management system configures association information of the UPF network element corresponding to the first EES for the first EAS.

[0164] Similar to step S803, in this step, the ECSP management system creates a corresponding configuration file for the first EAS, in which the address information of the first EAS is associated with the address information of the UPF network element corresponding to the first EES, so that the first EAS can transmit data to the UPF network element corresponding to the first EES during the data interaction process.

[0165] In this embodiment, the UPF network element corresponding to the first EES is used as the UPF network element corresponding to the first EAS, ensuring that the first EAS and the UPF network element corresponding to the associated first EES are the same UPF network element, thereby obtaining the optimal user plane path between the UE and the EAS, and reducing the communication delay during data interaction between the UE and the first EAS. The PLMN management system selects the UPF network element corresponding to the first EES as the UPF network element corresponding to the first EAS on the premise that the UPF network element can match the service requirements of the first EAS. Taking into account the N6 delay between the UE and the EAS, the first EAS requires that the geographical distance between the deployment location of the UPF network element corresponding to the first EES and the deployment location of the first EAS cannot exceed a preset threshold. If the geographical distance between the first EAS and the UPF network element exceeds the preset threshold, the N6 delay between the first EAS and its corresponding UPF network element cannot meet the requirements for data interaction between the UE and the EAS. Therefore, in the embodiment shown in FIG8 , the distance between the UPF network element corresponding to the first EES and the first EAS is less than or equal to a preset threshold, and the PLMN management system determines the UPF network element corresponding to the first EES as the UPF network element corresponding to the first EAS.

[0166] When the distance between the UPF network element corresponding to the first EES and the first EAS is greater than a preset threshold, the PLMN management system needs to select a new UPF network element for the first EAS. Figure 9 is a flowchart of a UPF network element selection method provided in another embodiment of the present application. Step S901 shown in Figure 9 is consistent with step S801 in the embodiment shown in Figure 8. The ECSP management system first requests the PLMN management system to connect the first EAS to the UPF network element through a first request message. The difference is that:

[0167] S902. The PLMN management system determines a first UPF network element based on the second information, and determines the first UPF network element as the UPF network element corresponding to the first EAS.

[0168] In the embodiment shown in FIG9 , the first request information further includes second information, and the second information includes at least one of the following information: EDN information corresponding to the first EAS, service area information, or N6 traffic routing information.

[0169] Therefore, in this step, when the distance between the UPF network element corresponding to the first EES and the first EAS is greater than the preset threshold, it indicates that the UPF network element cannot match the service requirements of the first EAS. The PLMN management system reselects a UPF network element for the first EAS based on the second information. The UPF determined based on the second information is the first UPF network element. The PLMN management system determines that the first UPF network element is the UPF network element corresponding to the first EAS.

[0170] It should be noted that, as an integral part of the edge application architecture, the UPF network element, like the EES and EAS, is a software-defined network function, or VNF. Similar to the uninstantiated EAS on the EES platform, the PLMN management system can discover uninstantiated UPF network elements. Therefore, in step S602, the first UPF network element determined by the PLMN management system based on the second information may be an uninstantiated UPF network element.

[0171] When establishing the user plane path between UE and EAS, the UPF network element must be an instantiated UPF network element. In some implementations, when the first UPF network element determined by the PLMN management system is not instantiated, the NFVO is required to allocate and schedule the virtual resources required by the first UPF network element, specifically:

[0172] S903-1. The PLMN management system sends a response message to the ECSP management system. The response message is used to indicate that the first UPF network element is being instantiated.

[0173] S903-2. The PLMN management system sends a second request message to the NFVO, where the second request message requests deployment of the first UPF network element.

[0174] Through the above steps, the second request information triggers NFVO to allocate and schedule the resources required for the instantiation of the first UPF network element. When all the virtual deployment units required by the first UPF network element are deployed, the instantiation of the first UPF network element is completed, so that it can be used to establish the user plane path between UE-EAS.

[0175] S904, the PLMN management system configures first access information for the first UPF network element, and the first access information indicates that the EES corresponding to the first UPF network element is the first EES.

[0176] According to step S902, the UPF network element corresponding to the current first EES is not the first UPF network element. When the PLMN management system determines that the UPF network element corresponding to the first EAS is the first UPF network element based on the second information, in order to ensure that the UPF network element corresponding to the first EAS and the first EES are the same UPF network element, the UPF network element corresponding to the first EES needs to be updated to the first UPF network element.

[0177] Therefore, in this step, the PLMN management system configures the first access information for the first UPF network element. Configuring the first access information is equivalent to creating a configuration file corresponding to the first EES for the first UPF network element. Associating the address information of the first UPF network element with the address information of the first EES in the configuration file is equivalent to indicating that the EES corresponding to the first UPF network element is the first EES. The address information of the first UPF network element and the address information of the first EES associated with each other in the configuration file indicate the connection relationship between the first UPF network element and the first EES.

[0178] In some implementations, a configuration file corresponding to the first UPF network element needs to be configured for the first EES in the first EES. Therefore, the embodiment shown in FIG9 further includes step S905:

[0179] S905: The PLMN management system sends a third request message to the ECSP management system, where the third request message requests to establish a connection relationship between the first EES and the first UPF network element.

[0180] Among them, the third request information includes the address information of the first UPF network element, and the address information of the first UPF network element is used to indicate the IP address of the first UPF network element and / or the ID of the first UPF network element. Since the third request information requests to establish a connection relationship between the first EES and the first UPF network element, the ECSP management system triggers the creation of a configuration file corresponding to the first UPF network element for the first EES after receiving the third request information. In the configuration file, the address information of the first EES is associated with the address information of the first UPF network element, thereby establishing a connection relationship between the first UPF network element and the first EES.

[0181] In the above steps S904 and S905, when the UPF network element corresponding to the first EES cannot match the service requirements of the first EAS, the PLMN management system selects the first UPF network element for the first EAS based on the second information. Since the first EAS is registered on the first EES, it is necessary to recreate the connection relationship between the first UPF network element and the first EES.

[0182] It should be noted that EES, EAS, and UPF network elements all have their own corresponding service areas. When the distance between the UPF network element corresponding to the first EES and the first EAS exceeds the preset threshold and cannot match the business needs of the first EAS, it means that the service area of ​​the UPF network element cannot match the service area of ​​the first EAS. Since the first UPF network element is a new UPF network element selected by the PLMN management system for the first EAS based on the second information, the service area of ​​the first UPF network element must match the service area of ​​the first EAS. However, the service area of ​​the first UPF network element selected by the PLMN management system may not match the service area of ​​the first EES. When the service area of ​​the first UPF network element cannot match the service area of ​​the first EES, even after the connection between the first UPF network element and the first EES is rebuilt, the first EAS registered on the first EES will not be found.

[0183] In some implementations, when the service area of ​​the first UPF network element does not include the service area of ​​the first EES, the second EES can be determined based on the service area of ​​the first UPF network element, and the service area of ​​the second EES is included in the service area of ​​the first UPF network element.

[0184] It is understandable that when the service area of ​​the first UPF network element does not include the service area of ​​the first EES, the service area of ​​the first UPF network element and the service area of ​​the first EES are completely incompatible, so a new EES needs to be determined. The second EES is an EES determined based on the service area of ​​the first UPF network element, and the service area of ​​the second EES is included in the service area of ​​the second UPF. Therefore, the service area of ​​the second EES can match the service area of ​​the first UPF network element. Obviously, the role of the second EES is to replace the first EES in the embodiment shown in Figure 9.

[0185] Therefore, the ECSP management system first needs to request the PLMN management system to connect the second EES to the first UPF network element. Similar to step S904, the PLMN management system configures second access information for the second EES. The second access information is used to indicate that the EES corresponding to the first UPF network element is the second EES. Configuring the second access information is equivalent to creating a configuration file corresponding to the second EES for the first UPF network element. The configuration file associates the address information of the first UPF network element with the address information of the second EES. The associated address information of the first UPF network element and the address information of the second EES in the configuration file indicates the connection relationship between the first UPF network element and the second EES.

[0186] Similarly, in some implementations, a configuration file corresponding to the first UPF network element needs to be configured for the second EES in the second EES. Therefore, the PLMN management system sends a fourth request message to the ECSP management system, requesting the establishment of a connection relationship between the second EES and the first UPF network element. Similar to step S905, the fourth request message includes address information of the first UPF network element, where the address information of the first UPF network element indicates the IP address and / or ID of the first UPF network element. After receiving the fourth request message, the ECSP management system can trigger the creation of a configuration file corresponding to the first UPF network element for the second EES. The ECSP management system associates the address information of the second EES with the address information of the first UPF network element in the configuration file corresponding to the first UPF network element, thereby establishing a connection relationship between the first UPF network element and the second EES.

[0187] Considering that the first EAS is registered on the first EES, that is, the EES associated with the first EAS is still the first EES, the PLMN management system also needs to send a fifth request message to the ECSP management system. The fifth request message requests that the EES registered with the first EAS be updated to the second EES. After receiving the fifth request message, the ECSP management system sends a sixth request message to the NFVO. The sixth request message requests that the EES associated with the first EAS be updated to the second EES.

[0188] When the NFVO instantiates the EAS, it writes the address information of the EES associated with the EAS into the EAS configuration information. When the first EAS is registered on the first EES, the configuration information of the first EAS includes the address information of the first EES. Therefore, if you want to register the first EAS with a different EES, you need to update the address information of the EES in the first EAS configuration information through the NFVO. Because the UPF network element selected by the PLMN management system for the first EAS is the first UPF network element, after establishing the connection relationship between the first UPF network element and the second EES, the NFVO updates the address information of the EES associated with the first EAS to the address information of the second EES based on the sixth request information, so that the EES associated with the first EAS is changed from the first EES to the second EES, that is, the first EAS is registered with the second EES.

[0189] Correspondingly, the NFVO returns modification indication information to the ECSP management system, where the modification indication information is used to indicate whether the address information of the EES associated with the first EAS is successfully modified.

[0190] By modifying the EES platform information registered with the first EAS, the UE is ensured to directly interact with the first EAS through the first UPF network element selected by the PLMN management system, ensuring the optimal user plane path between the UE and the first EAS and shortening the communication delay.

[0191] It should be noted that the second EES determined based on the service area of ​​the first UPF network element may also be an EES that has not yet been instantiated. In some implementations, when the second EES is not deployed, the PLMN management system sends a seventh request message to the ECSP management system. The seventh request message is used to request the deployment of the second EES. The deployment process of the second EES is not further described here.

[0192] As shown in step S902 of FIG9 , the PLMN management system determines that the first UPF network element is the UPF network element corresponding to the first EAS based on the second information. Similar to the embodiment shown in FIG3 , in the embodiment shown in FIG9 , a user plane path between the UE and the EAS is not actually established. Therefore, in the above implementation, regardless of whether it is necessary to modify the EES associated with the first EAS, the subsequent process needs to refer to the embodiment shown in FIG8 , respectively configuring a configuration file corresponding to the first EAS in the first UPF network element, configuring a configuration file corresponding to the first UPF network element in the first EAS, and associating the address information of the first EAS with the address information of the first UPF network element, thereby establishing a connection between the first EAS and the first UPF network element.

[0193] In this embodiment, when the UPF network element corresponding to the EES associated with the first EAS cannot match the service requirements of the first EAS, the PLMN management system selects a new UPF network element for the first EAS based on the second information, and adaptively adjusts the EES associated with the first EAS to ensure that the user plane path between the UE and the first EAS is the optimal user plane path, thereby reducing the N6 delay.

[0194] Figure 10 is a structural diagram of a user plane function network element selection device provided by an embodiment of the present application. As shown in Figure 10, the device 1000 of this embodiment may include: a communication module 1001 and a processing module 1002. It should be understood that the device 1000 is embodied in the form of a functional module. The term "module" may refer to a software module, or may refer to an application-specific integrated circuit, an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions.

[0195] The apparatus 1000 has the function of implementing the corresponding processes and / or steps in the above method embodiments; the above functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0196] Figure 11 is a schematic diagram of the structure of a user plane function network element selection device provided by another embodiment of the present application. The device 1100 shown in Figure 11 can be used to execute any of the aforementioned methods executed by the network management system.

[0197] As shown in Figure 11 , the apparatus 1100 of this embodiment includes a memory 1101, a processor 1102, a communication interface 1103, and a bus 1104. The memory 1101, the processor 1102, and the communication interface 1103 are connected to each other via the bus 1104.

[0198] The memory 1101 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1101 may store a program. When the program stored in the memory 1101 is executed by the processor 1102, the processor 1102 is configured to execute any of the aforementioned methods.

[0199] The processor 1102 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit, or one or more integrated circuits to execute related programs.

[0200] The processor 1102 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, the various related steps in the embodiment of the present application may be completed by hardware integrated logic circuits in the processor 1102 or software instructions.

[0201] The processor 1102 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 1102 may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor.

[0202] The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented as being executed by a hardware decoding processor, or can be implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1101, and processor 1102 reads the information in memory 1101 and, in combination with its hardware, completes the functions required to be performed by the units included in the device of the present application.

[0203] The communication interface 1103 may use, but is not limited to, a transceiver or other transceiver device to implement communication between the apparatus 1100 and other devices or apparatuses.

[0204] The bus 1104 may include a path for transmitting information between various components of the device 1100 (eg, the memory 1101 , the processor 1102 , and the communication interface 1103 ).

[0205] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When a processor executes the computer instructions, each step of the method in the above embodiment is implemented.

[0206] An embodiment of the present application further provides a computer program product, including computer instructions, which, when executed by a processor, implement the various steps of the method in the above embodiment.

[0207] It should be noted that the modules or components shown in the above embodiments may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays. For another example, when a module is implemented by a processing element calling program code, the processing element may be a general-purpose processor, such as a central processing unit or other processor that can call program code, such as a controller. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0208] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, software modules or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0209] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the contents disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0210] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A user plane function network element selection method, applied to a public land mobile network PLMN management system, characterized in that: The method comprises: Receiving a first request message from an edge computing service provider (ECSP) management system, wherein the first request message requests to connect a first edge application server (EAS) to a user plane function (UPF) network element; Determine the UPF network element corresponding to the first EAS, and the deployment location of the UPF network element corresponding to the first EAS is the same as the deployment location of the first EAS.

2. The method according to claim 1, characterized in that Before receiving the first request information from the edge computing service provider ECSP management system, the method further includes: receiving first indication information from the ECSP management system, where the first indication information indicates a location where the first EAS is expected to be deployed; Determine a first position according to at least one position corresponding to the first indication information and at least one UPF network element; A second request message is sent to the ECSP management system, wherein the second request message requests to deploy the first EAS at the first location.

3. The method according to claim 2, characterized in that The first position is the same position as the position where the first EAS is expected to be deployed among at least one position corresponding to the at least one UPF network element, or the first position is the position that is closest to the position where the first EAS is expected to be deployed among at least one position corresponding to the at least one UPF network element.

4. The method according to claim 2 or 3, characterized in that: After sending the second request information to the ECSP management system, the method further includes: Configure first access information, wherein the first access information indicates that the EES corresponding to the first UPF network element is the EES registered with the first EAS, and / or send a third request information to the ECSP management system, wherein the third request information requests to create a connection relationship between the EES registered with the first EAS and the first UPF network element, and the first UPF network element is the UPF network element corresponding to the first position.

5. The method according to claim 1, characterized in that Before receiving the first request information from the edge computing service provider ECSP management system, the method further includes: receiving second indication information from the ECSP management system, where the second indication information indicates a second location, where the second location is a location where the first EAS is deployed; According to the second indication information, a fourth request information is sent to the network function virtualization orchestrator NFVO, and the fourth request information requests to deploy a UPF network element at the second location.

6. The method according to claim 5, characterized in that After sending fourth request information to the network function virtualization orchestrator NFVO according to the second indication information, the method further includes: Configure second access information, wherein the second access information indicates that the EES corresponding to the second UPF network element is the EES registered with the first EAS, and / or send a fifth request information to the ECSP management system, wherein the fifth request information requests to create a connection relationship between the EES registered with the first EAS and the second UPF network element, and the second UPF network element is the UPF network element corresponding to the second position.

7. The method according to claim 4 or 6, characterized in that: The first request information includes first information, where the first information indicates a UPF network element corresponding to a first edge enabling server EES, where the first EES is an EES registered with the first EAS; The determining of the UPF network element corresponding to the first EAS includes: The UPF network element indicated by the first information is determined as the UPF network element corresponding to the first EAS.

8. A user plane function network element selection method, applied to a PLMN management system, characterized in that: The method comprises: Receiving a first request message from an ECSP management system, wherein the first request message requests to connect a first EAS to a UPF network element; Determine the UPF network element corresponding to the first EAS, wherein the UPF network element corresponding to the first EAS is the same as the UPF network element corresponding to the EES registered with the first EAS.

9. The method according to claim 8, characterized in that The first request information includes first information, where the first information indicates a UPF network element corresponding to a first EES, where the first EES is an EES registered with the first EAS; The determining of the UPF network element corresponding to the first EAS includes: The UPF network element indicated by the first information is determined as the UPF network element corresponding to the first EAS.

10. The method according to claim 9, characterized in that The first request information further includes second information, and the second information includes at least one of the following information: edge data network EDN information, service area information, or N6 traffic routing information of the first EAS; Wherein, when the distance between the UPF network element indicated by the first information and the first EAS is greater than a preset threshold, the method further includes: Determine a first UPF network element based on the second information; Determine the first UPF network element as the UPF network element corresponding to the first EAS; Configure first access information, wherein the first access information indicates that the EES corresponding to the first UPF network element is the first EES, and / or send second request information to the ECSP management system, wherein the second request information requests to establish a connection relationship between the first EES and the first UPF network element.

11. The method according to claim 10, characterized in that The method further comprises: When the first UPF network element is not deployed, a third request message is sent to the NFVO, wherein the third request message requests deployment of the first UPF network element.

12. The method according to claim 10 or 11, characterized in that: When the service area of ​​the first UPF network element does not include the service area of ​​the first EES, the method further includes: Determine a second EES according to the service area of ​​the first UPF network element, wherein the service area of ​​the second EES is included in the service area of ​​the first UPF network element; configuring second access information, where the second access information indicates that the EES corresponding to the first UPF network element is the second EES, and / or sending fourth request information to the ECSP management system, where the fourth request information requests to establish a connection relationship between the second EES and the first UPF network element; Sending a fifth request message to the ECSP management system, wherein the fifth request message requests to update the EES registered with the first EAS to the second EES.

13. The method according to claim 12, characterized in that The method further comprises: When the second EES is not deployed, sixth request information is sent to the ECSP management system, where the sixth request information requests deployment of the second EES.

14. A user plane function network element selection method, applied to an ECSP management system, characterized in that: The method comprises: A first request message is sent to a PLMN management system, wherein the first request message requests to connect the first EAS to a UPF network element.

15. The method according to claim 14, characterized in that Before sending the first request information to the PLMN management system, the method further includes: receiving a second request message from an application service provider ASP, wherein the second request message requests the deployment of the first EAS, and the second request message includes second information, wherein the second information indicates a location where the first EAS is expected to be deployed; Sending first indication information to the PLMN management system, where the first indication information indicates a location where the first EAS is expected to be deployed; Receive a third request message from the PLMN management system, wherein the third request message requests deployment of the first EAS at a first location, wherein the first location is the same location as the location where the first EAS is expected to be deployed among at least one location in a one-to-one correspondence between at least one UPF network element, or the first location is the location that is closest to the location where the first EAS is expected to be deployed among at least one location in a one-to-one correspondence between at least one UPF network element.

16. The method according to claim 15, characterized in that After receiving the third request information from the PLMN management system, the method further includes: receiving a fourth request message from the PLMN management system, wherein the fourth request message requests to establish a connection relationship between the EES registered with the first EAS and a first UPF network element, wherein the first UPF network element is a UPF network element corresponding to the first location; Configure the first access information, wherein the first access information indicates that the UPF network element corresponding to the EES registered with the first EAS is the first UPF network element.

17. The method according to claim 14, characterized in that Before sending the first request information to the PLMN management system, the method further includes: Sending second indication information to the PLMN management system, where the second indication information indicates a second location, where the second location is a location where the first EAS is deployed.

18. The method according to claim 17, characterized in that After sending the second indication information to the PLMN management system, the method further includes: receiving a fifth request message from the PLMN management system, wherein the fifth request message requests to establish a connection relationship between the EES registered with the first EAS and a second UPF network element, where the second UPF network element is a UPF network element corresponding to the second location; Configure the second access information, wherein the second access information indicates that the UPF network element corresponding to the EES registered with the first EAS is the second UPF network element.

19. The method according to claim 14, characterized in that The first request information includes first information, and the first information indicates the UPF network element corresponding to the first EES, and the first EES is the EES registered with the first EAS.

20. The method according to claim 19, characterized in that The method further comprises: receiving a sixth request message from the PLMN management system, wherein the sixth request message requests to establish a connection relationship between the first EES and a third UPF network element, wherein the third UPF network element is a UPF network element corresponding to the first EAS; Configure the third access information, and the third access information indicates that the UPF network element corresponding to the first EES is the third UPF network element.

21. The method according to claim 19, characterized in that The method further comprises: receiving a seventh request message from the PLMN management system, wherein the seventh request message requests to establish a connection relationship between a second EES and a third UPF network element, wherein the third UPF network element is a UPF network element corresponding to the first EAS, and the second EES is an EES determined according to a service area of ​​the third UPF network element; Configure fourth access information, where the fourth access information indicates the UPF network element corresponding to the second EES and the third UPF network element; receiving an eighth request message from the PLMN management system, wherein the eighth request message requests to update the EES registered with the first EAS to the second EES; A ninth request message is sent to the NFVO, wherein the ninth request message requests to update the EES registered with the first EAS to the second EES.

22. The method according to claim 21, characterized in that Before receiving the seventh request information from the PLMN management system, the method further includes: receiving a tenth request message from the PLMN management system, the tenth request message requesting deployment of the second EES; An eleventh request message is sent to the NFVO, where the eleventh request message requests to deploy the second EES.

23. A user plane function network element selection device, characterized in that: The user plane function network element selection device includes a functional module for implementing the user plane function network element selection method as described in any one of claims 1 to 8, or any one of 8 to 13, or any one of 14 to 22.

24. A user plane function network element selection device, characterized in that: include: Processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the user plane function network element selection device performs the user plane function network element selection method as described in any one of claims 1 to 7, or any one of 8 to 13, or any one of 14 to 22.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the user plane function network element selection method as described in any one of claims 1 to 7, or any one of 8 to 13, or any one of 14 to 22.

26. A computer program product, characterized in that It includes a computer program, which, when executed by a processor, implements the user plane function network element selection method as described in any one of claims 1 to 7, or any one of claims 8 to 13, or any one of claims 14 to 22.

Images