MEC information transmission method and device

Abstract

The invention provides a multi-access edge computing (MEC) information transmission method and device, and the method comprises the steps: storing MEC configuration information and service configuration information in a UDM, and completing the registration of an MEC and the registration of a service; initiating authentication and a request to unified data management (UDM), and obtaining MEC configuration information and service configuration information; and according to the MEC configuration information and the service configuration information, realizing mutual communication between the MECs and communication between user equipment (UE) and services on the MECs. Therefore, the MEC platform management (MEPM module) in the fusion architecture of the 5G core network and the MEC defined by the existing standard is reduced, the architecture complexity is reduced, the MEC can be ensured to quickly register, discover and complete mutual access, and convenience is provided for the user terminal to access the service carried on the MEC.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a multi-access edge computing (MEC) information transmission method and device. Background Art

[0002] According to the definition of the International Telecommunication Union (ITU), 2020 is designated as the year for the commercialization of the fifth generation of mobile communication technology (5G), the so-called first year of 5G. However, in fact, my country has already begun to study and explore 5G technology as early as 2019. 5G has the characteristics of high bandwidth, low latency and large connection. The key technologies mainly include network function virtualization (NFV), software defined network (SDN), network slicing and MEC. MEC is a cloud-based information technology computing and storage environment located at the edge of the network. It is closer to the edge of the user, reduces network latency, and can better provide low-latency, high-bandwidth applications, greatly improving user experience.

[0003] Currently, the 3rd Generation Partnership Project (3GPP) has given the following suggestions for the combination of 5G and MEC in standards TS23.501 and TS23.502. Figure 1 The reference design mainly includes two parts. First, to enable low-latency, high-bandwidth, and high-reliability edge applications in vertical industries, the user plane function (UPF) is moved down to the campus close to the MEC, and the data is forwarded to the MEC edge server through the UPF's local diversion technology, the uplink classifier / IPv6 branching point (UL-CL / IPv6 BP). Second, the application function (AF) of the core network is moved down to the MEC to provide better data flow control strategies (coding strategies, QoS strategies, routing strategies, etc.) for applications deployed on the MEC platform.

[0004] In order to meet the growing business needs and ensure the continuity of user equipment UE service access, the source MEC edge computing host needs to switch or migrate the application instance and access path to the target MEC edge computing host. This process involves urgent issues such as how to register and discover MEC edge computing hosts, how to access between MECs, and how to switch service access between terminals and MECs. Summary of the invention

[0005] In order to solve the existing technical problems, the present invention provides a method and device for transmitting MEC information, which are used to realize registration, discovery, mutual access of MEC, and access to services on MEC.

[0006] In a first aspect, the present invention provides a method for transmitting MEC information, which is performed by a unified data management (UDM) network element, and the method includes:

[0007] Receiving authentication information sent by the first MEC;

[0008] Authenticate the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM;

[0009] After the first MEC is successfully authenticated, the MEC configuration information of the second MEC is sent to the first MEC;

[0010] The MEC configuration information of the second MEC is used for communication between the first MEC and the second MEC.

[0011] In the above solution, the method may further include:

[0012] receiving request information from a user equipment (UE), wherein the request information is used to request the UDM to obtain service configuration information of a first service stored in the UDM;

[0013] Sending service configuration information of the first service to the UE;

[0014] The service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a third MEC corresponding to the first service; wherein the third MEC includes the first MEC and / or the second MEC.

[0015] In the above solution, the method may further include:

[0016] Before receiving the authentication information sent by the first MEC, receiving MEC configuration information of the first MEC sent by the AF entity; and / or

[0017] Before receiving the request information from the UE, service configuration information of the second service sent by the AF entity is received.

[0018] In the above solution, the authentication of the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM includes:

[0019] Determine that the second authentication information included in at least one of the MEC configuration information in the UDM matches the first authentication information sent by the first MEC, and determine that the first MEC authentication is successful.

[0020] In the above solution, the receiving the authentication information sent by the first MEC includes:

[0021] Receiving authentication information of the first MEC sent by the first MEC through at least one of the following: an element management system (EMS), a network exposure function (NEF);

[0022] In the above solution, the sending the MEC configuration information of the second MEC to the first MEC includes:

[0023] The MEC configuration information of the second MEC is sent to the first MEC through at least one of the following: EMS, NEF.

[0024] In a second aspect, the present invention provides a method for transmitting MEC information, which is performed by a first MEC, and the method includes:

[0025] Sending authentication information of the first MEC to the UDM network element; wherein the authentication information of the first MEC is used for the UDM to authenticate the first MEC in combination with the MEC configuration information stored in the UDM;

[0026] Receiving MEC configuration information of a second MEC sent by the UDM;

[0027] The MEC configuration information of the second MEC is sent to the first MEC after the UDM successfully authenticates the first MEC;

[0028] The MEC configuration information of the second MEC is used for communication between the first MEC and the second MEC.

[0029] In the above solution, before sending the authentication information of the first MEC to the UDM network element, the method may further include:

[0030] The MEC configuration information of the first MEC is sent to the UDM network element through the AF entity.

[0031] In a third aspect, the present invention provides a method for transmitting MEC information, which is performed by a UE, and the method includes:

[0032] Sending a request message to a UDM network element, wherein the request message is used to request the UDM to obtain service configuration information of the first service stored in the UDM;

[0033] Receiving service configuration information of the first service sent by the UDM;

[0034] The service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a first MEC corresponding to the first service.

[0035] In the above solution, before sending the request information to the UDM network element, the method may further include:

[0036] The service configuration information of the second service corresponding to the UE is sent to the UDM network element through the AF entity.

[0037] In a fourth aspect, the present invention provides a device for implementing MEC information transmission, the device is applied to a UDM server, and the device includes: a first receiving module, an authentication module, and a first sending module; wherein,

[0038] The first receiving module is used to receive authentication information sent by the first MEC;

[0039] The authentication module is used to authenticate the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM;

[0040] The first sending module is used to send MEC configuration information of the second MEC to the first MEC after the first MEC is successfully authenticated; wherein the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

[0041] In the above solution, the first receiving module is further used to receive request information from the UE, wherein the request information is used to request the UDM to obtain service configuration information of the first service stored in the UDM.

[0042] In the above scheme, the first sending module is also used to send service configuration information of the first service to the UE; wherein the service configuration information of the first service includes at least MEC identification information, and the MEC identification information is used to indicate the third MEC corresponding to the first service; wherein the third MEC includes the first MEC and / or the second MEC.

[0043] In the above solution, the authentication module is further used to determine whether the second authentication information contained in at least one of the MEC configuration information in the UDM matches the first authentication information sent by the first MEC, and determine that the authentication of the first MEC is successful.

[0044] In a fifth aspect, the present invention provides a device for implementing MEC information transmission, the device is applied to a MEC server, and the device includes: a second sending module and a second receiving module; wherein,

[0045] The second sending module is used to send authentication information of the first MEC to the UDM network element; wherein the authentication information of the first MEC is used for the UDM to authenticate the first MEC in combination with the MEC configuration information stored in the UDM;

[0046] The second receiving module is used to receive MEC configuration information of the second MEC sent by the UDM; wherein the MEC configuration information of the second MEC is sent to the first MEC after the UDM successfully authenticates the first MEC; the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

[0047] In the above solution, the second sending module is also used to send the MEC configuration information of the first MEC to the UDM.

[0048] In a sixth aspect, the present invention provides a device for implementing MEC information transmission, the device is applied to a UE terminal, and the device includes: a third sending module and a third receiving module; wherein,

[0049] The third sending module is used to send request information to the UDM network element; wherein the request information is used to request the UDM to obtain the service configuration information of the first service stored in the UDM;

[0050] The third receiving module is used to receive the service configuration information of the first service sent by the UDM; wherein the service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate the first MEC corresponding to the first service.

[0051] In the above solution, the third sending module is also used to send the service configuration information of the second service corresponding to the UE to the UDM network element.

[0052] In a seventh aspect, the present invention provides a computer storage medium storing an executable program, which, when executed by a processor, implements the method described in any of the preceding aspects.

[0053] The present invention provides a method and device for transmitting MEC information. Figure 2 As shown, by storing MEC configuration information and service configuration information in UDM, MEC registration and service registration are completed; authentication and request are initiated to UDM to obtain MEC configuration information and service configuration information; according to MEC configuration information and service configuration information, communication between MECs and communication between UE and services on MEC are realized. The present invention reduces the MEC platform management (MEC Platform Manager, MEPM) module in the fusion architecture of the 5G core network (Fifth Generation Corenetwork, 5GC) and MEC defined by the existing standards, reduces the complexity of the architecture, ensures that MEC can quickly register, discover, and complete access between MECs, and at the same time provides convenience for user terminals to access services carried on MEC. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 This is the structural diagram of the 5G and MEC combination solution currently defined by 3GPP.

[0055] Figure 2 This is the overall flow chart of the MEC information transmission method of the present invention.

[0056] Figure 3 This is a standard architecture diagram of MEC in the prior art.

[0057] Figure 4 A schematic diagram of an optional flow chart of a method for transmitting MEC information provided by an embodiment of the present invention, which is executed by UDM;

[0058] Figure 5 A schematic diagram of an optional flow chart of another method for transmitting MEC information provided by an embodiment of the present invention, which is executed by UDM;

[0059] Figure 6 A schematic diagram of an optional flow chart of another method for transmitting MEC information provided in an embodiment of the present invention, which is executed by a first MEC;

[0060] Figure 7 A schematic diagram of an optional flow chart of another method for transmitting MEC information provided in an embodiment of the present invention, which is executed by a UE;

[0061] Figure 8 A schematic diagram of the composition structure of a MEC information transmission device provided in an embodiment of the present invention, which is applied to a UDM server;

[0062] Fig. 9 A schematic diagram of the composition structure of another MEC information transmission device provided in an embodiment of the present invention, which is applied to a MEC server;

[0063] Fig.10 A schematic diagram of the composition structure of another MEC information transmission device provided in an embodiment of the present invention is applied to a UE terminal. DETAILED DESCRIPTION

[0064] Regarding how to register and discover MEC edge hosts and how to access each other, the current mature technical solution is to use MEPM to manage MEC, such as Figure 3 As shown in the figure. The functions of MEPM include: (1) managing the life cycle of MEC applications and reporting related events of MEC applications to the mobile edge orchestrator; (2) providing network element management functions for the MEC platform (MEP); (3) managing the rules and requirements of MEC applications, including service authorization, flow rule configuration, Domain Name System (DNS) configuration, etc.; (4) managing the fault reports and performance test data of the Virtual Infrastructure Manager (VIM). MEPM implements the registration, publishing, discovery and information push functions of MEC through the management function interface Mm5, realizing comprehensive management of MEC. As the number of MECs continues to increase, MEPM will become a bottleneck, hindering the development of business and making maintenance difficult.

[0065] Regarding the problem of how to quickly switch business access, the current mature technical solution is the Content Delivery Network (CDN), which is a virtual network built on the existing network. It relies on edge servers deployed in various places, and through the load balancing, content distribution, scheduling and other functional modules of the central platform, users can obtain the required content nearby, reduce network congestion, and improve user access response speed and hit rate. CDN is applicable in public clouds, with a unified access address, and obtains the required content by location nearby. However, in MEC, different MECs may not form network connectivity, data between different MECs cannot be interoperable, and applications in different edge clouds may have customized development. Therefore, in MEC, CDN is not the best technical solution to solve the access problem between terminals and MEC applications, and new technical solutions need to be explored.

[0066] With the increasing number of businesses, in order to improve the fluency of business access and enhance user experience, the number of MECs is bound to become more and more. So how can MECs quickly register, discover and access each other? How can businesses quickly access businesses on MECs, quickly switch to the nearest MEC, and ensure fluency? The above problems can be solved by existing technical solutions. In the existing technical solutions, MEPM can be used to manage MECs. Each MEC is registered with MEPM, and MECs can quickly register, discover and access each other through MEPM. In the existing technical solutions, CDN technology can be used to complete the rapid switching of nearby business access, but there is still a central point. Once the central point is overloaded and the network is congested, CDN will be paralyzed and lose its essential functions. Its specific shortcomings and deficiencies are as follows:

[0067] (1) MEPM will become a bottleneck and the system architecture will be complex. As business needs develop, the number of MECs will gradually increase. The pressure on MEPM to manage MECs will increase, and its architecture will become more and more complex. At the same time, once MEPM fails or becomes abnormal, it will inevitably affect the access efficiency of MEC services, and the user experience will deteriorate. The system architecture will also be unfavorable for evolution and rapid iteration.

[0068] (2) CDN maintenance costs are high, and it has limitations for MEC with network restrictions. Currently, large websites with high traffic in China all use CDN network acceleration technology, the purpose of which is to allow users to obtain the required content nearby, solve the problem of network congestion, and increase access speed. However, the existing CDN technology is not applicable to small MECs and is costly, especially for MECs in some specific scenarios. CDN cannot be universal and has limitations, such as vertical industries such as medical care and education.

[0069] (3) The combined technical solution of MEPM+CDN cannot bring out the greatest advantages of each, and the configuration is cumbersome, which is not conducive to long-term evolution. MEPM mainly manages MEC, while CDN is mainly to improve the service access rate on MEC. When adding a new MEC, in addition to infrastructure construction and network configuration, it is also necessary to configure MEPM and CDN. The operation is cumbersome, the two are separated, and there is no linkage, which is not conducive to long-term evolution and iteration.

[0070] Therefore, in response to the above-mentioned problems, the present invention provides a method and device for transmitting MEC information, which are used to realize registration, discovery, mutual access of MEC, and switching access to services on MEC.

[0071] The present invention clarifies the configuration method, service configuration and access method of MEC in 5GC. In the process of 5GC and MEC integration, the MEPM module in the traditional system architecture is reduced, the complexity of the system architecture is reduced, and the problem of fast registration and discovery of MEC is solved. At the same time, from the perspective of actual business and top-level planning, mutual discovery and access between MECs are conveniently realized, and it also facilitates the terminal to switch access to the services carried on MEC.

[0072] The present invention will be further described in detail below in conjunction with the embodiments. In order to make the purpose, technical solutions and advantages of the embodiments disclosed in the present invention clearer, the technical solutions in the embodiments disclosed in the present invention will be clearly and completely described in conjunction with the drawings in the embodiments disclosed in the present invention. Obviously, the described embodiments are part of the embodiments disclosed in the present invention, rather than all the embodiments. Based on the embodiments disclosed in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection disclosed in the present invention.

[0073] See attached Figure 4 , which shows a flow chart of a method for transmitting MEC information provided by an embodiment of the present invention, which is executed by UDM. Figure 4 As shown, the method includes:

[0074] Step 101: receiving authentication information sent by the first MEC;

[0075] Specifically, the first MEC may refer to any MEC. When the first MEC needs to discover or access other MECs managed by the UDM, it needs to pass the authentication of the UDM to confirm that the first MEC has access rights. The first MEC may send authentication information to the UDM for authentication.

[0076] In some embodiments, the UDM receives authentication information of the first MEC sent by the first MEC through the NEF.

[0077] In some embodiments, the UDM receives the authentication information of the first MEC sent by the first MEC through the EMS. The EMS is a network element management system, and the EMS manages network elements such as the UDM.

[0078] Step 102: authenticating the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM;

[0079] Specifically, the UDM stores the MEC configuration information of a certain number of MECs, and the MEC configuration information of each MEC at least includes identification information, authentication information and address information. When the UDM receives the authentication information of the first MEC, it will compare and authenticate the authentication information sent by the first MEC with the authentication information in the stored MEC configuration information.

[0080] In some embodiments, the method further includes, before step 101, receiving MEC configuration information of the first MEC sent by the AF entity.

[0081] Specifically, after the first MEC completes the construction of infrastructure (hardware and network), it can send its own MEC configuration information to the UDM through core network network elements such as AF and other entities. The UDM receives the MEC configuration information to realize the registration of the first MEC.

[0082] During the process of the first MEC sending MEC configuration information to UDM through AF, if UDM fails to successfully receive the MEC configuration information of the first MEC, UDM feeds back a registration failure prompt to the first MEC and / or AF; if UDM successfully receives the MEC configuration information of the first MEC, UDM feeds back a registration completion prompt to the first MEC and / or AF.

[0083] In some embodiments, the MEC configuration information stored on the UDM may include at least one of the following: identification information, authentication information, address information, capability information, and reservation information.

[0084] Specifically, the identification information may include at least one of the following: MEC number, MEC location, MEC owner, etc. MEC number is used to number each MEC, and is numbered in the regional manner of country-province-city-county-township (town)-serial number. This information is unique, for example: MEC86211101, 86-China, 21-Beijing, 11-Chaoyang District, 01-serial number. MEC location is used to record the location of MEC deployment in detail, providing a basis for the selection of the nearest service access, and may include longitude and latitude, for example: 116.2° and 40.6° east longitude. MEC owner is used to mark which operator the MEC belongs to, for example: 1-Operator A, 2-Operator B, 3-Operator C.

[0085] The authentication information includes at least one of the following: MEC access ID and MEC access key. MEC access ID is used to identify and authenticate the MEC access ID. The MEC access ID is a randomly generated unique string of characters, including at least one of the following: letters and numbers. MEC access key is used as the basis for MEC access authentication.

[0086] The address information includes the MEC address, which is used to record the address for accessing the corresponding MEC.

[0087] Capability information may include at least one of the following: priority, MEC status. Priority is used to determine the priority of MEC access under the same circumstances, for example, divided into 5 levels, 1-highest priority, 5-lowest priority. MEC status is used to enable MEC, that is, whether MEC is allowed to be accessed, for example: 0-not allowed, 1-allowed.

[0088] The reserved information includes other reserved fields and can be used for emergency information configuration.

[0089] In some embodiments, the UDM performs authentication of the first MEC, which may be to determine whether the second authentication information included in at least one MEC configuration information in the UDM matches the first authentication information of the first MEC. The first authentication information may include at least one of the following: access ID information; access key information. The second authentication information may also include at least one of the following: access ID information; access key information. The UDM determines whether the first authentication information and the second authentication information match, which may be to determine whether the first authentication information and the second authentication information are completely consistent, or to confirm whether the first authentication information and the second authentication information comply with preset rules. If the UDM determines that the first authentication information and the second authentication information match, it determines that the first MEC authentication is successful; if the UDM determines that the first authentication information and the second authentication information do not match, it determines that the first MEC authentication has failed.

[0090] In some embodiments, UDM performs authentication of the first MEC. If the authentication of the first MEC fails, UDM returns a prompt "Authentication failed" to the first MEC, and UDM terminates subsequent processes; if the authentication of the first MEC succeeds, UDM returns a prompt "Authentication successful" to the first MEC, and UDM enters the next process step.

[0091] Step 103: After the first MEC is successfully authenticated, MEC configuration information of the second MEC is sent to the first MEC; wherein the MEC configuration information of the second MEC is used for communication between the first MEC and the second MEC.

[0092] Specifically, after UDM confirms that the first MEC has passed the authentication, it sends the MEC configuration information of the second MEC to the first MEC; wherein the second MEC is any MEC except the first MEC among all MECs whose MEC configuration information is recorded in UDM. Since the MEC configuration information of the second MEC at least includes the address information of the second MEC, after the first MEC obtains the MEC configuration information of the second MEC, it can read the address information of the second MEC from it, and then access the second MEC according to the address information of the second MEC. Thus, the communication between the first MEC and the second MEC is established, and mutual discovery and access between different MECs are realized.

[0093] In some embodiments, the UDM sends the MEC configuration information of the second MEC to the first MEC through the NEF.

[0094] In some embodiments, the UDM sends the MEC configuration information of the second MEC to the first MEC via the EMS. The EMS is a network element management system, and the EMS manages network elements such as the UDM.

[0095] A flowchart of another method for transmitting MEC information provided by an embodiment of the present invention is performed by UDM. Figure 5 As shown, the method includes:

[0096] Step 201: Receive request information from a UE, wherein the request information is used to request the UDM to obtain service configuration information of a first service stored in the UDM;

[0097] Specifically, UDM stores service configuration information for a certain number of services, and the service configuration information for each service includes at least service attribute information and MEC identification information. The first service may refer to any service for which service configuration information is stored in UDM. The MEC identification information included in the service configuration information of the first service corresponds to the MEC where the first service is located. The MEC identification information of the first service can uniquely identify an MEC, representing the MEC to which the first service belongs.

[0098] For example, the MEC identification information of the first service may be in the form of the above Figure 4 In the embodiment, the form of the identification information in the MEC configuration information may include at least one of the following: MEC number, MEC location, MEC owner, etc. For the specific explanation and form of MEC number, MEC location, and MEC owner, refer to Figure 4 The relevant contents in the embodiments will not be repeated here.

[0099] The request information of the UE may be service configuration information requesting access to a certain service, service configuration information requesting access to all services, or service configuration information requesting access to a specified part of services.

[0100] In some embodiments, the UDM receives request information from the user equipment UE through a core network element access and mobility management function (Access and Mobility Management Function, AMF).

[0101] In some embodiments, the UE sends information to a core network element through an access network device.

[0102] Step 202: Send service configuration information of the first service to the UE; wherein the service configuration information of the first service includes at least MEC identification information, and the MEC identification information is used to indicate a third MEC corresponding to the first service; wherein the third MEC includes the first MEC and / or the second MEC.

[0103] Specifically, in response to the request information of the UE, the UDM sends the service configuration information of the first service to the UE. Since the service configuration information at least includes the MEC identification information, after the UE obtains the service configuration information of the first service, it can read the MEC identification information of the first service therefrom, and then know that the first service is running on the corresponding third MEC, and switch to access the first service on the third MEC. Here, the third MEC can be the above-mentioned Figure 4 The first MEC and / or the second MEC in the embodiment.

[0104] In some embodiments, before step 201, the method further includes receiving service configuration information of the second service sent by the AF entity.

[0105] Specifically, the UE sends the service configuration information of the second service known to the UE to the UDM through the core network element such as the AF entity, and the UDM receives the service configuration information to realize the registration of the second service. The second service can be a new service that is not registered in the UDM, or it can be a first service that needs to update information after a change. If the UDM fails to successfully receive the second service configuration information, it will feedback a registration failure prompt to the UE and / or AF. If the UDM successfully receives the second service configuration information, it will feedback a registration completion prompt to the UE and / or AF.

[0106] In some embodiments, the service configuration information of the first service stored in the UDM should at least include service attribute information and MEC identification information.

[0107] Specifically, the service attribute information is used to record the attribute information necessary for the service, and may include at least one of the following: data network name (Data Network Name, DNN), network slice selection auxiliary information (Single Network Slice Selection Assistance Information, S-NSSAI), UE identification, location area, authorized application information list (APPID, APPINFO, IP, domain name, etc.).

[0108] MEC identification information is used to identify which MEC the service belongs to, so that the UE can selectively access the service when accessing the service. Any information form that can uniquely identify an MEC can be used as the MEC identification information in the service configuration information. For example, the above Figure 4 In the embodiment, the MEC number in the MEC configuration information is used as the MEC identification information in the service configuration information.

[0109] In some embodiments, UDM sends service configuration information of the first service to the UE through the core network element AMF.

[0110] See attached Figure 6 , which shows a flow chart of a method for transmitting MEC information provided by an embodiment of the present invention, which is executed by the first MEC. Figure 6 In the method, the method comprises:

[0111] Step 301: Sending authentication information of the first MEC to a unified data management (UDM) network element; wherein the authentication information of the first MEC is used by the UDM to authenticate the first MEC in combination with MEC configuration information stored in the UDM;

[0112] Specifically, when the first MEC needs to discover or access other MECs managed by UDM, the first MEC should first be authenticated by UDM to confirm that the first MEC has access rights. The basis for UDM to authenticate the first MEC is the authentication information sent by the first MEC and the MEC configuration information stored by UDM. UDM stores the MEC configuration information of a certain number of MECs, and the MEC configuration information of each MEC contains at least identification information, authentication information, and address information.

[0113] The authentication information may include at least one of the following: MEC access ID and MEC access key. MEC access ID is used to identify and authenticate the MEC access ID. The MEC access ID is a randomly generated unique string of characters, including at least one of the following: letters and numbers. MEC access key is used as the basis for MEC access authentication.

[0114] In some embodiments, the UDM performs authentication of the first MEC, which may be to determine whether the second authentication information included in at least one MEC configuration information in the UDM matches the first authentication information of the first MEC. The first authentication information may include at least one of the following: access ID information; access key information. The second authentication information may also include at least one of the following: access ID information; access key information. The UDM determines whether the first authentication information and the second authentication information match, which may be to determine whether the first authentication information and the second authentication information are completely consistent, or to confirm whether the first authentication information and the second authentication information comply with preset rules. If the UDM determines that the first authentication information and the second authentication information match, it determines that the first MEC authentication is successful; if the UDM determines that the first authentication information and the second authentication information do not match, it determines that the first MEC authentication has failed.

[0115] In some embodiments, the MEC configuration information stored on the UDM may include at least one of the following: identification information, authentication information, address information, capability information, and reservation information. Figure 4 The relevant contents in the embodiments will not be repeated here.

[0116] In some embodiments, the first MEC sends authentication information of the first MEC to the UDM via the NEF.

[0117] In some embodiments, the first MEC sends authentication information of the first MEC to the UDM via the EMS.

[0118] In some embodiments, when the first MEC initiates authentication, if the network connection fails, the network returns "Access network abnormality, please retry" to the first MEC, and the UDM terminates the authentication process; if the network connection is successful, the UDM returns "Authentication in progress" to the first MEC and starts the authentication process.

[0119] In some embodiments, before step 301, the method further includes:

[0120] The MEC configuration information of the first MEC is sent to the UDM network element through the AF entity.

[0121] Specifically, after the infrastructure (hardware and network) is built, the first MEC sends its own MEC configuration information to the UDM through the AF entity, and the UDM receives the MEC configuration information to realize the registration of the first MEC. The MEC configuration information of the first MEC can be carried through the ordinary IP data stream N33 interface or through the traditional authentication request process.

[0122] The first MEC sends the MEC configuration information of the first MEC to the UDM network element through the application function AF entity, and the MEC configuration information of the first MEC may be transmitted through the AF Request standard interface defined by 3GPP.

[0123] For example, based on the AF Request standard interface, the MEC configuration information of the first MEC is transmitted. The interface configuration method is as follows:

[0124] The parameter list of MEC Config Information is as follows:

[0125] mec_location, required, data type is String, represents the location information of mec, including longitude and latitude.

[0126] mec_belonging, required field, data type is int, indicating the mec belonging party.

[0127] mec_priority, required, data type is int, represents mec priority, the priority of being accessed.

[0128] mec_status, required, data type is Boolean, indicating the status of mec, enabled or disabled.

[0129] mec_access_id, required, data type is String, represents the ID of mec access, the basis for access authentication.

[0130] mec_access_secret, required, data type is String, represents the key for mec access, the basis for access authentication.

[0131] mec_address, optional, data type is String, indicating the address for accessing mec.

[0132] others, optional item, data type is String, indicating other non-mandatory information.

[0133] Step 302: Receive MEC configuration information of the second MEC sent by the UDM; wherein the MEC configuration information of the second MEC is sent to the first MEC after the UDM successfully authenticates the first MEC; the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

[0134] Specifically, UDM stores MEC configuration information of a certain number of MECs, and the MEC configuration information of each MEC includes at least identification information, authentication information and address information; after UDM confirms that the first MEC has passed the authentication, it will send the MEC configuration information of the second MEC to the first MEC; the first MEC receives the MEC configuration information of the second MEC sent by UDM. Since the MEC configuration information of the second MEC includes at least address information, after the first MEC obtains the MEC configuration information of the second MEC, it can read the address information of the second MEC therefrom, and then access the second MEC based on the address information of the second MEC. In this way, communication between the first MEC and the second MEC is established, and mutual discovery and access between different MECs are realized.

[0135] In some embodiments, the first MEC receives MEC configuration information of the second MEC sent by the UDM through the NEF.

[0136] In some embodiments, the first MEC receives MEC configuration information of the second MEC sent by the UDM through the EMS.

[0137] In some embodiments, when the first MEC receives the MEC configuration information of the second MEC, if the first MEC fails to obtain the MEC configuration information of the second MEC, it feeds back "failed to obtain MEC information" information to the UDM; if the first MEC successfully obtains the MEC configuration information of the second MEC, it feeds back "successful to obtain MEC information" information to the UDM.

[0138] Specifically, the first MEC receives the MEC configuration information of the second MEC sent by the UDM, and the MEC configuration information may be transmitted through the AF Request standard interface defined by 3GPP.

[0139] For example, based on the AF Request standard interface, the MEC configuration information of the second MEC is transmitted. The interface configuration method is as follows:

[0140] The returned parameter list of the obtained MEC configuration information is as follows:

[0141] mec_location, data type is String, which indicates the location information of mec, including longitude and latitude.

[0142] mec_belonging, data type is int, indicating the mec belonging party.

[0143] mec_priority, data type is int, indicating mec priority, the priority of being accessed.

[0144] mec_status, data type is Boolean, indicating the status of mec, enabled or disabled.

[0145] mec_access_id, data type is String, which indicates the ID of mec access and the basis for access authentication.

[0146] mec_access_secret, data type is String, which indicates the key for mec access and the basis for access authentication.

[0147] mec_address, data type is String, indicating the address for accessing mec.

[0148] others, data type is String, indicating other non-mandatory information.

[0149] See attached Figure 7 , which shows a flow chart of a method for transmitting MEC information provided by an embodiment of the present invention, which is executed by UE. Figure 7 In the method, the method comprises:

[0150] Step 401: Sending a request message to a UDM network element, wherein the request message is used to request the UDM to obtain service configuration information of a first service stored in the UDM;

[0151] Specifically, UDM stores service configuration information for a certain number of services, and the service configuration information for each service includes at least service attribute information and MEC identification information. The first service may refer to any service for which service configuration information is stored in UDM. The MEC identification information included in the service configuration information of the first service corresponds to the MEC where the first service is located. The MEC identification information of the first service can uniquely identify an MEC, representing the MEC to which the first service belongs.

[0152] When the UE needs to access services on other MECs, it should first send a request message to the UDM. The request message can be service configuration information requesting access to a certain service, service configuration information requesting access to all services, or service configuration information requesting access to a specified portion of services.

[0153] In some embodiments, the UE sends a request message to the UDM through a core network element such as an AMF.

[0154] In some embodiments, the UE sends information to a core network element through an access network device.

[0155] In some embodiments, before step 401, the method further includes sending service configuration information of the second service corresponding to the UE to the UDM network element.

[0156] Specifically, the UE sends the service configuration information of the second service known to it to the UDM through the core network element such as the AF entity, and the UDM receives the service configuration information to register the second service. The second service can be a new service that is not registered in the UDM, or a first service that needs to update information after a change.

[0157] The UE sends the service configuration information of the second service corresponding to the UE to the UDM network element through the AF entity, and the service configuration information may be transmitted through the AF Request standard interface defined by 3GPP.

[0158] In some embodiments, when the UE sends a request message to the UDM network element, it should have the authority to access the first service. If the UDM detects that the UE does not have the authority to access the first service, it returns a prompt "request failed" and terminates the process; if the UDM detects that the UE has the authority to access the first service, it returns a prompt "request successful" and proceeds to the next step.

[0159] Step 402: Receive the service configuration information of the first service sent by the UDM; wherein the service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a first MEC corresponding to the first service.

[0160] Specifically, after the request is successful, the UE receives the service configuration information of the first service sent by the UDM. Since the service configuration information at least includes the MEC identification information, after the UE obtains the service configuration information of the first service, it can read the MEC identification information of the first service therefrom, and then, based on the unique correspondence between the MEC identification information and the third MEC, it is known that the first service is running on the corresponding third MEC. On this basis, a communication connection can be established between the UE and the third MEC where the first service is located. Thus, the UE's access to the first service on the third MEC is realized.

[0161] In some embodiments, the service configuration information of the first service stored in the UDM should at least include service attribute information and MEC identification information. Figure 5 The relevant contents in the embodiments will not be repeated here.

[0162] In some embodiments, the UE receives service configuration information of the first service sent by the UDM through the AMF.

[0163] In some embodiments, when the UE receives service configuration information, if the acquisition fails, the UE feeds back "failed to obtain service information" information to the UDM; if the acquisition succeeds, the UE feeds back "successful to obtain service information" information to the UDM.

[0164] In some embodiments, the UE receives the service configuration information of the first service sent by the UDM, and the service configuration information of the first service may be transmitted through the AF Request standard interface defined by 3GPP.

[0165] On the premise of no contradiction, Figures 4 to 7 The embodiments shown can be implemented individually or in combination. Figure 4 and Figure 5 The embodiments shown can be implemented in combination. Figure 5 and Figure 7 The illustrated embodiments can be implemented in combination, but not exclusively.

[0166] See attached Figure 8 , which shows a schematic diagram of a device for MEC information transmission provided by an embodiment of the present invention, which is applied to a UDM server. Figure 8 In the embodiment, the device 100 comprises:

[0167] The first receiving module 110 is used to receive authentication information sent by the first MEC;

[0168] An authentication module 120, configured to authenticate the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM;

[0169] The first sending module 130 is used to send MEC configuration information of the second MEC to the first MEC; wherein the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

[0170] In some embodiments, the first receiving module is further used to receive request information from the UE, wherein the request information is used to request the UDM to obtain service configuration information of the first service stored in the UDM.

[0171] In some embodiments, the first sending module is also used to send service configuration information of the first service to the UE; wherein the service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a third MEC corresponding to the first service; wherein the third MEC includes the first MEC and / or the second MEC.

[0172] In some embodiments, the authentication module is further used to determine whether second authentication information included in at least one MEC configuration information in the UDM matches first authentication information of the first MEC, and determine that the first MEC authentication is successful.

[0173] See attached Fig. 9 , which shows a schematic diagram of a device for MEC information transmission provided by an embodiment of the present invention, which is applied to a MEC server. Fig. 9 In the embodiment, the device 200 comprises:

[0174] The second sending module 210 is used to send the authentication information of the first MEC to the unified data management UDM network element; wherein the authentication information of the first MEC is used for the UDM to authenticate the first MEC in combination with the MEC configuration information stored in the UDM;

[0175] The second receiving module 220 is used to receive the MEC configuration information of the second MEC sent by the UDM; wherein the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

[0176] In some embodiments, the second sending module is further used to send the MEC configuration information of the first MEC to the UDM network element through the AF entity.

[0177] See attached Fig.10 , which shows a schematic diagram of a device for MEC information transmission provided by an embodiment of the present invention, which is applied to a UE terminal. Fig.10 In the embodiment, the device 300 comprises:

[0178] The third sending module 310 is used to send a request message to a unified data management (UDM) network element; wherein the request message is used to request the UDM to obtain the service configuration information of the first service stored in the UDM;

[0179] The third receiving module 320 is used to receive the service configuration information of the first service sent by the UDM; wherein the service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate the first MEC corresponding to the first service.

[0180] In some embodiments, the third sending module is further used to send service configuration information of the second service corresponding to the UE to the UDM through the AF entity.

[0181] An embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any step in the above data processing method is implemented.

[0182] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A multi-access edge computing MEC information transmission method, executed by a unified data management UDM network element, characterized in that: The method comprises: Receiving authentication information sent by the first MEC; Authenticate the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM; After the first MEC is successfully authenticated, the MEC configuration information of the second MEC is sent to the first MEC; The MEC configuration information of the second MEC is used for communication between the first MEC and the second MEC.

2. The method according to claim 1, characterized in that The method further comprises: receiving request information from a user equipment UE, wherein the request information is used to request the UDM to obtain service configuration information of a first service stored in the UDM; Sending service configuration information of the first service to the UE; The service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a third MEC corresponding to the first service; wherein the third MEC includes the first MEC and / or the second MEC.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Before receiving the authentication information sent by the first MEC, receiving MEC configuration information of the first MEC sent by an application function AF entity; and / or Before receiving the request information from the user equipment UE, service configuration information of the second service sent by the AF entity is received.

4. The method according to claim 1, characterized in that The performing authentication of the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM includes: Determine that the second authentication information included in at least one of the MEC configuration information in the UDM matches the first authentication information sent by the first MEC, and determine that the first MEC authentication is successful.

5. According to the method of claim 1, the receiving authentication information sent by the first MEC comprises: Receiving authentication information of the first MEC sent by the first MEC through at least one of the following: an element management system EMS, a network open function NEF; The sending the MEC configuration information of the second MEC to the first MEC includes: The MEC configuration information of the second MEC is sent to the first MEC through at least one of the following: EMS, NEF.

6. A multi-access edge computing MEC information transmission method, performed by a first MEC, characterized in that: The method comprises: Sending the authentication information of the first MEC to the unified data management (UDM) network element; The authentication information of the first MEC is used by the UDM to authenticate the first MEC in combination with the MEC configuration information stored in the UDM; Receiving MEC configuration information of a second MEC sent by the UDM; The MEC configuration information of the second MEC is sent to the first MEC after the UDM successfully authenticates the first MEC; The MEC configuration information of the second MEC is used for communication between the first MEC and the second MEC.

7. The method according to claim 6, characterized in that Before sending the authentication information of the first MEC to the UDM network element, the method further includes: The MEC configuration information of the first MEC is sent to the UDM through the application function AF entity.

8. A multi-access edge computing MEC information transmission method, executed by a user equipment UE, characterized in that: The method comprises: Sending a request message to a unified data management (UDM) network element; wherein the request message is used to request the UDM to obtain service configuration information of the first service stored in the UDM; Receiving service configuration information of the first service sent by the UDM; The service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate a first MEC corresponding to the first service.

9. The method according to claim 8, characterized in that Before sending the request information to the UDM network element, the method further includes: The service configuration information of the second service corresponding to the UE is sent to the UDM through the application function AF entity.

10. A device for implementing multi-access edge computing MEC information transmission, characterized in that: The device is applied to a unified data management (UDM) server, and comprises: a first receiving module, an authentication module, and a first sending module; wherein: The first receiving module is used to receive authentication information sent by the first MEC; The authentication module is used to authenticate the first MEC according to the authentication information of the first MEC and the MEC configuration information stored in the UDM; The first sending module is used to send MEC configuration information of the second MEC to the first MEC after the first MEC is successfully authenticated; wherein the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

11. A device for implementing multi-access edge computing MEC information transmission, characterized in that: The device is applied to a MEC server, and comprises: a second sending module and a second receiving module; wherein, The second sending module is used to send the authentication information of the first MEC to the unified data management UDM network element; wherein the authentication information of the first MEC is used for the UDM to authenticate the first MEC in combination with the MEC configuration information stored in the UDM; The second receiving module is used to receive MEC configuration information of the second MEC sent by the UDM; wherein the MEC configuration information of the second MEC is sent to the first MEC after the UDM successfully authenticates the first MEC; the MEC configuration information of the second MEC is used for the first MEC to communicate with the second MEC.

12. A device for implementing multi-access edge computing MEC information transmission, characterized in that: The device is applied to a UE terminal, and comprises: a third sending module and a third receiving module; wherein: The third sending module is used to send request information to the unified data management UDM network element; wherein the request information is used to request the UDM to obtain service configuration information of the first service in the UDM; The third receiving module is used to receive the service configuration information of the first service sent by the UDM; wherein the service configuration information of the first service at least includes MEC identification information, and the MEC identification information is used to indicate the first MEC corresponding to the first service.

13. A device for implementing multi-access edge computing MEC information transmission, characterized in that: The device comprises: a processor and a memory for storing a computer program that can be run on the processor, When the processor is used to run the computer program, it executes the steps of the method described in any one of claims 1 to 5, or executes the steps of the method described in any one of claims 6 to 7, or executes the steps of the method described in any one of claims 8 to 9.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the computer program implements the steps of the method described in any one of claims 1 to 5, or the steps of the method described in any one of claims 6 to 7, or the steps of the method described in any one of claims 8 to 9.

Images