WO2023280118A1 - 一种实例化边缘应用服务器的方法和装置 - Google Patents

一种实例化边缘应用服务器的方法和装置 Download PDF

Info

Publication number
WO2023280118A1
WO2023280118A1 PCT/CN2022/103709 CN2022103709W WO2023280118A1 WO 2023280118 A1 WO2023280118 A1 WO 2023280118A1 CN 2022103709 W CN2022103709 W CN 2022103709W WO 2023280118 A1 WO2023280118 A1 WO 2023280118A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
information
network
edge
network element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/103709
Other languages
English (en)
French (fr)
Inventor
姚琦
李世涛
宗在峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP22836869.2A priority Critical patent/EP4354815B1/en
Priority to CN202280045495.2A priority patent/CN117561703A/zh
Priority to JP2024500144A priority patent/JP7744060B2/ja
Publication of WO2023280118A1 publication Critical patent/WO2023280118A1/zh
Priority to US18/405,034 priority patent/US20240235929A9/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level

Definitions

  • the present application relates to the technical field of communications, and in particular to a method and device for instantiating an edge application server.
  • the edge data network can be a local data center.
  • the EDN includes an edge enabler server (EES) and multiple edge application servers (EAS).
  • EES edge enabler server
  • EAS edge application servers
  • Each EDN has a specific service scope.
  • EES can be the control network element or management network element in the mobile edge computing (mobile edge computing, MEC) node, responsible for managing each EAS deployed in the EDN, such as registration and domain name server (domain name system, DNS) resolution Wait.
  • MEC mobile edge computing
  • DNS domain name system
  • EES can invoke the capability exposure function of the network.
  • a user equipment may include an edge enabler client (edge enabler client, EEC) and an application client (application client, AC).
  • EEC edge enabler client
  • application client application client
  • the EEC provides necessary support for the application client on the UE, and the UE can register with the EES through the EDGE-1 interface.
  • the EES when the UE registers with the EES, the EES can detect whether the deployed EAS meets the application information accessed by the UE. When the EES detects that the deployed EAS does not satisfy the application information accessed by the UE or when the EES finds that there is no instantiated EAS in the current EDN, how to satisfy the UE's access request has not yet been defined.
  • Embodiments of the present application provide a method and device for instantiating an edge application server, which are used to dynamically instantiate the edge application server.
  • a method for instantiating an edge application server may be executed by the first network element, or by a chip similar to the first network element.
  • the first network element may be an application service provider or a management system.
  • the first network element may receive the first information from the second network element.
  • the first information may include network information and application information, the network information may be used to indicate the first network, and the application information may be used to indicate the first application.
  • the first information may also include information about a first event of the first application in the first network.
  • the first event may include not finding an edge application server corresponding to the first application in the first network, not finding an edge enabling server corresponding to the first application in the first network and not finding a corresponding first application in the first network At least one of the performance information of the edge application server.
  • the first network element may determine to instantiate the first edge application server corresponding to the first application in the first network when the first event satisfies the first condition.
  • the first network element can determine, according to the first event reported by the second network element, that when the first event meets the first condition, it dynamically instantiates the edge application server of the first application, which can improve the efficiency of operation and maintenance management.
  • no edge application server corresponding to the first application is found in the first network, including: no edge application server corresponding to the first application is deployed or instantiated in the first network;
  • no edge application server corresponding to the first application is found in the first network, including: no edge application corresponding to the first application that meets the terminal requirements (UE required) is found in the first network server. That is, although the edge application server corresponding to the first application is deployed or instantiated in the first network, the performance of the edge application server of the first application cannot meet the requirements of the terminal.
  • the first condition when the first event includes not finding an edge application server corresponding to the first application in the first network, the first condition may include not finding a corresponding edge application server in the first network within the first duration. The number of times of the edge application server of the first application is greater than or equal to the first threshold.
  • the first condition may include not finding an edge-enabled server corresponding to the first application in the first network within the second duration The number of times is greater than or equal to the second threshold.
  • the first condition when 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 of the edge application server being greater than or equal to a third threshold and an edge application server being down.
  • the edge application server of the first application can be instantiated, which can improve user experience.
  • the first network element may send a request to the management system to instantiate an edge application server, where the instantiation edge application server request is used to instantiate the edge application server, and the instantiation edge application server request includes network information and application information.
  • the first information may further include the number of occurrences of the first event.
  • the second network element can report to the first network element when multiple first events are detected, which can improve the utilization rate of transmission resources.
  • the number of times the edge-enabled server corresponding to the first application is not found in the first network may be the number of times the first network element receives the first event.
  • the number of times the edge-enabled server corresponding to the first application is not found in the first network may be the number of times the first network element receives the first event.
  • the second network element can report the first event to the first network element multiple times, and can report the first event to the first network element in time when the terminal wants to access the first application but the edge application server of the first application is not deployed in the network. Report terminal requirements to improve user experience.
  • the first network element when the first network element is the management system, before the first network element instantiates the first edge application server corresponding to the first application in the first network, the first network element may start the application service
  • the provider gets the application installation information that allows instantiation.
  • the management system After the management system obtains the application installation information that allows instantiation, it can directly communicate with the second network element, reducing complexity.
  • the first network element may send second information to the second network element, and the second information may be used to indicate that the instantiation of the first edge application server is successful.
  • the first network element may subscribe to the first information.
  • the first network element receives the first information of the second network element by subscribing to the first information, which can improve the success rate of the first network element receiving the first information.
  • a method for instantiating an edge application server may be executed by the second network element, or by a chip that functions similarly to the second network element.
  • the second network element may be an edge enabling server or an edge network configuration server.
  • the second network element may detect the first event.
  • the first event may include not finding an edge application server corresponding to the first application in the first network, not finding an edge enabling server corresponding to the first application in the first network, and not finding an edge enabling server corresponding to the first application in the first network.
  • the second network element may send the first information to the first network element or send indication information to one or more terminals according to the detected first event.
  • the first information may include network information and application information, and the indication information may be used to indicate that an edge application server needs to be instantiated.
  • the network information may be used to indicate the first network, and the application information may be used to indicate the first application.
  • the edge enabling server corresponding to the first application is not found in the first network, including: the edge application server corresponding to the first application is not deployed or instantiated in the first network, or, the first An edge application server corresponding to the first application that meets terminal requirements (UE required) is not found in the network, and the edge configuration server determines that an edge enabling server corresponding to the first application is not found in the first network.
  • the indication information is used to indicate that no edge application server or edge enablement server corresponding to the first application has been found in the first network, or used to indicate a registration failure, and the name of the indication information is not Do limited.
  • the second network element can report the first event about the first application detected in the first network to the first network element, so as to realize whether the first network element instantiates the edge application server in the first network judgment.
  • the second network element may receive second information, the second information may be used to indicate that the instantiation of the first edge application server is successful, and the first information may be used to determine the instantiation of the first edge application server .
  • the first network element can determine, according to the first event reported by the second network element, that when the first event meets the first condition, it dynamically instantiates the edge application server of the first application, which can improve the efficiency of operation and maintenance management.
  • the first information may further include the number of occurrences of the first event.
  • the indication information may be used to indicate that the edge application server search fails or the edge-enabled client fails to register.
  • the second network element may indicate to one or more terminals whether to dynamically instantiate the edge application server through indication information.
  • a method for instantiating an edge application server may be executed by the first network element, or executed by a chip similar to the function of the first network element.
  • the first network element may be an application service provider or a management system.
  • 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 terminal identification.
  • the network information may be used to indicate the first network
  • the application information may be used to indicate the first application
  • the terminal identifier may be used to identify the terminal sending the first request information.
  • the first network element may determine whether to instantiate the edge application server corresponding to the first application in the first network according to the first request information.
  • the terminal sends the first request information to the first network element to request the edge application server of the first application to be instantiated in the first network, which can provide differentiated service experience for the terminal and improve the efficiency of operation and maintenance management.
  • the number of one or more terminals when the number of one or more terminals reaches a first threshold, it may be determined to instantiate an edge application server corresponding to the first application in the first network. And/or, when the subscription level of the terminal identified by the terminal identifier is higher than or equal to the specified level, it may be determined to instantiate the edge application server corresponding to the first application in the first network.
  • the edge application server of the first application can be instantiated, which can provide differentiated service experience for the terminal and improve Efficiency of operation and maintenance management.
  • the first network element may send the second request information to the management system.
  • the second request information may be used to request instantiation of the edge application server, and the second request information may include network information and application information.
  • the network information may include at least one of a network identifier and a location identifier.
  • the network identifier and the location identifier may be used to identify the first network
  • the application information includes at least one of an applicable identifier and an application performance requirement.
  • the first network element determines that before instantiating the edge application server corresponding to the first application in the first network, the first network element can provide The provider obtains the application installation information that allows instantiation.
  • the management system After the management system obtains the application installation information that allows instantiation, it can directly communicate with the terminal, reducing complexity.
  • the first network element may send second information to the second network element or one or more terminals, and the second information may be used to indicate that the edge application server corresponding to the first application is instantiated successfully.
  • third information may be sent to one or more terminals.
  • the third information may be used to indicate that no edge application server of the first application has been found in the first network.
  • the third information may be sent to one or more terminals.
  • the third information may be used to indicate that no edge application server of the first application has been found in the first network.
  • the first network element can send the third information to the terminal, that is, the edge application server of the first application is not instantiated in the first network, which can save resources in the EDN network.
  • a method for instantiating an edge application server is provided.
  • the method can be executed by a terminal, or by a chip that functions similarly to the terminal.
  • the edge-enabled client may receive indication information from the edge-enabled server or the edge network configuration server.
  • the indication information may be used to indicate that the search for the edge application server fails or the registration of the edge-enabled client fails, or the edge application server needs to be instantiated.
  • the edge-enabled client may send request information to the first network element according to the instruction information, and the request information may include network information and application information.
  • the network information may be used to indicate the first network
  • the application information may be used to indicate the first application.
  • the terminal sends the first request information to the first network element to request the edge application server of the first application to be instantiated in the first network, which can provide differentiated service experience for the terminal and improve the efficiency of operation and maintenance management.
  • the edge-enabled client may send indication information to the application client.
  • the edge-enabled client may receive request information from the application client.
  • the edge-enabled client may receive second information from the first network element, and the second information may be used to indicate that the edge application server corresponding to the first application is instantiated successfully.
  • a communication device may include various modules/units for implementing the first aspect or any possible implementation manner of the first aspect. Such as transceiver unit and processing unit.
  • the transceiver unit is used to receive the first information from the second network element, the first information includes network information and application information, the network information is used to indicate the first network, the application information is used to indicate the first application, and the first information also includes Information about the first event of the first application in the first network; the first event includes not finding an edge application server corresponding to the first application in the first network, and not finding an edge application server corresponding to the first application in the first network At least one of the edge-enabled server and the performance information of the edge application server corresponding to the first application in the first network.
  • a processing unit configured to instantiate a first edge application server corresponding to the first application in the first network when the first event satisfies the first condition.
  • the first condition when the first event includes not finding an edge application server corresponding to the first application in the first network, the first condition includes not finding an edge application server corresponding to the first application in the first network within the first duration.
  • the number of edge application servers is greater than or equal to the first threshold; when the first event includes not finding an edge-enabled server corresponding to the first application in the first network, the first condition includes not finding an edge-enabled server in the first network within the second duration.
  • the number of times the edge-enabled server corresponding to the first application is found is greater than or equal to the second threshold; when the first event includes performance information of the edge application server corresponding to the first application in the first network, the first condition includes the edge application server
  • the load is greater than or equal to at least one of the third threshold and the edge application server is down.
  • the transceiver unit is further configured to send a request to the management system for instantiating the edge application server.
  • the request for instantiating the edge application server is used for instantiating the edge application server.
  • the request for instantiating the edge application server includes network information and application information.
  • the first information further includes the number of occurrences of the first event.
  • the number of times the edge-enabled server corresponding to the first application is not found in the first network is the number of times the first network element receives the first event; or, the number of times the edge-enabled server corresponding to the first application is not found in the first network
  • the number of times the edge-enabled server of the application is the number of times the first network element receives the first event.
  • the processing unit is further configured to: acquire application installation information allowing instantiation from an application service provider.
  • the transceiving unit is further configured to: send second information to the second network element, where the second information is used to indicate that the instantiation of the first edge application server is successful.
  • the transceiver unit is further configured to: send a subscription request to the second network element, where the subscription request is used to subscribe to the first information.
  • a communication device may include various modules/units for implementing the second aspect or any possible implementation manner of the second aspect. Such as transceiver unit and processing unit.
  • the processing unit is used to detect a first event; the first event includes not finding an edge application server corresponding to the first application in the first network, not finding an edge enabling server corresponding to the first application in the first network, and At least one of the performance information of the edge application server corresponding to the first application in the first network; a transceiver unit configured to send the first information to the first network element or send the first information to one or more terminals according to the detected first event Indication information: the first information includes network information and application information, the indication information is used to indicate that the edge application server needs to be instantiated; the network information is used to indicate the first network, and the application information is used to indicate the first application.
  • the transceiving unit is further configured to receive second information, the second information is used to indicate that the instantiation of the first edge application server is successful, and the first information is used to determine the instantiation of the first edge application server.
  • the first information further includes the number of occurrences of the first event.
  • the indication information is used to indicate that the edge application server search fails or the edge-enabled client fails to register.
  • a communication device in a seventh aspect, may include various modules/units for implementing the third aspect or any possible implementation manner of the third aspect. Such as transceiver unit and processing unit.
  • the transceiver unit is used to receive the first request information from one or more terminals, the first request information is used to request instantiation of the edge application server; the first request information includes network information, application information and terminal identification; the network information is used For indicating the first network, the application information is used to indicate the first application, and the terminal identifier is used to identify the terminal sending the first request information; the processing unit is used to determine whether to instantiate the first application in the first network according to the first request information Corresponding edge application server.
  • the processing unit determines whether to instantiate the edge application server corresponding to the first application in the first network according to the first request information, it is specifically configured to: when the number of one or more terminals reaches a first threshold , determine to instantiate the edge application server corresponding to the first application in the first network; and/or, when the subscription level of the terminal identified by the terminal identifier is higher than or equal to the specified level, determine to instantiate the first application server in the first network The edge application server corresponding to the application.
  • the transceiver unit is further configured to send second request information to the management system; wherein the second request information is used to request instantiation of the edge application server, and the second request information includes network information and application information.
  • the network information includes at least one of a network identifier and a location identifier; the network identifier and the location identifier are used to identify the first network, and the application information includes at least one of an application identifier and an application performance requirement.
  • the processing unit is further configured to obtain application installation information allowing instantiation from an application service provider.
  • the transceiving unit is further configured to send second information to the second network element or one or more terminals, and the second information is used to indicate that the first application provides a corresponding edge application server instantiation success.
  • the transceiver unit is further configured to: when the number of one or more terminals does not reach the first threshold, send third information to one or more terminals; the third information is used to indicate that there is no Finding the edge application server of the first application; and/or, when the subscription level of the terminal identified by the terminal identifier is lower than the specified level, sending third information to one or more terminals; the third information is used to indicate that the terminal in the first The edge application server of the first application is not found in the network.
  • a communication device may include various modules/units for implementing the fourth aspect or any possible implementation manner of the fourth aspect. Such as transceiver unit and processing unit.
  • the transceiving unit is used for receiving indication information from the edge enabling server or the edge network configuration server, and the indication information is used to indicate that the edge application server search fails or the edge enabling client fails to register or the edge application server needs to be instantiated.
  • a processing unit configured to generate request information according to the indication information.
  • the request information includes network information, application information and terminal identification; the network information is used to indicate the first network, the application information is used to indicate the first application, and the terminal identification is used to identify the terminal sending the request information.
  • the transceiver unit is further configured to send request information to the first network element.
  • the transceiver unit is further configured to: send indication information to the application client; and receive request information from the application client.
  • the transceiver unit is further configured to receive second information from the first network element, where the second information is used to indicate that the edge application server corresponding to the first application is instantiated successfully.
  • a communication device including a processor and a memory.
  • the memory is used to store computer programs or instructions
  • the processor executes the computer programs or instructions in the memory to realize the first aspect or any possible implementation of the first aspect, or realize the second aspect or any possible implementation of the second aspect.
  • the memory can be located inside the device, or it can also be located outside the device and connected to the device.
  • the memory can be integrated with the processor.
  • the communication device may further include a transceiver.
  • the transceiver performs the transceiving operation of the method in the first aspect or any possible implementation manner of the first aspect, or performs the transceiving operation of the method in the second aspect or any possible implementation manner of the second aspect, or executes the third aspect or the first aspect
  • a chip in a tenth aspect, includes a logic circuit and a communication interface.
  • the communication interface is used to input first information
  • the first information includes network information and application information
  • the network information is used to indicate the first network
  • the application information is used to indicate the first application
  • the first information also includes Information about the first event of the first application;
  • the first event includes not finding an edge application server corresponding to the first application in the first network, not finding an edge enabling server corresponding to the first application in the first network and at least one of the performance information of the edge application server corresponding to the first application in the first network.
  • a logic circuit configured to instantiate a first edge application server corresponding to the first application in the first network when the first event satisfies the first condition.
  • the logic circuit is used to detect a first event; the first event includes not finding an edge application server corresponding to the first application in the first network, not finding an edge enabling server corresponding to the first application in the first network At least one of the server and the performance information of the edge application server corresponding to the first application in the first network.
  • the communication interface is used to output first information or indication information; the first information includes network information and application information, and the indication information is used to indicate that an edge application server needs to be instantiated; the network information is used to indicate the first network, and the application information is used to indicate the second one application.
  • the user of the communication interface inputs first request information, and the first request information is used to request instantiation of the edge application server; the first request information includes network information, application information and terminal identification; the network information is used to indicate the first network, The application information is used to indicate the first application, and the terminal identifier is used to identify the terminal sending the first request information.
  • a logic circuit configured to determine whether to instantiate an edge application server corresponding to the first application in the first network according to the first request information.
  • the communication interface is used to input instruction information, and the instruction information is used to indicate that the edge application server search fails or the edge-enabled client fails to register or the edge application server needs to be instantiated.
  • the logic circuit is used for generating request information according to the indication information.
  • the request information includes network information, application information and terminal identification; the network information is used to indicate the first network, the application information is used to indicate the first application, and the terminal identification is used to identify the terminal sending the request information.
  • the communication interface is also used to output request information.
  • the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, it causes the computer to execute the methods in the above aspects.
  • the present application provides a computer program product storing instructions, which, when run on a computer, causes the computer to execute the methods in the above aspects.
  • the present application provides a communication system, including at least one first network element and at least one second network element above, or at least one first network element above and at least one terminal above.
  • beneficial effects of the fifth aspect to the thirteenth aspect can refer to the beneficial effects shown in the first aspect to the fourth aspect.
  • Figure 1 is an exemplary flowchart of EEC registration
  • Fig. 2 is the network architecture provided by the embodiment of the present application.
  • FIG. 3 is one of the exemplary flow charts of the method for instantiating EAS provided by the embodiment of the present application.
  • FIG. 4 is one of the exemplary flow charts of the method for instantiating EAS provided by the embodiment of the present application.
  • FIG. 5 is one of the exemplary flowcharts of the method for instantiating an EAS provided in the embodiment of the present application
  • FIG. 6 is one of the exemplary flow charts of the method for instantiating an EAS provided in the embodiment of the present application.
  • FIG. 7 is a structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 8 is a block diagram of a communication device provided by an embodiment of the present application.
  • the EAS of the first application may refer to the EAS that can provide services for the first application, and can also be called the EAS corresponding to the first application, the EAS corresponding to the first application, or the EAS that can provide services for the first application or EAS, etc. that provide services for the first application.
  • EDN includes EES and multiple EAS, and each EDN has a specific service scope.
  • the EES may be a control network element or a management network element in the MEC node.
  • EES European Telecommunications Standard Institute
  • MEC nodes include MEC platform (MEC platform, MEP) and MEC application (application). Among them, EES and MEC have similar functions, and EAS and MEC application have similar functions.
  • the edge configuration server can be a global management network element, maintaining the information of each EDN, including service scope and EES address, etc. It should be noted that in some standard protocols, such as technical specification (TS) 23.501 and TS23.502, etc., the aforementioned EES, EAS, ECS, and MEP can be called application function network elements (application function, AF).
  • EES application function network elements
  • FIG. 1 it is a flow chart of EEC registration to EES, which may include the following operations.
  • S101 The EEC sends a service provisioning request (service provisioning request) to the ECS.
  • the above service configuration request may include application information that the UE wants to access, such as application identification and/or application performance requirements.
  • the ECS can search for the EES that meets the application that the UE wants to access. For example, the ECS can find out which EDN deploys the corresponding EAS according to the application identifier. If the ECS finds the above-mentioned EDN, it may send the information of the found EES in the above-mentioned EDN to the EEC.
  • the registration request may carry the EEC identifier, the security certificate and the application information that the UE wants to access, such as the application identifier and application performance requirements, and the EEC context identifier.
  • S104 The EES verifies whether the registration request of the EEC is legal.
  • EES can verify whether the EEC logo is consistent with the security certificate. If they are consistent, the registration request can be considered legal, and if they are inconsistent, the registration request can be considered illegal.
  • the EES can also determine whether the deployed EAS meets the access requirements of the UE, for example, the EES can determine whether the EAS of the application requested by the UE is deployed. Alternatively, the EES may determine whether the deployed EAS meets the requirements of the UE, for example, may determine whether the bandwidth and delay of the deployed EAS meet the requirements of the UE.
  • the EES obtains the EEC context according to the EEC context identifier.
  • the EES can determine the EES registered by the UE according to the EEC context identifier, and obtain the EEC context from the EES registered by the UE.
  • S106 The EES sends a response message to the EEC, notifying the EEC whether the registration is successful.
  • the EAS discovery request may include application information.
  • the EES can search for an EAS that satisfies the application that the UE wants to access according to the application information, and if the EES is found, it can send the found EAS information to the EEC.
  • the EES detects that the deployed EAS does not meet the application information that the UE wants to access, or after the EEC sends a registration request to the EES in S103, and the EES finds that no EAS has been instantiated in the current EDN, or in S107, the EEC sends a registration request to the EES.
  • the EES may dynamically trigger an EAS to satisfy the EEC's request. But how to instantiate EAS dynamically is not yet defined.
  • the embodiment of this application provides a method for instantiating an EAS.
  • the EAS when the deployed EAS does not meet the application information that the UE wants to access or the EAS has not been instantiated in the current EDN, the EAS can be instantiated to meet the request of the EEC.
  • FIG. 2 shows a communication system to which the technical solution provided by the embodiment of the present application is applicable, and shows an edge application server and an edge-enabled server on the edge data network side, and an application client and an edge-enabled client on the terminal device side. end.
  • the EDN corresponds to a data network deployed at the edge, which may be a local data network (local DN) or a local area data network (local area data network, LADN).
  • the edge data network includes edge enabling functions, which can be identified by a data network access identifier (DNAI) and a data network name (DNN) or by using a data network name and a data network service area (service area) ) logo. Or it can be understood that the edge data network can be regarded as a data center deployed locally relative to the central cloud.
  • DNAI can be used to identify edge data networks, and an edge data network can contain multiple local data networks (local DN).
  • EAS the server application program deployed in the edge data network
  • applications such as social media software, augmented reality (augmented reality, AR), and virtual reality (virtual reality, VR) are deployed and run on application instances (instances) on the EDN.
  • one application can deploy one or more EASs in one or more EDNs, and EASs deployed and running in different EDNs can be regarded as different EASs of one application.
  • Different EASs of an application can share a domain name; different EASs of an application can use one anycast IP address, or use different IP addresses.
  • the edge application server EAS can also include the application context of the application corresponding to the EAS.
  • the application context can also include the context of one or more application users using the application on the EAS, for example, an application context using the application or multiple application user-related running status information, and the transaction identifier of the subscription of the EAS to the one or multiple application users.
  • the application context may also include the subscription context between the EAS and the core network of one or more application users using the application, such as a subscribed transaction ID.
  • EES is deployed in EDN, and can provide edge computing enabling services for application instances deployed in EDN, that is, the aforementioned EAS, to better support the deployment and operation of applications in MEC.
  • EES can support EAS registration, authentication and authentication of terminal equipment (user equipment, UE) or authentication and authorization of edge-enabled clients, and provide UE with application instance information including IP address information, etc.
  • an EAS can be registered to an EES, or the information of an EAS can be configured on an EES through the management system, then the EES is called the EES associated with the EAS, and the EES can control (manage) the registration or It is the EAS configured on this EES or the service EES of this EAS.
  • EES also supports the acquisition of application instance information including application instance identifiers and application instance address information (such as IP address information), and further sends application instance information such as application instance identifiers to the edge data network configuration server (edge configuration server , ECS).
  • the ECS is responsible for the configuration of the EDN, such as providing EES information to the UE, providing EAS information to the UE, and interacting with the DNS of the application to obtain EAS information, etc. Further, the information of the application instance and the IP address may be obtained and stored from other functional entities.
  • the MEC architecture model shown in FIG. 2 also shows the aforementioned ECS.
  • AC is the client program applied on the terminal device side, and is the peer entity of EAS on the terminal device side.
  • the application client is used for the application user (user) to obtain application services from the application server.
  • the application client can connect to the application server on the cloud to obtain application services, and can also connect to the EAS where the application is deployed and runs in one or more EDNs to obtain application services.
  • EEC is the peer entity of EES on the terminal device side.
  • EEC is used to register EEC information and application client AC information with EES, perform security authentication and authentication, and obtain EAS information from EES, including EAS address information (such as IP address) and provide edge computing enabling capabilities to application clients, for example, the EEC discovery service can return the IP address of EAS to application clients.
  • EES address information such as IP address
  • a communication connection is established between the application client AC on the terminal device side and the edge application server EAS; a communication connection is established between the edge-enabled client EEC on the terminal device side and the edge-enabled server EES.
  • the application user signs a service agreement with the application provider, and can log in to the application client AC deployed on the terminal device to use the application, and exchange application data (application data) through the communication connection between the application client AC and the EAS;
  • the application client AC acquires the services provided by the edge-enabling server EES from the edge-enabling client EEC in the form of an application programming interface (application program interface, API).
  • FIG. 3 it is an exemplary flowchart of a method for instantiating an EAS provided by an embodiment of the present application, which may include the following operations.
  • S301 The second network element detects the first event.
  • the second network element may be an EES or an ECS.
  • the ECS may be a centrally deployed network element, and may not necessarily be deployed in the EDN network. This embodiment of the present application does not specifically limit the location of the ECS deployment.
  • the first event may include at least one of the following:
  • the EES may determine whether the deployed EAS meets the first application that the UE wants to access. When the EES determines that there is no EAS of the first application that the UE wants to access in the deployed EAS, it may be considered that no available EAS corresponding to the first application has been found in the first network. In S107, the EES may search for an EAS that satisfies the first application that the UE wants to access according to the application information, and if not found, it may be considered that no available EAS corresponding to the first application has been found in the first network. For the convenience of description, this application may describe it as no available EAS found, which will not be repeated below.
  • the delay and bandwidth of the EAS do not satisfy the first application that the UE wants to access, it may also be considered that no available EAS corresponding to the first application has been found in the first network.
  • the first application that the UE wants to access has a higher latency requirement, but the EAS deployed in the first network corresponding to the first application has a lower latency requirement, and the service processing delay is relatively large, then the first application can be considered as The EAS in the network does not satisfy the first application that the UE wants to access.
  • the ECS may search for an EDN or an EES deployed with an EAS that satisfies the first application that the UE wants to access. If the ECS does not find the above-mentioned EDN or EES, it can be considered that no available EES corresponding to the first application has been found, or the ECS can consider that no available EAS corresponding to the first application has been found, which may be described in this application for the convenience of description Since no available EES was found, details will not be described below.
  • EES or ECS can determine the EAS performance corresponding to the first application in the first network, such as EAS load (including one or more of memory, CPU, bandwidth, number of connections, delay, etc.) and whether it is online or not.
  • EAS load including one or more of memory, CPU, bandwidth, number of connections, delay, etc.
  • the performance information of the EAS may not be reported.
  • the EES or the ECS determines that the load of the EAS is greater than or equal to the first value, or the EAS is down, the performance information of the EAS may be reported.
  • the first value here may be determined based on empirical values, for example, it may be 50% or 80% of the bandwidth of the EAS, which is not specifically limited in this application. For ease of description, this application may describe it as the EAS performance, which will not be described in detail below.
  • the second network element sends the first information to the first network element, and the corresponding first network element receives the first information from the second network element.
  • the first network element may be an ASP or a management system.
  • the foregoing first information may include network information and application information.
  • the network information may be used to indicate the first network, and the application information may be used to indicate the first application.
  • the network information may include at least one of a network identifier, a location identifier, an EES identifier, or an ECS identifier.
  • the network identifier may indicate an EDN network, such as DNAI or DNN.
  • the location identifier can indicate a node in the EDN network
  • the ECS identifier can identify an ECS
  • the EES identifier can identify an EES.
  • Application information may include application identification and application performance requirements.
  • the application identifier can indicate an application, such as EAS ID or FQDN.
  • the application performance requirement may indicate the performance requirement of the application indicated by the aforementioned application identifier, such as bandwidth and delay requirements.
  • the first information may further include information about the first event of the first application in the first network.
  • the second network element may send the first information to the first network element according to the detected first event.
  • the EES or the ECS may send the first information to the ASP or the management system each time after detecting the above-mentioned first event.
  • the ECS may send the first information to the ASP or the management system.
  • the EES or the ECS may send the first information to the ASP or the management system after detecting multiple first events.
  • the first information may further carry the number of occurrences of the first event.
  • the EES or ECS may detect the first event multiple times and then send the first information may be that the number of times the EES or ECS detects the first event satisfies a preset number of times, such as 10 times. For example, when the EES or the ECS detects that no available EES is found for 10 times, it sends the first information to the ASP or the management system. Alternatively, the EES or ECS may detect multiple first events within a specified period, and send the first information to the ASP or the management system after the specified period expires.
  • the first network element may subscribe to the first event or the first information.
  • the management system or the ASP may send a subscription request to the EES or the ECS, and the subscription request may be used to subscribe to the first information or the first event.
  • the first network element by subscribing the first information or the first event by the first network element, it is possible to prevent the first network element from missing the first information or the first event.
  • the first network element determines to instantiate the EAS corresponding to the first application in the first network when the first event satisfies the first condition.
  • the first condition may include at least one of the following:
  • Condition 1 The number of times no available EAS is found within the first duration is greater than or equal to the first threshold.
  • the first duration may be predetermined based on empirical values, such as 10s or 20s, and the first threshold may be predetermined based on empirical values, such as 5 or 6 times, which are not specifically limited in this application.
  • the ASP or the management system may receive the first information multiple times, and if the number of times no available EAS is found within the first duration is greater than or equal to the first threshold, it may be considered that more UEs want to access the first application Or a UE wants to access the first application multiple times, but the EAS capable of providing services for the first application has not been instantiated in the first network, then the management system or ASP may determine that it is necessary to instantiate the first application in the first network EAS providing services.
  • the first information may include the number of occurrences of the first event.
  • condition 1 may also include that the number of occurrences of no available EAS being found is greater than or equal to the second value.
  • the second value may be the same as or different from the first threshold, which is not specifically limited in this application.
  • Condition 2 the number of times no available EES is found within the second time period is greater than or equal to the second threshold.
  • the second duration may be predetermined based on empirical values, such as 8s or 10s, and the second threshold may be predetermined based on empirical values, such as 10 times or 15 times, which are not specifically limited in this 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, which is not specifically limited in this application.
  • the ASP or the management system may receive the first information multiple times, and if the number of times no available EES is found within the second duration is greater than or equal to the second threshold, it may be considered that more UEs want to access the first application Or the same UE wants to access the first application multiple times, but because the first network has not yet instantiated an EAS that can provide services for the first application, it cannot find an EES that is deployed with an EAS that can provide services for the first application, then the management The system or the ASP may determine that it is necessary to instantiate an EAS capable of providing services for the first application in the first network.
  • the first information may include the number of occurrences of the first event.
  • condition 2 may also include that the number of occurrences of no available EES being found is greater than or equal to the third value.
  • the third value may be the same as or different from the second threshold, which is not specifically limited in this application.
  • Condition 3 the load of the EAS is greater than or equal to the third threshold.
  • the EAS performance in the first information includes that the load of the EAS is greater than or equal to the third threshold, it can be considered that the EAS that can provide services for the first application in the first network cannot meet the needs of the UE, then the ASP or the management system determines that It is necessary to instantiate an EAS capable of providing services for the first application in the first network.
  • the third threshold may be 50% or 85% of the bandwidth of the EAS, etc., which is not specifically limited in this application.
  • EAS downtime can be all EAS downtimes in the network, or some EAS downtimes. For example, it can be one EAS downtime in the first network or more than or equal to half of the number of EAS downtimes. This application does not specify limited.
  • the management system may obtain the installation information of the application that allows instantiation from the ASP in advance, that is, the management system may obtain the authorization of the application that allows instantiation.
  • the application installation information may include application identification, application description file and other information. If the management system is authorized to allow instantiation of the application, the EES or ECS may send the first information to the management system. When the first event meets the first condition, the management system may instantiate the EAS corresponding to the first application in the first network.
  • the EES or ECS may send the first information to the ASP.
  • the ASP sends an instantiation EAS request to the management system, requesting the management system to instantiate an EAS capable of providing services for the first application in the first network.
  • instantiating the EAS corresponding to the first application may include allocating virtual machine resources, memory, CPU, bandwidth, etc. required by the application for the EAS, or in other words, deploying a server corresponding to the first application in the first network EDN.
  • This application does not specifically limit the operation of instantiating the EAS.
  • S304 The first network element sends the second information to the second network element.
  • the second information may be used to indicate that the EAS instantiation of the first application is successful.
  • the management system may send the second information to the EES or the ECS. If the EES or ECS sends the first information to the management system, after instantiating the EAS, the management system may send the second information to the EES or ECS.
  • the management system may send the second information to the ASP, and then the ASP sends the second information to the EES or the ECS. If EES or ECS sends first information to ASP, then after instantiating EAS, the management system can send second information to ASP, and ASP can send second information to EES or ECS.
  • the EES may receive the second information from the ASP or the management system, and may send instantiated EAS information corresponding to the first application to the EEC.
  • the ECS may send EES information to the EEC, and the EEC may send an EAS discovery request to the EES after receiving the EES information, as in S107.
  • FIG. 4 another exemplary flow chart for instantiating an EAS provided by an embodiment of the present application may include the following operations.
  • S401 The ASP sends a list of applications allowed to be instantiated, application installation information, application performance requirements, etc. to the management system.
  • the above information can be pre-configured on the management system.
  • the management system may store the above-mentioned application installation information that is allowed to be instantiated, performance requirements of the application, and the like.
  • S402 The EES or the ECS detects an EAS abnormal event.
  • EES detects EAS abnormal events, which may include EES receiving an EAS discovery request from EEC, but EES does not find an EAS that meets the conditions, or EES receives a registration request from EEC, but EES does not find an EAS that meets the conditions.
  • the aforementioned satisfying condition may refer to satisfying the requirements of the application that the UE wants to access.
  • the EES can monitor changes in the performance of the EAS. For example, whether the EAS is overloaded or down.
  • the ECS detects EAS abnormal events, which may include that the ECS receives an EES discovery request from the EES, but the ECS does not find an EES that meets the conditions, or the ECS receives a service configuration request from the EEC, but the ECS does not find an EES that meets the conditions.
  • EES abnormal events may include that the ECS receives an EES discovery request from the EES, but the ECS does not find an EES that meets the conditions, or the ECS receives a service configuration request from the EEC, but the ECS does not find an EES that meets the conditions.
  • the aforementioned EES that meets the conditions may refer to the EAS deployed in the EES that meets the requirements of the application that the UE wants to access.
  • the EES or the ECS sends the first information to the management system or the ASP, and sends the detected abnormal event of the EAS to the management system or the ASP.
  • the performance of the EAS may be carried in the first information and sent to the management system or the ASP.
  • the EES or ECS may directly send the first information to the management system.
  • the first information may not include the number of occurrences of the EAS abnormal event, or may default to one occurrence.
  • the first information includes the occurrence times of the EAS abnormal events.
  • S404 The ASP or the management system determines whether to instantiate the EAS in the corresponding network according to the local policy.
  • the ASP or the management system may determine whether the EAS abnormal event or the EAS performance satisfies the first condition. For details, please refer to the relevant description in the first condition, which will not be repeated here.
  • the ASP may send an instantiation EAS request to the management system when determining that the EAS abnormal event or the EAS performance meets the first condition.
  • the instantiation EAS request may include application information and network information, and is used to determine which network to deploy the EAS of which application.
  • S405 The management system instantiates the EAS in the EDN network.
  • the management system may instantiate the EAS of the application indicated by the application information on the EDN indicated by the network information according to the application information and the network information.
  • the management system can allocate virtual machine resources, memory, CPU, bandwidth, etc. required by the application to the EAS, and this application does not specifically limit the operation of instantiating the EAS.
  • the management system may first send a message to the management network element of the edge network, such as MEC Platform Management (MEPM), and then the management network element of the edge network interacts with the EES or MEP to instantiate the EAS.
  • MEC Platform Management MEC Platform Management
  • S406 The management system sends a second message to the EES or the ECS, notifying the EES or the ECS that the EAS is instantiated successfully.
  • the management system first notifies ASP of the successful instantiation of EAS, and then ASP notifies EES or ECS of successful instantiation of EAS. It should be noted that the process of notifying the EES or ECS of successful EAS instantiation shown in FIG. 4 is only exemplary.
  • S407 may also be performed.
  • the EES may send information about newly instantiated EAS to the EEC; or, since a new EAS is deployed on the EES, the ECS may send EES information to the EEC, and the EEC may send an EAS discovery request to the EES after receiving the EES information.
  • the management system can determine whether to dynamically instantiate EAS based on the reported events, and the management system deploys EAS as needed, which can significantly improve the efficiency of operation and maintenance management.
  • Fig. 5 is an exemplary flow chart of another method for instantiating an EAS provided by an embodiment of the present application, which may include the following operations.
  • S501 The second network element detects the first event.
  • the second network element may be an EES or an ECS
  • the first event may refer to related descriptions in the method embodiment shown in FIG. 3 above, and details are not repeated here.
  • the second network element sends indication information to one or more terminals.
  • the above one or more terminals may be EEC function modules in the terminals.
  • EES can send instruction information to EEC when no available EAS is found, or EAS is overloaded or down.
  • ECS can send instructions to EEC when no available EES is found, or EAS is overloaded or down.
  • the indication information may be used to indicate EAS search failure or EES search failure, or may be used to indicate EEC registration failure, or indication information may be used to indicate that the first application that the UE wants to access needs to dynamically instantiate EAS, or indication information It is used to indicate that the performance of the EAS deployed in the current EDN cannot meet the performance requirement requested by the UE.
  • S503 One or more terminals send first request information to the first network element.
  • the EEC may send the indication information to the AC.
  • the above-mentioned first network element may be an ASP, a management system, or a user application lifecycle proxy (user app LCM proxy, UEAPPLCM proxy).
  • the aforementioned UEAPPLCM proxy is an entity that can be used by users to request services such as instantiation and termination related to applications.
  • the foregoing first request information may include network information, application information, and terminal identifier.
  • the terminal identifier may be a user permanent identifier (subscription permanent identifier, SUPI) or a general public subscription identifier (generic public subscription identifier, GPSI), etc., and may be used to determine which UE wants to access the first application.
  • the first network element determines whether to instantiate the EAS of the first application in the first network according to the first request information.
  • the first network element determines whether to instantiate the EAS of the first application in the first network based on a local policy or configuration. For example, if the number of UEs wanting to access the first application reaches a first threshold, it may be determined to instantiate the EAS of the first application in the first network. Wherein, the number of UEs may be determined by the number of terminal identities received by the first network element, and if the number of terminal identities reaches a first threshold, it may be considered that the number of UEs wanting to access the first application reaches the first threshold.
  • first network element determines that the second threshold is reached according to the number of times of the first request, it may be considered that there is a greater need to access the first application, and thus determine to instantiate the EAS of the first application in the first network.
  • the foregoing first threshold and second threshold may be predetermined based on empirical values, such as 1 or 5, which are not specifically limited in this application.
  • the subscription level of the terminal identified by the terminal identifier may be higher than or equal to the specified level, it may be determined to instantiate the EAS of the first application in the first network.
  • the first request information may include the subscription level of the terminal identified by the terminal identifier.
  • the first network element may store the correspondence between the terminal identifier and the subscription level, and the first network element may determine in the stored correspondence whether the subscription level corresponding to the terminal identifier contained in the first request information is higher than or equal to the specified level .
  • the management system may obtain the installation information of the application that allows instantiation from the ASP in advance, that is, the management system may obtain the authorization of the application that allows instantiation.
  • the application installation information may include application identification, application description file and other information. If the management system is authorized to allow instantiation of the application, the terminal may send the 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 according to the first request information. If the management system determines to instantiate the EAS of the first application in the first network, S505 may be executed; otherwise, the management system may execute S507.
  • the terminal may send the first request information to ASP or UEAPPLECM proxy.
  • the ASP or UEAPPLECM proxy may determine whether to instantiate the EAS of the first application in the first network according to the first request information. If the ASP or UEAPPLCM proxy determines to instantiate the EAS of the first application in the first network, it may send the second request information to the management system.
  • the second request information may include the above application information and network information.
  • the management system instantiates an EAS capable of providing services for the first application in the first network, that is, executes S505. If the ASP or UEAPPLCM proxy determines not to instantiate the EAS of the first application in the first network, the ASP or UEAPPLCM proxy executes S507.
  • the first network element instantiates an EAS capable of providing services for the first application in the first network.
  • the first network element sends the second information to one or more terminals.
  • the management system or ASP or UEAPPLCMA proxy can first notify the EEC of the successful instantiation of the EAS, and then the EEC notifies the AC of the successful instantiation of the EAS.
  • the management system may send the second information to the one or more terminals after instantiating the EAS.
  • the management system can send second information to ASP or UEAPPLCM proxy after instantiating EAS, and ASP or UEAPPLCM proxy sends a second message to one or Multiple terminals send the second information.
  • the first network element sends third information to one or more terminals.
  • the third information may be used to indicate that no EAS of the first application is found in the first network.
  • the management system sends the third information to the one or more terminals. If one or more terminals send the first request information to ASP or UEAPPLCM proxy, then the third information is sent to one or more terminals by ASP or UEAPPLCM proxy.
  • the management system can instantiate EAS according to the needs of UEs, which can provide users with differentiated service experience and improve the efficiency of operation and maintenance management.
  • FIG. 6 it is an exemplary flowchart of another method for instantiating an EAS provided by an embodiment of the present application, which may include the following operations.
  • the S600 is the same as the S401.
  • the EEC sends an EAS discovery request or a registration request to the EES.
  • the EAS discovery request or registration request may include application information.
  • the EEC sends a service configuration request to the ECS, and the service configuration request includes application information.
  • S602 is the same as S402.
  • S603 The EES or the ECS sends indication information to the EEC.
  • the indication information may be used to indicate that the EAS needs to be instantiated.
  • the EAS needs to be instantiated.
  • the EEC may perform the following operation S604:
  • S604 The EEC sends the indication information to the AC.
  • the EEC sends an instantiated EAS request to the UEAPPLCM proxy/ASP/management system.
  • the instantiated EAS request may include network identifier or location identifier, application information and UE identifier, etc.
  • network identifier or location identifier For details, please refer to related descriptions in the method embodiments shown in FIGS. 3-5 , which will not be repeated here.
  • the AC may first send the instantiation EAS request to the EEC, and then the EEC sends the instantiation EAS request to the ASP or UEAPPLCM proxy. And the instantiated EAS request is sent to the management system by ASP or UEAPPLCM proxy.
  • the instantiated EAS request may include network information and application information, and may not include a terminal identifier.
  • the AC sends the instantiation EAS request to ASP or user app LCM proxy.
  • the AC/EEC may send an instantiated EAS request to the management system.
  • S606 UEAPPLCM proxy/ASP/management system authenticates and authorizes the instantiated EAS request.
  • the instantiation EAS request can be authenticated and authorized by ASP or UEAPPLCM proxy.
  • the following operation S607 may be performed.
  • UEAPPLCM proxy/ASP sends an instantiated EAS request carrying network information and application information to the management system.
  • the management system may include network elements such as an operation support system (operation support system, OSS), an MEC orchestrator (MEO) and a MEPM.
  • operation support system operation support system
  • MEC MEC orchestrator
  • S608 is the same as S405.
  • S609 The UEAPPLCM proxy/ASP/management system sends a second message to the AC/EEC, notifying the AC/EEC that the EAS is instantiated successfully.
  • the UEAPPLCM proxy/ASP EAS can be instantiated successfully by the management system, and then the UEAPPLCM proxy/ASP can notify the EEC/AC EAS instantiation successful.
  • the EEC may be notified first of the successful instantiation of the EAS, and the EEC may notify the AC of the successful instantiation of the EAS, or the AC may be notified of the successful instantiation of the EAS, and the AC may notify the EEC of the successful instantiation of the EAS.
  • S610 The EEC may resend the request in S601.
  • UE sends dynamic instantiation EAS request to UEAPPLCM proxy or ASP or management system, which can provide users with differentiated service experience, and management system deploys EAS on demand to improve the efficiency of operation and maintenance management.
  • FIG. 7 and FIG. 8 are schematic structural diagrams of a possible communication device provided by an embodiment of the present application. These communication devices may be used to implement the functions of the first network element, the second network element, or the terminal in the foregoing method embodiments, and thus also realize the beneficial effects of the foregoing method embodiments.
  • a communication device 700 includes a processing unit 710 and a transceiver unit 720 .
  • the communication device 700 is configured to implement functions of the first network element, the second network element, or the terminal in the method embodiment shown in FIG. 3 or FIG. 5 above.
  • the transceiver unit is used to receive the first information from the second network element, the first information includes network information and application information, and the network The information is used to indicate the first network, the application information is used to indicate the first application, and the first information also includes information about the first event of the first application in the first network; the first event includes information not found in the first network At least one of the edge application server corresponding to the first application, the edge enabling server corresponding to the first application not found in the first network, and the performance information of the edge application server corresponding to the first application in the first network.
  • a processing unit configured to instantiate a first edge application server corresponding to the first application in the first network when the first event satisfies the first condition.
  • the transceiver unit is used to receive the first request information from one or more terminals, and the first request information is used to request instantiation The edge application server;
  • the first request information includes network information, application information and terminal identification;
  • the network information is used to indicate the first network, the application information is used to indicate the first application, and the terminal identification is used to identify the terminal sending the first request information;
  • a processing unit configured to determine whether to instantiate an edge application server corresponding to the first application in the first network according to the first request information.
  • the processing unit is used to detect the first event; the first event includes not finding the corresponding first application in the first network At least one of the edge application server, the edge enabling server corresponding to the first application in the first network and the performance information of the edge application server corresponding to the first application in the first network are not found;
  • the first event received sends first information to the first network element or sends instruction information to one or more terminals; the first information includes network information and application information, and the instruction information is used to indicate that an edge application server needs to be instantiated; the network information uses To indicate the first network, the application information is used to indicate the first application.
  • the transceiver unit is used to receive indication information from the edge enabling server or the edge network configuration server, and the indication information is used to indicate that the edge application server search fails or Edge-enabled client registration failed or edge application server needs to be instantiated.
  • a processing unit configured to generate request information according to the indication information.
  • the request information includes network information, application information and terminal identification; the network information is used to indicate the first network, the application information is used to indicate the first application, and the terminal identification is used to identify the terminal sending the request information.
  • the transceiver unit is further configured to send request information to the first network element.
  • processing unit 710 and the transceiver unit 720 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 3 or FIG. 4 , and will not be repeated here.
  • the communication device 800 includes a processor 810 and an interface circuit 820 .
  • the processor 810 and the interface circuit 820 are coupled to each other.
  • the interface circuit 820 may be a transceiver or an input/output interface.
  • the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810 or storing input data required by the processor 810 to execute the instructions or storing data generated after the processor 810 executes the instructions.
  • the processor 810 is used to implement the functions of the processing unit 710
  • the interface circuit 820 is used to implement the functions of the transceiver unit 720 .
  • the terminal chip implements the functions of the terminal in the above method embodiment.
  • the terminal chip receives information from other modules in the terminal (such as radio frequency modules or antennas), and the information is sent to the terminal by the first network element; or, the terminal chip sends information to other modules in the terminal (such as radio frequency modules or antennas) information, the information is sent by the terminal to the first network element.
  • the first network element module implements the functions of the first network element in the above method embodiment.
  • the first network element module receives information from other modules (such as radio frequency modules or antennas) in the first network element, and the information is sent to the first network element by the terminal or the second network element; or, the first network element module Send information to other modules (such as radio frequency modules or antennas) in the first network element, where the information is sent by the first network element to the terminal or the second network element.
  • the second network element module implements the functions of the second network element in the above method embodiment.
  • the second network element module receives information from other modules in the second network element (such as radio frequency modules or antennas), and the information is sent by the first network element to the second network element; or, the first network element module sends information to the second network element Other modules (such as radio frequency modules or antennas) in a network element send information, and the information is sent by the second network element to the first network element.
  • the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can 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.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC may be located in the first network element, the second network element or the terminal.
  • the processor and the storage medium may also exist in the first network element, the second network element, or the terminal as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; or it may be a semiconductor medium, such as a solid-state hard disk.
  • the computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
  • “at least one” means one or more, and “multiple” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a “division” Relationship.
  • “Including at least one of A, B and C” may mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种实例化边缘应用服务器的方法和装置，涉及通信技术领域，用以动态实例化边缘应用服务器。方法中，第一网元接收来自第二网元的第一信息。其中，第一信息包括网络信息和应用信息，网络信息用于指示第一网络，应用信息用于指示第一应用。第一信息还包括第一网络中的关于第一应用的第一事件的信息。第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。第一网元确定在第一事件满足第一条件时，在第一网络中实例化第一应用对应的第一边缘应用服务器。

Description

一种实例化边缘应用服务器的方法和装置
相关申请的交叉引用
本申请要求在2021年07月07日提交中国专利局、申请号为202110766584.3、申请名称为“一种实例化边缘应用服务器的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种实例化边缘应用服务器的方法和装置。
背景技术
边缘数据网络(edge data network，EDN)可以是本地数据中心，EDN包含边缘使能服务器(edge enabler server，EES)和多个边缘应用服务器(edge application server，EAS)，每个EDN有特定的服务范围。其中，EES可以是移动边缘计算(mobile edge computing，MEC)节点中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册和域名服务器(domain name system，DNS)解析等。此外，EES可以调用网络的能力开放功能。
用户设备(user equipment，UE)可以包括边缘使能客户端(edge enabler client，EEC)和应用客户端(application client，AC)。其中，EEC为UE上的应用客户端提供必要的支持，UE可以通过EDGE-1接口注册到EES。
相关技术中，在UE注册到EES时，EES可以检测已部署的EAS是否满足UE访问的应用信息。在EES检测已部署的EAS不满足UE访问的应用信息时或者EES发现当前EDN里尚没有实例化的EAS时，如何满足UE的访问请求尚未定义。
发明内容
本申请实施例提供一种实例化边缘应用服务器的方法和装置，用来动态实例化边缘应用服务器。
第一方面，提供了实例化边缘应用服务器的方法。该方法可以由第一网元执行，或者类似第一网元的芯片执行。其中，第一网元可以是应用服务提供商或管理系统。该方法中，第一网元可以接收来自第二网元的第一信息。其中，第一信息可以包括网络信息和应用信息，网络信息可以用于指示第一网络，应用信息可以用于指示第一应用。第一信息还可以包括第一网络中的关于第一应用的第一事件的信息。第一事可以件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。第一网元可以确定在第一事件满足第一条件时，在第一网络中实例化第一应用对应的第一边缘应用服务器。
基于上述方案，第一网元可以根据第二网元上报的第一事件，确定在第一事件满足第一条件时，动态实例化第一应用的边缘应用服务器，能提升运维管理的效率。
在一种可能的实现方式中，第一网络中未查找到对应第一应用的边缘应用服务器，包括：第一网络中未部署或未实例化第一应用对应的边缘应用服务器；
在另一种可能的实现方式中，第一网络中未查找到对应第一应用的边缘应用服务器，包括：第一网络中未查找到符合终端需求(UE required)的对应第一应用的边缘应用服务器。即，第一网络中虽然部署了或实例化了第一应用对应的边缘应用服务器，但第一应用的边缘应用服务器的性能无法满足终端需求。
在一种可能的实现方式中，在第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器时，第一条件可以包括在第一时长内在第一网络中未查找到对应第一应用的边缘应用服务器的次数大于或等于第一阈值。在第一事件包括在第一网络里未查找到对应第一应用的边缘使能服务器时，第一条件可以包括在第二时长内在第一网络里未查找到对应第一应用的边缘使能服务器的次数大于或等于第二阈值。在第一事件包括第一网络中的对应第一应用的边缘应用服务器的性能信息时，第一条件可以包括边缘应用服务器的负载大于或等于第三阈值和边缘应用服务器宕机中的至少一个。
基于上述方案，可以在多个终端想要访问第一应用或者一个终端多次想要访问第一应用时，实例化第一应用的边缘应用服务器，可以提高用户的体验感。
在一种可能的实现方式中，第一网元可以向管理系统发送实例化边缘应用服务器请求，实例化边缘应用服务器请求用于实例化边缘应用服务器，实例化边缘应用服务器请求中包含网络信息和应用信息。
在一种可能的实现方式中，第一信息还可以包括第一事件的发生次数。
基于上述方案，第二网元可以在检测到多次第一事件时向第一网元上报，可以提高传输资源的利用率。
在一种可能的实现方式中，在第一网络里未查找到对应第一应用的边缘使能服务器的次数可以是第一网元接收第一事件的次数。或者，在第一网络里未查找到对应第一应用的边缘使能服务器的次数可以是第一网元接收第一事件的次数。
基于上述方案，第二网元可以多次向第一网元上报第一事件，可以在终端想要访问第一应用但网络中未部署第一应用的边缘应用服务器时，及时向第一网元上报终端的需求，提高用户体验感。
在一种可能的实现方式中，在第一网元为管理系统时，第一网元在第一网络中实例化第一应用对应的第一边缘应用服务器之前，第一网元可以从应用服务提供商获取允许实例化的应用安装信息。
基于上述方案，管理系统在获得允许实例化的应用安装信息后，可以直接与第二网元进行通信，减少复杂度。
在一种可能的实现方式中，第一网元可以向第二网元发送第二信息，第二信息可以用于指示第一边缘应用服务器实例化成功。
在一种可能的实现方式中，第一网元可以订阅第一信息。
基于上述方案，通过第一网元订阅第一信息，来接收第二网元的第一信息，可以提高第一网元接收第一信息的成功率。
第二方面，提供了实例化边缘应用服务器的方法。该方法可以由第二网元执行，或者类似第二网元功能的芯片执行。其中，第二网元可以是边缘使能服务器或者边缘网络配置 服务器。该方法中，第二网元可以检测第一事件。其中，第一事件可以包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。第二网元可以根据检测到的第一事件向第一网元发送第一信息或者向一个或多个终端发送指示信息。其中，第一信息可以包括网络信息和应用信息，指示信息可以用于指示需要实例化边缘应用服务器。网络信息用于可以指示第一网络，应用信息可以用于指示第一应用。
在一种可能的实现方式中，第一网络中未查找到对应第一应用的边缘使能服务器，包括：第一网络中未部署或未实例化第一应用对应的边缘应用服务器，或者，第一网络中未查找到符合终端需求(UE required)的对应第一应用的边缘应用服务器，边缘配置服务器确定第一网络中未查找到对应第一应用的边缘使能服务器。
在一种可能的实现方式中，指示信息用于指示在第一网络里未查找到对应第一应用的边缘应用服务器或边缘使能服务器，或者，用于指示注册失败，对指示信息的名称不做限定。
基于上述方案，第二网元可以向第一网元上报在第一网络中检测到的关于第一应用的第一事件，以实现第一网元对是否在第一网络中实例化边缘应用服务器的判断。
在一种可能的实现方式中，第二网元可以接收第二信息，第二信息可以用于指示第一边缘应用服务器实例化成功，第一信息可以用于实例化第一边缘应用服务器的判断。
基于上述方案，第一网元可以根据第二网元上报的第一事件，确定在第一事件满足第一条件时，动态实例化第一应用的边缘应用服务器，能提升运维管理的效率。
在一种可能的实现方式中，第一信息还可以包括第一事件的发生次数。
在一种可能的实现方式中，指示信息可以用于指示边缘应用服务器查找失败或边缘使能客户端注册失败。
基于上述方案，第二网元可以通过指示信息向一个或多个终端指示是否需要动态实例化边缘应用服务器。
第三方面，提供了实例化边缘应用服务器的方法。该方法可以由第一网元执行，或者而类似第一网元功能的芯片执行。其中，第一网元可以是应用服务提供商或管理系统。该方法中，第一网元可以接收来自一个或多个终端的第一请求信息，第一请求信息可以用于请求实例化边缘应用服务器。其中，第一请求信息中可以包含网络信息、应用信息和终端标识。网络信息可以用于指示第一网络，应用信息可以用于指示第一应用，终端标识可以用于标识发送第一请求信息的终端。第一网元可以根据第一请求信息确定是否在第一网络中实例化第一应用对应的边缘应用服务器。
基于上述方案，终端向第一网元发送第一请求信息，以请求在第一网络中实例化第一应用的边缘应用服务器，可以为终端提供差异化的服务体验，提升运维管理的效率。
在一种可能的实现方式中，在一个或多个终端的数量达到第一阈值时，可以确定在第一网络中实例化第一应用对应的边缘应用服务器。和/或，在终端标识所标识的终端的签约等级高于或等于指定等级时，可以确定在第一网络中实例化第一应用对应的边缘应用服务器。
基于上述方案，可以在多个终端想要访问第一应用或者想要访问第一应用的签约等级较高时，实例化第一应用的边缘应用服务器，可以为终端提供差异化的服务体验，提升运 维管理的效率。
在一种可能的实现方式中，第一网元可以向管理系统发送第二请求信息。其中，第二请求信息可以用于请求实例化边缘应用服务器，第二请求信息可以包含网络信息和应用信息。
在一种可能的实现方式中，网络信息可以包括网络标识和位置标识中的至少一个。其中，网络标识和位置标识可以用于标识第一网络，应用信息包括可以应用标识和应用性能需求中的至少一个。
在一种可能的实现方式中，在第一网元为管理系统时，第一网元确定在第一网络中实例化第一应用对应的边缘应用服务器之前，第一网元可以从应用服务提供商获取允许实例化的应用安装信息。
基于上述方案，管理系统在获得允许实例化的应用安装信息后，可以直接与终端进行通信，减少复杂度。
在一种可能的实现方式中，第一网元可以向第二网元或一个或多个终端发送第二信息，第二信息可以用于指示第一应用对应的边缘应用服务器实例化成功。
在一种可能的实现方式中，在一个或多个终端的数量未达到第一阈值时，可以向一个或多个终端发送第三信息。第三信息可以用于指示在第一网络中未查找到第一应用的边缘应用服务器。和/或，在终端标识所标识的终端的签约等级低于指定等级时，可以向一个或多个终端发送第三信息。第三信息可以用于指示在第一网络中未查找到第一应用的边缘应用服务器。
基于上述方案，在不满足上述条件时第一网元可以向终端发送第三信息，也就是不在第一网络中实例化第一应用的边缘应用服务器，可以节省EDN网络中的资源。
第四方面，提供了实例化边缘应用服务器的方法。该方法可以由终端执行，或者类似终端功能的芯片执行。该方法中，边缘使能客户端可以从边缘使能服务器或边缘网络配置服务器接收指示信息。其中，指示信息可以用于指示边缘应用服务器查找失败或边缘使能客户端注册失败或需要实例化边缘应用服务器。边缘使能客户端可以根据指示信息向第一网元发送请求信息，请求信息中可以包含网络信息和应用信息。网络信息可以用于指示第一网络，应用信息可以用于指示第一应用。
基于上述方案，终端向第一网元发送第一请求信息，以请求在第一网络中实例化第一应用的边缘应用服务器，可以为终端提供差异化的服务体验，提升运维管理的效率。
在一种可能的实现方式中，边缘使能客户端可以向应用客户端发送指示信息。
在一种可能的实现方式中，边缘使能客户端可以接收来自应用客户端的请求信息。
在一种可能的实现方式中，边缘使能客户端可以接收来自第一网元的第二信息，第二信息可以用于指示第一应用对应的边缘应用服务器实例化成功。
第五方面，提供了一种通信装置。该装置可以包括用于执行第一方面或第一方面任一种可能实现方式中的各个模块/单元。如收发单元和处理单元。
其中，收发单元用于接收来自第二网元的第一信息，第一信息包括网络信息和应用信息，网络信息用于指示第一网络，应用信息用于指示第一应用，第一信息还包括第一网络中的关于第一应用的第一事件的信息；第一事件包括在第一网络中未查找到对应第一应用 的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。处理单元，用于确定在第一事件满足第一条件时，在第一网络中实例化第一应用对应的第一边缘应用服务器。
在一种设计中，在第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器时，第一条件包括在第一时长内在第一网络中未查找到对应第一应用的边缘应用服务器的次数大于或等于第一阈值；在第一事件包括在第一网络里未查找到对应第一应用的边缘使能服务器时，第一条件包括在第二时长内在第一网络里未查找到对应第一应用的边缘使能服务器的次数大于或等于第二阈值；在第一事件包括第一网络中的对应第一应用的边缘应用服务器的性能信息时，第一条件包括边缘应用服务器的负载大于或等于第三阈值和边缘应用服务器宕机中的至少一个。
在一种设计中，收发单元还用于向管理系统发送实例化边缘应用服务器请求，实例化边缘应用服务器请求用于实例化边缘应用服务器，实例化边缘应用服务器请求中包含网络信息和应用信息。
在一种设计中，第一信息还包括第一事件的发生次数。
在一种设计中，在第一网络里未查找到对应第一应用的边缘使能服务器的次数是第一网元接收第一事件的次数；或者，在第一网络里未查找到对应第一应用的边缘使能服务器的次数是第一网元接收第一事件的次数。
在一种设计中，处理单元还用于：从应用服务提供商获取允许实例化的应用安装信息。
在一种设计中，收发单元还用于：向第二网元发送第二信息，第二信息用于指示第一边缘应用服务器实例化成功。
在一种设计中，收发单元还用于：向第二网元发送订阅请求，订阅请求用于订阅第一信息。
第六方面，提供了一种通信装置。该装置可以包括用于执行第二方面或第二方面任一种可能实现方式中的各个模块/单元。如收发单元和处理单元。
其中，处理单元用于检测第一事件；第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个；收发单元，用于根据检测到的第一事件向第一网元发送第一信息或者向一个或多个终端发送指示信息；第一信息包括网络信息和应用信息，指示信息用于指示需要实例化边缘应用服务器；网络信息用于指示第一网络，应用信息用于指示第一应用。
在一种设计中，收发单元还用于接收第二信息，第二信息用于指示第一边缘应用服务器实例化成功，第一信息用于实例化第一边缘应用服务器的判断。
在一种设计中，第一信息还包括第一事件的发生次数。
在一种设计中，指示信息用于指示边缘应用服务器查找失败或边缘使能客户端注册失败。
第七方面，提供了一种通信装置。该装置可以包括用于执行第三方面或第三方面任一种可能实现方式中的各个模块/单元。如收发单元和处理单元。
其中，收发单元用于接收来自一个或多个终端的第一请求信息，第一请求信息用于请求实例化边缘应用服务器；第一请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送第一请求信息 的终端；处理单元，用于根据第一请求信息确定是否在第一网络中实例化第一应用对应的边缘应用服务器。
在一种设计中，处理单元在根据第一请求信息确定是否在第一网络中实例化第一应用对应的边缘应用服务器时，具体用于：在一个或多个终端的数量达到第一阈值时，确定在第一网络中实例化第一应用对应的边缘应用服务器；和/或，在终端标识所标识的终端的签约等级高于或等于指定等级时，确定在第一网络中实例化第一应用对应的边缘应用服务器。
在一种设计中，收发单元还用于向管理系统发送第二请求信息；其中，第二请求信息用于请求实例化边缘应用服务器，第二请求信息包含网络信息和应用信息。
在一种设计中，网络信息包括网络标识和位置标识中的至少一个；网络标识和位置标识用于标识第一网络，应用信息包括应用标识和应用性能需求中的至少一个。
在一种设计中，处理单元还用于从应用服务提供商获取允许实例化的应用安装信息。
在一种设计中，收发单元还用于向第二网元或一个或多个终端发送第二信息，第二信息用于指示第一应用提供对应的边缘应用服务器实例化成功。
在一种设计中，收发单元还用于：在一个或多个终端的数量未达到第一阈值时，向一个或多个终端发送第三信息；第三信息用于指示在第一网络中未查找到第一应用的边缘应用服务器；和/或，在终端标识所标识的终端的签约等级低于指定等级时，向一个或多个终端发送第三信息；第三信息用于指示在第一网络中未查找到第一应用的边缘应用服务器。
第八方面，提供了一种通信装置。该装置可以包括用于执行第四方面或第四方面任一种可能实现方式中的各个模块/单元。如收发单元和处理单元。
其中，收发单元用于从边缘使能服务器或边缘网络配置服务器接收指示信息，指示信息用于指示边缘应用服务器查找失败或边缘使能客户端注册失败或需要实例化边缘应用服务器。处理单元，用于根据指示信息生成请求信息。请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送请求信息的终端。收发单元，还用于向第一网元发送请求信息。
在一种设计中，收发单元还用于：向应用客户端发送指示信息；接收来自应用客户端的请求信息。
在一种设计中，收发单元还用于接收来自第一网元的第二信息，第二信息用于指示第一应用对应的边缘应用服务器实例化成功。
第九方面，提供了一种通信装置，包括处理器和存储器。其中，存储器用于存储计算机程序或指令，处理器执行存储器中的计算机程序或指令，实现第一方面或第一方面任一种可能实现方式，或者实现第二方面或第二方面任一种可能实现方式，或者实现第三方面或第三方面任一种可能实现方式，或者实现第四方面或第四方面任一种可能实现方式。
该存储器可以位于装置内部，或者也可以位于装置外部，与所述装置相连。
在一种可能的实现方式中，存储器可以与处理器集成在一起。
在一种可能的实现方式中，通信装置还可以包括收发机。收发机执行第一方面或第一方面任一种可能实现方式中方法的收发操作，或者执行第二方面或第二方面任一种可能实现方式中方法的收发操作，或者执行第三方面或第三方面任一种可能实现方式中方法的收发操作，或者执行第四方面或第四方面任一种可能实现方式中方法的收发操作。
第十方面，提供了一种芯片，该芯片包括逻辑电路和通信接口。
示例性的，通信接口用于输入第一信息，第一信息包括网络信息和应用信息，网络信息用于指示第一网络，应用信息用于指示第一应用，第一信息还包括第一网络中的关于第一应用的第一事件的信息；第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。逻辑电路，用于在第一事件满足第一条件时，在第一网络中实例化第一应用对应的第一边缘应用服务器。
示例性的，逻辑电路用于检测第一事件；第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。通信接口，用于输出第一信息或指示信息；第一信息包括网络信息和应用信息，指示信息用于指示需要实例化边缘应用服务器；网络信息用于指示第一网络，应用信息用于指示第一应用。
示例性的，通信接口用户输入第一请求信息，第一请求信息用于请求实例化边缘应用服务器；第一请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送第一请求信息的终端。逻辑电路，用于根据第一请求信息确定是否在第一网络中实例化第一应用对应的边缘应用服务器。
示例性的，通信接口用于输入指示信息，指示信息用于指示边缘应用服务器查找失败或边缘使能客户端注册失败或需要实例化边缘应用服务器。逻辑电路，用于根据指示信息生成请求信息。请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送请求信息的终端。通信接口，还用于输出请求信息。
第十一方面，本申请提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面的方法。
第十二方面，本申请提供了一种存储指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面的方法。
第十三方面，本申请提供一种通信系统，包括至少一个上述的第一网元和至少一个上述的第二网元，或者包括至少一个上述的第一网元和至少一个上述的终端。
另外，第五方面至第十三方面的有益效果可以参见如第一方面至第四方面所示的有益效果。
附图说明
图1为EEC注册的示例性流程图；
图2为本申请实施例提供的网络架构；
图3为本申请实施例提供的实例化EAS的方法的示例性流程图之一；
图4为本申请实施例提供的实例化EAS的方法的示例性流程图之一；
图5为本申请实施例提供的实例化EAS的方法的示例性流程图之一；
图6为本申请实施例提供的实例化EAS的方法的示例性流程图之一；
图7为本申请实施例提供的通信装置的结构图；
图8为本申请实施例提供的通信装置的框图。
具体实施方式
为便于理解，首先对本申请实施例涉及的术语进行解释和说明。
1)第一应用的EAS，可以是指能够为第一应用提供服务的EAS，还可以称为对应第一应用的EAS，第一应用对应的EAS，或者能够为第一应用提供服务的EAS或者为第一应用提供服务的EAS等。
EDN包含EES和多个EAS，每个EDN有特定的服务范围。其中，EES可以是MEC节点中的控制网元或者管理网元。在欧洲电信标准协会(european telecommunication standard institute，ETSI)MEC架构中，一个EDN又可以称为MEC节点、MEC局点等。MEC节点中包含MEC平台(MEC platform，MEP)和MEC应用(application)。其中，EES与MEC具有相似的功能，EAS和MEC application具有相似的功能。
边缘配置服务器(edge configuration server，ECS)可以是全局管理网元，维护各个EDN的信息，包括服务范围和EES地址等。需要说明的是，在一些标准协议中，比如技术规范(technical specification，TS)23.501和TS23.502等，上述EES、EAS、ECS和MEP等可以称为应用功能网元(application function，AF)。
参阅图1，为EEC注册到EES的流程图，可以包括以下操作。
S101：EEC向ECS发送服务配置请求(service provisioning request)。
其中，上述服务配置请求中可以包含UE想要访问的应用信息，如应用标识和/或应用性能需求等。
S102：ECS向EEC发送EES的信息。
其中，ECS可以查找满足UE想要访问的应用的EES。例如，ECS可以根据应用标识，查找哪一个EDN中部署了对应的EAS。如果ECS查找到上述EDN，则可以向EEC发送查找到的上述EDN中的EES的信息。
S103：EEC向EES发送注册请求。
其中，注册请求中可以携带EEC标识，安全证书和UE想要访问的应用信息，如应用标识和应用性能需求等，以及EEC上下文标识。
S104：EES验证EEC的注册请求是否合法。
其中，EES可以验证EEC标识和安全证书是否一致，如果一致则可以认为注册请求合法，如果不一致则可以认为注册请求不合法。
此外，EES还可以确定已部署的EAS是否满足UE的访问需求，如EES可以确定是否部署了UE请求的应用的EAS。或者，EES可以确定已部署的EAS是否满足UE的需求，例如可以确定已部署的EAS的带宽和时延等是否满足UE的需求。
可选的，还可以执行下述操作S105。
S105：EES根据EEC上下文标识获取EEC上下文。
其中，EES可以根据EEC上下文标识确定UE注册过的EES，并从UE注册过的EES获取EEC上下文。
S106：EES向EEC发送响应消息，通知EEC是否注册成功。
在EEC注册成功后，还可以执行下述操作S107。
S107：EEC向EES发送EAS发现请求。
其中，EAS发现请求中可以包含应用信息。EES可以根据应用信息查找满足UE想要访问的应用的EAS，如果查找到EES可以向EEC发送查找到的EAS的信息。
在上述S104中如果EES检测已部署的EAS不满足UE想访问的应用信息，或者S103中EEC向EES发送注册请求后，EES发现当前EDN中尚未实例化EAS时，或者在S107中EEC向EES发送EAS发现请求后，EES未查找到满足UE想要访问的应用信息的EAS时，EES可能动态触发一个EAS用于满足EEC的请求。但如何动态实例化EAS尚未定义。
本申请实施例提供一种实例化EAS的方法。该方法中，在已部署的EAS不满足UE想访问的应用信息或者当前EDN中尚未实例化EAS时，可以实例化EAS以满足EEC的请求。参阅图2，示出了本申请实施例提供的技术方案适用的通信系统，示意出了边缘数据网络侧的边缘应用服务器以及边缘使能服务器，以及终端设备侧的应用客户端、边缘使能客户端。
其中，EDN对应一个部署在边缘的数据网络，可以是本地数据网络(local DN)或本地区域数据网络(local area data network，LADN)。边缘数据网络包含边缘使能功能，可以采用数据网络接入标识符(data network access identifier，DNAI)和数据网络名称(data network name，DNN)标识或者使用数据网络名称和数据网络服务区域(service area)标识。或者可以理解，边缘数据网络可以被视为一个相对于中心云部署在本地的数据中心。可使用DNAI来标识边缘数据网络，一个边缘数据网络可以包含多个本地数据网络(local DN)。
EAS，部署在边缘数据网络中的服务器应用程序，也可称为应用实例、边缘应用实例、MEC应用(服务器)、EAS功能等。例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等应用部署运行在EDN的应用实例(instance)。其中，一个应用可在一个或多个EDN中部署一个或多个EAS，部署运行在不同EDN中的EAS可以视为是一个应用的不同EAS。一个应用的不同EAS可以共享一个域名；一个应用的不同EAS可以使用一个任播IP地址，也可以使用不同的IP地址。边缘应用服务器EAS上还可包含有该EAS对应的应用的应用上下文，可选的，该应用上下文还可包含使用该应用的一个或多个应用用户在EAS上的上下文，例如使用该应用的一个或多个应用用户相关的运行状态信息、EAS对于该一个或多个应用用户的订阅的事务标识。可选的，该应用上下文也可以包含使用该应用的一个或多个应用用户在EAS与核心网的订阅的上下文例如订阅的事务标识等。
EES部署在EDN中，可以为部署在EDN中的应用实例即前述EAS提供边缘计算使能服务，以更好的支持应用在MEC的部署和运行。EES可以支持EAS的注册、对终端设备(user equipment，UE)的认证和鉴权或对边缘使能客户端的认证和授权，为UE提供应用实例的信息包括如IP地址信息等。一般情况下，可将一个EAS注册到一个EES上，或者，可通过管理系统将一个EAS的信息配置在一个EES上，则该EES称为该EAS关联的EES，EES可控制(管理)注册或者是配置在该EES上的EAS或者是该EAS的服务EES。EES还支持获取应用实例的信息包括如应用实例的标识和应用实例的地址信息(如IP地址信息)，并进一步将应用实例的信息如应用实例的标识发送给边缘数据网络配置服务器(edge configuration server，ECS)。其中，ECS负责EDN的配置，例如向UE提供EES的信息，向UE提供EAS的信息，以及和应用的DNS交互获取EAS的信息等。进一步还可从其他功能实体获取并保存应用实例和IP地址的信息。如图2示意的MEC架构模型，还示意出了前述ECS。
AC为应用在终端设备侧的客户端程序，是EAS在终端设备侧的对等实体，应用客户 端用于应用用户(user)从应用服务器获取应用业务。应用客户端可以连接到云上的应用服务器获取应用业务，也可以连接到应用部署运行在一个或多个EDN中的EAS以获取应用业务。
EEC是EES在终端设备侧的对等实体，EEC用于向EES注册EEC的信息及应用客户端AC的信息，执行安全认证和鉴权，从EES获取EAS的信息包括如EAS的地址信息(如IP地址)以及向应用客户端提供边缘计算使能能力，例如EEC发现服务可将EAS的IP地址返回给应用客户端。
如图2所示，前述终端设备侧的应用客户端AC与边缘应用服务器EAS之间建立通信连接；终端设备侧的边缘使能客户端EEC与边缘使能服务器EES之间建立通信连接。应用用户与应用提供商签订服务协议，可以登录部署在终端设备上的应用客户端AC的方式使用该应用，并通过应用客户端AC与EAS的通信连接交互传输应用数据(application data)；还可通过应用客户端AC以应用编程接口(application program interface，API)的方式，从边缘使能客户端EEC获取边缘使能服务器EES所提供的服务。
参阅图3，为本申请实施例提供的实例化EAS的方法的示例性流程图，可以包括以下操作。
S301：第二网元检测第一事件。
第二网元可以是EES或者ECS。需要说明的是，ECS可能是一个集中部署的网元，不一定部署在EDN网络中，本申请实施例对ECS部署的位置不做具体限定。其中，第一事件可以包括以下中的至少一个：
1、在第一网络中未查找到可用的对应第一应用的EAS。
在S104中，EES可以确定已部署的EAS是否满足UE想要访问的第一应用。在EES确定已部署的EAS中，不存在UE想要访问的第一应用的EAS时，可以认为在第一网络中未查找到可用的对应第一应用的EAS。在S107中，EES可以根据应用信息查找满足UE想要访问的第一应用的EAS，如果未查找到则可以认为在第一网络中未查找到可用的对应第一应用的EAS。为便于描述本申请可能将其描述为未查找到可用的EAS，以下不再赘述。
可选的，在EAS的时延和带宽不满足UE想要访问的第一应用时，也可以认为在第一网络中未查找到可用的对应第一应用的EAS。例如，UE想要访问的第一应用对时延要求较高，而第一网络中已部署的对应第一应用的EAS的时延要求较低，处理业务时时延较大，那么可以认为第一网络中的EAS不满足UE想要访问的第一应用。
2、在第一网络中未查找到可用的对应第一应用的EES。
在S102中，ECS可以查找部署有满足UE想要访问的第一应用的EAS的EDN或EES。如果ECS未查找到上述EDN或EES，可以认为未查找到可用的对应第一应用的EES，或者，ECS可以认为未查找到可用的对应第一应用的EAS，为便于描述本申请可能将其描述为未查找到可用的EES，以下不再赘述。
3、第一网络中对应第一应用的EAS的性能信息。
EES或ECS可以确定第一网络中对应第一应用的EAS性能，如EAS的负载(可以包括内存、CPU、带宽、连接数、时延等中的一项或多项)和是否在线等。可选的，在EES或ECS确定EAS的负载未超过第一值，以及EAS在线时，可以不上报EAS的性能信息。在EES或ECS确定EAS的负载大于或等于第一值，或者EAS宕机时，可以上报EAS的性能信息。这里的第一值可以是根据经验值确定的，例如可以是EAS的带宽的50％或者带 宽的80％等，本申请不做具体限定。为便于描述本申请可能将其描述为EAS性能，以下不再赘述。
S302：第二网元向第一网元发送第一信息，相应的第一网元接收来自第二网元的第一信息。
第一网元可以是ASP或者管理系统。上述第一信息中可以包括网络信息和应用信息。其中，网络信息可以用于指示第一网络，应用信息可以用于指示第一应用。网络信息可以包括网络标识、位置标识、EES标识或者ECS标识中的至少一个。其中，网络标识可以指示一个EDN网络，如可以是DNAI或DNN等。位置标识可以指示EDN网络中的一个节点，ECS标识可以标识一个ECS，EES标识可以标识一个EES。应用信息可以包括应用标识和应用性能需求。其中，应用标识可以指示一个应用，例如EAS ID或FQDN等。应用性能需求可以指示前述应用标识所指示的应用的性能需求，如带宽和时延要求等。第一信息中还可以包括第一网络中的关于第一应用的第一事件的信息。
其中，第二网元可以根据检测到的第一事件向第一网元发送第一信息。在一种可能的实现方式中，EES或ECS可以在每一次检测上述第一事件后，就向ASP或者管理系统发送第一信息。例如，在S102中ECS未查找到可用的EES时，可以向ASP或者管理系统发送第一信息。或者，EES或ECS可以检测多次第一事件后向ASP或管理系统发送第一信息。其中，EES或ECS在检测多次第一事件后发送第一信息时，第一信息中还可以携带第一事件发生的次数。如，ECS未查找到可用的EES的发生次数，EES未查找到可用的EAS的发生次数或EAS负载过高或EAS宕机的次数等。具体的，EES或ECS可以检测多次第一事件后发送第一信息可以是EES或ECS检测到第一事件的次数满足预先设定的次数，如10次。举例来说，EES或ECS在检测到10次未查找到可用的EES时，向ASP或者管理系统发送第一信息。或者，EES或ECS可以在指定周期内检测多次第一事件，在指定周期期满后向ASP或者管理系统发送第一信息。
在一种可能的实现方式中，第一网元可以订阅第一事件或者第一信息。示例性的，管理系统或ASP可以向EES或ECS发送订阅请求，该订阅请求可以用于订阅上述第一信息或者上述第一事件。这样，通过第一网元订阅第一信息或者第一事件，可以避免第一网元遗漏第一信息或者第一事件。
S303：第一网元确定在第一事件满足第一条件时，在第一网络中实例化第一应用对应的EAS。
其中，第一条件可以包括以下中的至少一个：
条件1、在第一时长内未查找到可用的EAS的次数大于或等于第一阈值。
第一时长可以是根据经验值预先确定的，如10s或20s等，第一阈值可以是根据经验值预先确定的，如5次或6次等，本申请不做具体限定。可选的，ASP或者管理系统可以多次接收第一信息，如果在第一时长内未查找到可用的EAS的次数大于或等于第一阈值，则可以认为较多的UE想要访问第一应用或者一个UE想要多次访问第一应用，但第一网络中尚未实例化能够为第一应用提供服务的EAS，那么管理系统或者ASP可以确定有必要在第一网络里实例化为第一应用提供服务的EAS。
可选的，如果EES在检测到多次第一事件后发送第一信息，第一信息中可能会包含第一事件的发生次数。那么条件1也可以包括未查找到可用的EAS的发生次数大于或等于第二值。第二值可以与第一阈值相同或者不相同，本申请不做具体限定。
条件2、在第二时长内未查找到可用的EES的次数大于或等于第二阈值。
第二时长可以是根据经验值预先确定的，如8s或10s等，第二阈值可以是根据经验值预先确定的，如10次或15次等，本申请不做具体限定。第二时长可以与第一时长相同或者不相同，第一阈值可以与第二阈值相同或者不相同，本申请不做具体限定。
可选的，ASP或者管理系统可以多次接收第一信息，如果在第二时长内未查找到可用的EES的次数大于或等于第二阈值，则可以认为较多的UE想要访问第一应用或同一UE想要多次访问第一应用，但由于第一网络尚未实例化能够为第一应用提供服务的EAS，因此无法查找到部署有能够为第一应用提供服务的EAS的EES，那么管理系统或者ASP可以确定有必要在第一网络里实例化能够为第一应用提供服务的EAS。
可选的，如果ECS在检测到多次第一事件后发送第一信息，第一信息中可能会包含第一事件的发生次数。那么条件2也可以包括未查找到可用的EES的发生次数大于或等于第三值。第三值可以与第二阈值相同或者不相同，本申请不做具体限定。
条件3、EAS的负载大于或等于第三阈值。
其中，如果第一信息中EAS性能包括EAS的负载大于或等于第三阈值，则可以认为第一网络中的能够为第一应用提供服务的EAS不能够满足UE的需求，那么ASP或者管理系统确定有必要在第一网络里实例化能够为第一应用提供服务的EAS。第三阈值可以是EAS的带宽的50％或者85％等，本申请不做具体限定。
条件4、EAS宕机。
如果第一信息中EAS性能包括EAS宕机，也就是EAS下线无法提供服务，那么ASP或者管理系统确定有必要在第一网络里实例化能够为第一应用提供服务的EAS。可选的，EAS宕机可以是网络中全部EAS宕机，或者部分EAS宕机，如可以是第一网络中的一个EAS宕机或者大于或等于一半数量的EAS宕机，本申请不做具体限定。
在一个示例中，管理系统可以预先从ASP获取允许实例化的应用安装信息，也就是管理系统可以获得允许实例化的应用的授权。其中，应用安装信息可以包含应用标识、应用描述文件等信息。如果管理系统获得允许实例化的应用的授权，那么EES或ECS可以向管理系统发送第一信息。管理系统在第一事件满足第一条件时，可以在第一网络中实例化第一应用对应的EAS。
另一个示例中，如果管理系统未获得允许实例化的应用列表和应用安装信息，那么EES或ECS可以向ASP发送第一信息。ASP在第一事件满足第一条件时，向管理系统发送实例化EAS请求，请求管理系统在第一网络中实例化能够为第一应用提供服务的EAS。
其中，实例化第一应用对应的EAS可以包括为EAS分配应用所需的虚拟机资源、内存、CPU和带宽等，或者说，第一网络EDN中部署第一应用对应的服务器。本申请对实例化EAS的操作不做具体限定。
S304：第一网元向第二网元发送第二信息。
第二信息可以用于指示第一应用的EAS实例化成功。
在一种可能的实现方式中，管理系统可以向EES或ECS发送第二信息。如果EES或ECS向管理系统发送第一信息，则在实例化EAS后，管理系统可以向EES或ECS发送第二信息。
或者管理系统可以向ASP发送第二信息，再由ASP向EES或ECS发送第二信息。如果EES或ECS向ASP发送第一信息，则在实例化EAS后，管理系统可以向ASP发送第 二信息，ASP可以向EES或ECS发送第二信息。
可选的，EES可以接收来自ASP或者管理系统的第二信息，并可以向EEC发送实例化的对应第一应用的EAS的信息。或者，由于EES上已部署对应第一应用的EAS，ECS可以向EEC发送EES信息，EEC接收到EES信息后可以向该EES发送EAS发现请求，如S107。
以下，根据图4详细介绍本申请实施例提供的实例化EAS的方法。
参阅图4，为本申请实施例提供的又一实例化EAS的示例性流程图，可以包括以下操作。
可选的，S401：ASP将允许实例化的应用列表、应用安装信息以及应用的性能需求等发送给管理系统。或者，可以将上述信息预配置到管理系统上。管理系统可以存储上述允许实例化的应用安装信息以及应用的性能需求等。
S402：EES或ECS检测EAS异常事件。
EES检测EAS异常事件，可以包括EES从EEC收到EAS发现请求，但EES没有查找到满足条件的EAS，或者EES从EEC收到注册请求，但EES没有查找到满足条件的EAS。前述满足条件可以是指满足UE想要访问的应用的需求。或者，EES可以监测EAS的性能变化。如，EAS是否发生过载或宕机等。
ECS检测EAS异常事件，可以包括ECS从EES收到EES发现请求，但ECS没有查找到满足条件的EES，或者ECS从EEC收到服务配置请求，但ECS没有查找到满足条件的EES。前述满足条件的EES可以是指EES中部署了满足UE想要访问的应用的需求的EAS。
S403：EES或ECS给管理系统或ASP发送第一信息，将检测到的EAS异常事件发送给管理系统或ASP。或者，可以将EAS的性能携带在第一信息中发送给管理系统或ASP。
若S401执行了，则EES或ECS可以直接向管理系统发送上述第一信息。
在一个示例中，如果EES或ECS可以检测到EAS异常事件就上报，则第一信息中可以不包含EAS异常事件的发生次数，或者可以默认为发生次数是1次。
另一个示例中，如果EES或ECS检测到多次EAS异常事件时才上报，则第一信息中包含EAS异常事件的发生次数。
S404：ASP或管理系统根据本地策略，确定是否在对应的网络里实例化EAS。
例如，ASP或者管理系统可以确定上述EAS异常事件或者EAS性能是否满足第一条件，具体可以参见上述第一条件中的相关描述，此处不再赘述。
可选的，如果EES或ECS向ASP发送第一信息，ASP可以在确定EAS异常事件或EAS性能满足第一条件时，向管理系统发送实例化EAS请求。其中，实例化EAS请求中可以包含应用信息和网络信息，用于确定在哪个网络部署哪个应用的EAS。
S405：管理系统在EDN网络里实例化EAS。
管理系统可以根据应用信息和网络信息，在网络信息指示的EDN网络实例化应用信息指示的应用的EAS。管理系统可以为该EAS分配应用所需的虚拟机资源、内存、CPU和带宽等，本申请对实例化EAS的操作不做具体限定。
例如，管理系统可能先发消息给边缘网络的管理网元，比如MEC平台管理(MEC Platform management，MEPM)，再由边缘网络的管理网元与EES或MEP交互，实例化EAS。
S406：管理系统向EES或ECS发送第二信息，通知EES或ECS EAS实例化成功。
可选的，管理系统先通知给ASP EAS实例化成功，再由ASP通知EES或ECS EAS实例化成功。需要说明的是，图4中示出的通知EES或ECS EAS实例化成功的流程仅是示例性的。
可选的，还可以执行S407。
S407：EES可向EEC发送新实例化EAS的信息；或者，由于EES上部署了新的EAS，ECS可向EEC发送EES信息，EEC收到EES信息后可向该EES发送EAS发现请求。
基于上述方案，通过定义EES或ECS的检测机制，向管理系统上报事件，管理系统能基于上报事件确定是否动态实例化EAS，管理系统按需部署EAS，能显著提升运维管理的效率。
参阅图5，本申请提供另一种实例化EAS的方法。图5为本申请实施例提供的又一实例化EAS的方法的示例性流程图，可以包括以下操作。
S501：第二网元检测第一事件。
其中，第二网元可以是EES或者ECS，第一事件可以参见上述图3示出的方法实施例中的相关说明，此处不再赘述。
S502：第二网元向一个或多个终端发送指示信息。
上述一个或多个终端可以是终端中的EEC功能模块。
EES可以在未查找到可用的EAS，或者EAS过载或宕机时向EEC发送指示信息。ECS可以在未查找到可用的EES，或者EAS过载或宕机时向EEC发送指示信息。
其中，指示信息可以用于指示EAS查找失败或EES查找失败，或者可以用于指示EEC注册失败，或者指示信息可以用于显示指示UE想要访问的第一应用需要动态实例化EAS，或者指示信息用于指示当前EDN中部署的EAS的性能不能满足UE请求的性能需求。
S503：一个或多个终端向第一网元发送第一请求信息。
可选的，EEC可以将指示信息发送给AC。上述第一网元可以是ASP、管理系统或者可以是用户应用生命周期代理(user app LCM proxy，UEAPPLCM proxy)。前述UEAPPLCM proxy可以供用户请求应用相关的实例化和终止等服务的实体。
上述第一请求信息可以包括网络信息、应用信息和终端标识。其中，终端标识可以是用户永久标识符(subscription permanent identifier，SUPI)或通用公共用户标识(generic public subscription identifier，GPSI)等，可以用于确定是哪个UE想要访问第一应用。
S504：第一网元根据第一请求信息确定是否在第一网络中实例化第一应用的EAS。
第一网元基于本地策略或者配置，确定是否在第一网络中实例化第一应用的EAS。例如，如果想要访问第一应用的UE数量达到第一阈值，则可以确定在第一网络中实例化第一应用的EAS。其中，UE数量可以通过第一网元接收到的终端标识的数量确定，如果终端标识的数量达到第一阈值，则可以认为想要访问第一应用的UE数量达到第一阈值。又例如，第一网元根据第一请求的次数确定达到第二阈值，则可以认为想要访问第一应用的需求较大，从而确定在第一网络中实例化第一应用的EAS。上述第一阈值和第二阈值可以是根据经验值预先确定的，如1或5等，本申请不做具体限定。
或者，如果终端标识所标识的终端的签约等级高于或等于指定等级，则可以确定在第一网络中实例化第一应用的EAS。其中，第一请求信息中可以包含终端标识所标识的终端 的签约等级。或者，第一网元可以存储终端标识与签约等级的对应关系，第一网元可以在存储的对应关系中确定第一请求信息中包含的终端标识所对应的签约等级是否高于或等于指定等级。
在一个示例中，管理系统可以预先从ASP获取允许实例化的应用安装信息，也就是管理系统可以获得允许实例化的应用的授权。其中，应用安装信息可以包含应用标识、应用描述文件等信息。如果管理系统获得允许实例化的应用的授权，那么终端可以向管理系统发送第一请求信息。管理系统可以根据第一请求信息确定是否在第一网络中实例化第一应用的EAS。如果管理系统确定在第一网络中实例化第一应用的EAS，则可以执行S505，否则管理系统执行S507。
另一个示例中，如果管理系统未获得允许实例化的应用安装信息，那么终端可以向ASP或UEAPPLECM proxy发送第一请求信息。ASP或UEAPPLECM proxy可以根据第一请求信息确定是否在第一网络中实例化第一应用的EAS。如果ASP或UEAPPLCM proxy确定在第一网络中实例化第一应用的EAS，则可以向管理系统发送第二请求信息。该第二请求信息中可以包含上述应用信息和网络信息。由管理系统在第一网络中实例化能够第一应用提供服务的EAS，即执行S505。果ASP或UEAPPLCM proxy确定不在第一网络中实例化第一应用的EAS，ASP或UEAPPLCM proxy执行S507。
S505：第一网元在第一网络中实例化能够为第一应用提供服务的EAS。
第一网元实例化EAS的操作可以参见前述相关描述，此处不再赘述。
S506：第一网元向一个或多个终端发送第二信息。
其中，上述第二信息用于指示EAS实例化成功。可选的，管理系统或ASP或UEAPPLCMA proxy可以先通知EEC EAS实例化成功，再由EEC通知AC EAS实例化成功。
在一个示例中，如果一个或多个终端向管理系统发送第一请求信息，那么管理系统在实例化EAS后，可以向一个或多个终端发送第二信息。
另一个示例中，如果一个或多个终端向ASP或UEAPPLCM proxy发送第一请求信息，那么管理系统在实例化EAS后，可以向ASP或UEAPPLCM proxy发送第二信息，由ASP或UEAPPLCM proxy向一个或多个终端发送第二信息。
S507：第一网元向一个或多个终端发送第三信息。
其中，该第三信息可以用于指示在第一网络中未查找到第一应用的EAS。
需要说明的是，如果一个或多个终端向管理系统发送第一请求信息，则由管理系统向一个或多个终端发送第三信息。如果一个或多个终端向ASP或UEAPPLCM proxy发送第一请求信息，则由ASP或UEAPPLCM proxy向一个或多个终端发送第三信息。
基于上述方案，管理系统可以按照UE的需求实例化EAS，能够为用户提供差异化的服务体验，提升运维管理的效率。
以下，通过图6对本申请实施例提供的实例化EAS的方法进行详细介绍。
参阅图6，为本申请实施例提供的又一实例化EAS的方法的示例性流程图，可以包括以下操作。
可选的，S600与S401相同。
S601：EEC向EES发送EAS发现请求或者注册请求。
其中，EAS发现请求或者注册请求中可以包含应用信息。
或者，EEC向ECS发送服务配置请求，服务配置请求中包含应用信息。
S602与S402相同。
S603：EES或ECS向EEC发送指示信息。
其中，指示信息可以用于指示需要实例化EAS，具体可以参见图5所示的方法实施例中的相关描述，此处不再赘述。
可选的，EEC可以执行下述操作S604：
S604：EEC将指示信息发送给AC。
S605：EEC向UEAPPLCM proxy/ASP/管理系统发送实例化EAS请求。
其中，实例化EAS请求中可能包含网络标识或位置标识、应用信息和UE标识等，具体可以参见图3-图5所示的方法实施例中的相关描述，此处不再赘述。
在一个示例中，AC可以先将实例化EAS请求发送到EEC，再由EEC将实例化EAS请求发送给ASP或UEAPPLCM proxy。并由ASP或UEAPPLCM proxy将实例化EAS请求发送给管理系统。其中，该实例化EAS请求中可以包含网络信息和应用信息，可以不包含终端标识。
另一个示例中，由AC将实例化EAS请求发送给ASP或user app LCM proxy。
再一个示例中，如果上述操作S600已执行，AC/EEC可以将实例化EAS请求发送给管理系统。
S606：UEAPPLCM proxy/ASP/管理系统对实例化EAS请求进行验证授权。
比如，基于本地策略或配置，确定请求是否合理，具体可以参见图5所示的方法实施例中的相关描述，此处不再赘述。
可选的，如果AC/EEC将实例化EAS请求发送给ASP或UEAPPLCM proxy，则可以由ASP或UEAPPLCM proxy对实例化EAS请求进行验证授权。在验证通过后，可以执行下述操作S607。
S607：UEAPPLCM proxy/ASP向管理系统发送携带网络信息和应用信息的实例化EAS请求。
如果AC/EEC将实例化EAS请求发送给管理系统，则可以由管理系统对实例化EAS请求进行验证。其中，管理系统可能包含运营支撑系统(operation support system，OSS)、MEC编排器(MEC orchestrator，MEO)和MEPM等网元。
S608与S405相同。
S609：UEAPPLCM proxy/ASP/管理系统向AC/EEC发送第二信息，通知AC/EEC EAS实例化成功。
在一个示例中，可以由管理系统通知UEAPPLCM proxy/ASP EAS实例化成功，再由UEAPPLCM proxy/ASP通知EEC/AC EAS实例化成功。
另一个示例中，可以先通知EEC EAS实例化成功，由EEC通知给AC EAS实例化成功，或者，可以先通知AC EAS实例化成功，由AC通知给EEC EAS实例化成功。
需要说明的是，图6示出的通知AC/EEC EAS实例化成功的流程仅是示例性的。
可选的，可以执行下述操作S610。
S610：EEC可重新发送S601中的请求。
基于上述方案，UE向UEAPPLCM proxy或ASP或管理系统发送动态实例化EAS请求，能为用户提供差异化的服务体验，管理系统按需部署EAS，提升运维管理的效率。
图7和图8为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中第一网元、第二网元或终端的功能，因此也能实现上述方法实施例所具备的有益效果。
如图7所示，通信装置700包括处理单元710和收发单元720。通信装置700用于实现上述图3或图5中所示的方法实施例中第一网元、第二网元或终端的功能。
当通信装置700用于实现图3所示的方法实施例中第一网元的功能时：收发单元用于接收来自第二网元的第一信息，第一信息包括网络信息和应用信息，网络信息用于指示第一网络，应用信息用于指示第一应用，第一信息还包括第一网络中的关于第一应用的第一事件的信息；第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个。处理单元，用于确定在第一事件满足第一条件时，在第一网络中实例化第一应用对应的第一边缘应用服务器。
当通信装置700用于实现图5所示的方法实施例中第一网元的功能时：收发单元用于接收来自一个或多个终端的第一请求信息，第一请求信息用于请求实例化边缘应用服务器；第一请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送第一请求信息的终端；处理单元，用于根据第一请求信息确定是否在第一网络中实例化第一应用对应的边缘应用服务器。
当通信装置700用于实现图3所示的方法实施例中第二网元的功能时：处理单元用于检测第一事件；第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个；收发单元，用于根据检测到的第一事件向第一网元发送第一信息或者向一个或多个终端发送指示信息；第一信息包括网络信息和应用信息，指示信息用于指示需要实例化边缘应用服务器；网络信息用于指示第一网络，应用信息用于指示第一应用。
当通信装置700用于实现图5所示的方法实施例中终端的功能时：收发单元用于从边缘使能服务器或边缘网络配置服务器接收指示信息，指示信息用于指示边缘应用服务器查找失败或边缘使能客户端注册失败或需要实例化边缘应用服务器。处理单元，用于根据指示信息生成请求信息。请求信息中包含网络信息、应用信息和终端标识；网络信息用于指示第一网络，应用信息用于指示第一应用，终端标识用于标识发送请求信息的终端。收发单元，还用于向第一网元发送请求信息。
有关上述处理单元710和收发单元720更详细的描述可以直接参考图3或图4所示的方法实施例中相关描述直接得到，这里不加赘述。
如图8所示，通信装置800包括处理器810和接口电路820。处理器810和接口电路820之间相互耦合。可以理解的是，接口电路820可以为收发器或输入输出接口。可选的，通信装置800还可以包括存储器830，用于存储处理器810执行的指令或存储处理器810运行指令所需要的输入数据或存储处理器810运行指令后产生的数据。
当通信装置800用于实现图3或图5所示的方法时，处理器810用于实现上述处理单元710的功能，接口电路820用于实现上述收发单元720的功能。
当上述通信装置为应用于终端的芯片时，该终端芯片实现上述方法实施例中终端的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收信息，该信息是第一网元 发送给终端的；或者，该终端芯片向终端中的其它模块(如射频模块或天线)发送信息，该信息是终端发送给第一网元的。
当上述通信装置为应用于第一网元的模块时，该第一网元模块实现上述方法实施例中第一网元的功能。该第一网元模块从第一网元中的其它模块(如射频模块或天线)接收信息，该信息是终端或第二网元发送给第一网元的；或者，该第一网元模块向第一网元中的其它模块(如射频模块或天线)发送信息，该信息是第一网元发送给终端或第二网元的。
当上述通信装置为应用于第二网元的模块时，该第二网元模块实现上述方法实施例中第二网元的功能。该第二网元模块从第二网元中的其它模块(如射频模块或天线)接收信息，该信息是第一网元发送给第二网元的；或者，该第一网元模块向第一网元中的其它模块(如射频模块或天线)发送信息，该信息是第二网元发送给第一网元的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一网元、第二网元或终端中。当然，处理器和存储介质也可以作为分立组件存在于第一网元、第二网元或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描 述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。“包括A，B和C中的至少一个”可以表示：包括A；包括B；包括C；包括A和B；包括A和C；包括B和C；包括A、B和C。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (27)

  1. 一种实例化边缘应用服务器的方法，其特征在于，包括：
    第一网元接收来自第二网元的第一信息，所述第一信息包括网络信息和应用信息，所述网络信息用于指示第一网络，所述应用信息用于指示第一应用，所述第一信息还包括所述第一网络中的关于所述第一应用的第一事件的信息；所述第一事件包括在所述第一网络中未查找到对应所述第一应用的边缘应用服务器、在所述第一网络里未查找到对应所述第一应用的边缘使能服务器和所述第一网络中的对应所述第一应用的边缘应用服务器的性能信息中的至少一个；
    所述第一网元确定在所述第一事件满足第一条件时，在所述第一网络中实例化所述第一应用对应的第一边缘应用服务器。
  2. 根据权利要求1所述的方法，其特征在于，在所述第一事件包括在所述第一网络中未查找到对应所述第一应用的边缘应用服务器时，所述第一条件包括在第一时长内在所述第一网络中未查找到对应所述第一应用的边缘应用服务器的次数大于或等于第一阈值；或，
    在所述第一事件包括在所述第一网络里未查找到对应所述第一应用的边缘使能服务器时，所述第一条件包括在第二时长内在所述第一网络里未查找到对应所述第一应用的边缘使能服务器的次数大于或等于第二阈值；或，
    在所述第一事件包括所述第一网络中的对应所述第一应用的边缘应用服务器的性能信息时，所述第一条件包括边缘应用服务器的负载大于或等于第三阈值和边缘应用服务器宕机中的至少一个。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述第一网元为应用服务提供商时，所述在所述第一网络中实例化所述第一应用对应的第一边缘应用服务器，包括：
    所述第一网元向管理系统发送实例化边缘应用服务器请求，所述实例化边缘应用服务器请求用于实例化边缘应用服务器，所述实例化边缘应用服务器请求中包含所述网络信息和所述应用信息。
  4. 根据权利要求1～3任一所述的方法，其特征在于，所述第一信息还包括所述第一事件的发生次数。
  5. 根据权利要求2所述的方法，其特征在于，所述在所述第一网络里未查找到对应所述第一应用的边缘应用服务器的次数是所述第一网元接收所述第一信息的次数；或者，
    所述在所述第一网络里未查找到对应所述第一应用的边缘使能服务器的次数是所述第一网元接收所述第一信息的次数。
  6. 根据权利要求1～5任一所述的方法，其特征在于，在所述第一网元为管理系统时，所述第一网元在所述第一网络中实例化所述第一应用对应的第一边缘应用服务器之前，还包括：
    所述第一网元从应用服务提供商获取一个或多个允许实例化的应用安装信息。
  7. 根据权利要求1～6任一所述的方法，其特征在于，还包括：
    所述第一网元向所述第二网元发送第二信息，所述第二信息用于指示所述第一边缘应用服务器实例化成功。
  8. 根据权利要求1～7任一所述的方法，其特征在于，还包括：
    所述第一网元向第二网元发送订阅请求，所述订阅请求用于订阅所述第一信息。
  9. 一种实例化边缘应用服务器的方法，其特征在于，包括：
    第二网元检测第一事件；所述第一事件包括在第一网络中未查找到对应第一应用的边缘应用服务器、在第一网络里未查找到对应第一应用的边缘使能服务器和第一网络中的对应第一应用的边缘应用服务器的性能信息中的至少一个；
    所述第二网元根据检测到的所述第一事件向第一网元发送第一信息或者向一个或多个终端发送指示信息；所述第一信息包括网络信息和应用信息，所述指示信息用于指示需要实例化边缘应用服务器；所述网络信息用于指示所述第一网络，所述应用信息用于指示所述第一应用。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    所述第二网元接收第二信息，所述第二信息用于指示第一边缘应用服务器实例化成功，所述第一信息用于实例化所述第一边缘应用服务器的判断。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第一信息还包括所述第一事件的发生次数。
  12. 根据权利要求9所述的方法，其特征在于，所述指示信息用于指示需要实例化边缘应用服务器，还包括：所述指示信息为指示边缘应用服务器查找失败，或边缘使能客户端注册失败，或在所述第一网络中未查找到对应第一应用的边缘应用服务器。
  13. 一种实例化边缘应用服务器的方法，其特征在于，包括：
    第一网元接收来自一个或多个终端的第一请求信息，所述第一请求信息用于请求实例化边缘应用服务器；所述第一请求信息中包含网络信息、应用信息和终端标识；所述网络信息用于指示第一网络，所述应用信息用于指示第一应用，所述终端标识用于标识发送所述第一请求信息的终端；
    所述第一网元根据所述第一请求信息确定是否在所述第一网络中实例化所述第一应用对应的边缘应用服务器。
  14. 根据权利要求13所述的方法，其特征在于，所述第一网元根据所述第一请求信息确定是否在所述第一网络中实例化所述第一应用对应的边缘应用服务器，包括：
    在所述第一请求的数量达到第一阈值时，确定在所述第一网络中实例化所述第一应用对应的边缘应用服务器；和/或，
    在所述终端标识所标识的终端的签约等级高于或等于指定等级时，确定在所述第一网络中实例化所述第一应用对应的边缘应用服务器。
  15. 根据权利要求14所述的方法，其特征在于，在所述第一网元是应用服务提供商时，所述第一网元确定在所述第一网络中实例化所述第一应用对应的边缘应用服务器，包括：
    所述第一网元向管理系统发送第二请求信息；其中，所述第二请求信息用于请求实例化边缘应用服务器，所述第二请求信息包含所述网络信息和所述应用信息。
  16. 根据权利要求13～15任一所述的方法，其特征在于，所述网络信息包括网络标识和位置标识中的至少一个；所述网络标识和位置标识用于标识所述第一网络，所述应用信息包括应用标识和应用性能需求中的至少一个。
  17. 根据权利要求14所述的方法，其特征在于，在所述第一网元为管理系统时，所述 第一网元确定在所述第一网络中实例化所述第一应用对应的边缘应用服务器之前，还包括：
    所述第一网元从应用服务提供商获取允许实例化的应用安装信息。
  18. 根据权利要求13～17任一所述的方法，其特征在于，还包括：
    所述第一网元发送第二信息，所述第二信息用于指示所述第一应用的边缘应用服务器实例化成功。
  19. 根据权利要求13～18任一所述的方法，其特征在于，所述第一网元根据所述第一请求确定是否在第一网络中实例化所述第一应用的边缘应用服务器，包括：
    在所述第一请求的数量未达到第一阈值时，向所述一个或多个终端发送第三信息；所述第三信息用于指示在所述第一网络中未查找到所述第一应用的边缘应用服务器；和/或，
    在所述终端标识所标识的终端的签约等级低于指定等级时，向所述一个或多个终端发送第三信息；所述第三信息用于指示在所述第一网络中未查找到所述第一应用的边缘应用服务器。
  20. 一种实例化边缘应用该服务器的方法，其特征在于，包括：
    边缘使能客户端从边缘使能服务器或边缘网络配置服务器接收指示信息，所述指示信息用于指示边缘应用服务器查找失败或所述边缘使能客户端注册失败或需要实例化边缘应用服务器；
    所述边缘使能客户端根据所述指示信息向第一网元发送请求信息，所述请求信息中包含网络信息和应用信息；所述网络信息用于指示第一网络，所述应用信息用于指示第一应用。
  21. 根据权利要求20所述的方法，其特征在于，还包括：
    所述边缘使能客户端向应用客户端发送所述指示信息。
  22. 根据权利要求21所述的方法，其特征在于，还包括：
    所述边缘使能客户端接收来自所述应用客户端的所述请求信息。
  23. 根据权利要求20～22任一所述的方法，其特征在于，还包括：
    所述边缘使能客户端接收来自所述第一网元的第二信息，所述第二信息用于指示所述第一应用的边缘应用服务器实例化成功。
  24. 一种通信装置，其特征在于，用于执行如权利要求1～8任一所述的方法，或者用于执行如权利要求9～12任一所述的方法，或者用于执行如权利要求13～19任一所述的方法，或者用于执行如权利要求20～23任一所述的方法。
  25. 一种通信装置，其特征在于，包括：处理器和存储器，
    所述存储器，用于存储计算机程序或指令；
    所述处理器，用于执行存储器中的计算机程序或指令，使得权利要求1～8中任一项所述的方法被执行或者使得权利要求9～12任一项所述的方法被执行或者使得权利要求13～19任一项所述的方法被执行或者使得权利要求20～23任一项所述的方法被执行。
  26. 一种计算机存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令在被计算机调用时，使所述计算机执行如权利要求1～8任一项所述的方法或者执行如权利要求9～12任一项所述的方法或者执行如权利要求13～19任一项所述的方法或者执行如权利要求20～23任一项所述的方法。
  27. 一种计算机程序产品，其特征在于，包含计算机可执行指令，当所述指令在计算机上运行时，使得如权利要求1～8中任一项所述的方法被执行；或者如权利要求9～12中任一项所述的方法被执行；或者如权利要求13～19中任一项所述的方法被执行；或者如权利要求20～23中任一项所述的方法被执行。
PCT/CN2022/103709 2021-07-07 2022-07-04 一种实例化边缘应用服务器的方法和装置 Ceased WO2023280118A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP22836869.2A EP4354815B1 (en) 2021-07-07 2022-07-04 INSTANCIATING A PERIPHERAL APPLICATION SERVER
CN202280045495.2A CN117561703A (zh) 2021-07-07 2022-07-04 一种实例化边缘应用服务器的方法和装置
JP2024500144A JP7744060B2 (ja) 2021-07-07 2022-07-04 エッジ・アプリケーション・サーバーをインスタンス化する方法及び装置
US18/405,034 US20240235929A9 (en) 2021-07-07 2024-01-05 Method for instantiating edge application server and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110766584.3 2021-07-07
CN202110766584.3A CN113630266B (zh) 2021-07-07 2021-07-07 一种实例化边缘应用服务器的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/405,034 Continuation US20240235929A9 (en) 2021-07-07 2024-01-05 Method for instantiating edge application server and apparatus

Publications (1)

Publication Number Publication Date
WO2023280118A1 true WO2023280118A1 (zh) 2023-01-12

Family

ID=78379177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103709 Ceased WO2023280118A1 (zh) 2021-07-07 2022-07-04 一种实例化边缘应用服务器的方法和装置

Country Status (5)

Country Link
US (1) US20240235929A9 (zh)
EP (1) EP4354815B1 (zh)
JP (1) JP7744060B2 (zh)
CN (2) CN113630266B (zh)
WO (1) WO2023280118A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024237677A1 (en) * 2023-05-16 2024-11-21 Samsung Electronics Co., Ltd. Method and apparatus for communication between application client (ac) and edge enabler client (eec) in a wireless communication system

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114079618B (zh) * 2020-08-12 2024-09-03 华为技术有限公司 一种通信方法和通信装置
CN113630266B (zh) * 2021-07-07 2023-04-28 华为技术有限公司 一种实例化边缘应用服务器的方法和装置
CN113840293B (zh) * 2021-08-18 2023-04-18 华为技术有限公司 获取边缘服务的方法和装置
US20240430781A1 (en) * 2021-11-09 2024-12-26 Interdigital Patent Holdings, Inc. Methods and apparatuses for enabling wireless transmit/receive unit (wtru)-based edge computing scaling
KR102849781B1 (ko) * 2022-03-24 2025-08-22 인터디지탈 패튼 홀딩스, 인크 공유 애플리케이션 수직 세션 기반 에지 애플리케이션 인스턴스 발견 및 선택
CN116939008A (zh) * 2022-03-29 2023-10-24 华为技术有限公司 一种通信方法、装置及设备
CN117295047A (zh) * 2022-06-24 2023-12-26 华为技术有限公司 一种通信方法及装置
CN118265009A (zh) * 2022-12-26 2024-06-28 中国移动通信有限公司研究院 提供无线服务的方法、装置、相关设备及存储介质
KR102786899B1 (ko) * 2023-01-06 2025-03-26 삼성전자 주식회사 무선 통신시스템을 통한 에지 컴퓨팅 서비스 정보 제공 방법
CN118945140B (zh) * 2023-05-10 2025-12-12 中国电信股份有限公司 基于算力的边缘应用寻址方法、装置、设备及介质
CN119966995A (zh) * 2023-11-07 2025-05-09 华为技术有限公司 一种边缘应用服务器发现方法及装置
CN121418786A (zh) * 2024-07-25 2026-01-27 华为技术有限公司 一种通信方法及相关装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210111953A1 (en) * 2019-10-09 2021-04-15 Qualcomm Incorporated Edge discovery techniques in wireless communications systems
CN113630266A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种实例化边缘应用服务器的方法和装置
US20210352156A1 (en) * 2020-05-08 2021-11-11 Samsung Electronics Co., Ltd. Method and apparatus for managing information related to edge computing service

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11310148B2 (en) * 2019-06-03 2022-04-19 At&T Intellectual Property I, L.P. Methods, systems, and computer programs for intelligent content delivery using a software defined network and edge computing
KR20220070266A (ko) * 2019-09-25 2022-05-30 삼성전자주식회사 에지 컴퓨팅을 위한 분산된 탐색 및 통지를 위한 방법 및 시스템
US20210117859A1 (en) * 2019-10-20 2021-04-22 Nvidia Corporation Live updating of machine learning models
CN113068232B (zh) * 2020-01-02 2022-06-07 大唐移动通信设备有限公司 一种边缘应用服务器的切换方法及装置
GB2592300B (en) * 2020-01-15 2023-03-29 Samsung Electronics Co Ltd Improvements in and relating to a multi-access edge computing (MEC) network
WO2022041205A1 (zh) * 2020-08-31 2022-03-03 华为技术有限公司 通信方法及多接入边缘计算服务器
CN112631753B (zh) * 2020-12-29 2024-03-22 深圳艾灵网络有限公司 一种任务卸载方法、设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210111953A1 (en) * 2019-10-09 2021-04-15 Qualcomm Incorporated Edge discovery techniques in wireless communications systems
US20210352156A1 (en) * 2020-05-08 2021-11-11 Samsung Electronics Co., Ltd. Method and apparatus for managing information related to edge computing service
CN113630266A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种实例化边缘应用服务器的方法和装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP TSG SA: ""Architecture for Enabling Edge Applications; (Release 17)"", 3GPP TS 23.558 V17.0.0, 28 June 2021 (2021-06-28), XP052029833 *
3GPP TSG SA: ""Management and Orchestration; Study on Enhancements of Edge Computing Management(Release 17)"", 3GPP TR 28.814 V1.0.0, 8 June 2021 (2021-06-08), XP052029496 *
SAMSUNG: ""Resolve EN on Dynamic EAS Instantiation"", 3GPP TSG-SA WG6 MEETING #43 S6-211170, 19 May 2021 (2021-05-19), XP052012634 *
See also references of EP4354815A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024237677A1 (en) * 2023-05-16 2024-11-21 Samsung Electronics Co., Ltd. Method and apparatus for communication between application client (ac) and edge enabler client (eec) in a wireless communication system

Also Published As

Publication number Publication date
CN113630266B (zh) 2023-04-28
EP4354815A1 (en) 2024-04-17
EP4354815A4 (en) 2024-10-30
JP2024524536A (ja) 2024-07-05
CN113630266A (zh) 2021-11-09
US20240235929A9 (en) 2024-07-11
EP4354815B1 (en) 2025-12-31
US20240137269A1 (en) 2024-04-25
JP7744060B2 (ja) 2025-09-25
CN117561703A (zh) 2024-02-13

Similar Documents

Publication Publication Date Title
CN113630266B (zh) 一种实例化边缘应用服务器的方法和装置
US12120092B2 (en) Security platform for service provider network environments
US11777994B2 (en) Dynamic per subscriber policy enablement for security platforms within service provider network environments
EP3920562B1 (en) Methods and system for performing charging processing on network slice client, and related devices
WO2020057163A1 (zh) Mec平台部署方法及装置
KR20200012945A (ko) 서비스 발견을 위한 방법, 등록 센터 및 디바이스
CN113891430A (zh) 一种通信的方法、装置及系统
US20230076228A1 (en) Method of enablement of service api exposed by eas and devices for performing the same
WO2020015634A1 (zh) 一种mec信息获取方法及装置
US11750708B2 (en) Method and device for proxy between different architectures
JP2023519873A (ja) 接続確立方法、通信装置、およびシステム
JP2019525604A (ja) ネットワーク機能ｎｆ管理方法及びｎｆ管理装置
US12200585B2 (en) Method of performing dynamic edge application server (EAS) instantiation triggering and apparatus for performing the same
US20250126178A1 (en) Communication method and apparatus
US20250227461A1 (en) Base station device and method for operating base station device
CN105191226B (zh) 用于基于服务意识调节专用信道的服务质量的方法和布置
KR20230157869A (ko) 동적 eas 인스턴스화 트리거링을 수행하는 방법 및 이를 수행하는 장치
US20240248777A1 (en) Method for enablement of service api exposed by eas and a device performing the same
AU2023286920B2 (en) Communication method and apparatus
US20250286832A1 (en) Communication method, apparatus, and system, storage medium, and program product
GB2641386A (en) Method, apparatus and computer program
WO2025153427A1 (en) Discovery of masque endpoints in a communications network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22836869

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280045495.2

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2024500144

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2022836869

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022836869

Country of ref document: EP

Effective date: 20240112

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2022836869

Country of ref document: EP