A method and device for determining MEC access points

Abstract

The present application discloses a method and apparatus for selecting an MEC access point, relating to the field of communications, and enabling determination of an optimally distributed MEC access point for a terminal group user relative to their location, thereby improving service quality. The specific solution is as follows: a first network element obtains a first MEC access point for access by a terminal group supporting a first service, where the first MEC access point is obtained based on at least network topology information of the MEC access point closest to each terminal in the terminal group that supports the first service; the first network element sends an identifier of the first MEC access point to a session management network element that controls each terminal, for each terminal in the group to access the first MEC access point.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a method and apparatus for determining a multi-access edge computing (MEC) access point. Background Art

[0002] Fifth-generation mobile communication (5G) networks require lower latency and greater decentralization. Multi-access edge computing (MEC) technology can effectively meet these requirements. The basic concept of MEC is to migrate the cloud computing platform from the mobile core network to the edge of the mobile access network to achieve flexible utilization of computing and storage resources. MEC servers can be regarded as cloud servers running at the edge of the mobile network, performing specific tasks.

[0003] When deploying MEC scenarios in 5G networks, it is necessary to deploy small-scale or portable data centers at the edge of the network, called MEC servers, to perform local processing of terminal requests. This helps to achieve application localization, content distribution, and edge computing to meet ultra-low latency requirements.

[0004] To better leverage edge computing capabilities, 5G edge computing draws on the European Telecommunications Standards Institute (ETSI)'s reference architecture for edge computing. The user plane function (UPF) serves as the data plane anchor, making it a key point of convergence between ETSI and the 3rd Generation Partnership Project (3GPP). In 5G edge computing, the edge computing platform (i.e., MEC server) implements the functions of the data network (DN) and AF.

[0005] In the MEC scenario, when it is decided to enable the MEC server to provide services for user equipment (UE) or the MEC server providing services changes after the UE location changes or the service changes, the network side AF selects the data network access identifier (DNAI) corresponding to the MEC server that supports the relevant service as the access point of the UE, and the SMF starts the DNAI change process, inserts a branch point to the UPF corresponding to the selected DNAI in the PDU session of the UE, and realizes the connection or path adjustment from the UE to the MEC server.

[0006] For terminal group users, in order to ensure their service quality, AF will select the same DNAI as the access point for each UE in the terminal group. Currently, AF selects DNAI according to the Internet protocol (IP) address of the UE in the group. Therefore, the DNAI selected by AF may not be optimal for the location of the group user, causing the UE to access a non-optimal MEC server, affecting service quality. Summary of the Invention

[0007] The present application provides a method, device, and system for determining MEC access points, which enable selection of MEC access points with optimal location distribution relative to terminal group users to improve service quality.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a method for determining an MEC access point is provided. The method may include: a first network element obtaining a first MEC access point to which a terminal group for a first service accesses, the first MEC access point being obtained based on at least, for example, network topology information of a MEC access point closest to each terminal in the terminal group that supports the first service; the network topology information being used to indicate whether at least two MEC access points are connected, and / or the network topology information being used to indicate link performance between at least two MEC access points; the first network element sending an identifier of the first MEC access point to a session management network element that controls each terminal, respectively, for each terminal to access the first MEC access point. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0010] Through the method for determining MEC access points provided in the embodiments of the present application, the MEC access point to be accessed by the terminal group users is determined based on the network topology information of the MEC access point closest to each terminal in the terminal group. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0011] The first network element may be an application function (AF) network element or a network exposure function (NEF) network element.

[0012] In one possible implementation, the first network element obtains the first MEC access point accessed by the terminal group of the first service, which can be specifically implemented as follows: the first network element sends first information to the second network element corresponding to each terminal in the terminal group of the first service, respectively, the first information including the identifier of the MEC access point supporting the first service and the identifier of the terminal managed by the second network element in the terminal group; the first network element receives the identifier of the MEC access point closest to each terminal in the terminal group determined according to the first information from each second network element; the first network element sends second information to the third network element, the second information including the identifier of the MEC access point closest to each terminal in the terminal group; the first network element receives network topology information obtained according to the second information from the third network element; the first network element determines the first MEC access point from the MEC access points closest to each terminal according to the preset rules and the received network topology information. The first network element obtains the MEC access point closest to each terminal in the terminal group, and then obtains the network topology information of the MEC access point closest to each terminal. Then, the first network element determines the first MEC access point based on the obtained network topology information, thereby achieving the purpose of saving network resources while improving user experience. The execution entity of the solution is designed effectively and flexibly, and the applicable scenarios are expanded.

[0013] The second network element may be a session management network element. The first information may be used to obtain the MEC access point closest to each terminal included in the first information. The second information may be used to obtain network topology information of the MEC access point closest to each terminal.

[0014] In another possible implementation, a first network element obtains a first MEC access point accessed by a terminal group supporting a first service. Specifically, the first network element sends first information to each second network element corresponding to each terminal in the terminal group. The first information includes an identifier of the MEC access point supporting the first service and an identifier of the terminal managed by the second network element in the terminal group. The first network element receives from each second network element the MEC access point closest to each terminal in the terminal group, as determined based on the first information. The first network element sends third information to a fourth network element, the third information includes an identifier of the MEC access point closest to each terminal in the terminal group. The first network element receives from the fourth network element the identifier of the first MEC access point determined based on the third information. The first network element obtains the MEC access point closest to each terminal in the terminal group, then provides the identifier of the MEC access point closest to each terminal in the terminal group to the fourth network element. The fourth network element determines the first MEC access point and then feeds it back to the first network element. This achieves the goal of conserving network resources while improving user experience. The implementation of this solution is effectively and flexibly designed, expanding its applicable scenarios.

[0015] The fourth network element may be a session management network element or an edge configuration server (ECS). The third information is used to indicate a first MEC access point to which the terminal group of the first service is to access.

[0016] In another possible implementation, the first network element obtains the first MEC access point accessed by the terminal group supporting the first service. Specifically, the first network element sends fourth information to the fifth network element, the fourth information including the identifier of each terminal in the terminal group and the identifier of the MEC access point supporting the first service; and the first network element receives the identifier of the first MEC access point determined based on the fourth information from the fifth network element. The fifth network element selects the first MEC access point, thereby achieving the goal of conserving network resources while improving user experience. This solution effectively and flexibly designs the execution entity and expands its applicable scenarios.

[0017] The fifth network element may be a session management network element. The fourth information may be used to indicate the selection of the first MEC access point.

[0018] In another possible implementation, the preset rule may include: determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can save network resources while improving user experience.

[0019] In a second aspect, another method for determining MEC access points is provided. The method may include: a third network element receiving second information from a first network element, the second information including identifiers of multiple MEC access points, the multiple MEC access points supporting a first service; the third network element obtaining a sixth network element corresponding to each of the multiple MEC access points; the third network element sending fifth information to each sixth network element, the fifth information including the identifiers of the multiple MEC access points in the second information; the third network element receiving, from each sixth network element, topology information between MEC access points known to the sixth network element among the multiple MEC access points obtained based on the fifth information, the topology information indicating whether at least two MEC access points are connected and / or indicating link performance between at least two MEC access points; the third network element aggregating the received topology information to obtain the aforementioned network topology information; and the third network element sending the network topology information to the first network element, the network topology information being used to determine MEC access points to which a terminal group for the first service accesses. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0020] Through the method for determining MEC access points provided in the embodiments of the present application, the third network element can obtain network topology information of multiple MEC access points supporting the first service according to the instruction of the first network element, and provide the network topology information to the first network element. The first network element selects the MEC access point for access by the terminal group users based on the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access point, when determining the MEC access point based on the network topology information of the MEC access point, the actual location of the terminal in the terminal group can be considered, so that the MEC access point selected for the terminal group user has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0021] The sixth network element may be a session management network element or an operations administration maintenance (OAM) network element. The fifth information may be used to obtain topology information between the multiple MEC access points included in the fifth information and known to the sixth network element.

[0022] In a possible implementation, the identifiers of the multiple MEC access points included in the second information may be the MEC access points closest to each terminal in the terminal group.

[0023] It should be noted that the method for determining the MEC access point provided in the second aspect and the method for determining the MEC access point provided in the first aspect are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0024] According to a third aspect, another method for determining MEC access points is provided. The method may include: a fourth network element receiving third information from a first network element, the third information including identifiers of multiple MEC access points, the multiple MEC access points supporting a first service; the fourth network element obtaining network topology information of the multiple MEC access points; the network topology information indicating whether at least two MEC access points are connected and / or indicating link performance between at least two MEC access points; the fourth network element determining, from the multiple MEC access points, a first MEC access point to be accessed by a terminal group for the first service based on a preset rule and the network topology information; and the fourth network element sending the identifier of the first MEC access point to the first network element. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0025] With the method for determining MEC access points provided in the embodiments of the present application, the fourth network element, based on the instruction of the first network element, first obtains network topology information of MEC access points that support the first service, and then selects MEC access points to be accessed by terminal group users according to the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access points, when selecting MEC access points based on the network topology information of the MEC access points, the actual location of the terminals in the terminal group can be considered, so that the MEC access points selected for the terminal group users have the optimal path for the users in the terminal group, thereby saving network resources while improving user experience.

[0026] In a possible implementation, the identifiers of the multiple MEC access points included in the third information may be the MEC access points closest to each terminal in the terminal group.

[0027] In another possible implementation, the fourth network element obtains the network topology information of multiple MEC access points, which can be specifically implemented as follows: the fourth network element stores the network topology information, and the fourth network element reads the locally stored network topology information.

[0028] In another possible implementation, the fourth network element obtains network topology information of multiple MEC access points, which can be specifically implemented as follows: the fourth network element obtains the sixth network element corresponding to each MEC access point; the fourth network element sends fifth information to each sixth network element, where the fifth information includes identifiers of the multiple MEC access points; the fourth network element receives topology information of the MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information from each sixth network element, where the topology information is used to indicate whether at least two MEC access points are connected, and / or, the topology information is used to indicate the link performance between at least two MEC access points; the fourth network element aggregates the above-mentioned network topology information based on the topology information.

[0029] The fifth information may be used to obtain the topology between MEC access points known to the sixth network element among multiple MEC access points.

[0030] In another possible implementation, the preset rule may include: determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can achieve the purpose of saving network resources while improving user experience.

[0031] In another possible implementation, the sixth network element may be an operation and maintenance management network element or a session management network element.

[0032] It should be noted that the method for determining the MEC access point provided in the third aspect and the method for determining the MEC access point provided in the first aspect are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0033] In a fourth aspect, a method for determining an MEC access point is provided, which may include: a fifth network element receiving fourth information from a first network element, the fourth information including an identifier of a terminal in a terminal group for a first service, and an identifier of an MEC access point supporting the first service; the fifth network element obtaining a context of each terminal in the terminal group, the context of a terminal including network topology information of an access network element accessed by the terminal and a MEC access point supporting the first service; the network topology information is used to indicate whether connectivity exists between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points; the fifth network element determines, from the MEC access points supporting the first service, a first MEC access point to which the terminal group for the first service accesses based on preset rules and the network topology information in the context of each terminal; the fifth network element sends the identifier of the first MEC access point to the first network element.

[0034] The terminal group for the first service includes terminals that request the first service and / or terminals that subscribe to the first service.

[0035] Through the method for determining MEC access points provided in the embodiments of the present application, network topology information of access network elements accessed by terminals in the terminal group and MEC access points supporting the first service is first obtained. Then, according to the network topology information, a MEC access point for access by the terminal group users is selected. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0036] In one possible implementation, the preset rule may include determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can save network resources while improving user experience.

[0037] In another possible implementation method, the fifth network element obtains the context of each terminal in the terminal group, which can be specifically implemented as follows: the fifth network element obtains the context of each terminal from the data storage function query; the fifth network element queries the session management network element corresponding to the terminal other than the terminal corresponding to the fifth network element from the unified data management platform; the fifth network element obtains the context of the terminal other than the terminal corresponding to the fifth network element from the session management network element corresponding to the terminal.

[0038] It should be noted that the method for determining the MEC access point provided in the fourth aspect and the method for determining the MEC access point provided in the first aspect are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0039] In a fifth aspect, a method for determining an MEC access point is provided, which may include: a first network element obtaining an identifier of the MEC access point closest to each terminal in a terminal group for a first service, the MEC access point supporting the first service; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; the first network element sends second information to a third network element, the second information including the identifier of the MEC access point closest to each terminal; the third network element receives the second information from the first network element; the third network element determines, based on the second information, network topology information of the MEC access point closest to each terminal, the network topology information being used to indicate whether at least two MEC access points are connected, and / or, the network topology information being used to indicate link performance between at least two MEC access points; the third network element sends the network topology information to the first network element; the first network element receives the network topology information obtained based on the second information from the third network element; the first network element determines, based on a preset rule and the network topology information, the first MEC access point to which the terminal group for the first service accesses from the MEC access points closest to each terminal.

[0040] Through the method for determining MEC access points provided in the embodiments of the present application, the third network can obtain network topology information of multiple MEC access points supporting the first service according to the instruction of the first network element, and provide the network topology information to the first network element. The first network element selects the MEC access point for access by the terminal group users based on the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access point, when determining the MEC access point based on the network topology information of the MEC access point, the actual location of the terminal in the terminal group can be considered, so that the MEC access point selected for the terminal group user has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0041] It should be noted that the method for determining the MEC access point provided in the fifth aspect and the method for determining the MEC access point provided in the first and second aspects are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0042] In a sixth aspect, a method for determining an MEC access point is provided, which may include: a first network element obtaining an identifier of the MEC access point closest to each terminal in a terminal group for a first service, and the MEC access point supports the first service; the terminal group for the first service includes terminals requesting the first service, and / or terminals subscribing to the first service; the first network element sends third information to a fourth network element, and the third information includes an identifier of the MEC access point closest to each terminal; the fourth network element receives the third information from the first network element; the fourth network element obtains network topology information of the MEC access point closest to each terminal, and the network topology information is used to indicate whether at least two MEC access points are connected, and / or, the network topology information is used to indicate the link performance between at least two MEC access points; the fourth network element determines, according to a preset rule and the network topology information, a first MEC access point to which the terminal group for the first service accesses from the MEC access points closest to each terminal; the fourth network element sends the identifier of the first MEC access point to the first network element; the first network element receives the identifier of the first MEC access point determined according to the third information from the fourth network element.

[0043] With the method for determining MEC access points provided in the embodiments of the present application, the fourth network element, based on the instruction of the first network element, first obtains network topology information of MEC access points that support the first service, and then selects MEC access points to be accessed by terminal group users according to the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access points, when selecting MEC access points based on the network topology information of the MEC access points, the actual location of the terminals in the terminal group can be considered, so that the MEC access points selected for the terminal group users have the optimal path for the users in the terminal group, thereby saving network resources while improving user experience.

[0044] It should be noted that the method for determining the MEC access point provided in the sixth aspect and the method for determining the MEC access point provided in the first and third aspects are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0045] In a seventh aspect, a method for determining an MEC access point is provided, the method may include: a first network element sends fourth information to a fifth network element, the fourth information including an identifier of each terminal in a terminal group of a first service and an identifier of an MEC access point supporting the first service; the terminal group of the first service includes a terminal requesting the first service and / or a terminal signing for the first service; the fifth network element receives the fourth information from the first network element; the fifth network element obtains a context of each terminal in the terminal group, the context of a terminal including network topology information of an access network element accessed by the terminal and a MEC access point supporting the first service, the network topology information The information is used to indicate whether the access network network element and the MEC access point, or between at least two MEC access points, are connected, and / or the network topology information is used to indicate the link performance between the access network network element and the MEC access point, or between at least two MEC access points; the fifth network element determines, from the MEC access points supporting the first service, a first MEC access point to which the terminal group accesses the first service; the fifth network element sends an identifier of the first MEC access point to the first network element; and the first network element receives, from the fifth network element, an identifier of the first MEC access point determined according to the fourth information.

[0046] With the method for determining MEC access points provided in an embodiment of the present application, the fifth network element obtains, according to an instruction of the first network element, network topology information of the access network elements accessed by the terminals in the terminal group and the MEC access points supporting the first service, and then selects the MEC access points accessed by the terminal group users according to the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access points, when selecting the MEC access points based on the network topology information of the MEC access points, the actual location of the terminals in the terminal group can be considered, so that the MEC access points selected for the terminal group users have the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0047] It should be noted that the method for determining the MEC access point provided in the seventh aspect and the method for determining the MEC access point provided in the first and fourth aspects are descriptions of the same solution from different angles. The specific implementations can refer to each other and will not be repeated here.

[0048] In an eighth aspect, a device for determining an MEC access point is provided, which may include: an acquisition unit and a sending unit.

[0049] An acquisition unit is configured to acquire a first MEC access point accessed by a terminal group for a first service, the first MEC access point being obtained based on at least network topology information of a MEC access point closest to each terminal in the terminal group that supports the first service; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between the at least two MEC access points. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0050] The sending unit is configured to send the identifier of the first MEC access point obtained by the obtaining unit to the session management network element that controls each terminal in the group, so that each terminal in the group can access the first MEC access point.

[0051] Through the device for determining MEC access points provided by the embodiments of the present application, the MEC access point to be accessed by the terminal group users is determined based on the network topology information of the MEC access point closest to each terminal in the terminal group. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0052] In a possible implementation, the device may be an AF network element or a NEF.

[0053] In one possible implementation, the acquisition unit is specifically configured to: send first information to the second network element corresponding to each terminal in the terminal group supporting the first service, the first information including the identifier of the MEC access point supporting the first service and the identifier of the terminal managed by the second network element in the terminal group; receive the identifier of the MEC access point closest to each terminal determined based on the first information from each second network element; send second information to the third network element, the second information including the identifier of the MEC access point closest to each terminal; receive the network topology information obtained based on the second information from the third network element; and determine the first MEC access point from the MEC access points closest to each terminal according to a preset rule and the network topology information. The device obtains the MEC access point closest to each terminal in the terminal group, then obtains the network topology information of the MEC access point closest to each terminal. The first network element then determines the first MEC access point based on the obtained network topology information, thereby achieving the goal of saving network resources while improving the user experience. This effectively and flexibly designs the execution entity of the solution and expands its applicable scenarios.

[0054] The second network element may be a session management network element. The first information may be used to obtain the MEC access point closest to each terminal included in the first information. The second information may be used to obtain network topology information of the MEC access point closest to each terminal.

[0055] In another possible implementation, the acquisition unit is specifically configured to: send first information to the second network element corresponding to each terminal in the terminal group, the first information including the identifier of the MEC access point supporting the first service and the identifier of the terminal managed by the second network element in the terminal group; receive from each second network element the MEC access point closest to each terminal in the terminal group, as determined based on the first information; send third information to the fourth network element, the third information including the identifier of the MEC access point closest to each terminal in the terminal group; and receive from the fourth network element the identifier of the first MEC access point determined based on the third information. The device acquires the MEC access point closest to each terminal in the terminal group, then provides the identifier of the MEC access point closest to each terminal in the terminal group to the fourth network element. The fourth network element determines the first MEC access point and feeds it back to the first network element, thereby achieving the goal of conserving network resources while improving the user experience. The execution entity of the solution is effectively and flexibly designed, expanding its applicable scenarios.

[0056] The fourth network element may be a session management network element or an ECS. The third information is used to indicate a first MEC access point to which the terminal group of the first service is to access.

[0057] In another possible implementation, the acquiring unit is specifically configured to: send fourth information to a fifth network element, the fourth information including an identifier of each terminal in the terminal group and an identifier of an MEC access point supporting the first service; and receive from the fifth network element the identifier of a first MEC access point determined based on the fourth information. The fifth network element selects the first MEC access point, thereby achieving the goal of conserving network resources while improving user experience. The execution entity of the solution is effectively and flexibly designed, expanding its applicable scenarios.

[0058] The fifth network element may be a session management network element. The fourth information may be used to indicate the selection of the first MEC access point.

[0059] In another possible implementation, the preset rule may include: determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can save network resources while improving user experience.

[0060] It should be noted that the device for determining the MEC access point provided in the eighth aspect is used to execute the method for determining the MEC access point provided in the first aspect. The specific implementation can refer to the specific implementation of the first aspect, and can achieve the same effect as the first aspect.

[0061] In a ninth aspect, a device for determining an MEC access point is provided, which may include: a receiving unit, an acquiring unit, an aggregation unit, and a sending unit.

[0062] A receiving unit is configured to receive second information from a first network element, where the second information includes identifiers of multiple MEC access points, and the multiple MEC access points support the first service.

[0063] An acquiring unit is configured to acquire a sixth network element corresponding to each MEC access point in the multiple MEC access points included in the second information.

[0064] A sending unit is configured to send fifth information to each sixth network element, where the fifth information includes identifiers of multiple MEC access points in the second information.

[0065] The receiving unit is further used to receive, from each sixth network element, topology information between the MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information, where the topology information is used to indicate whether at least two MEC access points are connected, and / or, the topology information is used to indicate link performance between at least two MEC access points.

[0066] The aggregation unit is used to aggregate the received topology information to obtain the above network topology information.

[0067] The sending unit is further configured to send the network topology information to the first network element, where the network topology information is used to determine an MEC access point to be accessed by a terminal group of the first service. The terminal group of the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0068] Through the device for determining MEC access points provided by the embodiments of the present application, network topology information of multiple MEC access points supporting a first service can be obtained according to an instruction of a first network element, and the network topology information can be provided to the first network element. The first network element selects an MEC access point for access by terminal group users based on the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access point, when determining the MEC access point based on the network topology information of the MEC access point, the actual location of the terminal in the terminal group can be considered, so that the MEC access point selected for the terminal group user has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0069] It should be noted that the device for determining the MEC access point provided in the ninth aspect is used to execute the method for determining the MEC access point provided in the second aspect. The specific implementation can refer to the specific implementation of the second aspect, and can achieve the same effect as the second aspect.

[0070] In a tenth aspect, a device for determining an MEC access point is provided, which may include: a receiving unit, an acquiring unit, a determining unit, and a sending unit.

[0071] A receiving unit is configured to receive third information from the first network element, where the third information includes identifiers of multiple MEC access points, and the multiple MEC access points support the first service.

[0072] An acquiring unit is configured to acquire network topology information of the multiple MEC access points; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points.

[0073] The determining unit is configured to determine, from the plurality of MEC access points, a first MEC access point to be accessed by a terminal group of the first service, based on a preset rule and the network topology information. The terminal group of the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0074] A sending unit is configured to send an identifier of the first MEC access point to the first network element.

[0075] With the device for determining MEC access points provided in an embodiment of the present application, the device first obtains network topology information of MEC access points supporting the first service according to an instruction of the first network element, and then selects a MEC access point for access by terminal group users according to the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered, so that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0076] In a possible implementation, the acquiring unit is specifically configured to: the network topology information is stored in the device, and the acquiring unit only needs to read the locally stored network topology information.

[0077] In another possible implementation, the acquisition unit is specifically used to: obtain a sixth network element corresponding to each MEC access point; send fifth information to each sixth network element, the fifth information including identifiers of the multiple MEC access points; receive topology information of the MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information from each sixth network element, the topology information being used to indicate whether at least two MEC access points are connected, and / or, the topology information being used to indicate link performance between at least two MEC access points; and obtain the above-mentioned network topology information by aggregating the topology information.

[0078] The fifth information may be used to obtain the topology between MEC access points known to the sixth network element among multiple MEC access points.

[0079] In another possible implementation, the preset rule may include: determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can achieve the purpose of saving network resources while improving user experience.

[0080] In another possible implementation, the sixth network element may be an operation and maintenance management network element or a session management network element.

[0081] It should be noted that the device for determining the MEC access point provided in the tenth aspect is used to execute the method for determining the MEC access point provided in the third aspect. The specific implementation can refer to the specific implementation of the third aspect, and can achieve the same effect as the third aspect.

[0082] In an eleventh aspect, a device for determining an MEC access point is provided, which may include: a receiving unit, an acquiring unit, a determining unit, and a sending unit.

[0083] The receiving unit is configured to receive fourth information from the first network element, where the fourth information includes an identifier of a terminal in a terminal group of the first service and an identifier of an MEC access point supporting the first service.

[0084] An acquisition unit is configured to acquire a context of each terminal in a terminal group, where the context of a terminal includes network topology information of an access network element accessed by the terminal and a MEC access point supporting a first service; the network topology information is used to indicate whether connectivity exists between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points.

[0085] A determining unit is configured to determine, from MEC access points supporting the first service, a first MEC access point to be accessed by a terminal group for the first service based on a preset rule and network topology information in the context of each terminal. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0086] A sending unit is configured to send an identifier of the first MEC access point to the first network element.

[0087] Through the apparatus for determining MEC access points provided in the embodiments of the present application, network topology information of access network elements accessed by terminals in the terminal group and MEC access points supporting the first service is first obtained. Then, according to the network topology information, a MEC access point for access by the terminal group users is selected. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving user experience.

[0088] In one possible implementation, the preset rule may include determining the first MEC access point from the network topology information based on the load and / or delay of the MEC access point, so as to select the first MEC access point that meets actual needs and can save network resources while improving user experience.

[0089] In another possible implementation, the acquisition unit is specifically used to: obtain the context of each terminal from the data storage function query; query the session management network element corresponding to the terminal other than the terminal corresponding to the device from the unified data management platform; and obtain the context of the terminal other than the terminal corresponding to the device from the session management network element corresponding to the terminal.

[0090] It should be noted that the device for determining the MEC access point provided in the eleventh aspect is used to execute the method for determining the MEC access point provided in the fourth aspect. The specific implementation can refer to the specific implementation of the fourth aspect, and can achieve the same effect as the fourth aspect.

[0091] In a twelfth aspect, a communication device is provided, comprising: a processor and a memory. The memory is connected to the processor; the memory is configured to store computer instructions, and when the processor executes the computer instructions, the communication device executes the method for determining an MEC access point provided in any of the above aspects or any possible implementations.

[0092] In a thirteenth aspect, a communication device is provided, which can implement the functions of the method examples described in any of the above aspects. The 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. The communication device can exist in the form of a chip product.

[0093] In one possible implementation, the communication device may include a processor and a transmission interface. The transmission interface is configured to receive and send data. The processor is configured to invoke program instructions stored in a memory to cause the communication device to perform the functions of the method examples described in any of the above aspects.

[0094] In a fourteenth aspect, a communication system is provided, which may include a first communication device, and the first communication device is used to execute the method for determining the MEC access point provided in the first aspect above.

[0095] In a possible implementation, the system may further include one or more of a second communication device, a third communication device, and a fourth communication device, the second communication device being used to execute the method for determining the MEC access point provided in the second aspect above, the third communication device being used to execute the method for determining the MEC access point provided in the third aspect above, and the fourth communication device being used to execute the method for determining the MEC access point provided in the fourth aspect above.

[0096] In a fifteenth aspect, a computer-readable storage medium is provided, comprising instructions, which, when executed on a computer, enables the computer to execute the method for determining an MEC access point as described in any one of the above aspects or any one of the possible implementations.

[0097] In a sixteenth aspect, a computer program product is provided, which, when executed on a computer, enables the computer to execute the method for determining an MEC access point as described in any one of the above aspects or any one of the possible implementations.

[0098] In a seventeenth aspect, a chip system is provided, comprising a processor and a memory, configured to implement the functions performed by the first network element, the third network element, the fourth network element, or the fifth network element in the above method. The chip system may be composed of a chip alone, or may include a chip and other discrete components.

[0099] The solutions provided in the above-mentioned aspects 12 to 17 are used to implement the methods for determining MEC access points provided in the above-mentioned aspects 1 to 7, and therefore can achieve the same beneficial effects as the first to seventh aspects, and will not be repeated here.

[0100] It should be noted that various possible implementations of any of the above aspects can be combined under the premise that the solutions are not contradictory. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] Figure 1a A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0102] Figure 1b A schematic diagram of an AF influence traffic routing process provided in an embodiment of the present application;

[0103] Figure 1c A schematic diagram of a ULCL insertion process provided in an embodiment of the present application;

[0104] Figure 1d A schematic diagram of an AF notification process provided in an embodiment of the present application;

[0105] Figure 1e A schematic diagram of a DNAI change triggering process provided in an embodiment of the present application;

[0106] Figure 2 A schematic diagram of a game scene system architecture provided in an embodiment of the present application;

[0107] Figure 3 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0108] Figure 4 A flowchart of a method for determining an MEC access point provided in an embodiment of the present application;

[0109] Figure 5 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0110] Figure 6 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0111] Figure 7 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0112] Figure 8 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0113] Figure 9 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0114] Figure 10 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0115] Figure 11 A flowchart of another method for determining an MEC access point provided in an embodiment of the present application;

[0116] Figure 12 A schematic diagram of the structure of a device for determining an MEC access point provided in an embodiment of the present application;

[0117] Figure 13 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0118] Figure 14 A schematic diagram of the structure of another device for determining an MEC access point provided in an embodiment of the present application;

[0119] Figure 15 A schematic structural diagram of another communication device provided in an embodiment of the present application;

[0120] Figure 16 A schematic diagram of the structure of another apparatus for determining an MEC access point provided in an embodiment of the present application;

[0121] Figure 17 A schematic structural diagram of another communication device provided in an embodiment of the present application;

[0122] Figure 18 A schematic diagram of the structure of another apparatus for determining an MEC access point provided in an embodiment of the present application;

[0123] Figure 19 A structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0124] In the embodiments of the present application, in order to clearly describe the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean different. There is no order of precedence or priority between the technical features described by "first" and "second".

[0125] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0126] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0127] In the embodiments of the present application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application.

[0128] It should be noted that, in the description of this application, A sends a certain content to B. When A and B are not directly connected in the network architecture, the content can be forwarded step by step through the network elements between A and B so that the content reaches B. This article uniformly describes it as "A sends the content to B."

[0129] In addition, the network architecture and scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0130] Before describing the embodiments of the present application, the terms involved in the present application are explained here in a unified manner and will not be explained one by one later.

[0131] An MEC server can refer to a platform server that provides MEC services. An MEC server can run one or more specific tasks, which are used to provide corresponding services to users. An MEC server is a platform deployed locally to provide services to users. An MEC server can be deployed in a local device in the core network, for example, in a user plane function (UPF) network element.

[0132] DNAI refers to the access network entity where the MEC server providing business services is located. An MEC server corresponds to one or more DNAIs, and the number of DNAIs corresponding to a MEC server is related to the types of services it provides. A DNAI corresponds to (or is associated with) at least one UPF and is used to identify the data network (DN) of the application server.

[0133] An MEC access point is a local device used to provide MEC services to users. The MEC access point can be the DNAI accessed by the user, or the MEC access point can correspond to the DNAI accessed by the user. For example, the MEC access point can be the DNAI accessed by the user, or the UPF corresponding to the DNAI accessed by the user.

[0134] The method provided in the embodiment of the present application is applied to any communication system, which may be a third generation partnership project (3GPP) communication system, for example, a long term evolution (LTE) system, or a 5G mobile communication system or a new radio (NR) system, or a non-3GPP communication system without limitation.

[0135] like Figure 1a Figure 1 shows an architecture diagram of a communication system, which may include terminals, (radio) access network (R)AN equipment, a core network, and a DN. The access network equipment implements functions related to wireless access. Terminals access the core network through the access network equipment, access the DN, and complete service data exchange.

[0136] Figure 1a The core network and access network are taken as the fifth generation (5G) mobile communication network as an example. Figure 1aThe core network equipment may include access and mobility management function (AMF), session management function (SMF), UPF, unified data management (UDM) network element, policy control function (PCF), application function (AF), authentication server function (AUSF), and network slice selection function (NSSF). Figure 1a , introduces the communication system involved in this application.

[0137] Terminal can be called UE or terminal equipment. Figure 1a The terminals shown may include but are not limited to vehicle-mounted terminals, mobile phones, Internet of Things terminal devices, tablet computers or computers with wireless transceiver functions, smart gas stations, smart traffic lights, etc.

[0138] (R)AN is a device that provides wireless access to terminals and can be called an access network device. 5G-RAN is connected to the UPF through the user plane interface N3 to transmit data of the terminal device; 5G-RAN establishes a control plane signaling connection with the AMF through the control plane interface N2 to implement functions such as wireless access bearer control. For example, the access network device can be a base station, a broadband network gateway (BNG), an aggregation switch, a non-3GPP access device, etc. The base station can include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, etc., which are not specifically limited in the embodiments of the present application. For the equipment for terminal access to the core network, they are uniformly referred to as access network equipment in this article and will not be explained again. For example, the access network equipment can be the evolved universal terrestrial radio access network (E-UTRAN) equipment in the fourth generation mobile communication technology (4th generation, 4G) network, the next generation radio access network (NG-RAN) equipment in the 5G network, the evolved Node B (eNodeB), the WIFI access point (AP), the world interoperability for microwave access (WIMAX) base station (BS), etc.

[0139] The AMF is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handovers. The AMF's main functions include terminal authentication, terminal mobility management, network slice selection, and SMF selection. It serves as the anchor point for N1 and N2 signaling connections and provides routing for N1 / N2SM messages for the SMF. It also maintains and manages UE status information.

[0140] The SMF is responsible for all control plane functions related to terminal session management in mobile networks, such as session establishment, modification, and release. Specific functions include selecting and providing the packet forwarding function (UPF), Internet Protocol (IP) address allocation, and session Quality of Service (QoS) management.

[0141] As the anchor point for protocol data unit (PDU) session connections, the UPF is primarily responsible for filtering user equipment data packets, performing data transmission / forwarding, rate control, and generating billing information.

[0142] The UDM network element is mainly responsible for managing user data, such as contract information, including obtaining contract information from the unified data repository (UDR) and providing it to other network elements (such as AMF); generating 3GPP authentication credentials for terminals; and registering and maintaining network elements currently serving terminals.

[0143] The UDR network element is mainly used to store user data, including the subscription data called by the UDM.

[0144] DN is a network that provides data transmission services to users, such as IP multimedia subsystem (IMS) and Internet network.

[0145] The AF is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0146] Specifically, in Figure 1a In the illustrated communication system, the terminal accesses the DN by establishing a session and user plane connection from the terminal to the (R)AN to the UPF to the DN.

[0147] It should be noted that the network composed of operator network elements other than (R)AN can be called the core network. In the 5G network, the core network includes AMF, SMF, UPF and other network elements. Figure 1a The 5G network is used as an example only, and there is no specific limitation on the core network elements.

[0148] It should be noted that the network architecture used in the embodiments of the present application is not limited to Figure 1a The network architecture shown. In addition, Figure 1a The network architecture shown is only an example architecture diagram, and the number and name of the network elements included in the communication system are not limited. Figure 1a In addition to the network functional entities shown, Figure 1a The shown network may also include other functional entities.

[0149] It should be noted that the network architecture used in the embodiments of the present application is not limited to Figure 1a The network architecture shown. In addition, Figure 1a The network architecture shown is only an example architecture diagram, and the number and name of the network elements included in the communication system are not limited. Figure 1a In addition to the network functional entities shown, Figure 1a The network shown may also include other functional entities. For example, Figure 1aThe names of the network elements, interfaces between network elements, and protocol layers in the architecture are just examples. In specific implementations, the names of network elements, interfaces between network elements, and protocol layers can be other names, and the embodiments of this application do not specifically limit this.

[0150] In the network architecture where MEC is deployed, the DNAI change process is triggered in many cases. The core network then selects the MEC access point of the terminal (addition or replacement), inserts the UPF corresponding to the selected MEC access point as an uplink classifier (ULCL) and connects it to the local server. The selected MEC access point then provides MEC services to the terminal.

[0151] Currently, the DNAI change process in the MEC scenario can refer to 3Gpp 23.502, which is mainly implemented by the following three processes: data routing process, ULCL insertion process and notification process. Among them:

[0152] The data routing process is to notify the core network equipment of the DNAI supporting MEC services, the corresponding location area, and service flow information. For example, the data routing process can refer to the AF influence traffic routing process in 5G defined in 3GPP 23.502. The AF uses the DNAI supporting MEC services, the corresponding location area, and service flow information as rules and sends them to the SMF through the PCF.

[0153] For example, the AF influence traffic routing process can be Figure 1bAs shown in the figure, the AF first creates an AF request (carrying information such as the DNAI supporting MEC services, the corresponding location area, and service flows). The AF then sends the request to the NEF via the Nnef_TrafficInfluence_Create / Update / Delete signaling. The NEF and the UDR use the Storing / Updating / Removing the Information signaling to store the request in the UDR. The NEF then sends the Nnef_TrafficInfluence_Create / Update / Delete Response back to the AF. After receiving the request, the UDR sends it to the PCF via the Nudr_DM_Notify message. The PCF notifies the SMF of the corresponding PCC rules via the Npcf_SM_PolicyControl_Update Notify message. The SMF can then select the MEC access point to complete the user plane reconfiguration (User Plane Reconfiguration).

[0154] The ULCL insertion process triggers the execution of the data routing process based on the actual network conditions, and then selects the MEC access point and inserts the ULCL to achieve uplink diversion. The ULCL insertion process can refer to the ULCL insertion process (Addition of ULCL) defined in 3Gpp 23.502. The SMF decides to execute the rules issued by the AF influencetraffic routing process based on regional changes or detection of corresponding business flows, selects the MEC access point, and inserts the ULCL. In this ULCL insertion process, the SMF needs to adjust the forwarding rules of the ULCL in the PDU session anchor (PSA) 1 (original PSA) and PSA2 (newly inserted PSA) respectively to ensure that the corresponding uplink and downlink data packets are transmitted from the correct user plane network element.

[0155] For example, Figure 1c The ULCL insertion process is shown in FIG. Figure 1cAs shown, after the UE establishes a PDU session with PSA1, the SMF decides to execute the rules issued by the process of Figure 1 and insert ULCL through changes in the area or detection of the corresponding service flow. The SMF selects PSA2 and configures relevant information, inserts a branch point or ULCL to implement the ULCL function. The function of ULCL is to forward the uplink traffic to different PDU session anchor points according to the filter requirements and merge the downlink data of multiple anchor points of the UE. The SMF updates the rules for the downlink service of PSA1 so that the downlink traffic of multiple anchor points of the UE is merged into ULCL and transmitted to the UE. At this time, the uplink traffic of the UE is sent through PSA1. Next, the SMF updates the uplink traffic rules for PSA2 so that the uplink traffic of the UE is forwarded to different PDU session anchor points according to the filter requirements. The SMF also updates the uplink traffic configuration information in the (R)AN so that the uplink traffic of the UE is sent to ULCL. At this time, the uplink traffic of the UE is sent to PSA1 through ULCL. Optionally, if the session uses the Internet Protocol version 6 (IPv6) address, SMF notifies the UE of the IPv6 address of PSA2, and SMF reconfigures the UE's IPv6 address to PSA1. After that, when the UE's uplink traffic reaches ULCL, it can be forwarded to PSA2 according to the filter requirements.

[0156] The notification process is that the core network device notifies the AF of the DNAI change, and the AF feeds back an AF notification response (AF notification response) to the core network device, which includes the configuration options of the N6 connection, which is used by the core network device to configure the ULCL or the N6 connection between the local PSA and the MEC server (if the local PSA and MEC server are co-located or pre-configured with the N6 connection, the AF does not need to feed back the AF Notification Response). The notification process can refer to the notification process (AF notification process) defined in 3Gpp 23.502.

[0157] For example, Figure 1d The figure shows an AF notification process, which can be divided into early notification and late notification. The main function is to notify the AF of DNAI changes after the SMF inserts the ULCL. Figure 1d The SMF in the process selects PSA2 and configures related information, and inserts branch points or ULCL. If Early Notification is required, such as Figure 1dIn the part above the dotted line, after selecting the new PSA, SMF sends an early notification message (EarlyNotification) to AF, waits for AF to feedback AF Notification Response containing N6 configuration message, and then configures the new PSA. The EarlyNotification can be sent through Nsmf_EventExposure_Notify, and the AF Notification Response can be sent through Nsmf_EventExposure AppRelocationgInfo. If Late Notification is required, after selecting ULCL, SMF will first send a late notification message (Late Notification), wait for AF to feedback AF NotificationResponse, which contains the routing rules for data packets that need to be routed to the new PSA, and then start configuring ULCL. The LateNotification can be sent through Nsmf_EventExposure_Notify, and the AF Notification Response can be sent through Nsmf_EventExposure AppRelocationgInfo. As shown Figure 1d As shown, the interaction process between SMF and AF can be carried out directly or forwarded through NEF, which is not limited in the embodiment of the present application.

[0158] Exemplary situations in which the core network is triggered to select the MEC access point of the terminal may include:

[0159] 1. When a terminal reaches a specific tracking area (TA) due to mobility, the core network detects this behavior, triggers the DNAI change process, and inserts a ULCL connection with the local server.

[0160] 2. When a terminal sends data streams for a specific application (APP) within a specific TA area, the core network device detects this behavior, triggers the DNAI change process, and inserts a ULCL connection to the local server.

[0161] 3. When the terminal makes a new service request, it first sends a domain name system (DNS) request to query the server address corresponding to the service. After the core network device receives the DNS request, it triggers the DNAI change process and inserts the ULCL and local server connection, and feeds back the MEC server address to the terminal. The terminal directly establishes a connection with the MEC server to provide the corresponding service.

[0162] like Figure 1e As shown, when the terminal makes a new service request, the DNAI change process may include: when the UE makes a new service request, it first sends a DNS request to the UPF to query the corresponding server address. The DNS request is reported by the UPF to the SMF, the SMF triggers the DNAI change, selects the DNAI to insert into the ULCL, and feeds back the DNAI change status to the AF, carrying the identifier of the selected DNAI. The AF performs application configuration and sends an AF response to the SMF (carrying the MEC server address corresponding to the selected DNAI and the UE identifier). The SMF sends a response message to the DNS request to the UPF through the N4 message. The SMF feeds back the address of the MEC server corresponding to the selected DNAI to the UE through the server change notification, and the UE directly establishes a connection with the MEC server to provide the corresponding service. However, this solution must require that the corresponding service needs to be initiated by the UE and a DNS query request needs to be sent.

[0163] Of course, there may be other situations that trigger the DNAI change process, which are not listed here one by one.

[0164] It can be seen from the above DNAI change process that in the MEC scenario, the connection and path adjustment of the MEC server are mainly implemented by the AFinfluence traffic routing related process. First, the AF provides the DNAI of the relevant application to the SMF through the PCF (that is, the MEC access point, or the access network entity where the MEC server is located). After the SMF moves due to terminal movement or detects the corresponding data flow or receives a DNS query request, it triggers the new PSA / ULCL insertion process. After selecting the corresponding PSA / ULCL, it notifies the AF of the DNAI change, obtains the N6 configuration options and related routing rules required by the PSA / ULCL through the AF notification response, and then configures the new PSA / ULCL.

[0165] Taking the game interoperability scenario as an example, we will explain the MEC scenario for group users. Currently, most mobile games are interactive and often require multiplayer matches. The game server architecture consists of a login server and a business server. The login server centrally manages user registration and personal information and provides grouping functionality during game matching. The business server, on the other hand, provides actual gaming services to users after they log in.

[0166] exist Figure 2In the illustrated gaming scenario system architecture, assume that UE1 and UE2 are located in different geographic locations, accessing the mobile network through gNB1 and gNB2, respectively. The UPF anchor points for UE1 and UE2 are UPF1 and UPF3, respectively, and they connect to the game's login server through UPF1 and UPF3. At this point, UE1 and UE2 initiate a matchmaking request, requiring the Login Server to assign a service server for the UEs to play the game. When the Service Server is an MEC server, the current Login Server operation process is as follows: Based on the IP addresses of UE1 and UE2 and the server load, it selects a service server and notifies both UEs to connect. Simultaneously, it notifies the SMF to insert a ULCL for both UE1 and UE2 and connect them to the corresponding UPF and Service Server, allowing the two UEs to begin playing the game. In this scenario, because the network does not support DNAI selection for dynamically grouped users, the Login Server must independently select a DNAI based on information such as the UE's IP address to ensure both UEs are assigned to the same service server. Once a unique service server is determined, it notifies the network to configure the DNAI. When the Login Server selects DNAI, it does not consider the actual location of the UE (the UE IP is allocated by the remote anchor points UPF1 and UPF3 and does not reflect the actual distribution of the UE) and the network topology. The Service Server connected to UE1 and UE2 may not be the optimal path, which affects the UE's gaming experience and wastes network resources.

[0167] Based on this, the present application provides a method for determining an MEC access point, which determines the MEC access point to which the terminal group of the first service accesses based on the network topology information of the MEC access point supporting the first service that is closest to each terminal in the terminal group of the first service. Since the network topology information reflects the location and connection relationship of the MEC access point, the actual location of the terminal in the terminal group can be considered when selecting the MEC access point, so that the MEC access point selected for the group users has the optimal path for the users in the terminal group, saving network resources while improving the user experience.

[0168] It should be noted that in the embodiment of the present application, the "nearest" can be either the closest in physical location or the closest in link length; in addition, in another possible implementation method, it is not limited to the nearest MEC access point that supports the service, but can also be other optimal MEC access points that support the service, such as the one with the best transmission performance, the most processing resources or the strongest processing capability, or the best compatibility, etc.

[0169] The following is a detailed description of the implementation of the embodiment of the present application in conjunction with the accompanying drawings. It should be noted that the message names between the various network elements or the names of the parameters in the messages in the following embodiments of the present application are only examples, and other names can also be used in specific implementations. The embodiments of the present application do not specifically limit this.

[0170] On the one hand, an embodiment of the present application provides a network device, Figure 3 A schematic diagram of the composition of a communication device 30 provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the communication device 30 may include at least one processor 31, a memory 32, a communication interface 33, and a communication bus 34. Figure 3 The components of the communication device 30 are described in detail.

[0171] The processor 31 may be a single processor or a collective term for multiple processing elements. For example, the processor 31 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more microprocessors (digital signal processors, DSPs) or one or more field programmable gate arrays (FPGAs).

[0172] The processor 31 can execute various functions of the function alias control server by running or executing the software program stored in the memory 32 and calling the data stored in the memory 32. In a specific implementation, as an embodiment, the processor 31 may include one or more CPUs, such as Figure 3 CPU0 and CPU1 are shown in the figure.

[0173] In a specific implementation, as an embodiment, the communication device 30 may include multiple processors, such as Figure 3 31 and processor 35 are shown in FIG. Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0174] The memory 32 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. The memory 32 can be independent and connected to the processor 31 via a communication bus 34. The memory 32 can also be integrated with the processor 31. Among them, the memory 32 is used to store the software program that executes the solution of the present application, and the execution is controlled by the processor 31.

[0175] The communication interface 33 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, AN, wireless local area network (WLAN), etc. The communication interface 33 may include a receiving unit and a sending unit.

[0176] The communication bus 34 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0177] It should be pointed out that Figure 3 The components shown in the figure do not constitute a limitation on the communication device, except Figure 3 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0178] In one possible implementation, the communication device 30 may be a first network element that determines a first MEC access point accessed by a terminal group of a first service. The first network element may be an AF or a NEF. The processor 31 performs the following functions by running or executing a software program and / or module stored in the memory 32 and calling data stored in the memory 32:

[0179] Obtain a first MEC access point accessed by a terminal group for a first service, where the first MEC access point is obtained based on at least, for example, network topology information of a MEC access point closest to each terminal in the terminal group that supports the first service; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; and send an identifier of the first MEC access point to a session management network element that controls each terminal, respectively, so that each terminal accesses the first MEC access point, thereby inserting the session management network element into the ULCL. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0180] In another possible implementation, the communication device 30 may be a third network element that can determine network topology information between multiple MEC access points. For example, the third network element may be a network data analytics function (NWDAF). The processor 31 performs the following functions by running or executing software programs and / or modules stored in the memory 32 and calling data stored in the memory 32:

[0181] Receiving second information from a first network element, the second information including identifiers of multiple MEC access points, the multiple MEC access points supporting a first service; obtaining a sixth network element corresponding to each of the multiple MEC access points; sending fifth information to each sixth network element, the fifth information including the identifiers of the multiple MEC access points in the second information; receiving from each sixth network element topology information between MEC access points known to the sixth network element among the multiple MEC access points obtained based on the fifth information, the topology information being used to indicate whether at least two MEC access points are connected and / or the link performance between at least two MEC access points; the third network element aggregating the received topology information to obtain the aforementioned network topology information; sending the network topology information to the first network element, the network topology information being used to determine MEC access points to be accessed by a terminal group for the first service. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0182] In one possible implementation, the communication device 30 may be a fourth network element that determines network topology information between multiple MEC access points. For example, the fourth network element may be an SMF or an ECS. The processor 31 performs the following functions by running or executing software programs and / or modules stored in the memory 32 and calling data stored in the memory 32:

[0183] The method includes receiving third information from a first network element, the third information including identifiers of multiple MEC access points, the multiple MEC access points supporting a first service; obtaining network topology information of the multiple MEC access points, the network topology information being used to indicate whether at least two MEC access points are connected and / or indicating link performance between at least two MEC access points; determining, based on a preset rule and the network topology information, a first MEC access point to be accessed by a terminal group for the first service from the multiple MEC access points; and sending the identifier of the first MEC access point to the first network element. The terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

[0184] In one possible implementation, the communication device 30 may be a fifth network element that determines network topology information between multiple MEC access points. For example, the fifth network element may be an SMF. The processor 31 performs the following functions by running or executing software programs and / or modules stored in the memory 32 and calling data stored in the memory 32:

[0185] Receive fourth information from the first network element, the fourth information including an identifier of a terminal in a terminal group for the first service and an identifier of an MEC access point supporting the first service; obtain a context for each terminal in the terminal group, the context of a terminal including network topology information of an access network element accessed by the terminal and a MEC access point supporting the first service; the network topology information is used to indicate whether connectivity exists between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points; determine a first MEC access point to which the terminal group for the first service accesses from the MEC access points supporting the first service according to preset rules and the network topology information in the context of each terminal; and send the identifier of the first MEC access point to the first network element.

[0186] On the other hand, an embodiment of the present application provides a method for determining an MEC access point, which is applied to the process in which a core network device selects an MEC access point for a terminal group to access.

[0187] It should be noted that for different terminal groups, the MEC access points to which they access can be determined according to the methods provided in the embodiments of the present application. In the embodiments of the present application, only the terminal group of the first service is used as an example to describe the process of determining the MEC access point to which the terminal group of the first service accesses, and other details are not repeated one by one. It should be understood that the terminal group described below is the terminal group of the first service.

[0188] like Figure 4 As shown, the method for determining an MEC access point provided in an embodiment of the present application may include:

[0189] S401: A first network element obtains a first MEC access point accessed by a terminal group for a first service, where the first MEC access point is obtained based on at least network topology information of a MEC access point supporting the first service that is closest to each terminal in the terminal group.

[0190] The terminal group for the first service includes multiple terminals, and the terminal group for the first service may include: terminals requesting the first service; or terminals subscribing to the first service. The characteristics of the terminals in the terminal group for the first service can be configured according to actual needs and are not specifically limited in this embodiment of the application.

[0191] It should be understood that the first network element is a core network device used to determine the MEC access point of the terminal in the mobile network architecture, and the embodiment of the present application does not limit the specific type of the first network element. Exemplarily, the first network element can be an AF or NEF or other functional network element.

[0192] Optionally, in S401, the first network element may determine the first MEC access point through a variety of different solutions, which are not specifically limited in this embodiment of the present application. For example, the first network element may determine the first MEC access point through, but not limited to, any of the following solutions:

[0193] Solution 1: The first network element obtains network topology information of the MEC access point closest to each terminal in the terminal group of the first service from other network elements, and the first network element determines the first MEC access point from the MEC access points closest to each terminal in the terminal group of the first service based on the network topology information.

[0194] In solution 1, the first network element first obtains the network topology information of the MEC access point closest to each terminal in the terminal group from the second network element corresponding to each terminal in the terminal group, and then determines the first MEC access point from the MEC access points closest to each terminal in the terminal group according to the preset rules. The specific implementation of solution 1 can refer to the following Figure 5 The process of determining the MEC access point is illustrated.

[0195] Among them, the second network element can be an SMF network element that controls the terminal.

[0196] The network topology information of the MEC access point closest to each terminal in the terminal group is used to indicate whether at least two MEC access points among the MEC access points closest to each terminal in the terminal group are connected, and / or the network topology information is used to indicate the link performance between at least two MEC access points among the MEC access points closest to each terminal in the terminal group. Link performance is used to indicate an indicator of the link between the two, and link performance may include but is not limited to latency, bandwidth, etc.

[0197] Optionally, the representation of the network topology information may record whether at least two MEC access points are connected and the link indicator, or may only record the link indicator between connected MEC access points.

[0198] For example, assume that DNAI1 and DNAI2 are reachable with a delay of d1 and a bandwidth of b1; DNAI2 and DNAI3 are reachable with a delay of d2 and a bandwidth of b2, and DNAI1 and DNAI3 are unreachable. The network topology information for these three DNAIs can be expressed as the fully connected mapping table shown in Table 1, using the connectivity and connection parameters between each DNAI.

[0199] Table 1

[0200] DNAI1 DNAI2 DNAI3 DNAI1 Yes, d1, b1 No DNAI2 Yes, d1, b1 Yes, d2, b2 DNAI3 No Yes, d2, b2

[0201] Alternatively, the network topology information of the three DNAIs can be expressed as a record table as shown in Table 2, which only records the endpoints and path parameters of each reachable connection.

[0202] Table 2

[0203] 1 DNAI1, DNAI2 d1, b1 2 DNAI2, DNAI3 d2, b2

[0204] It should be noted that Table 1 and Table 2 are merely examples for describing the above network topology information, and are not intended to limit the form and content of the network topology information.

[0205] In one possible implementation, the preset rule may include: the first network element may determine the first MEC access point from the MEC access points closest to each terminal in the terminal group based on the load and / or link delay of the MEC access point and the above-mentioned network topology information. The content of the preset rule can be configured according to actual needs and is not limited in this embodiment of the present application.

[0206] Exemplarily, the preset rule may be to determine, from among the MEC access points closest to each terminal in the terminal group, an MEC access point whose load is less than or equal to a first threshold and whose link delay is less than or equal to a second threshold.

[0207] The first threshold and the second threshold can be configured according to actual needs and are not limited.

[0208] It should be noted that when it is determined that there are multiple MEC access points whose load is less than or equal to the first threshold and whose link delay is less than or equal to the second threshold among the MEC access points closest to each terminal in the terminal group, a MEC access point with a load less than or equal to the first threshold and a link delay less than or equal to the second threshold can be randomly selected, or the MEC access point with the smallest load is selected from multiple MEC access points with a load less than or equal to the first threshold and a link delay less than or equal to the second threshold, or the MEC access point with the smallest link delay is selected, or an MEC access point is selected in other ways as the first MEC access point.

[0209] Solution 2: The first network element obtains the MEC access point closest to each terminal in the terminal group of the first service from other network elements, and the first network element sends the obtained MEC access point closest to each terminal in the terminal group of the first service to another network element, requesting the other network element to determine the first MEC access point.

[0210] In solution 2, the first network element requests the second network element corresponding to each terminal in the terminal group to obtain the MEC access point closest to each terminal. The first network element then sends the identifier of the MEC access point closest to each terminal in the terminal group to the fourth network element, instructing the fourth network element to determine the first MEC access point. Finally, the first network element receives the identifier of the first MEC access point from the fourth network element. The specific implementation of solution 2 can refer to the following Figure 6 The process of determining the MEC access point is illustrated.

[0211] Among them, the fourth network element can be an SMF network element or ECS network element selected by the first network element and can be used as an MEC access point selection. The first network element can select the fourth network element based on the functions of each network element. The embodiment of the present application does not limit the process of the first network element selecting the fourth network element.

[0212] It should be noted that the fourth network element may determine the first MEC access point from the MEC access points closest to each terminal in the terminal group according to a preset rule.

[0213] Solution 3: The first network element provides the identifiers of the terminals in the terminal group of the first service and the identifiers of the MEC access points supporting the first service to other network elements, and requests the other network elements to determine the first MEC access point.

[0214] In solution 3, the first network element sends fourth information to the fifth network element. The fourth information includes the identifier of each terminal in the terminal group and the identifier of the MEC access point supporting the first service. The fourth information is used to indicate the first MEC access point to be accessed by the terminal group. The first network element receives the identifier of the first MEC access point determined according to the fourth information from the fifth network element. The specific implementation of solution 3 can refer to the following Figure 7 The process of determining the MEC access point is illustrated.

[0215] The fifth network element is any network element having the function of selecting an MEC access point. For example, the fifth network element may be an SMF network element.

[0216] S402. The first network element sends an identifier of the first MEC access point to the session management network element that controls each terminal in the terminal group, so that each terminal in the terminal group can access the first MEC access point.

[0217] Specifically, after the session management network element (SMF) receives the identifier of the first MEC access point, it starts the connection process. The connection process can be the same as the aforementioned DNAI change process, which is not repeated here.

[0218] Through the method for determining MEC access points provided in the embodiments of the present application, the MEC access point to be accessed by the terminal group users is determined based on the network topology information of the MEC access point closest to each terminal in the terminal group. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0219] On the other hand, the embodiment of the present application provides a method for determining an MEC access point. Figure 5 As shown, the method adopts the solution 1 in the above S401. Figure 5 As shown, the method may include:

[0220] S501. A first network element sends first information to a second network element corresponding to each terminal in a terminal group.

[0221] The first information includes the identifier of the MEC access point that supports the first service and the identifier of the terminal managed by the second network element in the terminal group. The first information can be used to obtain the MEC access point closest to each terminal in the terminal group. The terminal identifier can be the terminal's IP address or other information, which is not limited in this embodiment of the present application.

[0222] Specifically, the identifier of the MEC access point supporting the first service included in the first information can be understood as the identifier of all MEC access points supporting the first service.

[0223] Specifically, when the second network element is an SMF network element, the first network element in S501 can first query the PCF corresponding to each terminal in the terminal group, send the first information to the PCF corresponding to each terminal, and the PCF sends the first information to the SMF controlling the terminal.

[0224] Optionally, the first information may further include an identifier of the first service. The identifier of the first service is used to uniquely indicate the first service. The embodiment of the present application does not limit the form and content of the identifier of the first service. For example, the identifier of the first service may be the name or mapping information of the APP of the first service.

[0225] Specifically, the first information may be newly defined information, or may be an existing request message, which is not limited in the embodiment of the present application. For example, the first request may be an AF request in the AF influence traffic routing process.

[0226] S502: The second network element receives the first information and determines the MEC access point closest to the terminal it controls.

[0227] Exemplarily, the second network element may determine the location of the terminal according to an identifier of the RAN accessed by the terminal, or according to the granularity of the TA where the terminal is located, and then determine the MEC access point closest to the terminal according to the location of the terminal.

[0228] S503: The second network element sends the identifier of the MEC access point closest to the terminal controlled by it to the first network element.

[0229] S504: The first network element receives, from each second network element, an identifier of the MEC access point closest to each terminal in the terminal group.

[0230] S505: The first network element sends second information to the third network element, where the second information includes an identifier of the MEC access point closest to each terminal in the terminal group.

[0231] The second information can be used to obtain network topology information of the MEC access point closest to each terminal in the terminal group. Specifically, the identifier of the MEC access point included in the second information is the identifier of the MEC access point closest to each terminal in the terminal group of the first service.

[0232] Optionally, the second information may further include an identifier of the first service.

[0233] Specifically, the third network element is a network element that can obtain network topology information of the MEC access point. The embodiment of the present application does not limit the type of the third network element. Exemplarily, the third network element can be an NWDAF network element.

[0234] Specifically, the second information may be newly defined information, or may be an existing request message, which is not limited in the embodiment of the present application. For example, the second information may be an Nnwdaf_AnalyticsInfo_Request message.

[0235] S506. The third network element receives second information from the first network element.

[0236] It should be noted that what the third network element receives in S506 is the second information sent by the first network element in S505.

[0237] The second information includes identifiers of multiple MEC access points, which are identifiers of the MEC access points closest to each terminal in the terminal group.

[0238] S507. The third network element obtains a sixth network element corresponding to each MEC access point in the multiple MEC access points.

[0239] Specifically, the third network element in S507 obtains the sixth network element corresponding to each MEC access point in the multiple MEC access points indicated by the identifier of the MEC access point included in the second information, that is, the third network element in S507 obtains the sixth network element corresponding to each MEC access point in the MEC access point closest to each terminal in the terminal group of the first service,

[0240] The sixth network element is a network element that records the network topology information between MEC access points. For example, the sixth network element can be an operation and maintenance management network element or a session management network element.

[0241] For example, the operation and maintenance management network element can be an OAM network element in a 5G network, and the session management network element can be an SMF network element in a 5G network.

[0242] Specifically, the third network element may query and obtain the sixth network element corresponding to the MEC access point from the network element performing the storage function in the network according to the identifier of the MEC access point. The network element performing the storage function may record the correspondence between the MEC access point and the sixth network element.

[0243] Exemplarily, the network element that performs the storage function may be a network repository function (NRF) network element in a 5G network.

[0244] S508. The third network element sends fifth information to each sixth network element.

[0245] The fifth information includes the identifiers of the multiple MEC access points included in the second information, that is, the fifth information includes the identifier of the MEC access point closest to each terminal in the terminal group.

[0246] Specifically, the fifth information may be newly defined information, or may be existing information, which is not limited in the embodiment of the present application.

[0247] S509. The third network element receives, from each sixth network element, topology information between the MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information.

[0248] The topology information is used to indicate whether at least two MEC access points are connected, and / or the topology information is used to indicate the link performance between at least two MEC access points. The topology information is a subset of the aforementioned network topology information, and its content is the same, so it is not repeated here.

[0249] S510. The third network element aggregates topology information to obtain network topology information.

[0250] Specifically, the third network element in S510 aggregates the topology information received from each sixth network element, that is, performs a merging operation, removes duplicate content, and merges it into one network topology information as the network topology information of the MEC access point closest to each terminal in the terminal group of the first service.

[0251] S511. The third network element sends network topology information to the first network element.

[0252] Specifically, the third network element sends the network topology information obtained in S510 to the first network element, where the network topology information is used to determine the MEC access point to which the terminal group of the first service accesses.

[0253] S512. The first network element receives network topology information obtained according to the second information from the third network element.

[0254] The network topology information obtained according to the second information is the network topology information between the MEC access points closest to each terminal in the terminal group of the first service.

[0255] S513: The first network element determines a first MEC access point from MEC access points closest to each terminal in the terminal group according to a preset rule and network topology information.

[0256] Specifically, the process of the first network element determining the first MEC access point according to the preset rules and network topology information has been described in detail in Solution 1 of S401 and will not be repeated here.

[0257] S514. The first network element sends an identifier of the first MEC access point to the session management network element that controls each terminal in the terminal group, so that each terminal in the terminal group can access the first MEC access point.

[0258] It should be noted that the specific implementation of S514 can refer to the description of S402 above, which will not be repeated here.

[0259] Through the method for determining MEC access points provided in the embodiments of the present application, the third network element can obtain network topology information of multiple MEC access points supporting the first service according to the instruction of the first network element, and provide the network topology information to the first network element. The first network element selects the MEC access point for access by the terminal group users based on the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access point, when determining the MEC access point based on the network topology information of the MEC access point, the actual location of the terminal in the terminal group can be considered, so that the MEC access point selected for the terminal group user has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0260] On the other hand, the embodiment of the present application provides a method for determining an MEC access point. Figure 6 As shown, the method adopts the solution 2 in the above S401. Figure 6 As shown, the method may include:

[0261] S601: A first network element obtains the MEC access point closest to each terminal in a terminal group.

[0262] It should be noted that the specific implementation of S601 can refer to the description of S501 to S504 above, which will not be repeated here.

[0263] S602: The first network element sends third information to the fourth network element, where the third information includes an identifier of the MEC access point closest to each terminal in the terminal group.

[0264] The third information may be used to indicate the selection of the first MEC access point for the terminal group to access.

[0265] For example, the first indication information may be carried in the third information, and the first indication information may be used to indicate the selection of an MEC access point from the MEC access points indicated by the MEC access point identifier carried by the third information as the first MEC access point for the terminal group to access. The content and form of the first indication information may be configured according to actual needs and are not limited in this embodiment of the present application.

[0266] Optionally, the third information may further include an identifier of the first service.

[0267] For example, when the fourth network element is an SMF network element, the first network element can send the third information to the PCF, and the PCF forwards the third information to the SMF network element.

[0268] Specifically, the third information may be newly defined information, or may be existing information, which is not limited in the embodiments of the present application.

[0269] S603: The fourth network element receives third information from the first network element.

[0270] It should be noted that the third information received by the fourth network element in S603 is the third information sent by the first network element in S602.

[0271] The third information received by the fourth network element includes identifiers of multiple MEC access points, the multiple MEC access points supporting the first service, and the multiple MEC access points being the MEC access points closest to each terminal in the terminal group. The third information can be used to request the fourth network element to determine the first MEC access point to which the terminal group for the first service accesses.

[0272] S604. The fourth network element obtains network topology information of the MEC access point closest to each terminal in the terminal group.

[0273] The network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate the link performance between at least two MEC access points. The network topology has been described in S401 and will not be repeated here.

[0274] In one possible implementation, the fourth network element obtains the network topology information of the MEC access point closest to each terminal in the terminal group, which can be implemented as follows: the fourth network element stores the network topology information, and the fourth network element reads the locally stored network topology information in S604.

[0275] Exemplarily, the fourth network element may store the topology information of all MEC access points in the network. In S604, the fourth network element selects the topology information of the MEC access point included in the third information from the locally stored topology information based on the MEC access point identifier in the third information to obtain the network topology information.

[0276] In another possible implementation, the fourth network element obtains the network topology information of the MEC access point closest to each terminal in the terminal group. This can be implemented as follows: the fourth network element obtains the network topology information from the sixth network element, which can specifically include the following steps:

[0277] Step 1: The fourth network element obtains the sixth network element corresponding to each MEC access point among the MEC access points closest to each terminal in the terminal group.

[0278] Step 2: The fourth network element sends fifth information to each sixth network element, where the fifth information includes identifiers of multiple MEC access points.

[0279] The MEC access point indicated by the identifiers of the multiple MEC access points included in the fifth information is the MEC access point closest to each terminal in the terminal group. The fifth information is used to obtain topology information between the MEC access points known to the sixth network element among the MEC access points closest to each terminal in the public anger single group.

[0280] Step 3: The fourth network element receives, from each sixth network element, topology information of MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information.

[0281] Step 4: The fourth network element aggregates the received topology information to obtain the network topology information.

[0282] It should be noted that the sixth network element and the fifth information have been described in detail in the aforementioned S507 to S510. The specific implementation of steps 1 to 4 can refer to the aforementioned S507 to S510, but they are executed here by the fourth network element, and the specific implementation will not be repeated here.

[0283] S605: The fourth network element determines a first MEC access point from MEC access points closest to each terminal in the terminal group according to a preset rule and network topology information.

[0284] The MEC access point closest to each terminal in the terminal group is included in the third information.

[0285] Specifically, the specific implementation of S605 can refer to the specific implementation of the first network element in the solution 1 in the aforementioned S401, which determines the first MEC access point from the MEC access point closest to each terminal in the terminal group according to the preset rules and network topology information. It will not be repeated here.

[0286] S606. The fourth network element sends the identifier of the first MEC access point to the first network element.

[0287] S607: The first network element receives, from the fourth network element, an identifier of the first MEC access point determined according to the third information.

[0288] In this way, through S601 to S607, the first network element obtains the first MEC access point to which the terminal group of the first service accesses.

[0289] S608. The first network element sends an identifier of the first MEC access point to the session management network element that controls each terminal in the terminal group, so that each terminal in the terminal group can access the first MEC access point.

[0290] It should be noted that the specific implementation of S608 can refer to the description of S402 above, which will not be repeated here.

[0291] With the method for determining MEC access points provided in the embodiments of the present application, the fourth network element, based on the instruction of the first network element, first obtains network topology information of MEC access points that support the first service, and then selects MEC access points to be accessed by terminal group users according to the network topology information. Since the network topology information reflects the location and connection relationship of the MEC access points, when selecting MEC access points based on the network topology information of the MEC access points, the actual location of the terminals in the terminal group can be considered, so that the MEC access points selected for the terminal group users have the optimal path for the users in the terminal group, thereby saving network resources while improving user experience.

[0292] On the other hand, the embodiment of the present application provides a method for determining an MEC access point. Figure 7 As shown, the method adopts the solution 3 in the above S401. Figure 7 As shown, the method may include:

[0293] S701. The first network element sends fourth information to the fifth network element. The fourth information includes an identifier of each terminal in the terminal group of the first service and an identifier of the MEC access point supporting the first service.

[0294] The fourth information may be used to indicate the first MEC access point to be accessed by the terminal group.

[0295] Specifically, the identifier of the MEC access point supporting the first service included in the fourth information can be understood as the identifier of all MEC access points supporting the first service.

[0296] The fifth network element may be any core network element that supports determining the MEC access point. For example, the fifth network element may be an SMF network element that controls any terminal in the terminal group.

[0297] For example, when the fifth network element is an SMF network element, the first network element can send the fourth information to the PCF, and the PCF forwards the fourth information to the SMF network element.

[0298] For example, the second indication information may be carried in the fourth information, and the second indication information may be used to indicate the selection of an MEC access point from the MEC access point indicated by the MEC access point identifier carried by the fourth information as the first MEC access point for access by the terminal group. The content and form of the second indication information may be configured according to actual needs and are not limited in this embodiment of the present application.

[0299] Optionally, the fourth information may further include an identifier of the first service.

[0300] Specifically, the fourth information may be newly defined information, or may be an existing request message, which is not limited in the embodiment of the present application. For example, the fourth information may be an AF request in the AF influence traffic routing process.

[0301] S702. The fifth network element receives fourth information from the first network element.

[0302] S703: The fifth network element obtains the context of each terminal in the terminal group.

[0303] The context of a terminal includes network topology information of an access network element accessed by the terminal and an MEC access point supporting the first service. The network topology information is used to indicate whether connectivity exists between the access network element accessed by the terminal and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element accessed by the terminal and the MEC access point, or between at least two MEC access points. For example, the access network element may be a RAN.

[0304] It should be noted that the format of the network topology information is similar to the network topology information described in the aforementioned S401, and will not be described in detail again.

[0305] In a possible implementation, the fifth network element obtains the context of each terminal in the terminal group in S703, which can be specifically implemented as follows: the fifth network element obtains the context of each terminal in the terminal group from a data storage function query.

[0306] Among them, the data storage function records the context of different terminals.

[0307] Exemplarily, when the terminals in the terminal group are controlled by different SMFs in the same SMF pool, different SMFs can perform data query through the unstructured data storage network function (UDSF), the fifth network element is the SMF network element, and the data storage function can be the UDSF network element.

[0308] In another possible implementation, the fifth network element queries the session management network element corresponding to the terminal other than the terminal corresponding to the fifth network element from the unified data management platform; the fifth network element obtains the context of the terminal other than the terminal corresponding to the fifth network element from the session management network element corresponding to the terminal.

[0309] The unified data management platform records the information of the corresponding session management network elements stored during the session creation phase of different terminals. The session management network elements record the context of the terminals they manage.

[0310] The terminal corresponding to the fifth network element may be a terminal managed by the fifth network element.

[0311] For example, when the terminals in a terminal group are controlled by different SMFs in the same SMF pool, different SMFs can query data through the interface between SMFs. The fifth network element is an SMF network element, the unified data management platform can be a UDM network element, and the session management network element can be an SMF network element.

[0312] S704: The fifth network element determines a first MEC access point from MEC access points supporting the first service according to a preset rule and network topology information in the context of each terminal.

[0313] Specifically, the specific implementation of S704 can refer to the specific implementation of the first network element in the solution 1 in the aforementioned S401, which determines the first MEC access point from the MEC access point closest to each terminal in the terminal group according to the preset rules and network topology information. It will not be repeated here.

[0314] S705. The fifth network element sends the identifier of the first MEC access point to the first network element.

[0315] S706. The first network element receives, from the fifth network element, an identifier of the first MEC access point determined according to the fourth information.

[0316] In this way, through S701 to S706, the first network element obtains the first MEC access point to which the terminal group accesses.

[0317] S707. The first network element sends an identifier of the first MEC access point to the session management network element that controls each terminal in the terminal group, so that each terminal in the terminal group can access the first MEC access point.

[0318] It should be noted that the specific implementation of S707 can refer to the description of S402 above, which will not be repeated here.

[0319] Through the method for determining MEC access points provided in the embodiments of the present application, network topology information of access network elements accessed by terminals in the terminal group and MEC access points supporting the first service is first obtained. Then, according to the network topology information, a MEC access point for access by the terminal group users is selected. Since the network topology information reflects the location and connection relationship of the MEC access point, when selecting the MEC access point based on the network topology information of the MEC access point, the actual location of the terminals in the terminal group can be considered. This ensures that the MEC access point selected for the terminal group users has the optimal path for the users in the terminal group, thereby saving network resources while improving the user experience.

[0320] The following describes the method for determining MEC access points provided in this application through specific embodiments.

[0321] Example 1

[0322] The method for determining the MEC access point provided in the first embodiment of the present application can be as follows: Figure 8 As shown, in this scenario, it is assumed that multiple UEs in the terminal group of the first service are controlled by multiple different SMFs. Figure 8 As shown, the method may include:

[0323] S801. Multiple UEs simultaneously initiate matching requests for a first service to a service server.

[0324] The matching request is used to request a first service, and the multiple UEs are UEs in a group for the first service.

[0325] S802: The service server determines to enable the MEC server to provide services for the group of UEs and sends a request 1 to the AF / NEF.

[0326] The request 1 includes the identifiers of multiple UEs and the identifier of the DNAI supporting the first service.

[0327] It should be noted that the embodiment of the present application does not elaborate on the specific method by which the business server determines whether to start the MEC server.

[0328] S803. The AF / NEF queries the PCF corresponding to each UE in the group through a binding support function (BSF).

[0329] S804: The AF / NEF initiates an AF request to the PCF.

[0330] The AF request carries the identifier of the DNAI supporting the first service and the identifier of the UE, and the AF request is used to query the latest DNAI of each UE.

[0331] S805. The PCF forwards the AF request to its corresponding SMF1.

[0332] S806. SMF1 determines the DNAI closest to the UE it controls.

[0333] Specifically, in S806, SMF1 determines the DNAI closest to the UE based on the DNAI supporting the first service in the AF request, the UE location information indicated by the UE identifier in the AF request, and the topology information of the UE.

[0334] S807. SMF1 feeds back to the AF / NEF the DNAI closest to the UE.

[0335] S808. The AF / NEF receives the DNAI closest to the UE fed back by the SMF1 corresponding to each terminal in the terminal group.

[0336] S809. The AF / NEF initiates a query request to the NWDAF.

[0337] The query request includes a first DNAI list, where the first DNAI list is the DNAI closest to each UE in the terminal group, and the query request is used to request feedback of DNAI topology information in the first DNAI list.

[0338] Exemplarily, the query request may be a Nnwdaf_AnalyticsInfo_Request message.

[0339] S810. NWDAF provides the first DNAI list to NRF and obtains the address of SMF2 corresponding to each DNAI in the first DNAI list.

[0340] S811. NWDAF provides the first DNAI list to each SMF2 according to the SMF2 address, and requests the topology information of the known DNAIs.

[0341] S812. SMF2 feeds back the topology information of its known DNAIs in the first DNAI list to NWDAF.

[0342] S813. NWDAF aggregates DNAI topology information based on the collected topology information and the first DNAI list to obtain network topology information of the first DNAI list.

[0343] S814. The NWDAF sends a query request response to the AF / NEF, feeding back the network topology information of the first DNAI list obtained through aggregation.

[0344] The query request response may be a Nnwdaf_AnalyticsInfo_Request response message.

[0345] S815. The AF / NEF determines the optimal DNAI for access by the terminal group of the first service based on the network topology information of the first DNAI list.

[0346] It should be noted that the specific implementation of S815 can refer to the process of the first network element determining the first MEC access point in Solution 1 of S401, and will not be repeated here.

[0347] S816. The AF / NEF sends the optimal DNAI to the service server.

[0348] S817. The AF / NEF sends the optimal DNAI to the SMF1 of each UE through the PCF of each UE.

[0349] S818. SMF1 selects a local PSA for the UE according to the optimal DNAI and inserts ULCL / BP.

[0350] Specifically, the specific implementation of S818 may refer to the process of inserting ULCL defined in 3Gpp 23.502, which is not described in detail in this application.

[0351] S819. After the path is established, SMF1 feeds back the path creation status to AF / NEF.

[0352] The path creation situation may include the determined optimal DNAI and the connectivity situation of the terminals in the terminal group to the determined optimal DNAI (for example, all the terminals in the group can connect to the determined optimal DNAI).

[0353] S820. The AF / NEF feeds back the path creation status to the service server.

[0354] S821. The service server sends the address of the MEC server corresponding to the optimal DNAI to the UE through the original user plane path according to the address of the MEC server corresponding to the optimal DNAI.

[0355] S822. The UE conducts business with the MEC server through the newly created DNAI path according to the address of the MEC server.

[0356] It should be noted that the above S803 to S807 and S817 to S821 are performed separately for each UE and will not be described in detail.

[0357] In embodiment 1, the basic process of AF influence traffic routing is first used to query the surrounding DNAIs for the terminal group of the first service one by one, and the list of DNAIs closest to each UE is provided to NWDAF. The network topology information between each DNAI is queried from NWDAF. Finally, AF / NEF makes a decision based on the network topology information to determine the optimal DNAI, and then allocates all UEs in the terminal group to the optimal DNAI through the AF influence traffic routing process.

[0358] Example 2

[0359] The method for determining the MEC access point provided in the second embodiment of the present application can be as follows: Figure 9 As shown, in this scenario, it is assumed that multiple UEs in the terminal group of the first service are controlled by multiple different SMFs. Figure 9 As shown, the method may include:

[0360] S901. Multiple UEs simultaneously initiate matching requests for a first service to a service server.

[0361] S902: The service server determines to enable the MEC server to provide services for the group of UEs and sends a request 1 to the AF / NEF.

[0362] S903. The AF / NEF queries the PCF corresponding to each UE in the group through the BSF.

[0363] S904: The AF / NEF initiates an AF request to the PCF.

[0364] S905. The PCF forwards the AF request to its corresponding SMF1.

[0365] S906. SMF1 determines the DNAI closest to the UE it controls.

[0366] S907. SMF1 feeds back the determined latest DNAI to AF / NEF.

[0367] It should be noted that the above S903 to S907 are performed separately for each UE and will not be described in detail.

[0368] S908. The AF / NEF receives the DNAI closest to the UE fed back by the SMF1 corresponding to each terminal in the terminal group.

[0369] It should be noted that the specific implementation of S901 to S908 is the same as that of S801 to S808, and will not be repeated here.

[0370] S909, AF / NEF select SMF3 / ECS that supports DNAI topology selection.

[0371] S910. AF / NEF sends the first DNAI list to SMF3 / ECS.

[0372] Among them, the first DNAI list is the DNAI closest to each UE in the terminal group

[0373] S911. SMF3 / ECS determines the optimal DNAI from the first DNAI list.

[0374] Specifically, SMF3 / ECS can determine the optimal DNAI based on the network topology information of the DNAI in the first DNAI list and preset rules.

[0375] It should be noted that the specific implementation of S911 can refer to the process of the first network element determining the first MEC access point in Solution 1 of S401, which will not be repeated here.

[0376] In a possible implementation, the network topology information of the DNAI in the first DNAI list is stored locally in the SMF3 / ECS.

[0377] In another possible implementation, if the network topology information of the first DNAI list is not stored locally in the SMF3 / ECS, the SMF3 / ECS may obtain the network topology information of the DNAI in the first DNAI list through the following steps A to D:

[0378] Step A: SMF3 / ECS provides the first DNAI list to NRF and obtains the address of SMF2 / OAM corresponding to each DNAI in the first DNAI list.

[0379] Step B: SMF3 / ECS provides the first DNAI list to each SMF2 / OAM according to the SMF2 / OAM address, and requests the topology information of its known DNAIs.

[0380] Step C: SMF2 / OAM feeds back the topology information of the known DNAIs in the first DNAI list to SMF3 / ECS.

[0381] Step D: SMF3 / ECS aggregates DNAI topology information based on the collected topology information and the first DNAI list to obtain the network topology information of the first DNAI list.

[0382] S912. SMF3 / ECS sends the optimal DNAI to AF / NEF.

[0383] After S912, the AF / NEF sends the selected DNAI to the SMF of each UE through the AF influencetraffic routing of each UE according to the process from S816 to S822 to perform the DNAI change process.

[0384] Example 2 is similar to Example 1. First, the basic process of AF influence traffic routing is used to query the surrounding DNAIs for the terminal group of the first service one by one, and the list of DNAIs closest to each UE is provided to SMF3 / ECS. SMF3 / ECS queries the network topology information between each DNAI and determines the optimal DNAI, which is fed back to AF / NEF. Then, all UEs in the terminal group are assigned to the optimal DNAI through the AF influence traffic routing process.

[0385] Example 3

[0386] The method for determining the MEC access point provided in the third embodiment of the present application can be as follows: Figure 10 As shown, in this scenario, it is assumed that multiple UEs are controlled by different SMFs in the same SMF pool. Different SMFs can query data through UDSF, and each SMF can control and adjust the UPF under its connection. Figure 10 As shown, the method may include:

[0387] S1001. Multiple UEs simultaneously initiate matching requests for a first service to a service server.

[0388] S1002: The service server determines to enable the MEC server to provide services for the group of UEs and sends a request 1 to the AF / NEF.

[0389] S1003. The AF / NEF queries the PCF corresponding to each UE in the group through the BSF.

[0390] S1004: The AF / NEF selects a PCF and initiates an AF request to the selected PCF.

[0391] The AF request includes first indication information, an identifier of the UE in the group of the first service, and an identifier of the first service. The first indication information is used to indicate the optimal DNAI for the UE in the query group to access the first service.

[0392] For example, the UE identifier may be the IP address of the UE.

[0393] S1005. PCF forwards the AF request to the corresponding SMF.

[0394] S1006. The SMF provides the UE identifier to the UDSF and queries the UE context.

[0395] The context of the UE includes network topology information between the access network device accessed by the UE and the DNAI supporting the first service, as well as network topology information between the DNAIs supporting the first service.

[0396] Specifically, in S1006, the SMF determines, based on the AF request, the optimal DNAI for accessing the group to which the terminal identifier in the AF request belongs, and the SMF queries the UDSF for the context of the UE.

[0397] S1007. The SMF determines the optimal DNAI from the second DNAI List according to the distribution of UEs and the network topology information in the context.

[0398] The second DNAI List includes all DNAIs that support the first service.

[0399] It should be noted that the specific implementation of S1007 can refer to the process of the first network element determining the first MEC access point in Solution 1 of S401, and will not be repeated here.

[0400] S1008. The SMF sends the optimal DNAI to the AF / NEF.

[0401] After S1008, the AF / NEF sends the determined optimal DNAI to the SMF of each UE through the AF influence traffic routing of each UE according to the process from S816 to S822 to perform the DNAI change process.

[0402] The solution adopted in Example 3 is that AF / NEF selects only one PCF / SMF when sending AF request, and carries the identifiers of all UEs in the terminal group in AFrequest. The selected SMF queries other SMFs for relevant information and topology information of the corresponding UE through UDSF, and the SMF selects DNAI, and then feeds back the determined optimal DNAI to AF / NEF. AF / NEF sends the selected optimal DNAI to the SMF of each UE through the AF influence traffic routing of each UE to perform the DNAI change process.

[0403] Example 4

[0404] The method for determining the MEC access point provided in the fourth embodiment of the present application can be as follows: Figure 11 As shown, in this scenario, it is assumed that multiple UEs are controlled by different SMFs in the same SMF pool. Different SMFs can query data through the interface between SMFs, and each SMF can control and adjust the UPF to which it is connected. Figure 11 As shown, the method may include:

[0405] S1101. Multiple UEs simultaneously initiate matching requests for a first service to a service server.

[0406] S1102: The service server determines to enable the MEC server to provide services for the group of UEs and sends a request 1 to the AF / NEF.

[0407] S1103. The AF / NEF queries the PCF corresponding to each UE in the terminal group through the BSF.

[0408] S1104: The AF / NEF selects a PCF and initiates an AF request to the selected PCF.

[0409] S1105. PCF forwards the AF request to the corresponding SMF.

[0410] It should be noted that S1101 to S1105 are the same as S1001 to S1005 and will not be described in detail.

[0411] S1106. The SMF provides the UE identifier to the UDM and queries the UE context.

[0412] The UE context is the same as that in S1006 and will not be described in detail.

[0413] Specifically, in S1006, the SMF determines the optimal DNAI for accessing the terminal group to which the terminal identifier in the AF request belongs based on the AF request, and the SMF queries the UDM for the context of the UE.

[0414] S1107. The SMF determines the optimal DNAI from the second DNAI List according to the distribution of UEs and the network topology information in the context.

[0415] It should be noted that the specific implementation of S1107 can refer to the process of the first network element determining the first MEC access point in Solution 1 of S401, and will not be repeated here.

[0416] S1108. The SMF sends the optimal DNAI to the AF / NEF.

[0417] After S1108, the AF / NEF sends the selected optimal DNAI to the SMF of each UE through the AF influence traffic routing of each UE according to the process from S816 to S822 to perform the DNAI change process.

[0418] The above mainly introduces the solution provided by the embodiment of the present invention from the perspective of the working principle of the network element. It can be understood that, in order to implement the above functions, each network element includes a hardware structure and / or software module corresponding to each function, which is called a device for selecting an MEC access point. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0419] In the embodiment of the present invention, the functional modules of the device for determining the MEC access point, etc. can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present invention is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0420] In the case of dividing each functional module into corresponding functional modules, Figure 12 The embodiment of the present application provides a device 120 for determining an MEC access point, which is used to implement the function of the first network element in the above embodiment. The device 120 for determining an MEC access point can be the first network element or the device 120 for determining an MEC access point can be deployed in the first network element. Figure 12 As shown, the device 120 for determining the MEC access point may include: an acquisition unit 1201 and a sending unit 1202. The acquisition unit 1201 is used to perform Figure 4 Process S401 in, or, Figure 5 Processes S501-S504, S505, S511 and S512 in, or, Figure 6 Process S601, S602, S607, or, Figure 7 Process S701, S706 in the sending unit 1202 is used to execute Figure 4 Process S402 in, or Figure 5 Process S513 in, or Figure 6 Process S608 in, or Figure 7 In the process S707, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.

[0421] In the case of integrated units, such as Figure 13 The communication device 130 provided in an embodiment of the present application is shown, which is used to implement the function of the first network element in the above method. The communication device 130 includes at least one processing module 1301. Exemplarily, the processing module 1301 can be used to execute the process S401 in 4, or, Figure 5 Processes S501-S504, S505, S511 and S512 in, or, Figure 6 Process S601, S602, S607, or, Figure 7 For details about processes S701 and S706, please refer to the detailed description in the method example and will not be repeated here.

[0422] The communication device 130 may also include at least one storage module 1302 for storing program instructions and / or data. The storage module 1302 is coupled to the processing module 1301. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processing module 1301 may operate in conjunction with the storage module 1302. The processing module 1301 can execute program instructions stored in the storage module 1302. At least one of the at least one storage module may be included in the processing module.

[0423] The communication device 130 may further include a communication module 1303 for communicating with other devices via a transmission medium, thereby determining whether the communication device 130 can communicate with other devices. The communication module 1303 is used for the device to communicate with other devices. For example, the processor 1301 may use the communication module 1303 to execute Figure 4 Process S402 in, or Figure 5 Process S513 in, or Figure 6 Process S608 in, or Figure 7 Process S707 in .

[0424] When the processing module 1301 is a processor, the storage module 1302 is a memory, and the communication module 1303 is a communication interface, the communication device 130 involved in this application can be Figure 3 The communication device 30 is shown.

[0425] As mentioned above, the device 120 or communication device 130 for determining the MEC access point provided in the embodiment of the present application can be used to implement the function of the first network element in the method implemented in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0426] In the case of dividing each functional module into corresponding functional modules, Figure 14 The embodiment of the present application provides a device 140 for determining an MEC access point, which is used to implement the function of the third network element in the above embodiment. The device 140 for determining an MEC access point can be a third network element or the device 140 for determining an MEC access point can be deployed in a third network element. Figure 14 As shown, the device 140 for determining the MEC access point may include: a receiving unit 1401, an acquiring unit 1402, a sending unit 1403 and an aggregation unit 1404. The receiving unit 1401 is used to perform Figure 5 Process S506, S509 in the acquisition unit 1402 is used to perform Figure 5 Process S507 in the sending unit 1403 is used to execute Figure 5 Process S508, S511 in; aggregation unit 1404 is used to perform Figure 5 In the process S510, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0427] In the case of integrated units, such as Figure 15 The figure shows a communication device 150 provided in an embodiment of the present application, which is used to implement the functions of the third network element in the above method. Communication device 150 includes at least one processing module 1501. For example, processing module 1501 can be used to perform process S507 in step 5. For details, please refer to the detailed description in the method example, which is not repeated here.

[0428] The communication device 150 may also include at least one storage module 1502 for storing program instructions and / or data. The storage module 1502 is coupled to the processing module 1501. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processing module 1501 may operate in conjunction with the storage module 1502. The processing module 1501 can execute program instructions stored in the storage module 1502. At least one of the at least one storage module may be included in the processing module.

[0429] The communication device 150 may further include a communication module 1503 for communicating with other devices via a transmission medium, thereby determining whether the communication device 150 can communicate with other devices. The communication module 1503 is used for the device to communicate with other devices. For example, the processor 1501 may use the communication module 1503 to execute Figure 5 Processes S506, S508, S509, and S510.

[0430] When the processing module 1501 is a processor, the storage module 1502 is a memory, and the communication module 1503 is a communication interface, the communication device 150 involved in this application can be Figure 3 The communication device 30 is shown.

[0431] As mentioned above, the device 140 or communication device 150 for determining the MEC access point provided in the embodiment of the present application can be used to implement the function of the third network element in the method implemented in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0432] In the case of dividing each functional module into corresponding functional modules, Figure 16 The embodiment of the present application provides a device 160 for determining an MEC access point, which is used to implement the function of the fourth network element in the above embodiment. The device 160 for determining an MEC access point can be the fourth network element or the device 160 for determining an MEC access point can be deployed in the fourth network element. Figure 16 As shown, the device 160 for determining an MEC access point may include: a receiving unit 1601, an acquiring unit 1602, a determining unit 1603, and a sending unit 1604. The receiving unit 1601 is configured to execute Figure 6 Process S603 in the acquisition unit 1602 is used to execute Figure 6 Process S604 in the determination unit 1603 is used to perform Figure 6 Process S605 in the sending unit 1604 is used to execute Figure 6 In the process S606, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.

[0433] In the case of integrated units, such as Figure 17 The figure shows a communication device 170 provided in an embodiment of the present application, which is used to implement the functions of the fourth network element in the above method. Communication device 170 includes at least one processing module 1701. For example, processing module 1701 can be used to perform processes S604 and S605 in step 6. For details, please refer to the detailed description in the method example and will not be repeated here.

[0434] The communication device 170 may also include at least one storage module 1702 for storing program instructions and / or data. The storage module 1702 is coupled to the processing module 1701. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processing module 1701 may operate in conjunction with the storage module 1702. The processing module 1701 can execute program instructions stored in the storage module 1702. At least one of the at least one storage module may be included in the processing module.

[0435] The communication device 170 may further include a communication module 1703 for communicating with other devices via a transmission medium, thereby determining whether the communication device 170 can communicate with other devices. The communication module 1703 is used for the device to communicate with other devices. For example, the processor 1701 may use the communication module 1703 to execute Figure 6 Processes S603 and S606 in .

[0436] When the processing module 1701 is a processor, the storage module 1702 is a memory, and the communication module 1703 is a communication interface, the communication device 170 involved in this application can be Figure 3 The communication device 30 is shown.

[0437] As mentioned above, the device 160 or communication device 170 for determining the MEC access point provided in the embodiment of the present application can be used to implement the function of the fourth network element in the method implemented in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0438] In the case of dividing each functional module into corresponding functional modules, Figure 18 The embodiment of the present application provides a device 180 for determining an MEC access point, which is used to implement the function of the fifth network element in the above embodiment. The device 180 for determining an MEC access point can be the fifth network element or the device 180 for determining an MEC access point can be deployed in the fifth network element. Figure 18 As shown, the device 180 for selecting an MEC access point may include: a receiving unit 1801, an acquiring unit 1802, a determining unit 1803, and a sending unit 1804. The receiving unit 1801 is used to perform Figure 7 Process S702 in the acquisition unit 1802 is used to execute Figure 7 Process S703 in the determination unit 1803 is used to perform Figure 7 Process S704 in the sending unit 1804 is used to execute Figure 7In the process S705, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.

[0439] In the case of integrated units, such as Figure 19 The figure shows a communication device 190 provided in an embodiment of the present application, which is used to implement the functions of the fifth network element in the above method. Communication device 190 includes at least one processing module 1901. For example, processing module 1901 can be used to perform processes S703 and S704 in 7. For details, please refer to the detailed description in the method example and will not be repeated here.

[0440] The communication device 190 may also include at least one storage module 1902 for storing program instructions and / or data. The storage module 1902 is coupled to the processing module 1901. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processing module 1901 may operate in conjunction with the storage module 1902. The processing module 1901 can execute program instructions stored in the storage module 1902. At least one of the at least one storage module may be included in the processing module.

[0441] The communication device 190 may further include a communication module 1903 for communicating with other devices via a transmission medium, thereby determining whether the communication device 190 can communicate with other devices. The communication module 1903 is used for the device to communicate with other devices. For example, the processor 1901 may use the communication module 1903 to execute Figure 7 Processes S702 and S705 in .

[0442] When the processing module 1901 is a processor, the storage module 1902 is a memory, and the communication module 1903 is a communication interface, the communication device 190 involved in this application can be Figure 3 The communication device 30 is shown.

[0443] As mentioned above, the device 180 or communication device 190 for determining the MEC access point provided in the embodiment of the present application can be used to implement the function of the fifth network element in the method implemented in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0444] An embodiment of the present application further provides a communication system, which may include a communication device 130 .

[0445] In a possible implementation, the communication system may further include one or more of the communication device 150 , the communication device 170 , and the communication device 190 .

[0446] As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored. When the instructions are executed, the method for determining an MEC access point in the above method embodiment is performed.

[0447] As another form of this embodiment, a computer program product including instructions is provided. When the computer program product is run on a computer, the computer is caused to perform the method for determining an MEC access point in the above method embodiment.

[0448] The embodiment of the present application further provides a chip system, which includes a processor for implementing the technical method of the embodiment of the present application. In one possible design, the chip system also includes a memory for storing the necessary program instructions and / or data of the embodiment of the present invention. In one possible design, the chip system also includes a memory for the processor to call the application code stored in the memory. The chip system can be composed of one or more chips, or can include chips and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0449] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0450] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0451] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0452] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0453] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0454] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The first network element obtains a first MEC access point accessed by a terminal group for a first service, where the first MEC access point is obtained based on at least network topology information of a MEC access point supporting the first service that is closest to each terminal in the terminal group; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; The first network element sends an identifier of the first MEC access point to a session management network element that controls each of the terminals, so that each of the terminals accesses the first MEC access point.

2. The method according to claim 1, characterized in that The first network element acquiring a first MEC access point accessed by a terminal group of the first service includes: The first network element sends first information to the second network element corresponding to each terminal, where the first information includes an identifier of the MEC access point supporting the first service and an identifier of the terminal managed by the second network element in the terminal group; The first network element receives, from each of the second network elements, an identifier of the MEC access point closest to each of the terminals, determined according to the first information; The first network element sends second information to the third network element, where the second information includes an identifier of the MEC access point closest to each of the terminals; The first network element receives the network topology information obtained according to the second information from the third network element; The first network element determines the first MEC access point from the MEC access points closest to each of the terminals according to a preset rule and the network topology information.

3. The method according to claim 1, characterized in that The first network element acquiring a first MEC access point accessed by a terminal group of the first service includes: The first network element sends first information to the second network element corresponding to each terminal respectively, where the first information includes an identifier of the MEC access point supporting the first service and an identifier of the terminal managed by the second network element in the terminal group; The first network element receives, from each of the second network elements, the MEC access point closest to each of the terminals, determined according to the first information; The first network element sends third information to the fourth network element, where the third information includes an identifier of the MEC access point closest to each of the terminals; The first network element receives, from the fourth network element, an identifier of the first MEC access point determined according to the third information.

4. The method according to claim 1, wherein The first network element acquiring a first MEC access point accessed by a terminal group of the first service includes: The first network element sends fourth information to the fifth network element, where the fourth information includes an identifier of each of the terminals and an identifier of the MEC access point supporting the first service; The first network element receives, from the fifth network element, an identifier of the first MEC access point determined according to the fourth information.

5. The method according to claim 2, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

6. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The third network element receives second information from the first network element, where the second information includes identifiers of multiple MEC access points; the MEC access points support the first service; The third network element obtains a sixth network element corresponding to each MEC access point in the multiple MEC access points; The third network element sends fifth information to each of the sixth network elements, where the fifth information includes identifiers of the multiple MEC access points; The third network element receives, from each of the sixth network elements, topology information between the MEC access points known to the sixth network element among the multiple MEC access points acquired according to the fifth information; the topology information is used to indicate whether at least two MEC access points are connected, and / or the topology information is used to indicate link performance between at least two MEC access points; The third network element aggregates the topology information to obtain network topology information; The third network element sends the network topology information to the first network element, where the network topology information is used to determine the MEC access point to which the terminal group of the first service accesses; the terminal group of the first service includes terminals requesting the first service and / or terminals subscribing to the first service.

7. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The fourth network element receives third information from the first network element, where the third information includes identifiers of multiple MEC access points, and the MEC access points support the first service; The fourth network element obtains network topology information of the multiple MEC access points; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; The fourth network element determines, from the multiple MEC access points, a first MEC access point to which a terminal group for the first service accesses according to a preset rule and the network topology information; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; The fourth network element sends the identifier of the first MEC access point to the first network element.

8. The method according to claim 7, characterized in that The fourth network element obtains network topology information of the multiple MEC access points, including: The fourth network element stores the network topology information; or, The fourth network element obtains a sixth network element corresponding to each MEC access point; the fourth network element sends fifth information to each sixth network element, where the fifth information includes identifiers of the multiple MEC access points; the fourth network element receives topology information of MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information from each sixth network element, where the topology information is used to indicate whether at least two MEC access points are connected and / or the topology information is used to indicate link performance between at least two MEC access points; and the network topology information is obtained by aggregating the topology information.

9. The method according to claim 7 or 8, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

10. The method according to claim 8, characterized in that The sixth network element is an operation and maintenance management network element or a session management network element.

11. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The fifth network element receives fourth information from the first network element, where the fourth information includes an identifier of a terminal in a terminal group for the first service and an identifier of an MEC access point that supports the first service; the terminal group for the first service includes a terminal that requests the first service and / or a terminal that subscribes to the first service; The fifth network element obtains a context of each terminal in the terminal group, where the context of one terminal includes network topology information of an access network element accessed by the one terminal and a MEC access point supporting the first service; the network topology information is used to indicate whether there is connectivity between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points; The fifth network element determines, according to a preset rule and the network topology information in the context of each terminal, a first MEC access point to be accessed by the terminal group from the MEC access points supporting the first service; The fifth network element sends the identifier of the first MEC access point to the first network element.

12. The method according to claim 11, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

13. The method according to claim 11 or 12, characterized in that The fifth network element obtains the context of each terminal in the terminal group, including: The fifth network element obtains the context of each terminal from a data storage function query; The fifth network element queries the session management network element corresponding to the terminal other than the terminal corresponding to the fifth network element from the unified data management platform; the fifth network element obtains the context of the terminal other than the terminal corresponding to the fifth network element from the session management network element corresponding to each of the terminals.

14. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The first network element obtains an identifier of an MEC access point closest to each terminal in a terminal group for a first service, where the MEC access point supports the first service; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; The first network element sends second information to the third network element, where the second information includes an identifier of the MEC access point closest to each of the terminals; The third network element receives the second information from the first network element; The third network element determines, based on the second information, network topology information of the MEC access point closest to each of the terminals; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; The third network element sends the network topology information to the first network element; The first network element receives the network topology information obtained according to the second information from the third network element; The first network element determines, according to a preset rule and the network topology information, a first MEC access point to be accessed by the terminal group from among the MEC access points closest to each of the terminals.

15. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The first network element obtains an identifier of an MEC access point closest to each terminal in a terminal group for a first service, where the MEC access point supports the first service; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; The first network element sends third information to the fourth network element, where the third information includes an identifier of the MEC access point closest to each of the terminals; The fourth network element receives the third information from the first network element; The fourth network element obtains network topology information of the MEC access point closest to each of the terminals; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; The fourth network element determines, according to a preset rule and the network topology information, a first MEC access point to be accessed by the terminal group from the MEC access points closest to each of the terminals; The fourth network element sends the identifier of the first MEC access point to the first network element; The first network element receives, from the fourth network element, an identifier of the first MEC access point determined according to the third information.

16. A method for determining a multi-access edge computing MEC access point, characterized in that: The method comprises: The first network element sends fourth information to the fifth network element, where the fourth information includes an identifier of each terminal in a terminal group for the first service and an identifier of an MEC access point that supports the first service; the terminal group for the first service includes terminals that request the first service and / or terminals that subscribe to the first service; The fifth network element receives the fourth information from the first network element; The fifth network element obtains a context of each terminal in the terminal group, where the context of one terminal includes network topology information of an access network element accessed by the one terminal and a MEC access point supporting the first service; the network topology information is used to indicate whether there is connectivity between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points; The fifth network element determines, according to a preset rule and the network topology information in the context of each terminal, a first MEC access point to be accessed by the terminal group from the MEC access points supporting the first service; The fifth network element sends the identifier of the first MEC access point to the first network element; The first network element receives, from the fifth network element, an identifier of the first MEC access point determined according to the fourth information.

17. A device for determining a multi-access edge computing MEC access point, characterized in that: The device comprises: an acquiring unit, configured to acquire a first MEC access point accessed by a terminal group for a first service, the first MEC access point being obtained based on at least network topology information of a MEC access point supporting the first service that is closest to each terminal in the terminal group; the network topology information being used to indicate whether at least two MEC access points are connected, and / or the network topology information being used to indicate link performance between at least two MEC access points; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; A sending unit is configured to send the identifier of the first MEC access point obtained by the obtaining unit to a session management network element that controls each of the terminals, so that each of the terminals accesses the first MEC access point.

18. The device according to claim 17, characterized in that The acquisition unit is specifically configured to: Sending first information to the second network element corresponding to each terminal respectively, where the first information includes an identifier of the MEC access point supporting the first service and an identifier of the terminal managed by the second network element in the terminal group; Receiving, from each of the second network elements, an identifier of the MEC access point closest to each of the terminals, determined according to the first information; Sending second information to the third network element, where the second information includes an identifier of the MEC access point closest to each of the terminals; receiving, from the third network element, the network topology information acquired according to the second information; According to a preset rule and the network topology information, the first MEC access point is determined from the MEC access points closest to each of the terminals.

19. The device according to claim 17, characterized in that The acquisition unit is specifically configured to: Sending first information to the second network element corresponding to each terminal respectively, where the first information includes an identifier of the MEC access point supporting the first service and an identifier of the terminal managed by the second network element in the terminal group; Receiving, from each of the second network elements, the MEC access point closest to each of the terminals, determined according to the first information; Sending third information to the fourth network element, where the third information includes an identifier of the MEC access point closest to each of the terminals; receiving, from the fourth network element, an identifier of the first MEC access point determined according to the third information.

20. The device according to claim 17, wherein The acquisition unit is specifically configured to: Sending fourth information to the fifth network element, where the fourth information includes an identifier of each of the terminals and an identifier of the MEC access point supporting the first service; receiving, from the fifth network element, an identifier of the first MEC access point determined according to the fourth information.

21. The device according to claim 18, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

22. A device for determining a multi-access edge computing MEC access point, characterized in that: The device comprises: A receiving unit, configured to receive second information from a first network element, where the second information includes identifiers of multiple MEC access points, where the MEC access points support a first service; An acquiring unit, configured to acquire a sixth network element corresponding to each MEC access point among the multiple MEC access points; a sending unit, configured to send fifth information to each of the sixth network elements, where the fifth information includes identifiers of the multiple MEC access points; The receiving unit is further configured to receive, from each of the sixth network elements, topology information between MEC access points known to the sixth network element among the multiple MEC access points obtained according to the fifth information; the topology information is used to indicate whether at least two MEC access points are connected, and / or the topology information is used to indicate link performance between at least two MEC access points; an aggregation unit, aggregating the topology information to obtain network topology information; The sending unit is further used to send the network topology information to the first network element, where the network topology information is used to determine the MEC access point accessed by the terminal group of the first service; the terminal group of the first service includes the terminal requesting the first service and / or the terminal subscribing to the first service.

23. A device for determining a multi-access edge computing MEC access point, characterized in that: The device comprises: A receiving unit, configured to receive third information from the first network element, where the third information includes identifiers of multiple MEC access points, where the MEC access points support the first service; an acquiring unit, configured to acquire network topology information of the multiple MEC access points; the network topology information is used to indicate whether at least two MEC access points are connected, and / or the network topology information is used to indicate link performance between at least two MEC access points; a determining unit, configured to determine, from the multiple MEC access points, a first MEC access point to be accessed by a terminal group for the first service, based on a preset rule and the network topology information; the terminal group for the first service includes terminals requesting the first service and / or terminals subscribing to the first service; A sending unit is configured to send an identifier of the first MEC access point to the first network element.

24. The device according to claim 23, characterized in that The acquisition unit is specifically configured to: obtaining the network topology information stored in the device; or, Obtain a sixth network element corresponding to each MEC access point; and send fifth information to each sixth network element, where the fifth information includes identifiers of the multiple MEC access points. Receiving, from each of the sixth network elements, topology information of a MEC access point known to the sixth network element among the multiple MEC access points obtained according to the fifth information, where the topology information is used to indicate whether at least two MEC access points are connected, and / or, the topology information is used to indicate link performance between at least two MEC access points; and obtaining the network topology information by aggregating the topology information.

25. The device according to claim 23 or 24, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

26. The device according to claim 24, characterized in that The sixth network element is an operation and maintenance management network element or a session management network element.

27. A device for determining a multi-access edge computing MEC access point, characterized in that: The device comprises: a receiving unit, configured to receive fourth information from the first network element, the fourth information including an identifier of a terminal in a terminal group for a first service and an identifier of an MEC access point supporting the first service; the terminal group for the first service includes a terminal requesting the first service and / or a terminal subscribing to the first service; an acquiring unit, configured to acquire a context of each terminal in the terminal group, the context of one terminal including network topology information of an access network element accessed by the one terminal and a MEC access point supporting the first service; the network topology information is used to indicate whether there is connectivity between the access network element and the MEC access point, or between at least two MEC access points, and / or the network topology information is used to indicate link performance between the access network element and the MEC access point, or between at least two MEC access points; a determining unit, configured to determine, from the MEC access points supporting the first service, a first MEC access point to be accessed by the terminal group, based on a preset rule and the network topology information in the context of each terminal; A sending unit is configured to send an identifier of the first MEC access point to the first network element.

28. The device according to claim 27, characterized in that The preset rules include: The first MEC access point is determined from the network topology information according to the load and / or delay of the MEC access point.

29. The device according to claim 27 or 28, characterized in that The acquisition unit is specifically configured to: Obtaining the context of each terminal from a data storage function query; The session management network elements corresponding to terminals other than the terminal corresponding to the device are queried from the unified data management platform; and the contexts of the terminals other than the terminal corresponding to the device are respectively obtained from the session management network elements corresponding to each of the terminals.

30. A communication device, characterized in that: The communication device includes: a processor and a memory; The memory is connected to the processor; the memory is used to store computer instructions, and when the processor executes the computer instructions, the communication device executes the method for determining a multi-access edge computing MEC access point according to any one of claims 1 to 16.

31. A communication system, characterized in that: Comprising the device according to claim 17 or 18 or 21, and the device according to claim 22.

32. A communication system, characterized in that: The invention comprises the device according to claim 17 or 19, and the device according to any one of claims 23 to 26.

33. A communication system, characterized in that: The invention comprises the device according to claim 17 or 20, and the device according to any one of claims 27 to 29.

34. A computer-readable storage medium, characterized in that The method comprises instructions which, when executed on a computer, cause the computer to execute the method for determining a multi-access edge computing MEC access point according to any one of claims 1 to 16.

35. A computer program product, characterized in that When the method is run on a computer, the computer is enabled to execute the method for determining a multi-access edge computing MEC access point according to any one of claims 1 to 16.

Images