MEC proxy method and device, computer equipment and storage medium
By deploying MEFB network elements in an external cloud environment and connecting them with multiple MEC systems, the problem of redundancy and unused MEFB network elements in the MEC system is solved, and efficient resource utilization and proxy operation of the MEC system are realized.
Patent Information
- Application Number
- CN202411955047.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-27
- Publication Date
- 2025-04-08
AI Technical Summary
In the MEC system, there may be multiple MEFB network elements of the MEF system, resulting in redundancy or not being used, resulting in waste of resources.
By deploying the mobile edge computing federated coordination agent MEFB network elements in an external cloud environment and communicating it with multiple MEC systems, receiving proxy requests sent by the first MEC system and forwarding them to the second MEC system for processing.
The existence of redundant MEFB network elements in the MEC joint is avoided, resource waste is reduced, and proxy operations on the MEC system are realized without setting MEFB network elements.
Smart Images

Figure CN119789130A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of wireless communication technology, and in particular to an MEC proxy method, apparatus, computer device and storage medium. Background Art
[0002] MEC federation refers to a federation model of MEC systems that allows the shared use of MEC services and applications. In the case of MEC federation, different stakeholders cooperate for a common business purpose and "federate" their edge computing resources by providing / exposing their MEC service capabilities, not only for mutual consumption, but also to provide these services to application developers and end customers (e.g. vertical market segments).
[0003] However, in the MEC system, there may be more than one MEF system with MEFB network elements (MEC FederatorBroker, mobile edge computing federation coordination agent), which may cause redundant or unused MEFB network elements, resulting in waste of resources. Summary of the invention
[0004] Based on this, it is necessary to provide a MEC proxy method, device, computer equipment and storage medium that can prevent MEFB network elements from being redundant or unused and reduce resource waste in response to the above technical problems.
[0005] In a first aspect, the present application provides a MEC proxy method, which is applied to a mobile edge computing federation coordination agent MEFB network element, where the MEFB network element is deployed in an external cloud environment, and the MEFB network element is connected to both a first multi-access edge computing MEC system and a second MEC system, and the method includes:
[0006] Receiving a proxy request sent by the first MEC system;
[0007] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0008] In one of the embodiments, no MEFB network element is provided in the first MEC system and the second MEC system.
[0009] In one embodiment, forwarding the proxy request to the second MEC system includes:
[0010] Extracting the first system identifier carried in the proxy request;
[0011] When it is determined, according to the first system identifier, that the first MEC system has proxy authority, the proxy request is forwarded to the second MEC system.
[0012] In one embodiment, determining, according to the first system identifier, that the first MEC system has proxy authority includes:
[0013] Obtaining a proxy authority whitelist for MEFB network elements; wherein the proxy authority whitelist records at least one candidate system identifier;
[0014] If the candidate system identifier that is identical to the first system identifier exists in the proxy authority whitelist, it is determined that the first MEC system has proxy authority.
[0015] In one embodiment, receiving a proxy request sent by the first MEC system includes:
[0016] Receiving proxy requests sent by at least two first MEC systems;
[0017] Accordingly, forwarding the proxy request to the second MEC system includes:
[0018] Determine the system priority corresponding to each of the first MEC systems;
[0019] According to the system priorities corresponding to the first MEC systems, at least two proxy requests are forwarded to the second MEC systems respectively.
[0020] In one embodiment, forwarding at least two of the proxy requests to the second MEC system respectively according to the system priorities corresponding to the first MEC systems includes:
[0021] Determining a sending order of each of the proxy requests according to the system priorities corresponding to each of the first MEC systems;
[0022] According to the sending order, at least two of the proxy requests are forwarded to the second MEC system in sequence.
[0023] In a second aspect, the present application further provides a MEC proxy device, which is configured in a mobile edge computing federation coordination agent MEFB network element, the MEFB network element is deployed in an external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, and the device includes:
[0024] A receiving module, used for receiving a proxy request sent by the first MEC system;
[0025] The forwarding module is used to forward the proxy request to the second MEC system so that the second MEC system processes the proxy request.
[0026] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:
[0027] Receiving a proxy request sent by the first MEC system;
[0028] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0029] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0030] Receiving a proxy request sent by the first MEC system;
[0031] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0032] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0033] Receiving a proxy request sent by the first MEC system;
[0034] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0035] The above-mentioned MEC proxy method, apparatus, computer equipment and storage medium receive the proxy request sent by the first MEC system and forward the proxy request to the second MEC system so that the second MEC system processes the proxy request. According to the above content, since the MEFB network element in the present application does not belong to the external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, after the first MEC system generates a proxy request, it can be transmitted to the MEFB network element in the external cloud environment, and then, the MEFB network element forwards the proxy request sent by the first MEC system to the second MEC system, so as to realize the proxy operation for the MEC system without setting up the MEFB network element in the first MEC system and the second MEC system, thereby avoiding the situation where there is more than one MEC system configured with MEFB network elements in the MEC union, causing redundancy and idleness of the MEFB network elements, and preventing the waste of resources for the MEFB network elements. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 An application environment diagram of an MEC proxy method provided in an embodiment of the present application;
[0037] Figure 2 A flowchart of the first MEC proxy method provided in the embodiment of the present application;
[0038] Figure 3 A schematic diagram of a joint reference architecture of a MEC system in the prior art provided in an embodiment of the present application;
[0039] Figure 4 A schematic diagram of a joint reference architecture of a MEC system in the present application provided for an embodiment of the present application;
[0040] Figure 5 A flowchart of a second MEC proxy method provided in an embodiment of the present application;
[0041] Figure 6 A flowchart of a third MEC proxy method provided in an embodiment of the present application;
[0042] Figure 7 A flowchart of the fourth MEC proxy method provided in the embodiment of the present application;
[0043] Figure 8 A schematic diagram of a variant of a MEC-joint multi-access edge system reference architecture provided in an embodiment of the present application;
[0044] Fig. 9 A structural block diagram of the first MEC proxy device provided in an embodiment of the present application;
[0045] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0046] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0047] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. In the description of the present application, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms is not necessarily for the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples without contradicting each other.
[0048] The MEC proxy method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the MEFB network element 102 communicates with the first MEC system 103 and the second MEC system 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. By receiving the proxy request sent by the first MEC system and forwarding the proxy request to the second MEC system, the second MEC system processes the proxy request.
[0049] In one embodiment, Figure 2 As shown, a MEC proxy method is provided, which is applied to a mobile edge computing federation coordination agent MEFB network element, the MEFB network element is deployed in an external cloud environment, and the MEFB network element is connected to both a first multi-access edge computing MEC system and a second MEC system, including the following steps:
[0050] S201, receiving a proxy request sent by the first MEC system.
[0051] It should be noted that after receiving the proxy request sent by the first MEC system, the proxy authority of the first MEC system is verified, and then, when it is determined that the first MEC system has the proxy authority, the subsequent operation of forwarding the proxy request to the second MEC system is performed.
[0052] In one embodiment of the present application, if a proxy request sent by a first MEC system is received, the proxy authority of the first MEC system is verified. If it is determined that the first MEC system has the proxy authority, the subsequent operation of forwarding the proxy request to the second MEC system is performed; if it is determined that the first MEC system does not have the proxy authority, the proxy request is returned, and the reason for the return of the proxy request is fed back.
[0053] S202: forward the proxy request to the second MEC system, so that the second MEC system processes the proxy request.
[0054] It should be noted that neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0055] In one embodiment of the present application, if a total of four first MEC systems are included, the four first MEC systems are MEC system 1, MEC system 2, MEC system 3 and MEC system 4; and a second MEC system is included, namely MEC system 0; in the prior art, the connection relationship between the first MEC system, the second MEC system and the MEFB network element is as follows Figure 3 As shown, when MEC system 1, MEC system 2, MEC system 3, and MEC system 4 are all combined with MEC system 0, the MEF of at least one of every two MEC systems must include a MEFB network element; since it is not certain whether the MEF of other MEC systems includes MEFB, the MEF of most MEC systems will include MEFB. Assuming that MEC system 0, MEC system 1, and MEC system 4 all include MEFB, at least three MEFBs are included in the reference architecture.
[0056] However, in this application, the connection relationship between the first MEC system, the second MEC system and the MEFB network element is as follows: Figure 4 As shown, a converged MEFB network element is preset in the external cloud environment, and the MEFB network elements in the MEF system of all MEC systems are removed. When MEC system 1, MEC system 2, MEC system 3, and MEC system 4 are all combined with MEC system 0, MEC system 1, MEC system 2, MEC system 3, and MEC system 4 can all initiate proxy requests to the converged MEFB network element, and then the converged MEFB initiates proxy requests to MEC system 0. Therefore, only one MEFB needs to be included in this reference architecture.
[0057] The above-mentioned MEC proxy method receives a proxy request sent by the first MEC system and forwards the proxy request to the second MEC system so that the second MEC system processes the proxy request. According to the above content, since the MEFB network element in this application does not belong to the external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, after the first MEC system generates a proxy request, it can be transmitted to the MEFB network element in the external cloud environment. Then, the MEFB network element forwards the proxy request sent by the first MEC system to the second MEC system, so as to realize the proxy operation for the MEC system without setting up MEFB network elements in the first MEC system and the second MEC system, thereby avoiding the situation in which there is more than one MEC system configured with MEFB network elements in the MEC union, causing redundancy and idleness of MEFB network elements, and preventing waste of resources for MEFB network elements.
[0058] In one embodiment, if Figure 5 As shown, when the proxy request needs to be forwarded to the second MEC system, the following contents may be included:
[0059] S501: extract the first system identifier carried in the proxy request.
[0060] It should be noted that in order to ensure that the first MEC system can be successfully verified later whether it has the proxy authority for the second MEC system, it is necessary to ensure that when the first MEC system sends a proxy request, the proxy request carries the first system identifier corresponding to the first MEC system.
[0061] The first system identifier corresponding to the first MEC system is a unique identity identifier used to characterize the first MEC system.
[0062] S502: When it is determined that the first MEC system has the proxy authority according to the first system identifier, forward the proxy request to the second MEC system.
[0063] It should be noted that when it is necessary to determine whether the first MEC system has proxy authority based on the first system identifier, the following contents may be included: obtaining a whitelist of proxy authority for MEFB network elements; wherein, at least one candidate system identifier is recorded in the proxy authority whitelist; if there is a candidate system identifier that is the same as the first system identifier in the proxy authority whitelist, it is determined that the first MEC system has proxy authority.
[0064] The above-mentioned MEC proxy method obtains the first system identifier carried in the proxy request to determine whether the first MEC system has proxy authority according to the first system identifier, so as to implement authority screening for the proxy request sent by the first MEC system, thereby preventing the first MEC system without proxy authority from accessing the second MEC system, causing a waste of resources.
[0065] In one embodiment, if Figure 6 As shown, since the MEFB network element may be connected to multiple first MEC systems, when it is necessary to receive a proxy request sent by a first MEC system, the following situation may be included: receiving proxy requests sent by at least two first MEC systems.
[0066] Furthermore, if the MEFB network element receives proxy requests sent by multiple first MEC systems at the same time, in order to prevent the proxy requests from being forwarded to the second MEC system at the same time, thereby causing communication congestion and affecting transmission efficiency, the present application may perform the following steps when forwarding the proxy request to the second MEC system:
[0067] S601, determining the system priority corresponding to each first MEC system.
[0068] It should be noted that by determining that system priority coefficients for multiple candidate MEC systems can be pre-set, when it is necessary to determine the system priority corresponding to each first MEC system, the system priority corresponding to the corresponding first MEC system is determined according to the system priority coefficient of each candidate MEC system.
[0069] Specifically, the system priority coefficient of the pre-set candidate MEC system includes at least one candidate MEC system, and records the priority coefficient corresponding to each candidate MEC system; wherein, the larger the priority coefficient, the higher the priority of the candidate MEC system corresponding to the priority coefficient; therefore, when it is necessary to determine the system priority corresponding to each first MEC system, the priority coefficient corresponding to each first MEC system can be determined from at least the system priority coefficient of the candidate MEC system; then, according to the value of the priority coefficient corresponding to each first MEC system, in the order of the priority coefficient from large to small, the first MEC systems are sorted, thereby obtaining the system priority corresponding to each first MEC system.
[0070] Among them, the system priority coefficient of the candidate MEC system can be set or adjusted according to the actual situation or the historical experience of the operation and maintenance personnel. The priority coefficient of each candidate MEC system in the system priority coefficient of the candidate MEC system is not limited. Furthermore, the priority coefficient of each MEC system can be analyzed according to the rules determined according to the pre-set priority coefficients, so as to obtain the system priority coefficient of each candidate MEC system.
[0071] S602: forward at least two proxy requests to the second MEC system respectively according to the system priorities corresponding to the first MEC systems.
[0072] It should be noted that when it is necessary to forward at least two proxy requests to the second MEC system respectively according to the system priorities corresponding to each first MEC system, the following contents may be included: determining the sending order of each proxy request according to the system priorities corresponding to each first MEC system; and forwarding at least two proxy requests to the second MEC system in sequence according to the sending order.
[0073] The above-mentioned MEC proxy method determines the system priority corresponding to each first MEC system, and determines the sending order of each proxy request according to the system priority, and then, according to the sending order, forwards at least two proxy requests to the second MEC system in sequence. This ensures that when the MEFB network element receives proxy requests sent by at least two first MEC systems at the same time, each proxy request can be sent to the second MEC system in an orderly manner, preventing data transmission congestion of the second MEC system and ensuring the smooth transmission of the proxy request.
[0074] In one embodiment, if Figure 7 As shown, when the proxy request needs to be forwarded to the second MEC system so that the second MEC system processes the proxy request, the following contents may be included:
[0075] S701, receiving proxy requests sent by at least two first MEC systems.
[0076] S702: Extract the first system identifier carried in each proxy request.
[0077] S703, obtaining a white list of proxy permissions for MEFB network elements; wherein the white list of proxy permissions records at least one candidate system identifier.
[0078] S704: If there are candidate system identifiers that are the same as each first system identifier in the proxy authority whitelist, it is determined that each first MEC system has the proxy authority.
[0079] S705: Determine the system priority corresponding to each first MEC system.
[0080] S706, forwarding at least two proxy requests to the second MEC system according to the system priorities corresponding to the first MEC systems, so that the second MEC system processes the proxy requests; wherein neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0081] In one embodiment of the present application, Figure 8As shown in the figure, the main modules of the MEC system include MEC host, MEC platform, MEC applications, MEC orchestrator, MEC platform manager and Virtualisation infrastructure manager. The MEF used for MEC federation includes MEFM (MECFederation Manager) and MEFB (optional). Among them, the Mff reference point between MEFs in the MEC federation is used to share information.
[0082] The above-mentioned MEC proxy method receives a proxy request sent by the first MEC system and forwards the proxy request to the second MEC system so that the second MEC system processes the proxy request. According to the above content, since the MEFB network element in this application does not belong to the external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, after the first MEC system generates a proxy request, it can be transmitted to the MEFB network element in the external cloud environment. Then, the MEFB network element forwards the proxy request sent by the first MEC system to the second MEC system, so as to realize the proxy operation for the MEC system without setting up MEFB network elements in the first MEC system and the second MEC system, thereby avoiding the situation in which there is more than one MEC system configured with MEFB network elements in the MEC union, causing redundancy and idleness of MEFB network elements, and preventing waste of resources for MEFB network elements.
[0083] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0084] Based on the same inventive concept, the embodiment of the present application also provides a MEC proxy device for implementing the MEC proxy method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more MEC proxy device embodiments provided below can refer to the limitations of the MEC proxy method above, and will not be repeated here.
[0085] In one embodiment, Fig. 9 As shown, a MEC proxy device is provided, which is configured in a mobile edge computing federation coordination agent MEFB network element, the MEFB network element is deployed in an external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, including: a receiving module 10 and a forwarding module 20, wherein:
[0086] The receiving module 10 is used to receive the proxy request sent by the first MEC system;
[0087] The forwarding module 20 is used to forward the proxy request to the second MEC system so that the second MEC system processes the proxy request.
[0088] In one embodiment, neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0089] In one embodiment, extracting the first system identifier carried in the proxy request;
[0090] When it is determined, according to the first system identifier, that the first MEC system has the proxy authority, the proxy request is forwarded to the second MEC system.
[0091] In one embodiment, a proxy authority whitelist for a MEFB network element is obtained; wherein the proxy authority whitelist records at least one candidate system identifier;
[0092] If there is a candidate system identifier that is the same as the first system identifier in the proxy authority whitelist, it is determined that the first MEC system has the proxy authority.
[0093] In one embodiment, receiving proxy requests sent by at least two first MEC systems;
[0094] Determine the system priority corresponding to each first MEC system;
[0095] According to the system priorities corresponding to the first MEC systems, at least two proxy requests are forwarded to the second MEC system respectively.
[0096] In one embodiment,
[0097] Determine the order of sending each proxy request according to the system priority corresponding to each first MEC system;
[0098] According to the sending order, at least two proxy requests are forwarded to the second MEC system in sequence.
[0099] The above-mentioned MEC proxy device receives the proxy request sent by the first MEC system and forwards the proxy request to the second MEC system so that the second MEC system processes the proxy request. According to the above content, since the MEFB network element in the present application does not belong to the external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, after the first MEC system generates a proxy request, it can be transmitted to the MEFB network element in the external cloud environment. Then, the MEFB network element forwards the proxy request sent by the first MEC system to the second MEC system, so as to realize the proxy operation for the MEC system without setting up MEFB network elements in the first MEC system and the second MEC system, thereby avoiding the situation in which there is more than one MEC system configured with MEFB network elements in the MEC union, causing redundancy and idleness of MEFB network elements, and preventing waste of resources for MEFB network elements.
[0100] Each module in the above-mentioned MEC proxy device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.
[0101] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.10As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a MEC proxy method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.
[0102] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0103] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:
[0104] Receiving a proxy request sent by the first MEC system;
[0105] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0106] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0107] Neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0108] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0109] Extract the first system identifier carried in the proxy request;
[0110] When it is determined, according to the first system identifier, that the first MEC system has the proxy authority, the proxy request is forwarded to the second MEC system.
[0111] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0112] Obtaining a whitelist of proxy permissions for MEFB network elements; wherein the proxy permission whitelist records at least one candidate system identifier;
[0113] If there is a candidate system identifier that is the same as the first system identifier in the proxy authority whitelist, it is determined that the first MEC system has the proxy authority.
[0114] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0115] Receiving proxy requests sent by at least two first MEC systems;
[0116] Accordingly, the proxy request is forwarded to the second MEC system, including:
[0117] Determine the system priority corresponding to each first MEC system;
[0118] According to the system priorities corresponding to the first MEC systems, at least two proxy requests are forwarded to the second MEC system respectively.
[0119] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0120] Determine the order of sending each proxy request according to the system priority corresponding to each first MEC system;
[0121] According to the sending order, at least two proxy requests are forwarded to the second MEC system in sequence.
[0122] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0123] Receiving a proxy request sent by the first MEC system;
[0124] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0125] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0126] Neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0127] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0128] Extract the first system identifier carried in the proxy request;
[0129] When it is determined, according to the first system identifier, that the first MEC system has the proxy authority, the proxy request is forwarded to the second MEC system.
[0130] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0131] Obtaining a whitelist of proxy permissions for MEFB network elements; wherein the proxy permission whitelist records at least one candidate system identifier;
[0132] If there is a candidate system identifier that is the same as the first system identifier in the proxy authority whitelist, it is determined that the first MEC system has the proxy authority.
[0133] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0134] Receiving proxy requests sent by at least two first MEC systems;
[0135] Accordingly, the proxy request is forwarded to the second MEC system, including:
[0136] Determine the system priority corresponding to each first MEC system;
[0137] According to the system priorities corresponding to the first MEC systems, at least two proxy requests are forwarded to the second MEC system respectively.
[0138] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0139] Determine the order of sending each proxy request according to the system priority corresponding to each first MEC system;
[0140] According to the sending order, at least two proxy requests are forwarded to the second MEC system in sequence.
[0141] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:
[0142] Receiving a proxy request sent by the first MEC system;
[0143] The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
[0144] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0145] Neither the first MEC system nor the second MEC system is provided with a MEFB network element.
[0146] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0147] Extract the first system identifier carried in the proxy request;
[0148] When it is determined, according to the first system identifier, that the first MEC system has the proxy authority, the proxy request is forwarded to the second MEC system.
[0149] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0150] Obtaining a whitelist of proxy permissions for MEFB network elements; wherein the proxy permission whitelist records at least one candidate system identifier;
[0151] If there is a candidate system identifier that is the same as the first system identifier in the proxy authority whitelist, it is determined that the first MEC system has the proxy authority.
[0152] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0153] Receiving proxy requests sent by at least two first MEC systems;
[0154] Accordingly, the proxy request is forwarded to the second MEC system, including:
[0155] Determine the system priority corresponding to each first MEC system;
[0156] According to the system priorities corresponding to the first MEC systems, at least two proxy requests are forwarded to the second MEC system respectively.
[0157] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:
[0158] Determine the order of sending each proxy request according to the system priority corresponding to each first MEC system;
[0159] According to the sending order, at least two proxy requests are forwarded to the second MEC system in sequence.
[0160] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.
[0161] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.
[0162] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0163] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A MEC proxy method, characterized in that: Applied to a mobile edge computing federation coordination agent MEFB network element, the MEFB network element is deployed in an external cloud environment, and the MEFB network element is connected to both a first multi-access edge computing MEC system and a second MEC system, the method comprising: Receiving a proxy request sent by the first MEC system; The proxy request is forwarded to the second MEC system so that the second MEC system processes the proxy request.
2. The method according to claim 1, characterized in that No MEFB network element is provided in the first MEC system or the second MEC system.
3. The method according to claim 1, characterized in that The forwarding the proxy request to the second MEC system includes: Extracting the first system identifier carried in the proxy request; When it is determined, according to the first system identifier, that the first MEC system has proxy authority, the proxy request is forwarded to the second MEC system.
4. The method according to claim 3, characterized in that The determining, according to the first system identifier, that the first MEC system has proxy authority includes: Obtaining a proxy authority whitelist for MEFB network elements; wherein the proxy authority whitelist records at least one candidate system identifier; If the candidate system identifier that is identical to the first system identifier exists in the proxy authority whitelist, it is determined that the first MEC system has proxy authority.
5. The method according to claim 1, characterized in that The receiving a proxy request sent by the first MEC system includes: Receiving proxy requests sent by at least two first MEC systems; Accordingly, forwarding the proxy request to the second MEC system includes: Determine the system priority corresponding to each of the first MEC systems; According to the system priorities corresponding to the first MEC systems, at least two of the proxy requests are forwarded to the second MEC system respectively.
6. The method according to claim 5, characterized in that The forwarding at least two proxy requests to the second MEC system respectively according to the system priorities corresponding to the first MEC systems includes: Determining a sending order of each of the proxy requests according to the system priorities corresponding to each of the first MEC systems; According to the sending order, at least two of the proxy requests are forwarded to the second MEC system in sequence.
7. A MEC proxy device, characterized in that: The device is configured in a mobile edge computing federation coordination agent MEFB network element, which is deployed in an external cloud environment, and the MEFB network element is connected to both the first multi-access edge computing MEC system and the second MEC system, and includes: A receiving module, used for receiving a proxy request sent by the first MEC system; The forwarding module is used to forward the proxy request to the second MEC system so that the second MEC system processes the proxy request.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
Citation Information
Patent Citations
Edge application processing method and platform, electronic equipment and storage medium
CN114844895A
Federated MEC framework for automotive services
US20230164241A1
MEC federation broker and manager enabling secure cross-platform communication
WO2022125456A1
Systems and methods for supporting application package management and lifecycle management
WO2024108370A1