Method and apparatus for instantiating an edge application server

Abstract

An embodiment of the present application provides a method and an apparatus for instantiating an edge application server, which is related to the field of communication technologies, for dynamically instantiating an edge application server. In the method, a first network element may receive first information from a second network element. The first information may include network information and application information. The network information may indicate a first network, and the application information may indicate a first application. The first information may further include information about a first event in the first network related to the first application. The first event includes at least one of: an edge application server corresponding to the first application is not discovered in the first network, an edge enabler server corresponding to the first application is not discovered in the first network, and performance information of an edge application server corresponding to the first application in the first network. The first network element may determine to instantiate a first edge application server corresponding to the first application in the first network if the first event satisfies a first condition.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202110766584.3, entitled "Method and Apparatus for Instantiating an Edge Application Server," filed with the State Intellectual Property Office of China on July 7, 2021, the entire contents of which are incorporated herein by reference.

[0002]

[0002] Technical field The present application relates to the field of communications technology, and in particular to methods for instantiating edge application servers and devices. [Background technology]

[0003]

[0003] An edge data network (EDN) may be a local data center. The EDN includes an edge enabler server (EES) and multiple edge application servers (EAS). Each EDN has a specific service scope. The EES may be a control or management network element within a mobile edge computing (MEC) node and is responsible for managing each EAS deployed within the EDN, for example, registration and domain name server (DNS) resolution. Additionally, the EES may invoke the network's capability exposure function.

[0004]

[0004] User equipment (UE) may include an edge enabler client (EEC) and an application client (AC). The EEC provides the necessary support for the application client on the UE, allowing the UE to register with the EES via the EDGE-1 interface.

[0005]

[0005] In the prior art, when a UE registers with an EES, the EES can detect whether the deployed EAS is compatible with the application information accessed by the UE. If the EES detects that the deployed EAS is not compatible with the application information accessed by the UE, or that there is no EAS instantiated in the current EDN, it is not defined how to match the access request of the UE. Summary of the Invention

[0006]

[0006] Embodiments of the present application provide a method and apparatus for instantiating an edge application server, for dynamically instantiating an edge application server.

[0007] According to a first aspect, a method for instantiating an edge application server is provided. The method may be performed by a first network element or may be performed by a chip as the first network element. The first network element may be an application service provider or a management system. In the method, the first network element may receive first information from a second network element. The first information may include network information and application information. The network information may indicate the first network, and the application information may indicate a first application. The first information may further include information regarding a first event in the first network related to the first application. The first event may include at least one of: an edge application server corresponding to the first application not being discovered in the first network; an edge enabler server corresponding to the first application not being discovered in the first network; and performance information of an edge application server corresponding to the first application in the first network. The first network element may determine to instantiate a first edge application server corresponding to a first application in the first network if a first event satisfies a first condition.

[0008]

[0008] Based on the above solution, the first network element may determine, based on a first event reported by a second network element, to dynamically instantiate an edge application server of a first application if the first event satisfies a first condition, which may improve the efficiency of operation and maintenance management.

[0009]

[0009] In a possible implementation, not finding an edge application server corresponding to the first application within the first network includes: not finding an edge application server corresponding to the first application within the first network.

[0010]

[0010] In another possible implementation, the fact that an edge application server corresponding to the first application is not found in the first network includes: an edge application server corresponding to the first application that satisfies the terminal requirements (UE required) does not exist in the first network. In other words, an edge application server corresponding to the first application is deployed or instantiated in the first network, but the performance of the edge application server for the first application cannot satisfy the terminal requirements.

[0011] In a possible implementation, if the first event includes an edge application server corresponding to a first application not being discovered in a first network, the first condition may include the number of times within a first time period that the edge application server corresponding to the first application is not discovered in the first network being equal to or greater than a first threshold. If the first event includes an edge enabler server corresponding to the first application not being discovered in the first network, the first condition may include the number of times within a second time period that the edge enabler server corresponding to the first application is not discovered in the first network being equal to or greater than a second threshold. If the first event includes performance information of an edge application server corresponding to the first application in the first network, the first condition may include at least one of a load on the edge application server being equal to or greater than a third threshold and the edge application server breaking down.

[0012]

[0012] Based on the above solution, when multiple terminals want to access the first application, or when one terminal wants to access the first application multiple times, an edge application server of the first application can be instantiated, which may improve user experience.

[0013]

[0013] In a possible implementation, the first network element may send an edge application server instantiation request to the management system, where the edge application server instantiation request is used to instantiate an edge application server, and the edge application server instantiation request includes network information and application information.

[0014] In a possible implementation, the first information may further include the number of times the first event occurred.

[0015]

[0015] Based on the above solution, the second network element may report the first event to the first network element if it detects the first event multiple times, which may improve the utilization of transmission resources.

[0016] In a possible implementation, the number of times that an edge enabler server corresponding to the first application has not been found in the first network may be the number of times that the first network element receives the first event. Alternatively, the number of times that an edge enabler server corresponding to the first application has not been found in the first network may be the number of times that the first network element receives the first event.

[0017]

[0017] Based on the above solution, the second network element may report the first event to the first network element multiple times, and when the terminal wants to access the first application but the edge application server of the first application is not deployed in the network, the second network element can report the terminal's requirements to the first network element in a timely manner, which improves the user experience.

[0018]

[0018] In a possible implementation, when the first network element is a management system, before the first network element instantiates a first edge application server corresponding to a first application in the first network, the first network element may obtain application installation information from an application service provider that is acceptable for the application to be instantiated.

[0019]

[0019] Based on the above solution, after obtaining the application installation information that is authorized to be instantiated, the management system can directly communicate with the second network element, which reduces complexity.

[0020]

[0020] In a possible implementation, the first network element may send second information to the second network element, and the second information may indicate that the first edge application server has been successfully instantiated.

[0021] In a possible implementation, the first network element may subscribe to the first information.

[0022]

[0022] Based on the above solution, the first network element subscribes to the first information and receives the first information of the second network element, which may improve the success rate of receiving the first information by the first network element.

[0023] According to a second aspect, a method for instantiating an edge application server is provided. The method may be performed by a second network element or a chip having functionality similar to that of the second network element. The second network element may be an edge enabler server or an edge network configuration server. In the method, the second network element may detect a first event. The first event may include at least one of: an edge application server corresponding to a first application not being discovered in the first network; an edge enabler server corresponding to the first application not being discovered in the first network; and performance information of an edge application server corresponding to the first application in the first network. Based on the detected first event, the second network element may send first information to the first network element or send indication information to one or more terminals. The first information may include network information and application information, and the indication information may indicate that an edge application server needs to be instantiated. The network information may indicate a first network, and the application information may indicate a first application.

[0024]

[0024] In a possible implementation, not finding an edge application server corresponding to the first application in the first network includes: an edge application server corresponding to the first application is not deployed or instantiated in the first network, or an edge application server corresponding to the first application that meets the terminal requirements (UE required) does not exist in the first network, and the edge configuration server determines that an edge enabler server corresponding to the first application is not found in the first network.

[0025]

[0025] In a possible implementation, the indication information indicates that an edge application server or an edge enabler server corresponding to the first application has not been found in the first network or has failed to register. The name of the indication information is not limited.

[0026]

[0026] Based on the above solution, the second network element may report a first event related to a first application that is detected within the first network to the first network element, so that the first network element may decide whether to instantiate an edge application server within the first network.

[0027]

[0027] In a possible implementation, the second network element may receive second information, the second information may indicate that the first edge application server has been successfully instantiated, and the first information may be used to determine whether to instantiate the first edge application server.

[0028]

[0028] Based on the above solution, the first network element may determine, based on a first event reported by a second network element, to dynamically instantiate an edge application server of a first application if the first event satisfies a first condition, which may improve the efficiency of operation and maintenance management.

[0029] In a possible implementation, the first information may further include the number of times the first event occurred.

[0030]

[0030] In a possible implementation, the indication may indicate that the edge application server failed to be discovered or that the edge enabler client failed to be registered.

[0031]

[0031] Based on the above solution, the second network element may instruct one or more terminals through indication information whether an edge application server needs to be dynamically instantiated.

[0032] According to a third aspect, a method for instantiating an edge application server is provided. The method may be performed by a first network element or a chip having similar functionality to that of the first network element. The first network element may be an application service provider or a management system. In the method, the first network element may receive first request information from one or more terminals, and the first request information may be used to request instantiation of an edge application server. The first request information may include network information, application information, and a terminal identifier. The network information may indicate the first network, the application information may indicate the first application, and the terminal identifier may identify the terminal that sent the first request information. The first network element may determine whether to instantiate an edge application server corresponding to the first application in the first network based on the first request information.

[0033]

[0033] Based on the above solution, a terminal sends first request information to a first network element to request instantiation of an edge application server of a first application in a first network, so that a differentiated service experience may be provided to the terminal, which improves the efficiency of operation and maintenance management.

[0034]

[0034] In a possible implementation, it may be decided to instantiate an edge application server corresponding to a first application in the first network when the number of one or more terminals reaches a first threshold; and / or it may be decided to instantiate an edge application server corresponding to a first application in the first network when the subscription level of a terminal identified by a terminal identifier is equal to or greater than a specified level.

[0035]

[0035] Based on the above solution, when multiple terminals wish to access the first application or a high subscription level of the first application, an edge application server of the first application may be instantiated, so that a differentiated service experience may be provided to the terminals, which improves the efficiency of operation and maintenance management.

[0036] In a possible implementation, the first network element may send second request information to the management system, where the second request information may be used to request instantiation of an edge application server, and the second request information may include network information and application information.

[0037] In a possible implementation, the network information may include at least one of a network identifier and a location identifier, which may identify the first network, and the application information may include at least one of an application identifier and an application performance condition.

[0038]

[0038] In a possible implementation, the first network element is a management system, and before the first network element decides to instantiate an edge application server corresponding to a first application in the first network, the first network element may obtain application installation information from an application service provider that is acceptable for the application to be instantiated.

[0039]

[0039] Based on the above solution, after obtaining the application installation information that is authorized for instantiation, the management system may directly communicate with the terminal, which reduces the complexity.

[0040]

[0040] In a possible implementation, the first network element may send second information to the second network element or one or more terminals, and the second information may indicate that an edge application server corresponding to the first application has been successfully instantiated.

[0041]

[0041] In a possible implementation, if the number of one or more terminals has not reached the first threshold, third information may be sent to one or more terminals. The third information may indicate that an edge application server for the first application has not been found in the first network; and / or if a subscription level of a terminal identified by a terminal identifier is lower than a specified level, the third information may be sent to one or more terminals. The third information may indicate that an edge application server for the first application has not been found in the first network.

[0042]

[0042] Based on the above solution, if the above condition is not met, the first network element may send the third information to the terminal. In other words, the edge application server of the first application is not instantiated in the first network. This may save resources in the EDN network.

[0043]

[0043] According to a fourth aspect, a method for instantiating an edge application server is provided. The method may be executed by a terminal or a chip having similar functions to those of a terminal. In the method, an edge enabler client may receive indication information from an edge enabler server or an edge network configuration server. The indication information may indicate that an edge application server has failed to be discovered, or that the edge enabler client has failed to register, or that the edge application server needs to be instantiated. The edge enabler client may send request information to a first network element based on the indication information, and the request information may include network information and application information. The network information may indicate a first network, and the application information may indicate a first application.

[0044]

[0044] Based on the above solution, a terminal sends first request information to a first network element to request instantiation of an edge application server of a first application in a first network, so that a differentiated service experience may be provided to the terminal, which improves the efficiency of operation and maintenance management.

[0045]

[0045] In a possible implementation, the edge enabler client may send instruction information to the application client.

[0046]

[0046] In a possible implementation, the edge enabler client may receive request information from the application client.

[0047]

[0047] In a possible implementation, the edge enabler client may receive second information from the first network element, and the second information may indicate that an edge application server corresponding to the first application has been successfully instantiated.

[0048] According to a fifth aspect, there is provided a communications device, which may include modules / units, such as a transceiver unit and a processing unit, configured to perform the first aspect or any possible implementation of the first aspect.

[0049] The transceiver unit is configured to receive first information from the second network element, the first information including network information and application information, the network information indicating a first network, the application information indicating a first application, and the first information further including information regarding a first event related to the first application, the first event in the first network, the first event including at least one of: an edge application server corresponding to the first application not being discovered in the first network, an edge enabler server corresponding to the first application not being discovered in the first network, and performance information of the edge application server corresponding to the first application in the first network. The processing unit is configured to determine to instantiate the first edge application server corresponding to the first application in the first network if the first event satisfies a first condition.

[0050]

[0050] In the design, when the first event includes an edge application server corresponding to the first application not being discovered within the first network, the first condition includes the number of times within a first period that the edge application server corresponding to the first application is not discovered within the first network being equal to or greater than a first threshold; If the first event includes an edge enabler server corresponding to the first application not being discovered within the first network, the first condition includes a number of times within a second time period that the edge enabler server corresponding to the first application is not discovered within the first network being equal to or greater than a second threshold; and When the first event includes performance information of an edge application server corresponding to the first application in the first network, the first condition includes at least one of a load on the edge application server being equal to or greater than a third threshold and the edge application server breaking down.

[0051]

[0051] In the design, the transceiver unit is further configured to send an edge application server instantiation request to the management system, where the edge application server instantiation request is used to instantiate the edge application server, and the edge application server instantiation request includes network information and application information.

[0052] In the design, the first information further includes the number of times the first event occurred.

[0053] In the design, the number of times that an edge enabler server corresponding to the first application is not found in the first network is the number of times that the first network element receives the first information; or The number of times that an edge enabler server corresponding to the first application is not discovered in the first network is the number of times the first network element receives the first event.

[0054]

[0054] In the design, the processing unit is further configured to obtain application installation information from the application service provider that is allowed to be instantiated.

[0055]

[0055] In the design, the transceiver unit is further configured to transmit second information to the second network element, the second information indicating that the first edge application server has been successfully instantiated.

[0056]

[0056] In the design, the transceiver unit is further configured to send a subscription request to the second network element, the subscription request being used to subscribe to the first information.

[0057] According to a sixth aspect, there is provided a communications device, which may include modules / units, such as a transceiver unit and a processing unit, configured to perform the second aspect or any possible implementation of the second aspect.

[0058]

[0058] The processing unit is configured to detect a first event, the first event including at least one of: an edge application server corresponding to the first application not being discovered in the first network, an edge enabler server corresponding to the first application not being discovered in the first network, and performance information of the edge application server corresponding to the first application in the first network; and the transceiver unit is configured to send first information to the first network element or send indication information to one or more terminals based on the detected first event. The first information includes network information and application information, the indication information indicating that an edge application server needs to be instantiated, the network information indicating the first network, and the application information indicating the first application.

[0059]

[0059] In the design, the transceiver unit is configured to receive second information, the second information indicating that the first edge application server has been successfully instantiated, and the first information is used to determine whether to instantiate the first edge application server.

[0060] In the design, the first information further comprises the number of times the first event occurred.

[0061]

[0061] In the design, the indication information indicates that the edge application server has failed to be discovered or that the edge enabler client has failed to be registered.

[0062] According to a seventh aspect, there is provided a communications device, which may include modules / units, such as a transceiver unit and a processing unit, configured to perform the third aspect or any possible implementation of the third aspect.

[0063]

[0063] The transceiver unit is configured to receive first request information from one or more terminals, the first request information is used to request instantiation of an edge application server, the first request information includes network information, application information, and a terminal identifier, the network information indicates a first network, the application information indicates a first application, and the terminal identifier identifies the terminal that sent the first request information, and the processing unit is configured to determine, based on the first request information, whether to instantiate an edge application server corresponding to the first application in the first network.

[0064]

[0064] In the design, when determining whether to instantiate an edge application server corresponding to a first application in a first network based on the first requirement information, the processing unit specifically: determining to instantiate an edge application server corresponding to the first application in the first network when the number of one or more terminals reaches a first threshold; and / or and determining to instantiate an edge application server corresponding to the first application in the first network when a subscription level of the terminal identified by the terminal identifier is equal to or greater than a specified level.

[0065]

[0065] In the design, the transceiver unit is further configured to send second request information to the management system, where the second request information is used to request instantiation of an edge application server, and the second request information includes network information and application information.

[0066]

[0066] In the design, the network information includes at least one of a network identifier and a location identifier, where the network identifier and the location identifier identify the first network, and the application information includes at least one of an application identifier and an application performance condition.

[0067]

[0067] In the design, the processing unit is further configured to obtain application installation information from the application service provider that is allowed to be instantiated.

[0068]

[0068] In the design, the transceiver unit is further configured to transmit second information to a second network element or one or more terminals, the second information indicating that the first application provides a corresponding edge application server that has been successfully instantiated.

[0069]

[0069] In the design, the transceiver unit is configured to send third information to one or more terminals when the number of the one or more terminals has not reached a first threshold, the third information indicating that an edge application server of the first application has not been found in the first network; and / or the transceiver unit is configured to send third information to one or more terminals when the subscription level of the terminal identified by the terminal identifier is lower than a specified level, the third information indicating that an edge application server of the first application has not been found in the first network.

[0070] According to an eighth aspect, there is provided a communications device, which may include modules / units, such as a transceiver unit and a processing unit, configured to perform the fourth aspect or any possible implementation of the fourth aspect.

[0071]

[0071] The transceiver unit is configured to receive indication information from the edge enabler server or the edge network configuration server, the indication information indicating that the edge application server has failed to be discovered, or that the edge enabler client has failed to register, or that the edge application server needs to be instantiated. The processing unit is configured to generate request information based on the indication information. The request information includes network information, application information, and a terminal identifier, where the network information indicates a first network, the application information indicates a first application, and the terminal identifier identifies a terminal sending the request information. The transceiver unit is further configured to send the request information to the first network element.

[0072]

[0072] In the design, the transceiver unit is further configured to send instruction information to the application client; and receive request information from the application client.

[0073]

[0073] In the design, the transceiver unit is further configured to receive second information from the first network element, the second information indicating that an edge application server corresponding to the first application has been successfully instantiated.

[0074] According to a ninth aspect, there is provided a communications device including a processor and a memory. The memory is configured to store computer programs or instructions. The processor executes the computer programs or instructions in the memory to implement the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect.

[0075]

[0075] The memory may be located within the device, external to the device, or connected to the device.

[0076]

[0076] In a possible implementation, the memory may be integrated with the processor.

[0077]

[0077] In a possible implementation, the communication device may further include a transceiver that performs receiving and transmitting operations in the manner of the first aspect or any possible implementation of the first aspect, receiving and transmitting operations in the manner of the second aspect or any possible implementation of the second aspect, receiving and transmitting operations in the manner of the third aspect or any possible implementation of the third aspect, and receiving and transmitting operations in the manner of the fourth aspect or any possible implementation of the fourth aspect.

[0078]

[0078] According to a tenth aspect, there is provided a chip, the chip including a logic circuit and a communication interface.

[0079] For example, the communication interface is configured to input first information, the first information including network information and application information, where the network information indicates a first network and the application information indicates a first application, and the first information further includes information regarding a first event related to the first application, the first event in the first network. The first event includes at least one of: an edge application server corresponding to the first application not being discovered in the first network; an edge enabler server corresponding to the first application not being discovered in the first network; and performance information of the edge application server corresponding to the first application in the first network. The logic circuit is configured to determine to instantiate the first edge application server corresponding to the first application in the first network if the first event satisfies a first condition.

[0080] For example, the logic circuit is configured to detect a first event, the first event including at least one of: an edge application server corresponding to the first application not being discovered in the first network; an edge enabler server corresponding to the first application not being discovered in the first network; and performance information of the edge application server corresponding to the first application in the first network. The communication interface is configured to output first information or indication information, the first information including network information and application information, the indication information indicating that an edge application server needs to be instantiated, the network information indicating the first network, and the application information indicating the first application.

[0081] For example, a user of the communication interface inputs first request information, the first request information being used to request instantiation of an edge application server, the first request information including network information, application information, and a terminal identifier, the network information indicating a first network, the application information indicating a first application, and the terminal identifier identifying a terminal sending the first request information. The logic circuit is configured to determine, based on the first request information, whether to instantiate an edge application server corresponding to the first application in the first network.

[0082]

[0082] For example, the communication interface is configured to input indication information, where the indication information indicates that the edge application server has failed to be discovered, or that the edge enabler client has failed to register, or that the edge application server needs to be instantiated. The logic circuit is configured to generate request information based on the indication information. The request information includes network information, application information, and a terminal identifier, where the network information indicates a first network, the application information indicates a first application, and the terminal identifier identifies a terminal sending the request information. The communication interface is further configured to output the request information.

[0083]

[0083] According to an eleventh aspect, the present application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the method of the aforementioned aspect.

[0084]

[0084] According to a twelfth aspect, the present application provides a computer program product storing instructions that, when executed on a computer, enable the computer to perform the method of the previous aspect.

[0085]

[0085] According to a thirteenth aspect, the present application provides a communication system including at least one first network element and at least one second network element, or including at least one first network element and at least one terminal.

[0086]

[0086] For the advantageous effects of the fifth to thirteenth aspects, please refer to the advantageous effects shown in the first to fourth aspects. [Brief explanation of the drawings]

[0087] [Figure 1]

[0087] Figure 1 is an exemplary flow chart of EEC registration. [Figure 2]

[0088] FIG. 2 illustrates a network architecture according to an embodiment of the present application. [Figure 3]

[0089] FIG. 3 is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. [Figure 4]

[0090] FIG. 4 is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. [Figure 5]

[0091] FIG. 5 is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. [Figure 6A]

[0092] FIG. 6A is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. [Figure 6B]

[0092] Figure 6B is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. [Figure 7]

[0093] FIG. 7 is a configuration diagram of a communication device according to an embodiment of the present application. [Figure 8]

[0094] FIG. 8 is a block diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0088]

[0095] For ease of understanding, first, terms in the embodiments of the present application will be explained and described.

[0089]

[0096] (1) the EAS of the first application may be an EAS capable of providing services for the first application; EAS, which is compatible with the first application, EAS for the first application, an EAS capable of providing services for the first application; It may also be referred to as an EAS that provides services for the first application.

[0090]

[0097] An EDN includes an EES and multiple EASs. Each EDN has a specific service range. An EES may be a control or management network element within an MEC node. In the European Telecommunications Standard Institute (ETSI) MEC architecture, an EDN may also be referred to as an MEC node or MEC site. An MEC node includes an MEC platform (MEP) and MEC applications. The EES and MEC have similar functions, and the EASs and MEC applications also have similar functions.

[0091]

[0098] The edge configuration server (ECS) may be a global management network element, which holds information for each EDN, including service range, EES address, etc. It should be noted that in some standard protocols such as technical specifications (TS) 23.501, TS 23.502, etc., the aforementioned EES, EAS, ECS, MEP, etc. may be referred to as application function (AF) network elements.

[0092]

[0099] Figure 1 is a flowchart for registering an EEC with the EES, which may include the following actions:

[0093]

[0100] S101: The EEC sends a service configuration request (service provisioning request) to the ECS.

[0094]

[0101] The service configuration request may include application information that the UE wishes to access, such as an application identifier, application performance requirements, and / or the like.

[0095]

[0102] S102: The ECS transmits information about the EES to the EEC.

[0096]

[0103] The ECS can search for an EES that matches the application that the UE wants to access. For example, the ECS can search for an EDN where a corresponding EAS is deployed based on an application identifier. If the ECS finds an EDN, the ECS can send information about the EES in the found EDN to the EEC.

[0097]

[0104] S103: The EEC sends a registration request to the EES.

[0098]

[0105] The registration request may carry an EEC identifier, security credentials, application information that the UE wishes to access (e.g., application identifier, application performance requirements, etc.), and an EEC context identifier.

[0099]

[0106] S104: The EES verifies whether the EEC's registration request is valid.

[0100]

[0107] The EES can verify whether the EEC identifier matches the security certificate, and if the EEC identifier matches the security certificate, it can determine that the registration request is valid; or if the EEC identifier does not match the security certificate, it can determine that the registration request is invalid.

[0101]

[0108] Furthermore, the EES may further determine whether the deployed EAS meets the access requirements of the UE. For example, the EES may determine whether an EAS for an application requested by the UE is deployed. Alternatively, the EES may determine whether the deployed EAS meets the requirements of the UE, for example, whether the bandwidth, delay, etc. of the deployed EAS meet the requirements of the UE.

[0102]

[0109] Optionally, the following operation S105 may be further performed.

[0103]

[0110] S105: The EES obtains the EEC context based on the EEC context identifier.

[0104]

[0111] The EES can determine the EES to which the UE is registered based on the EEC context identifier and obtain the EEC context from the EES to which the UE is registered.

[0105]

[0112] S106: The EES sends a response message to the EEC to notify the EEC whether the registration was successful.

[0106]

[0113] After the EEC registration is successful, the following operation S107 may be further performed.

[0107]

[0114] S107: The EEC sends an EAS discovery request to the EES.

[0108]

[0115] The EAS discovery request may include application information. Based on the application information, the EES can search for an EAS that matches the application that the UE wants to access. If the EES is found, the EES can send information about the found EAS to the EEC.

[0109]

[0116] In S104, if the EES detects that the deployed EAS does not match the application information that the UE wishes to access, or if the EES finds that the EAS is not instantiated in the current EDN after the EEC sends a registration request to the EES in S103, or if the EES does not find an EAS that matches the application information that the UE wishes to access after the EEC sends an EAS discovery request to the EES in S107, the EES can dynamically trigger an EAS to match the EEC's request. However, how to dynamically instantiate an EAS is not defined.

[0110]

[0117]

[0013] An embodiment of the present application provides a method for instantiating an EAS. In the method, if the deployed EAS does not match the application information that the UE wishes to access, or if the EAS is not instantiated in the current EDN, the EAS may be instantiated to match the requirements of the EEC. Figure 2 shows a communication system to which the technical solutions provided in the embodiment of the present application can be applied, showing an edge application server and an edge enabler server on the edge data network side, and an application client and an edge enabler client on the terminal device side.

[0111]

[0118] An EDN corresponds to a data network deployed at the edge and may be a local data network (local DN) or a local area data network (LADN). An edge data network includes an edge enabler function that may use a data network access identifier (DNAI) and a data network name (DNN) identifier, or a data network name and a data network service area identifier. Alternatively, it will be understood that an edge data network can be considered a data center deployed locally with respect to a central cloud. An edge data network is identified using a DNAI, and an edge data network may include multiple local data networks (local DN).

[0112]

[0119] An EAS is a server application program deployed in an edge data network and may be referred to as an application instance, edge application instance, MEC application (server), EAS function, or the like. For example, applications such as social media software, augmented reality (AR), and virtual reality (VR) are deployed and run on an application instance in an EDN. One or more EASs may be deployed for one application in one or more EDNs, and EASs deployed and running in different EDNs may be considered different EASs for one application. Different EASs for one application may share a domain name. Different EASs for one application may use a single anycast IP address or different IP addresses. An edge application server EAS may also contain the application context for the application corresponding to the EAS. Optionally, the application context may further include the context of one or more application users using the application in the EAS, e.g., execution status information related to one or more application users using the application, or a transaction identifier of a subscription in the EAS for one or more application users. Optionally, the application context may also include the subscription context of one or more application users using the application in the EAS and core network, e.g., a subscription transaction identifier.

[0113]

[0120] The EES is deployed in the EDN and provides edge compute enabler services to application instances (EASs) deployed in the EDN to better support the deployment and execution of applications in the MEC. The EES supports EAS registration, authentication and authorization in the user equipment (UE), or authentication and authorization in the edge enabler client, and can provide information about application instances, such as IP address information, to the UE. Generally, one EAS can be registered with one EES, or information about one EAS can be configured for one EES through a management system. In this case, the EES is called an EES associated with the EAS, and the EES can control (manage) the registration of the EAS configured for the EES or the serving EES of the EAS. The EES also supports obtaining information about application instances, including application instance identifiers and application instance address information (e.g., IP address information), and further transmits information about application instances, such as application instance identifiers, to an edge data network configuration server (ECS). The ECS is responsible for configuring the EDN, such as providing information about the EES to the UE, providing information about the EAS to the UE, interacting with the application DNS to obtain information about the EAS, etc. Furthermore, the ECS can obtain and store information about application instances and IP addresses from other functional entities. The MEC architecture model shown in Figure 2 further illustrates the aforementioned ECS.

[0114]

[0121] The AC is a client program of the application on the terminal device side and a peer entity of the EAS on the terminal device side. The application client is used by the application user to obtain application services from the application server. The application client may connect to the application server on the cloud to obtain application services, or it may connect to the EAS deployed and running on one or more EDNs to obtain application services.

[0115]

[0122] The EEC is a peer entity of the EES on the terminal device side. The EEC is configured to register information about the EEC and about the application client AC with the EES, perform security authentication and authorization, obtain information about the EAS, including the EAS's address information (e.g., IP address), from the EES, and provide edge compute enabler functions to the application client. For example, the EEC discovery service can return the EAS's IP address to the application client.

[0116]

[0123] As shown in Figure 2, a communication connection is established between the application client AC on the terminal device and the edge application server EAS; and a communication connection is established between the edge enabler client EEC on the terminal device and the edge enabler server EES. After signing a service contract with an application provider, an application user can log in to the application client AC deployed on the terminal device to use the application and transmit application data through the communication connection between the application client AC and the EAS. Furthermore, the application user can obtain services provided by the edge enabler server EES from the edge enabler client EEC via the application client AC in the form of an application programming interface (API).

[0117]

[0124] 3 is an exemplary flowchart of a method for instantiating an EAS according to an embodiment of the present application. The method may include the following operations:

[0118]

[0125] S301: A second network element detects a first event.

[0119]

[0126] The second network element may be an EES or an ECS. It should be noted that the ECS may be a network element deployed in a centralized manner and is not necessarily deployed in the EDN network. The deployment location of the ECS is not particularly limited in the embodiments of the present application. The first event may include at least one of the following:

[0120]

[0127] 1. No available EAS corresponding to the first application is found in the first network.

[0121]

[0128] In S104, the EES may determine whether the deployed EAS is compatible with the first application that the UE wishes to access. If the EES determines that the EAS for the first application that the UE wishes to access does not exist in the deployed EAS, it may be considered that an available EAS corresponding to the first application is not found in the first network. In S107, the EES may search for an EAS compatible with the first application that the UE wishes to access based on the application information. If no EAS is found, it may be considered that an available EAS corresponding to the first application is not found in the first network. For ease of explanation, the present application may be described as an available EAS is not found. Details will not be described again below.

[0122]

[0129] Optionally, if the latency and bandwidth of the EAS are not suitable for a first application that the UE wishes to access, it may be considered that an available EAS corresponding to the first application is not found in the first network. For example, if the first application that the UE wishes to access has a high requirement for latency, and the EAS corresponding to the first application and deployed in the first network has a low requirement for latency and experiences a large latency during service processing, it may be considered that the EAS in the first network is not suitable for the first application that the UE wishes to access.

[0123]

[0130] 2. No available EES corresponding to the first application is found in the first network.

[0124]

[0131] In S102, the ECS can search for an EDN or EES in which an EAS compatible with the first application that the UE wishes to access is deployed. If the ECS does not find an EDN or EES, it may be considered that an available EES corresponding to the first application has not been found, or the ECS may be considered that an available EAS corresponding to the first application has not been found. For ease of explanation, the present application may be described as an available EES has not been found. Details will not be described again below.

[0125]

[0132] 3. Performance information of the EAS corresponding to the first application in the first network.

[0133] The EES or ECS may determine EAS performance corresponding to a first application in a first network, such as the load of the EAS (which may include one or more of memory, CPU, bandwidth, number of connections, latency, etc.), whether the EAS is online, etc. Optionally, if the EES or ECS determines that the load of the EAS does not exceed a first value and the EAS is online, the performance information of the EAS may not be reported. If the EES or ECS determines that the load of the EAS is equal to or greater than the first value or if the EAS is out of service, the performance information of the EAS may be reported. The first value may be determined based on an empirical value, such as 50% of the bandwidth of the EAS, 80% of the bandwidth, etc. This is not particularly limited in the present application. For ease of explanation, in the present application, the first value may be described as EAS performance, and the details will not be described again below.

[0126]

[0134] S302: The second network element sends first information to the first network element, and in response, the first network element receives the first information from the second network element.

[0127]

[0135] The first network element may be an ASP or a management system. The first information may include network information and application information. The network information may indicate the first network, and the application information may indicate the first application. The network information may include at least one of a network identifier, a location identifier, an EES identifier, and an ECS identifier. The network identifier may indicate an EDN network, such as a DNAI or DNN. The location identifier may indicate a node in the EDN network, the ECS identifier may identify an ECS, and the EES identifier may identify an EES. The application information may include an application identifier and application performance requirements. The application identifier may indicate an application, such as an EAS ID or FQDN. The application performance requirements may indicate performance requirements, such as bandwidth requirements and latency requirements, of the application indicated by the application identifier. The first information may further include information regarding a first event associated with the first application, the first event occurring in the first network.

[0128]

[0136] The second network element can transmit the first information to the first network element based on the detected first event. In a possible implementation, the EES or ECS can transmit the first information to the ASP or management system each time after detecting the first event. For example, if the ECS does not find an available EES in S102, the ECS can transmit the first information to the ASP or management system. Alternatively, the EES or ECS can transmit the first information to the ASP or management system after detecting the first event multiple times. When the EES or ECS transmits the first information after detecting the first event multiple times, the first information can further include the number of times the first event occurred. For example, the number of times the ECS did not find an available EES, the number of times the EES did not find an available EAS, the number of times the EAS was overloaded, the number of times the EAS failed, etc. Specifically, the EES or ECS may transmit the first information after detecting the first event multiple times, which means that the EES or ECS may detect the first event a predetermined number of times, for example, 10 times. For example, if the EES or ECS detects that an available EES has not been found 10 times, the EES or ECS may transmit the first information to the ASP or management system. Alternatively, the EES or ECS may detect the first event multiple times at a specified interval and transmit the first information to the ASP or management system after the specified interval has elapsed.

[0129]

[0137] In a possible implementation, the first network element can subscribe to the first event or the first information. For example, the management system or the ASP can send a subscription request to the EES or the ECS, and the subscription request can be used to subscribe to the first information or the first event. In this way, the first network element subscribes to the first information or the first event, so that the first network element can avoid missing the first information or the first event.

[0130]

[0138] S303: The first network element determines to instantiate an EAS corresponding to a first application in the first network when a first event satisfies a first condition.

[0131]

[0139] The first condition may include at least one of the following:

[0140] Condition 1: The number of times an available EAS is not found within a first duration is equal to or greater than a first threshold.

[0132]

[0141] The first duration may be predetermined based on an empirical value, for example, 10 seconds or 20 seconds. The first threshold may be predetermined based on an empirical value, for example, 5 or 6 times. This is not particularly limited in the present application. Optionally, the ASP or management system may receive the first information multiple times. If the number of times an available EAS is not found during the first period is equal to or greater than the first threshold, it may be considered that many UEs want to access the first application, or one UE wants to access the first application multiple times, but an EAS capable of providing services for the first application is not instantiated in the first network. In this case, the management system or ASP may determine that an EAS providing services for the first application needs to be instantiated in the first network.

[0133]

[0142] Optionally, if the EES transmits the first information after detecting the first event multiple times, the first information may include the number of times the first event occurred. In this case, condition 1 may include the number of times an available EAS is not found being equal to or greater than a second value. The second value may be the same as or different from the first threshold value. This is not particularly limited in the present application.

[0134]

[0143] Condition 2: The number of times an available EES is not found within a second duration is equal to or greater than a second threshold.

[0135]

[0144] The second duration may be predetermined based on an empirical value, for example, 8 seconds or 10 seconds. The second threshold may be predetermined based on an empirical value, for example, 10 or 15 times. This is not particularly limited in the present application. The second duration may be the same as or different from the first duration, and the first threshold may be the same as or different from the second threshold. This is not particularly limited in the present application.

[0136]

[0145] Optionally, the ASP or management system may receive the first information multiple times. If the number of times an available EES is not found within a second duration is equal to or greater than a second threshold, it may be considered that many UEs wish to access the first application, or that the same UE wishes to access the first application multiple times. However, the first network has not instantiated an EAS capable of providing services to the first application, and therefore cannot find an EES in which an EAS capable of providing services to the first application is deployed. In this case, the management system or ASP may determine that an EAS capable of providing services to the first application needs to be instantiated in the first network.

[0137]

[0146] Optionally, if the ECS transmits the first information after detecting the first event multiple times, the first information may include the number of times the first event occurred. In this case, condition 2 may include the number of times an available EES is not found being equal to or greater than a third threshold. The third threshold may be the same as or different from the second threshold. This is not particularly limited in the present application.

[0138]

[0147] Condition 3: The load of the EAS is equal to or greater than the third threshold.

[0139]

[0148] If the EAS performance in the first information includes that the load of the EAS is equal to or greater than a third threshold, it may be determined that the EAS capable of providing service to the first application in the first network cannot meet the request of the UE. In this case, the ASP or management system determines that an EAS capable of providing service to the first application needs to be instantiated in the first network. The third threshold may be 50%, 85%, etc., of the bandwidth of the EAS. This is not particularly limited in the present application.

[0140]

[0149] Condition 4: EAS Breakdown

[0150] If the EAS performance in the first information includes an EAS breakdown, specifically, if the EAS is offline and unable to provide service, the ASP or management system determines that an EAS capable of providing service for the first application needs to be instantiated in the first network. Optionally, the EAS breakdown may be: all EASs in the network are broken down, or some EASs in the network are broken down. For example, the EAS breakdown may be: one EAS in the first network is broken down, or more than half of the EASs in the first network are broken down. This is not particularly limited in the present application.

[0141]

[0151] In one example, the management system can obtain application installation information from the ASP in advance, which allows an application to be instantiated. In other words, the management system can obtain authorization for the application to be instantiated. The application installation information can include information such as an application identifier and an application description file. When the management system obtains authorization for the application to be instantiated, the EES or ECS can send first information to the management system. When a first event satisfies a first condition, the management system can instantiate an EAS corresponding to the first application in the first network.

[0142]

[0152] In another example, if the management system does not obtain a list of applications that are allowed to be instantiated and application installation information, the EES or ECS can send first information to the ASP. If a first event satisfies a first condition, the ASP can send an EAS instantiation request to the management system, requesting the management system to instantiate an EAS in the first network that can provide services for the first application.

[0143]

[0153] Instantiating an EAS corresponding to the first application may include: allocating virtual machine resources, memory, CPU, bandwidth, etc. required by the application to the EAS, or deploying a server corresponding to the first application in the first network EDN. Note that the operation of instantiating an EAS is not particularly limited in this application.

[0144]

[0154] S304: The first network element sends the second information to the second network element.

[0145]

[0155] The second information may indicate that the EAS of the first application was successfully instantiated.

[0146]

[0156] In a possible implementation, the management system can send the second information to the EES or ECS. If the EES or ECS sends the first information to the management system, after the EAS is instantiated, the management system can send the second information to the EES or ECS.

[0147]

[0157] Alternatively, the management system may send the second information to the ASP, which may then send the second information to the EES or ECS. If the EES or ECS sends the first information to the ASP, after the EAS is instantiated, the management system may send the second information to the ASP, and the ASP may send the second information to the EES or ECS.

[0148]

[0158] Optionally, the EES can receive second information from the ASP or the management system and send information about the instantiated EAS corresponding to the first application to the EEC. Alternatively, since the EAS corresponding to the first application is deployed on the EES, the ECS can send the EES information to the EEC, and after receiving the EES information, the EEC can send an EAS discovery request to the EES, for example, in S107.

[0149]

[0159] Hereinafter, based on FIG. 4, a method for instantiating an EAS according to an embodiment of the present application will be described in detail.

[0150]

[0160] 4 is an exemplary flowchart of yet another method for instantiating an EAS according to an embodiment of the present application. The method may include the following operations.

[0151]

[0161] Optionally, S401:ASP transmits a list of applications that are allowed to be instantiated, application installation information, application performance requirements, etc. to the management system. Alternatively, the above information may be pre-configured in the management system. The management system can store application installation information that is allowed to be instantiated, application performance requirements, etc.

[0152]

[0162] S402: The EES or ECS detects an EAS exception event.

[0153]

[0163] The EES detects EAS exception events, which may include the following: the EES receives an EAS discovery request from the EEC, but the EES does not find an EAS that matches the conditions; or the EES receives a registration request from the EEC, but the EES does not find an EAS that matches the conditions. A condition match may be meeting the requirements of an application that the UE wishes to access. Alternatively, the EES may monitor performance changes of the EAS, for example, whether the EAS is overloaded or out of service.

[0154]

[0164] The ECS detects EAS exception events, which may include the following: the ECS receives an EES discovery request from the EES, but the ECS has not found a satisfying EES, or the ECS receives a service configuration request from the EES, but the ECS has not found a satisfying EES. A satisfying EES may be an EAS deployed in the EES that meets the requirements of the application that the UE wishes to access.

[0155]

[0165] S403: The EES or ECS transmits the first information to the management system or ASP and transmits the detected EAS exception event to the management system or ASP. Alternatively, the performance of the EAS may be carried in the first information and transmitted to the management system or ASP.

[0156]

[0166] When S401 is implemented, the EES or ECS can directly send the first information to the management system.

[0157]

[0167] In one example, when the EES or ECS detects an EAS exception event and reports the EAS exception event, the first information may not include the number of times the EAS exception event occurs, or the number of times the EAS exception event occurs may be 1 by default.

[0158]

[0168] In another example, if the EES or ECS reports an EAS exception event only when it detects multiple EAS exception events, the first information includes the number of times the EAS exception event occurred.

[0159]

[0169] S404: The ASP or management system determines whether to instantiate the EAS within the corresponding network according to local policies.

[0160]

[0170] For example, the ASP or management system can determine whether the EAS exception event or EAS performance satisfies the first condition. For details, please refer to the related description of the first condition. The details will not be described again here.

[0161]

[0171] Optionally, when the EES or ECS sends the first information to the ASP, the ASP can send an EAS instantiation request to the management system when it determines that an EAS exception event or EAS performance satisfies the first condition. The EAS instantiation request can include application information and network information and is used to determine a network on which the EAS of the application is to be deployed.

[0162]

[0172] S405: The management system instantiates an EAS within the EDN network.

[0163]

[0173] The management system can instantiate an EAS for the application indicated by the application information in the EDN network indicated by the network information based on the application information and the network information. The management system can allocate virtual machine resources, such as memory, CPU, and bandwidth, required by the application to the EAS. Note that the operation of instantiating the EAS is not particularly limited in this application.

[0164]

[0174] For example, the management system may first send a message to a management network element of the edge network, such as an MEC Platform management (MEPM), which may then interact with the EES or MEP to instantiate the EAS.

[0165]

[0175] S406: The management system sends second information to the EES or ECS to notify the EES or ECS that the EAS has been successfully instantiated.

[0166]

[0176] Optionally, the management system first notifies the ASP that the EAS has been successfully instantiated, and then the ASP notifies the EES or ECS that the EAS has been successfully instantiated. Note that the procedure for notifying the EES or ECS that the EAS has been successfully instantiated as shown in Figure 4 is merely an example.

[0167]

[0177] Optionally, step S407 may also be executed.

[0168]

[0178] S407: The EES may send information about the newly instantiated EAS to the EEC; or as a new EAS is deployed in the EES, the ECS may send the EES information to the EEC, and after receiving the EES information, the EEC may send an EAS discovery request to the EES.

[0169]

[0179] Based on the above solution, an EAS or ECS detection mechanism is defined to report events to the management system. Based on the reported events, the management system can dynamically decide whether to instantiate an EAS, and the management system will deploy the EAS as needed, which can greatly improve the efficiency of operation and maintenance management.

[0170]

[0180] Please refer to Figure 5. The present application provides another method for instantiating an EAS. Figure 5 is an exemplary flowchart of yet another method for instantiating an EAS according to an embodiment of the present application. The method may include the following operations:

[0171]

[0181] S501: A second network element detects a first event.

[0172]

[0182] The second network element may be an EES or an ECS. For the first event, please refer to the related description in the embodiment of the method shown in Figure 3. The details will not be described again here.

[0173]

[0183] S502: The second network element sends indication information to one or more terminals.

[0174]

[0184] One or more of the terminals may be EEC function modules within a terminal.

[0175]

[0185] The EES can send indication information to the EEC if an available EAS is not found or if the EAS is overloaded or has broken down.The ECS can send indication information to the EEC if an available EES is not found or if the EAS is overloaded or has broken down.

[0176]

[0186] The indication information may indicate that the EAS search has failed or that the EES search has failed, or may indicate that the EEC registration has failed, or the indication information may explicitly indicate that the first application that the UE wishes to access needs to dynamically instantiate an EAS, or the indication information may indicate that the performance of the EAS deployed in the current EDN cannot meet the performance requirements requested by the UE.

[0177]

[0187] S503: One or more terminals send first request information to a first network element.

[0178]

[0188] Optionally, the EEC may send instruction information to the AC. The first network element may be an ASP, a management system, or a user app LCM proxy (UEAPPLCM proxy). Such a UEAPPLCM proxy may be used by a user to request service entities such as application-related instantiation and termination.

[0179]

[0189] The first request information may include network information, application information, and a terminal identifier, which may be a subscription permanent identifier (SUPI), a generic public subscription identifier (GPSI), etc., and may be used to determine which UEs wish to access the first application.

[0180]

[0190] S504: The first network element determines, based on the first request information, whether to instantiate an EAS of the first application in the first network.

[0181]

[0191] The first network element may determine whether to instantiate an EAS for the first application in the first network based on a local policy or configuration. For example, if the number of UEs wishing to access the first application reaches a first threshold, the first network element may determine an EAS for instantiating the first application in the first network. The number of UEs may be determined by the number of terminal identifiers received by the first network element. If the number of terminal identifiers reaches the first threshold, the number of UEs wishing to access the first application may be considered to have reached the first threshold. For example, if the first network element determines that the second threshold has been reached based on the number of first requests, the first network element determines that the demand for accessing the first application is large and therefore determines an EAS for instantiating the first application in the first network. The first and second thresholds may be predetermined based on empirical values, such as 1 or 5. This is not particularly limited in the present application.

[0182]

[0192] Alternatively, if a subscription level of a terminal identified by the terminal identifier is equal to or greater than a specified level, an EAS that instantiates the first application in the first network may be determined. The first request information may include a subscription level of the terminal identified by the terminal identifier. Alternatively, the first network element may store a correspondence relationship between terminal identifiers and subscription levels, and the first network element may determine whether a subscription level corresponding to the terminal identifier included in the first request information is equal to or greater than a specified level in the stored correspondence relationship.

[0183]

[0193] In one example, the management system may obtain application installation information from the ASP in advance, which allows the application to be instantiated. In other words, the management system may obtain permission for the application to be instantiated. The application installation information may include information such as an application identifier and an application description file. If the management system obtains permission for the application to be instantiated, the terminal may send first request information to the management system. The management system may determine whether to instantiate the EAS of the first application in the first network based on the first request information. If the management system determines to instantiate the EAS of the first application in the first network, step S505 may be executed; otherwise, the management system executes step S507.

[0184]

[0194] In another example, if the management system does not obtain application installation information that allows the application to be instantiated, the terminal may send first request information to the ASP or UEAPPLCM proxy. The ASP or UEAPPLCM proxy may determine whether to instantiate an EAS for the first application in the first network based on the first request information. If the ASP or UEAPPLCM proxy determines to instantiate an EAS for the first application in the first network, the ASP or UEAPPLCM proxy may send second request information to the management system. The second request information may include application information and network information. The management system instantiates an EAS capable of providing a service to the first application in the first network, specifically, executes S505. If the ASP or UEAPPLCM proxy determines not to instantiate an EAS for the first application in the first network, the ASP or UEAPPLCM proxy executes S507.

[0185]

[0195] S505: The first network element instantiates an EAS capable of providing a service to the first application in the first network.

[0186]

[0196] For the operation of the first network element instantiating the EAS, please refer to the relevant description above, and the details will not be described again here.

[0187]

[0197] S506: The first network element sends the second information to one or more terminals.

[0188]

[0198] The second information indicates that the EAS has been successfully instantiated. Optionally, the management system, ASP, or UEAPPLCMA proxy can first notify the EEC that the EAS has been successfully instantiated, and then the EEC can notify the AC that the EAS has been successfully instantiated.

[0189]

[0199] In one example, when one or more terminals send first request information to the management system, the management system can send second information to the one or more terminals after instantiating the EAS.

[0190]

[0200] In another example, when one or more terminals send first request information to an ASP or UEAPPLCM proxy, after instantiating the EAS, the management system can send second information to the ASP or UEAPPLCM proxy, and the ASP or UEAPPLCM proxy can send the second information to one or more terminals.

[0191]

[0201] S507: The first network element sends the third information to one or more terminals.

[0192]

[0202] The third information may indicate that an EAS for the first application is not discovered in the first network.

[0193]

[0203] It should be noted that when one or more terminals send the first request information to the management system, the management system sends the third information to one or more terminals. When one or more terminals send the first request information to the ASP or UEAPPLCM proxy, the ASP or UEAPPLCM proxy sends the third information to one or more terminals.

[0194]

[0204] Based on the above solution, the management system can instantiate the EAS based on the requirements of the UE, so as to provide users with a differentiated service experience and improve the efficiency of operation and maintenance management.

[0195]

[0205] Hereinafter, a method for instantiating an EAS according to an embodiment of the present application will be described in detail with reference to FIGS. 6A and 6B.

[0196]

[0206] 6A and 6B are an exemplary flowchart of yet another method for instantiating an EAS according to an embodiment of the present application. The method may include the following operations.

[0197]

[0207] Optionally, the S600 is the same as the S401.

[0198]

[0208] S601: The EEC sends an EAS discovery request or registration request to the EES.

[0199]

[0209] The EAS discovery or registration request may include application information.

[0200]

[0210] Alternatively, the EEC sends a service configuration request to the ECS, and the service configuration request includes application information.

[0201]

[0211] S602 is the same as S402.

[0202]

[0212] S603: The EES or ECS transmits instruction information to the EEC.

[0203]

[0213] The indication information may indicate that an EAS needs to be instantiated. For details, please refer to the relevant description of the method embodiment shown in Figure 5. The details will not be described again here.

[0204]

[0214] Optionally, the EEC may perform the following operation S604.

[0205]

[0215] S604: The EEC sends instruction information to the AC.

[0206]

[0216] S605: The EEC sends an EAS instantiation request to the UEAPPLCM proxy / ASP / management system.

[0207]

[0217] The EAS instantiation request may include a network identifier or location identifier, application information, a UE identifier, etc. For details, please refer to the relevant descriptions of the method embodiments shown in Figures 3 to 5. The details will not be described again here.

[0208]

[0218] In one example, the AC first sends an EAS instantiation request to the EEC, and then the EEC can send the EAS instantiation request to the ASP or UEAPPLCM proxy. The ASP or UEAPPLCM proxy sends the EAS instantiation request to the management system. The EAS instantiation request may include network information and application information, and may not include a terminal identifier.

[0209]

[0219] In another example, the AC sends an EAS instantiation request to an ASP or user application LCM proxy.

[0210]

[0220] In yet another example, when operation S600 described above is performed, the AC / EEC can send an EAS instantiation request to the management system.

[0211]

[0221] S606: The UEAPPLCM proxy / ASP / management system performs validation and authorization for the EAS instantiation request.

[0212]

[0222] For example, whether the request is appropriate may be determined based on local policy or configuration. For details, please refer to the relevant description of the embodiment of the method shown in Figure 5. The details will not be described again here.

[0213]

[0223] Optionally, when the AC / EEC sends the EAS instance creation request to the ASP or UEAPPLCM proxy, the ASP or UEAPPLCM proxy can perform verification and authorization for the EAS instance creation request. After the verification is successful, the next operation S607 can be performed.

[0214]

[0224] S607: The UEAPPLCM proxy / ASP sends an EAS instance creation request carrying network information and application information to the management system.

[0215]

[0225] When the AC / EEC sends an EAS instantiation request to a management system, the management system can perform validation on the EAS instantiation request. The management system may include network elements such as an operation support system (OSS), an MEC orchestrator (MEO), and an MEPM.

[0216]

[0226] S608 is the same as S405.

[0217]

[0227] S609: The UEAPPLCM proxy / ASP / management system sends the second information to the AC / EEC to notify the AC / EEC that the EAS has been successfully instantiated.

[0218]

[0228] In one example, the management system may notify the UEAPPLCM proxy / ASP that the EAS has been successfully instantiated, and the UEAPPLCM proxy / ASP may then notify the EEC / AC that the EAS has been successfully instantiated.

[0219]

[0229] In another example, the EEC may be first notified that the EAS has been successfully instantiated, and then the EEC may notify the AC that the EAS has been successfully instantiated, or the AC may be first notified that the EAS has been successfully instantiated, and then the AC may notify the EEC that the EAS has been successfully instantiated.

[0220]

[0230] It should be noted that the procedure for notifying the AC / EEC that the EAS has been successfully instantiated, as shown in Figures 6A and 6B, is merely an example.

[0221]

[0231] Optionally, the following operation S610 may be performed.

[0222]

[0232] S610: The EEC may resend the request in S601.

[0223]

[0233] Based on the above solution, the UE sends a dynamic EAS instance creation request to the UE APPLCM proxy, ASP, or management system to provide users with differentiated service experiences. The management system then deploys the EAS as needed, which improves the efficiency of operation and maintenance management.

[0224]

[0234] 7 and 8 are schematic diagrams of possible communication device structures according to the embodiments of the present application, which are configured to implement the functions of the first network element, the second network element, or the terminal in the above method embodiments, and thus can also achieve the advantageous effects of the above method embodiments.

[0225]

[0235] As shown in Figure 7, the communication device 700 includes a processing unit 710 and a transceiver unit 720. The communication device 700 is configured to implement the functionality of a first network element, a second network element, or a terminal in the method embodiments shown in Figure 3 or Figure 5.

[0226]

[0236] 3 , the transceiver unit is configured to receive first information from the second network element, the first information including network information and application information, the network information indicating the first network and the application information indicating the first application, the first information further including information regarding a first event in the first network related to the first application, the first event including at least one of: an edge application server corresponding to the first application not being discovered in the first network, an edge enabler server corresponding to the first application not being discovered in the first network, and performance information of the edge application server corresponding to the first application in the first network. The processing unit is configured to determine to instantiate the first edge application server corresponding to the first application in the first network if the first event satisfies a first condition.

[0227]

[0237] When the communications device 700 is configured to implement the functionality of the first network element in the embodiment of the method shown in FIG. 5 , the transceiver unit is configured to receive first request information from one or more terminals, the first request information being used to request instantiation of an edge application server, the first request information including network information, application information, and a terminal identifier, the network information indicating the first network, the application information indicating the first application, and the terminal identifier identifying the terminal sending the first request information, and the processing unit is configured to determine, based on the first request information, whether to instantiate an edge application server corresponding to the first application in the first network.

[0228]

[0238] When the communications device 700 is configured to implement the functionality of the second network element in the embodiment of the method shown in FIG. 3 , the processing unit is configured to detect a first event, the first event including at least one of: an edge application server corresponding to the first application not being discovered in the first network; an edge enabler server corresponding to the first application not being discovered in the first network; and performance information of an edge application server corresponding to the first application in the first network; and the transceiver unit is configured to send first information to the first network element or send indication information to one or more terminals based on the detected first event, the first information including network information and application information, the indication information indicating that an edge application server needs to be instantiated, the network information indicating the first network, and the application information indicating the first application.

[0229]

[0239] When the communication device 700 is configured to implement the functionality of the terminal in the embodiment of the method shown in FIG. 5 , the transceiver unit is configured to receive indication information from an edge enabler server or an edge network configuration server, the indication information indicating that an edge application server has failed to be discovered, that an edge enabler client has failed to register, or that an edge application server needs to be instantiated. The processing unit is configured to generate request information based on the indication information. The request information includes network information, application information, and a terminal identifier, where the network information indicates a first network, the application information indicates a first application, and the terminal identifier identifies the terminal sending the request information. The transceiver unit is further configured to transmit the request information to the first network element.

[0230]

[0240] For a more detailed description of the processing unit 710 and the transceiver unit 720, please directly refer to the relevant description in the method embodiment shown in Figure 3 or Figure 4. The details will not be described again here.

[0231]

[0241] 8, the communication device 800 includes a processor 810 and an interface circuit 820. The processor 810 and the interface circuit 820 are connected to each other. It can be understood that the interface circuit 820 may be a transceiver or an input / output interface. Optionally, the communication device 800 may further include a memory 830, which is configured to store instructions to be executed by the processor 810, to store input data required for executing the instructions by the processor 810, or to store data generated after the processor 810 executes the instructions.

[0232]

[0242] When the communication device 800 is configured to perform the method shown in FIG. 3 or FIG. 5, the processor 810 is configured to implement the functions of the processing unit 710, and the interface circuit 820 is configured to implement the functions of the transceiver unit 720.

[0233]

[0243] If the communication device is a chip used in a terminal, the chip in the terminal realizes the functions of the terminal in the above-mentioned method embodiments. The terminal chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal, and the information is sent to the terminal by the first network element, or the terminal chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal, and the information is sent by the terminal to the first network element.

[0234]

[0244] If the communication device is a module applied to a first network element, the first network element module realizes the functions of the first network element in the aforementioned method embodiments. The first network element module receives information from another module (such as a radio frequency module or an antenna) in the first network element, and the information is transmitted to the first network element by the terminal or the second network element, or the first network element module transmits information to another module (such as a radio frequency module or an antenna) in the first network element, and the information is transmitted to the terminal or the second network element by the first network element.

[0235]

[0245] If the communication device is a module applied to a second network element, the second network element module realizes the functions of the second network element in the above-mentioned method embodiments. The second network element module receives information from another module (such as a radio frequency module or an antenna) in the second network element, and the information is transmitted to the second network element by the first network element, or the first network element module transmits information to another module (such as a radio frequency module or an antenna) in the first network element, and the information is transmitted to the first network element by the second network element.

[0236]

[0246] It can be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), or may be another general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0237]

[0247] The method steps in the embodiments of the present application may be implemented in hardware or by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. For example, the storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium. Of course, the storage medium may be a component of the processor. The processor and the storage medium may be disposed within an ASIC. Furthermore, the ASIC may be located within the first network element, the second network element, or the terminal. Of course, the processor and the storage medium may exist as separate components within the first network element, the second network element, or the terminal.

[0238]

[0248] All or part of the above-described embodiments may be realized using software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be embodied in the form of a computer program product. A computer program product includes one or more computer programs and instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the procedures or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired or wireless transmission. The computer-readable storage medium may be any available medium accessible by a computer or data storage device, such as a server or data center that integrates one or more available media. The available media may be magnetic media, such as floppy disks, hard disks, or magnetic tape; optical media, such as digital video disks; or semiconductor media, such as solid-state disks. The computer-readable storage medium may be volatile or nonvolatile; or may include both volatile and nonvolatile storage media.

[0239]

[0249] In the embodiments of the present application, unless otherwise stated or there is no logical contradiction, the terms and / or descriptions among different embodiments are consistent and may be cross-referenced, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

[0240]

[0250] In this application, "at least one" means one or more, and "plurality" means two or more. "And / or" is a conjunctive relationship used to describe related objects, indicating that three relationships may exist. For example, A and / or B may indicate the following: only A is present, both A and B are present, or only B is present, where A and B may be in the singular or plural. In text descriptions in this application, the character " / " generally indicates an "or" relationship between related objects. In mathematical formulas in this application, the character " / " indicates a "division" relationship between related objects. "Comprising at least one of A, B, and C" may express: including A; including B; including C; including A and B; including A and C; including B and C; and including A, B, and C.

[0241]

[0251] It will be understood that various numbers in the embodiments of the present application are merely used for distinction to facilitate description, and are not used to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not imply the order of execution, and the execution sequence of the processes should be determined based on the functions and internal logic of the processes.

Claims

1. 1. A method of instantiating an edge application server, comprising: receiving, by a first network element, first information from a second network element, the first information including network information and application information, the network information indicating a first network, the application information indicating a first application, the first information further including a number of times a first event has occurred, the first event being that an edge application server corresponding to the first application has not been discovered in the first network; and determining, by the first network element, to instantiate a first edge application server corresponding to the first application in the first network if the first event satisfies a first condition; A method comprising:

2. 2. The method of claim 1, wherein the first condition is that the number of times the first event has occurred is greater than or equal to a first value.

3. 10. The method of claim 1, wherein the first network element is an application service provider, the method comprising: the first network element sending an edge application server instantiation request to a management system, the edge application server instantiation request being used to instantiate the first edge application server, the edge application server instantiation request including the network information and the application information.

4. 10. The method of claim 1, further comprising: the first network element sending a subscription request to a second network element; wherein the subscription request is used to avoid missing the first information.

5. The method of claim 1 , wherein the network information is a location identifier.

6. 10. The method of claim 1, wherein the network information includes at least one of a network identifier, an edge enabler server identifier, or an edge configuration server identifier.

7. 10. The method of claim 1, further comprising: the second network element transmitting the first information to the first network element; A method comprising:

8. 8. The method of claim 7, further comprising: the second network element detecting the first event; A method comprising:

9. 4. The method of claim 3, further comprising: the management system receiving the edge application server instantiation request from the first network element; and instantiating the first edge application server; A method comprising:

10. 1. A method of instantiating an edge application server, comprising: detecting a first event by a second network element, the first event being that an edge application server corresponding to a first application has not been discovered in the first network; and transmitting, by the second network element, first information to the first network element based on the detected first event, the first information including network information and application information, the network information indicating a first network, the application information indicating a first application, and the first information further including a number of times the first event has occurred; A method comprising:

11. 11. The method of claim 10, wherein the first information is for determining to instantiate a first edge application server corresponding to the first application in the first network.

12. 11. The method of claim 10, further comprising: receiving, by the second network element, a subscription request from the first network element; wherein the subscription request is used to avoid missing the first information.

13. A communication device configured to perform the method according to any one of claims 1-6 or configured to perform the method according to any one of claims 10-12.

14. A computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions; the computer-executable instructions, when executed by a computer, causing the computer to: A method according to any one of claims 1 to 6, or A storage medium enabling the method according to any one of claims 10-12 to be carried out.

15. a first network element configured to perform the method according to any one of claims 1 to 6; a second network element configured to perform the method of any one of claims 10-12; and a management system configured to receive an edge application server instantiation request from the first network element and instantiate a first edge application server corresponding to a first application in the first network; A communication system including at least two of the devices.

Images