Communication method and device

Abstract

A communication method and apparatus are provided. The method includes: a step in which an edge configuration server receives a request message, where the request message is used to request information about an edge enabler server and the request message includes an identifier of a first edge application server; a step in which the edge configuration server determines a first edge enabler server based on status information of a plurality of first edge application servers, where the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated; and a step in which the edge configuration server sends a response message, where the response message includes information about the first edge enabler server. Only information about one first edge enabler server is sent, so that only the first edge application server on the first edge enabler server can be instantiated, avoiding the problem of waste of edge data network resources caused by instantiation of unnecessary edge application servers.

Description

【Technical Field】 【0001】 Cross - reference to Related Applications This application claims priority to Chinese Patent Application No. 202210731521.9, titled "Communication Method and Apparatus", filed with the China National Intellectual Property Administration on June 24, 2022, the entire content of which is incorporated herein by reference, and claims priority to Chinese Patent Application No. 202211218366.7, titled "Communication Method and Apparatus", filed with the China National Intellectual Property Administration on October 3, 2022, the entire content of which is incorporated herein by reference. 【0002】 Embodiments of this application relate to the field of wireless communication, and in particular, to communication methods and apparatuses. 【Background Art】 【0003】 Mobile Edge Computing (MEC), also known as multi - access edge computing, can use a wireless access network to provide services and cloud computing functions close to what users need. In other words, MEC can accelerate the high - speed download of various contents, services, and applications on the network, and provide a carrier - class service environment with high performance, low latency, and high bandwidth so that users can enjoy a high - quality network experience without interruption. 【0004】 For example, multiple edge application servers (EAS) may be deployed in an edge data network (EDN), and a terminal device can access a nearby EAS to obtain the corresponding application service. In this way, high bandwidth can be obtained, the response latency can be shortened, and the user's requirements for the application service can be met. 【0005】 Furthermore, to allow terminal devices to determine which EAS needs to be accessed, a two-stage EAS discovery mechanism currently exists. For example, an edge enabler client (EEC) first discovers an edge enabler server (EES) via an edge configuration server (ECS), and then the EEC discovers the EAS from the EES. In other words, the EES must be discovered first before the EAS is discovered. Therefore, how to select the appropriate EES is a noteworthy issue. [Overview of the Initiative] [Means for solving the problem] 【0006】 This application provides a communication method and apparatus for selecting an appropriate EES. 【0007】 According to a first aspect, the present application provides a communication method. The method includes: a step of an edge configuration server receiving a request message, the request message being used to request information about an edge enabler server, the request message including an identifier for a first edge application server; a step of the edge configuration server determining a first edge enabler server based on status information of a plurality of first edge application servers, the status of the first edge application server corresponding to the first edge enabler server being instantiable but not yet instantiated; and a step of the edge configuration server sending a response message, the response message including information about the first edge enabler server. 【0008】 According to the design described above, the edge configuration server can determine one first edge enabler server based on the status information of multiple first edge application servers, the status of the first edge application server corresponding to the first edge enabler server in this specification being instantiable but not yet instantiated. In other words, the edge configuration server selects only one first edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. Therefore, the edge configuration server can then send only an edge application server discovery request message to the first edge enabler server. In this way, only the first edge application server on the first edge enabler server can be instantiated, but not all first edge enabler servers on multiple edge enabler servers can be instantiated, and as a result, the problem of wasted edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided. 【0009】 In a possible design, the status information for the first edge application server would indicate whether the first edge application server is instantiated or can be instantiated but has not yet been instantiated. 【0010】 In a possible design, the edge configuration server retrieves status information for multiple first edge application servers from multiple edge enabler servers. 【0011】 For example, the edge configuration server can obtain status information of the first edge application server from the edge enabler server using a registration request message or a registration update message. 【0012】 In a possible design, the edge configuration server determines, based on the status information of multiple first edge application servers, that there are no first edge application servers with an instantiated status, before determining one first edge enabler server based on the status information of multiple first edge application servers. 【0013】 For example, an edge configuration server can determine, based on the status information of multiple first edge application servers, whether there are any first edge application servers whose status is instantiated. 【0014】 If it is determined that there is a first edge application server with an instantiated status, the edge configuration server can send information about the edge enabler server corresponding to that first edge application server with an instantiated status, and as a result, the edge enabler client or source edge enabler server can preferentially select the first edge application server that is instantiated and meets the conditions without instantiating a new edge application server. 【0015】 If it is determined that there are no first edge application servers with an instantiated status, the edge configuration server can determine one first edge enabler server based on the status information of multiple first edge application servers. Since the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated, if there are no first edge application servers with an instantiated status, it may be possible to instantiate a new first edge application server to provide the corresponding service application to terminal devices. 【0016】 In a possible design, the edge configuration server receives instruction information indicating that the instantiation of the first edge application server corresponding to the first edge enabler server has failed. The edge configuration server then sends information about one second edge enabler server other than the first edge enabler server, and the status of the first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated. 【0017】 According to the aforementioned design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, the edge configuration server can provide information about a new edge enabler server, indicating that the first edge application server corresponding to the edge enabler server is instantiable but has not yet been instantiated. 【0018】 It will be understood that the edge configuration server can receive instruction information from the edge enabler client and send information about a second edge enabler server to the edge enabler client. Alternatively, the edge configuration server can receive instruction information from the source edge enabler server and send information about a second edge enabler server to the source edge enabler server. 【0019】 In a possible design, when the edge configuration server receives a request message, it receives the request message from the edge enabler client, and when the edge configuration server sends a response message, it sends a response message to the edge enabler client. 【0020】 In a possible design, when the edge configuration server receives a request message, it receives the request message from the source edge enabler server, and when the edge configuration server sends a response message, it sends the response message to the source edge enabler server. 【0021】 According to a second aspect, the present application provides a communication method. The method includes the steps of: an edge configuration server receiving a request message, the request message being used to request information about an edge enabler server, the request message including an identifier for a first edge application server; and the edge configuration server sending a response message, the response message including information about at least one edge enabler server and status information for the first edge application server corresponding to each of the at least one edge enabler server. 【0022】 The status information of the first edge application server corresponding to at least one edge enabler server may be described as the status information of the first edge application server corresponding to at least one edge enabler server. 【0023】 According to the design described above, the edge configuration server can provide status information for a first edge application server corresponding to at least one edge enabler server, thereby assisting an edge enabler client or source edge enabler server in determining a single first edge enabler server. In this specification, the status of a first edge application server corresponding to a first edge enabler server is instantiable but not yet instantiated. In other words, the edge configuration server selects only one first edge enabler server. Therefore, the edge configuration server can then send only an edge application server discovery request message to the first edge enabler server. In this way, only the first edge application server on the first edge enabler server can be instantiated, but not all first edge enabler servers on multiple edge enabler servers can be instantiated, thus avoiding the problem of wasted edge data network resources caused by the instantiation of unnecessary edge application servers. 【0024】 In a possible design, the status information of a first edge application server, each corresponding to at least one edge enabler server, determines one first edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. 【0025】 In a possible design, the status information of the first edge application server indicates whether the status of the first edge application server is in an instantiated state or is instantiable but not yet instantiated. 【0026】 In a possible design, when the edge configuration server receives a request message, the edge configuration server receives the request message from the edge enabler client, and when the edge configuration server sends a response message, the edge configuration server sends the response message to the edge enabler client. 【0027】 In a possible design, when the edge configuration server receives a request message, the edge configuration server receives the request message from the source edge enabler server, and when the edge configuration server sends a response message, the edge configuration server sends the response message to the source edge enabler server. 【0028】 According to a third aspect, the present application provides a communication method. The method may be executed by an edge enable client or a source edge enable server. The method includes: sending a request message to an edge configuration server, where the request message is used to request information about an edge enable server, and the request message includes an identifier of a first edge application server; receiving a response message from the edge configuration server, where the response message includes information about at least one edge enable server and status information of the first edge application server corresponding to each of the at least one edge enable server; and determining one first edge enable server based on the status information of the first edge application server corresponding to each of the at least one edge enable server, where the status of the first edge application server corresponding to the first edge enable server is instantiable but not yet instantiated. 【0029】 The status information of the first edge application server corresponding to each of the at least one edge enable server may be described as the status information of the first edge application server corresponding to each of the at least one edge enable server. In addition, after the first edge enable server is determined, the edge enable client or the source edge enable server can send an edge application server discovery request message to the first edge enable server. 【0030】 According to the design described above, an edge enabler client or source edge enabler server can determine one first edge enabler server based on the status information of a first edge application server corresponding to at least one edge enabler server provided by the edge configuration server. In this specification, the status of a first edge application server corresponding to a first edge enabler server is instantiable but not yet instantiated. In other words, the edge configuration server selects only one first edge enabler server. Therefore, the edge configuration server can then send only an edge application server discovery request message to the first edge enabler server. In this way, only the first edge application server on the first edge enabler server can be instantiated, but not all first edge enabler servers on multiple edge enabler servers can be instantiated, and as a result, the problem of wasting edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided. 【0031】 In a possible design, the status information for the first edge application server would indicate whether the first edge application server is instantiated or can be instantiated but has not yet been instantiated. 【0032】 In a possible design, before determining one first edge enabler server based on the status information of the first edge application server corresponding to at least one edge enabler server, it is determined, based on the status information of the first edge application server corresponding to at least one edge enabler server, that there are no first edge application servers with an instantiated status. 【0033】 For example, an edge enabler client or source edge enabler server can determine whether there is a first edge application server whose status is instantiated, based on the status information of the first edge application server corresponding to at least one edge enabler server. 【0034】 If it is determined that there is a first edge application server whose status is instantiated, the edge enabler client or source edge enabler server may send an edge application server discovery request message to the edge enabler server corresponding to one or more first edge application servers whose status is instantiated, thereby allowing the edge enabler client or source edge enabler server to preferentially select a first edge application server that is instantiated and meets the conditions without instantiating a new edge application server. 【0035】 If it is determined that there is no first edge application server with an instantiated status, the edge enabler client or source edge enabler server can determine one first edge enabler server based on the status information of the first edge application server corresponding to at least one edge enabler server. Since the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated, if there is no first edge application server with an instantiated status, it may be possible to instantiate a new first edge application server to provide the corresponding service application to the terminal device. 【0036】 In a possible design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, a second edge enabler server other than the first edge enabler server is determined based on the status information of the first edge application servers corresponding to at least one edge enabler server, and the status of the first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated. 【0037】 According to the aforementioned design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, the edge enabler client or source edge enabler server can determine a new edge enabler server, and the first edge application server corresponding to the edge enabler server is instantiable but has not yet been instantiated. 【0038】 According to a fourth aspect, the present application provides a communication method. The method includes an edge enabler server obtaining status information of a first edge application server, and the edge enabler server transmitting the identifier of the first edge application server and the status information of the first edge application server to an edge configuration server. 【0039】 According to the design described above, the edge enabler server can obtain the identifier and status information of the first edge application server, and send the identifier and status information of the first edge application server to the edge configuration server. 【0040】 In a possible design, when the edge enabler server retrieves status information for the first edge application server, the edge enabler server retrieves status information for the first edge application server from the first edge application server, and the status information for the first edge application server indicates that the status of the first edge application server is instantiated. 【0041】 In a possible design, when the edge enabler server retrieves the status information for the first edge application server, it has already retrieved the status information for the first edge application server from the edge application server management system, and the status information for the first edge application server indicates that the first edge application server is instantiable but has not yet been instantiated. 【0042】 According to a fifth aspect, the present application further provides an apparatus capable of performing the method design described above. The apparatus may be a chip or circuit, or a device including a chip or circuit, capable of performing the function corresponding to the method described above. 【0043】 In a possible implementation, the device includes a processor and memory configured to store computer executable program code, the processor being coupled to the memory. The program code stored in memory includes instructions. When the processor executes an instruction, the device or the device on which the device is installed becomes capable of performing the method in any of the possible designs described above. 【0044】 The device may further include a communication interface. The communication interface may be a transceiver. Alternatively, if the device is a chip or circuit, the communication interface may be the chip's input / output interface, for example, input / output pins. 【0045】 In possible designs, the device includes corresponding functional units configured separately to perform the steps of the method described above. This functionality may be implemented by hardware or by running corresponding software in hardware. The hardware or software includes one or more units corresponding to the aforementioned functionality. 【0046】 According to a sixth aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed on the device, one of the methods of the possible designs described above is performed. 【0047】 According to the seventh aspect, the present application provides a computer program product, the computer program product comprising a computer program, which, when executed on a device, performs one of the methods of any of the possible designs described above. [Brief explanation of the drawing] 【0048】 [Figure 1] This is a schematic diagram of the edge computing application architecture and functional model of the application described in this application. [Figure 2] This is a flowchart of the EES discovery process based on this application. [Figure 3] This is a flowchart of the EAS discovery process according to this application. [Figure 4] This is flowchart 1, which requires EAS instantiation according to this application. [Figure 5] This is a flowchart showing how to initiate EAS discovery using S-EAS as described in this application. [Figure 6] This is a flowchart for performing T-EES detection using S-EES according to this application. [Figure 7] This is flowchart 2, which requires EAS instantiation according to this application. [Figure 8]This is flowchart 1 outlining the communication method in this application. [Figure 9] This is flowchart 2 outlining the communication method in this application. [Figure 10] This is Scenario 1 of the EAS discovery request message in this application. [Figure 11] This is scenario 2 of the EAS discovery request message according to this application. [Figure 12] This is scenario 3 of the EAS discovery request message according to this application. [Figure 13] This is a schematic diagram 1 of the structure of the communication device according to this application. [Figure 14] Figure 2 shows a schematic diagram of the structure of the communication device according to this application. [Modes for carrying out the invention] 【0049】 The technical solutions of the embodiments of this application will be described clearly and completely below with reference to the accompanying drawings of the embodiments of this application. It is clear that the embodiments described are only a part of, and not all, of, the embodiments of this application. In the specification, claims, and accompanying drawings of this application, “First,” “Second,” corresponding term numbers, etc., are intended to distinguish similar subjects and do not necessarily indicate a specific order or sequence. It should be understood that the terms used in this way are interchangeable in appropriate contexts and are merely a means of identification used when subjects having the same attributes are described in the embodiments of this application. Furthermore, the terms “include,” “contain,” and any other variations mean to cover non-exclusive inclusion, so that a process, method, system, product, or device including a set of units may include other units that are not explicitly enumerated or specific to such a process, method, system, product, or device, but are not necessarily limited to those units. 【0050】 In the description of this application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. In this application, "and / or" describes only the relating relationship to describe the related subjects, indicating that three relationships may exist. For example, A and / or B may represent the following three cases: the case where only A exists, the case where both A and B exist, and the case where only B exists. In addition, in the description of this application, "at least one item" means one or more items, and "multiple items" means two or more items. "At least one of the following items" or similar expressions means any combination of these, including any single item or any combination of multiple items. For example, at least one of a, b, or c may represent a, b, c, ab, ac, bc, or abc, where a, b, and c may be singular or plural. 【0051】 The functional entities in this application will be briefly described with reference to the edge computing application architecture and functional model shown in Figure 1. 【0052】 1. EDN: In a common understanding, an EDN corresponds to only one data network, a single special local data network (local DN). An EDN is a network logic concept that includes edge enabler functionality and can be identified by a data network access identifier (DNAI) and a data network name (DNN). Another understanding of an EDN is that it is a peer concept of a central cloud. An EDN may also be understood as a single local data center (a geographical location concept) that can be identified by a DNAI and can contain multiple local data networks. 【0053】 2.EAS: EAS refers to an application deployed on an edge data network, specifically an instance of a single server application program (e.g., social media software, augmented reality (AR), or virtual reality (VR)) deployed and running on the EDN. 【0054】 One or more EAS instances may be deployed to a single application on one or more EDNs. EAS instances deployed on different EDNs may be considered different EAS instances for the same application. EAS instances may share a single domain name, use a single IP address, or use different IP addresses. EAS instances may also be referred to as edge application instances, application instances, MEC applications (servers), EAS functionality, etc. 【0055】 3. Application client (AC): AC is the peer entity of EAS on the terminal device side. Application clients are the client programs of the application on the terminal side. Application clients may connect to an application server in the cloud to obtain application services, or they may connect to EAS deployed and running in one or more EDNs to obtain application services. 【0056】 4.EES: EES can provide several enabler functions to EAS deployed within the EDN to better support application deployment in the EDN. EES can support EAS registration, authentication and authorization of terminal devices, and provide EAS IP address information to terminal devices. EES can further support retrieving EAS identifier and IP address information, and further transmit EAS identifier and IP address information to ECS. EES is deployed within the EDN. 【0057】 Generally, an EAS is registered with one EES, or information about one EAS is configured on one EES using a management system (e.g., an EAS management system). An EES is referred to as an EES associated with an EAS. An EES can control, manage, or configure the EAS on the EES. 【0058】 5. Edge Enabler Client (EEC): The EEC is the peer entity of the EES on the terminal device side. The EEC is configured to register information about itself and the AC with the EES, perform security authentication and authorization, obtain the EAS's IP address from the EES, and provide edge computing enabler functionality to the AC. For example, the EAS discovery service returns the EAS's IP address to the AC. 【0059】 An application user enters into a service agreement with the application provider that provides services to the application user. The application user logs into the AC on the terminal device and communicates with the EAS using the connection between the AC and the EAS. The EEC is the middleware layer and is generally located within the operating system or between the AC and the operating system. The AC can obtain edge enabler services from the EEC via an application programming interface (API). 【0060】 6. Edge Configuration Server (ECS): The ECS is responsible for configuring the EDN. One or more EESs can be registered with the ECS, and then EES information can be provided to terminal devices. 【0061】 To facilitate understanding of the embodiments of this application, some basic concepts of the embodiments are briefly explained. 【0062】 1. The two-stage detection mechanism of EAS: The two-stage discovery mechanism of EAS may include, but is not limited to, the following two possible implementations: 【0063】 In the first possible implementation, the EEC first discovers the EES using the ECS corresponding to the EES discovery (also known as service provisioning) procedure, and then the EEC discovers the EAS from the EES corresponding to the EAS discovery procedure. 【0064】 Figure 2 shows the procedure for discovering EES. 【0065】 Step 201: The EEC sends an EES discovery request (also known as a service provisioning request) message to the ECS. 【0066】 For example, an EES discovery request message may include a user equipment (UE) identifier, such as a generic public subscription identifier (GPSI), connection information, UE location information, and AC configuration information (AC profile). The AC configuration information may include an EAS identifier. 【0067】 Step 202: The ECS determines information about at least one EES based on the EES discovery request message. 【0068】 For example, the ECS can match registered EESs, i.e., EESs that match the EES discovery request message, based on AC configuration information and UE location information in the EES discovery request message. 【0069】 Step 203: The ECS sends an EES discovery response message to the EEC. 【0070】 The message contains information about at least one EES. The message may also contain further information, such as EDN connection information. 【0071】 Information about each EES may be shown in Table 1. This information may include, but is not limited to, the following: the EES identifier and the EES endpoint address (e.g., a uniform resource identifier (URI) or IP address). 【0072】 Furthermore, if the ECS does not match the EES based on the EES discovery request message, the ECS sends an EES discovery response message to the EEC, which includes the reason for the failure. 【0073】 Figure 3 shows the EAS Discovery procedure. 【0074】 Step 301: The EEC sends an EAS discovery request message to the EES. 【0075】 For example, an EAS discovery request message may include an EEC identifier and security credentials, and may further include an EAS discovery filter. The EAS discovery filter is configured to search for information about a specific EAS or a specific type of EAS (e.g., a game application program). 【0076】 Step 302: The EES determines the EAS based on the EAS discovery request message. 【0077】 For example, an EES can identify an EAS based on an EAS discovery filter and UE location information (obtainable from the 3GPP® core network). 【0078】 In addition, as shown in Figure 4, if the EES does not have an available EAS corresponding to the current UE location or EAS discovery filter, the EES can send an EAS instantiation request message to the EAS management system. After receiving the EAS instantiation request message from the EES, the EAS management system performs EAS instantiation and sends the instantiation results to the EES. If the EAS instantiation is successful, the instantiation results include information about the instantiated EAS. 【0079】 Step 303: The EES sends an EAS discovery response message to the EEC, and the EAS discovery request includes information about the EAS, etc. 【0080】 Furthermore, if EAS discovery fails, for example, because the instantiation of EAS failed, the EAS discovery will include the reason for the failure in the EAS discovery response message. 【0081】 Furthermore, after receiving an EAS discovery response message, the EEC routes application data traffic to the EAS based on the information received about the EAS. 【0082】 [Table 1] 【0083】 The aforementioned two-stage discovery mechanism for the EAS is applicable to cases initiated by the EEC, and is applicable to the initial discovery of the EAS (e.g., the initial EAS is discovered after the AC is installed or activated), or the EEC detects an application context relocation event (e.g., a move of the UE, in which the aforementioned two-stage discovery mechanism for the EAS is aimed at discovering the target EAS (target EAS, T-EAS)). 【0084】 In the second possible implementation, the source edge application server (source EAS, S-EAS) triggers the source edge enabler server (source EES, S-EES) to request ECS to discover the target edge enabler server (target EES, T-EES), and then the S-EES requests T-EES to discover the T-EAS. 【0085】 As shown in Figure 5, S-EAS detects application context relocation events and initiates the EAS discovery procedure, which is specifically as follows: 【0086】 Step 501: S-EAS sends an EAS discovery request message to S-EES. 【0087】 An EAS discovery request message may include the EAS ID, security credentials, and EAS discovery filters. 【0088】 Step 502: S-EES checks if it is authorized to discover the requested T-EAS. If S-EAS is authorized to discover the requested T-EAS, S-EES performs the T-EES discovery. 【0089】 For the specific process, please refer to the steps shown in Figure 6. 【0090】 Step 503: S-EES sends an EAS discovery request message to T-EES. 【0091】 Step 504: T-EES determines T-EAS based on the EAS discovery request message. 【0092】 For details, please refer to step 302 in Figure 3. Details will not be repeated here. 【0093】 In addition, as shown in Figure 7, when S-EES initiates an EAS discovery request message to T-EES, if T-EES does not have an available EAS corresponding to the current UE location or AC application requirements, T-EES sends an EAS instantiation request message to the EAS management system. After receiving the EAS instantiation request from the EES, the EAS management system performs the EAS instantiation and sends the instantiation results to T-EES. If the EAS instantiation is successful, the instantiation results include information about the instantiated EAS, i.e., information about T-EAS. 【0094】 Step 505: T-EES sends an EAS discovery response message to S-EES. The EAS discovery response message contains information about T-EAS. 【0095】 Step 506: S-EES sends an EAS discovery response message to S-EAS. The EAS discovery response message contains information about T-EAS. 【0096】 Figure 6 shows the procedure by which S-EES discovers T-EES. 【0097】 Step 601: S-EES sends a target EES discovery (also known as retrieve EES) request message to ECS. 【0098】 For example, a retrieve EES request message may include UE location information, UE ID, EAS ID corresponding to S-EAS, target DNAI, etc. 【0099】 Step 602: The ECS determines the T-EES based on the target EES discovery request message. 【0100】 For details, please refer to step 202 in Figure 2. 【0101】 Step 603: The ECS sends a target EES discovery response message to the S-EES. 【0102】 For example, a target EES discovery response message may include information about the T-EES. 【0103】 The aforementioned two-stage discovery mechanism of EAS is intended for cases where discovery is initiated by S-EAS or S-EES (in other words, S-EES first requests ECS to discover T-EES, and then S-EES requests T-EES to discover T-EAS). EAS discovery initiated by S-EAS or S-EES is applicable when S-EAS or S-EES detects application context relocation events (e.g., UE movement). 【0104】 2. EAS instantiation To dynamically schedule and flexibly utilize resources, EAS can be dynamically instantiated to meet application requirements. For example, when an EAS corresponding to application A on an edge data network is not accessed by a user (or after the last user has finished accessing and left), the EAS may be terminated. When a user accesses the EAS (or when a first user accesses the EAS), the EAS can be dynamically instantiated based on application requirements (e.g., virtual resource information, required bandwidth, or required latency). 【0105】 Current standards allow for dynamic instantiation of EAS. In other words, when an edge data network accessed by a user does not have the necessary EAS, a request to the EAS management system can be initiated to trigger the instantiation of the EAS. 【0106】 3. EAS Status Information EAS status information can indicate whether the EAS is instantiated, or whether it is instantiable but not yet instantiated. 【0107】 The status of an EAS is "instantiated," which means that the EAS has completed the instantiation process. When the status of an EAS is "instantiated," the EAS may also be an available EAS, i.e., an instantiated and available EAS. In other words, the EAS can provide service applications corresponding to terminal devices. In this case, the status may also be referred to as available, or instantiated and available. Alternatively, when the status of an EAS is "instantiated," the EAS may also be an unavailable EAS, i.e., an instantiated and unavailable EAS. For example, the load on the EAS may be greater than a pre-set threshold, or the EAS may be a failed EAS. As a result, even if the EAS is instantiated, it cannot provide service applications corresponding to terminal devices. In this case, the status may also be referred to as unavailable, or instantiated and unavailable. Furthermore, an instantiated and unavailable EAS can become an instantiated and available EAS again if the load decreases or the failure is corrected. 【0108】 In this application, the status of the EAS described below is an instantiated state, which specifically means that the EAS is an available EAS, or an instantiated and available EAS, and that the EAS can provide a service application corresponding to a terminal device. 【0109】 The status of an EAS is that it is instantiable but has not yet been instantiated, meaning that the EAS can be instantiated, but has not yet been instantiated. 【0110】 The status of an EAS is instantiable but not yet instantiated, which can be understood as the EAS being available (i.e., an EAS that will be available after instantiation). The state of being instantiable but not yet instantiated can also be described as a specific case of the available state. 【0111】 Alternatively, the status of an EAS can be interpreted as "instantizable but not yet instantiated," which means the EAS is unavailable (i.e., currently unavailable because it has not been instantiated). The state of being instantiable but not yet instantiated can also be described as a specific case of the unavailable state. 【0112】 Alternatively, a state that is instantiable but has not yet been instantiated is a new status other than unavailable and available. 【0113】 In addition, EAS status information may further include a non-instantiated state. An EAS status of non-instantiated means that EAS instantiation cannot be completed because the virtual resources required for EAS instantiation are unavailable. When an EAS status is non-instantiated, it can be understood that the EAS is unavailable. The non-instantiated state can also be described as a specific case of the unavailable state. 【0114】 To select an appropriate EES, one embodiment of this application provides a communication method. First, status information of multiple edge application servers is obtained, and based on the status information of the multiple edge application servers, one edge enabler server is further determined. In this case, the status of the edge application servers corresponding to the determined edge enabler server is instantiable but not yet instantiated. Therefore, only the edge application servers on the edge enabler server may be instantiated, and not all edge enabler servers on multiple edge enabler servers may be instantiated. Thus, the problem of wasting edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided. 【0115】 The method described above will be explained below with reference to Figures 8 and 9. 【0116】 As shown in Figure 8, this method includes the following steps. 【0117】 Step 800: The edge configuration server receives a request message. The request message is used to request information about the edge enabler server, and the request message includes the identifier of the first edge application server. 【0118】 In possible implementations, the edge configuration server can receive a request message from the edge enabler client. Corresponding to step 820, the edge configuration server sends a response message to the edge enabler client. For example, the request message here may be an EES discovery request message, and the response message here may be an EES discovery response message. For specific content included in the EES discovery request message and the EES discovery response message, see steps 201 and 203. Details are not repeated here. In this case, the request message may include AC configuration information, and the identifier of the first edge application server may be conveyed in the AC configuration information. 【0119】 In another possible implementation, the edge configuration server can receive a request message from the source edge enabler server. Corresponding to step 820, the edge configuration server can send a response message to the source edge enabler server. For example, the request message here may be a target EES discovery request message, and the response message here may be a target EES discovery response message. For specific content included in the target EES discovery request message and the target EES discovery response message, see steps 601 and 603. Details are not repeated here. In this case, the identifier of the first edge application server may be provided to the source edge enabler server using the source edge application server. For example, see step 501. The EAS discovery request message sent to the S-EES by the S-EAS may include the EAS ID. 【0120】 Note that in Figure 8, for illustrative purposes, only an example is used in which the edge configuration server receives a request message from the edge enabler client and sends a response message to the edge enabler client. In other words, Figure 8 is based on the first possible implementation of the two-stage discovery mechanism of EAS described above. Based on the related description of the second possible implementation of the two-stage discovery mechanism of EAS, it will be understood that the edge enabler client may be replaced by a source edge enabler server, and the first edge enabler server may be replaced by a target edge enabler server. 【0121】 Step 810: The edge configuration server determines one first edge enabler server based on the status information of multiple first edge application servers, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. 【0122】 It will be understood that the edge configuration server may first obtain the status information of multiple first edge application servers before determining one first edge enabler server based on the status information of multiple first edge application servers. For example, before step 800, the edge configuration server obtains the status information of multiple first edge application servers. Alternatively, after step 800, the edge configuration server obtains the status information of multiple first edge application servers. This is not limited to the present application. 【0123】 In possible implementations, an edge configuration server can obtain status information for multiple first edge application servers from multiple edge enabler servers. It can also be described as multiple edge enabler servers providing corresponding first edge application server status information for the edge configuration server. 【0124】 Here, multiple edge enabler servers are each registered with the first edge application server, and it should be understood that the first edge application servers registered with different edge enabler servers are different edge application servers for the same application. For example, EAS#1 and EAS#2 are registered with EES#1. EAS#1 and EAS#3 are registered with EES#2. The EAS#1 registered with EES#1 and the EAS#1 registered with EES#2 are different EAS for the same application. 【0125】 For example, the edge enabler server sends the edge enabler server identifier, the identifier of the edge application server registered with the edge enabler server, and the status information of the edge application server registered with the edge enabler server to the edge configuration server. For example, the aforementioned content may be conveyed in a registration request message or registration update request message sent by the edge enabler server to the edge configuration server. 【0126】 For example, EAS#1 and EAS#2 are registered with EES#1. EAS#1 and EAS#3 are registered with EES#2. When EES#1 and EES#2 are registered with ECS, EES#1 sends its identifier, EAS#1 status information, EAS#1 identifier, EAS#2 status information, and EAS#2 identifier to ECS. EES#2 sends its identifier, EAS#1 status information, EAS#1 identifier, EAS#3 status information, and EAS#3 identifier to ECS. 【0127】 Please note that the edge enabler server can obtain status information of the edge application servers registered with the edge enabler server in multiple ways. 【0128】 Method 1: The edge enabler server receives the edge application server identifier and status information from the edge application server. The edge application server's status is instantiated. 【0129】 For example, an edge application server sends a registration request message to an edge enabler server. The registration request message includes the edge application server identifier and status information. Alternatively, the edge application server sends a registration update message to an edge enabler server. The registration update message includes the edge application server identifier and status information. 【0130】 Method 2: The edge enabler server receives the edge application server identifier and status information from the edge application server management system. The status of the edge application server is that it is instantiable but has not yet been instantiated. 【0131】 Furthermore, the edge enabler server can store the acquired content in the edge enabler server's configuration information (EES profile). 【0132】 For example, Table 2 shows the correspondence between EES registered in ECS, EAS registered in EES, and status information of EAS registered in EES. 【0133】 [Table 2] 【0134】 The following can be seen from Table 2. 【0135】 a. EESs registered with ECS include EES#1, EES#2, EES#3, and EES#4. 【0136】 b. An EAS registered with EES#1 includes EAS#1 and EAS#2. 【0137】 EAS registered with EES#2 includes EAS#1, EAS#2, and EAS#3. 【0138】 The EAS registered with EES#3 includes EAS#1 and EAS#2. 【0139】 EAS registered with EES#4 includes EAS#4 and EAS#5. 【0140】 The status of EAS#1 registered in c:EES#1 is instantiated, the status of EAS#1 registered in EES#2 is instantiated, and the status of EAS#1 registered in EES#3 is instantiable but not yet instantiated. 【0141】 The status of EAS#2 registered with EES#1 is that it is instantiable but has not yet been instantiated; the status of EAS#2 registered with EES#2 is that it is instantiable but has not yet been instantiated; and the status of EAS#2 registered with EES#3 is that it is instantiable but has not yet been instantiated. 【0142】 The status of EAS#3 registered with EES#2 is "instantized". 【0143】 The status of EAS#4 registered with EES#4 is "instantiated". 【0144】 The status of EAS#5 registered with EES#4 is "instantiated". 【0145】 In possible implementations, the edge configuration server can initially determine the status information of multiple first edge application servers based on the identifier of the first edge application server. For example, the edge configuration server can perform a query or lookup to retrieve the status information of multiple first edge application servers based on the identifier of the first edge application server, and then, based on the status information of multiple first edge application servers, further determine whether there are any first edge application servers whose status is instantiated. 【0146】 If there is a first edge application server whose status is instantiated, the edge configuration server can send information about the edge enabler servers corresponding to one or more of the first edge application servers that are instantiated, so that an edge enabler client or source edge enabler server can preferentially select a first edge application server that is instantiated and meets the conditions without instantiating a new edge application server. 【0147】 Furthermore, optionally, when the edge configuration server selects an edge enabler server, it may further refer to one or more of the following criteria: 【0148】 Specifically, this includes a list of edge computing service providers (ECSPs) preferred by AC, application context relocation (ACR) scenarios preferred by AC, the EES service area, EES DNAI information, and terminal device location information. 【0149】 The list of ECSPs preferred by AC and the ACR scenarios preferred by AC are contents included in the AC configuration information. 【0150】 The aforementioned content may be included in the request message or may be obtained by the edge configuration server. Specific criteria-based content is not limited in this application. 【0151】 For example, Table 2 is used as an example. If the identifier of the first edge application server is EAS#1, the edge configuration server determines several EAS#1 status information, including the following, based on EAS#1 and Table 2: 【0152】 In other words, the status of EAS#1 registered with EES#1 is that it is instantiated, the status of EAS#1 registered with EES#2 is that it is instantiated, and the status of EAS#1 registered with EES#3 is that it is instantiable but has not yet been instantiated. 【0153】 In this case, the edge configuration server can select one or both of EES#1 and EES#2 based on one or more of the aforementioned criteria. Even if the status information of EAS#1 registered with EES#3 indicates that it is instantiable but has not yet been instantiated, the edge application servers selected by the edge configuration server can include only EES#1 and / or EES#2, and not EES#3. As a result, available EAS will be used preferentially, avoiding the waste of resources caused by the instantiation of new EAS. Furthermore, if the edge enabler client receives EES#1 and EES#2, the edge enabler client can send an edge application server discovery request message to EES#1 and / or EES#2, i.e., it can send an edge application server discovery request message to one or more EESs. 【0154】 If it is determined that there are no first edge application servers with an instantiated status, the edge configuration server can determine one first edge enabler server based on the status information of multiple first edge application servers. Since the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated, if there are no first edge application servers with an instantiated status, it may be possible to instantiate a new first edge application server to provide the corresponding service application to terminal devices. 【0155】 In other words, before the edge configuration server determines one first edge enabler server based on the status information of multiple first edge application servers, the edge configuration server determines, based on the status information of multiple first edge application servers, that there are no first edge application servers with an instantiated status. 【0156】 For example, Table 2 is used as an example. If the identifier of the first edge application server is EAS#2, the edge configuration server can determine multiple EAS#2 status information based on EAS#2 and Table 2, including the following: the status of EAS#2 registered in EES#1 is instantiable but not yet instantiated; the status of EAS#2 registered in EES#2 is instantiable but not yet instantiated; and the status of EAS#2 registered in EES#3 is instantiable but not yet instantiated. In other words, the status of EAS#2 registered in EES#1, EES#2, and EES#3 is instantiable but not yet instantiated. Furthermore, the edge configuration server can select one EES from EES#1, EES#2, and EES#3 based on AC configuration information, terminal device location information, etc. 【0157】 According to the aforementioned design, the edge configuration server determines one first edge enabler server based on the status information of multiple first edge application servers. In other words, the edge configuration server selects only one first edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. Therefore, the edge configuration server can then send only an edge application server discovery request message to the first edge enabler server. In this way, only the first edge application server on the first edge enabler server can be instantiated, but not all first edge enabler servers on multiple edge enabler servers can be instantiated, thus avoiding the problem of wasted edge data network resources caused by the instantiation of unnecessary edge application servers. 【0158】 In possible implementations, it will be understood that the edge configuration server determines multiple first edge enabler servers based on the status information of multiple first edge application servers and sends a response message. The response message contains information about multiple first edge enabler servers. In this case, it will be further understood that by using directive information or protocols, an edge enabler client can send an edge application server discovery request message to only one first edge enabler server at a time, thereby avoiding the problem of wasted edge data network resources caused by the instantiation of unnecessary edge application servers. 【0159】 In addition, in possible scenarios, if the edge configuration server fails to obtain status information for the first edge application server, or if the status of multiple first edge application servers is each in an uninstantiated state, the discovery of the edge enabler server will fail. The edge configuration server will send a response message indicating that the discovery of the edge enabler server failed and may indicate the reason for the failure. 【0160】 Step 820: The edge configuration server sends a response message. The response message contains information about the first edge enabler server. 【0161】 Information about the first edge enabler server may include the identifier of the first edge enabler server, the endpoint address of the first edge enabler server, and so on. See Table 1 for details. 【0162】 Optionally, after the edge enabler client receives a response message, this method may further include the following steps: 【0163】 Step 830: The edge enabler client sends an edge application server discovery request message to the first edge enabler server. 【0164】 The edge application server discovery request message includes the identifier of the first edge application server and may contain other content. See step 301 for details. 【0165】 Step 840: The first edge enabler server sends an edge application server instantiation request message to the edge application server management system. 【0166】 For example, the first edge enabler server queries the status information of the first edge application server discovery request message based on the received edge application server discovery request message, determines that the status information of the first edge application server discovery request message indicates that the status of the first edge application server is instantiable but has not yet been instantiated, and sends an edge application server instantiation request message to the edge application server management system. 【0167】 Step 850: The edge application server management system sends the result of the edge application server instantiation to the first edge enabler server. 【0168】 For example, the edge application server management system executes the instantiation of an edge application server based on the received edge application server instantiation request message and determines the result of the edge application server instantiation. 【0169】 If the instantiation result of the edge application server indicates that the instantiation of the first edge application server was successful, the instantiation result includes information about the first edge application server. 【0170】 If the instantiation result of the edge application server indicates that the instantiation of the first edge application server failed, the instantiation result further indicates the cause of the failure of the instantiation of the first edge application server. 【0171】 Step 860: The first edge enabler server sends an edge application server discovery response message to the edge enabler client. 【0172】 For example, if the instantiation result of the edge application server indicates that the instantiation of the first edge application server was successful, the edge application server discovery response message will contain information about the first edge application server, and the procedure will end. 【0173】 For example, if the instantiation result of the edge application server indicates that the instantiation of the first edge application server failed, the edge application server discovery response message will indicate that the discovery of the first edge application server failed. In addition, the edge application server discovery response message may further indicate the reason why the discovery of the first edge application server failed. For example, the instantiation of the first edge application server fails. Optionally, the edge enabler client continues to execute step 870. 【0174】 Step 870: The edge enabler client sends instruction information to the edge configuration server, indicating that the instantiation of the first edge application server corresponding to the first edge enabler server has failed. 【0175】 Step 880: The edge configuration server sends information to the edge enabler client about one second edge enabler server other than the first edge enabler server, and the status of the first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated. 【0176】 For example, the edge configuration server can determine information about one second edge enabler server other than the first edge enabler server based on the status information of multiple first edge application servers, or the edge configuration server can determine information about one second edge enabler server other than the first edge enabler server based on the status information of multiple first edge application servers other than the status information of the first edge application server corresponding to the first edge application enabler server. 【0177】 For example, Table 2 is used as an example. If the identifier of the first edge application server is EAS#2, the edge configuration server can determine multiple EAS#2 status information based on EAS#2 and Table 2, including the following: the status of EAS#2 registered in EES#1 is instantiable but not yet instantiated; the status of EAS#2 registered in EES#2 is instantiable but not yet instantiated; and the status of EAS#2 registered in EES#3 is instantiable but not yet instantiated. Furthermore, the edge configuration server can determine one EES from EES#1, EES#2, and EES#3, for example EES#2, based on AC configuration information and terminal device location information, etc. If the edge configuration server receives instruction information indicating that the instantiation of EAS#2 registered in EES#2 has failed, the edge configuration server can determine one EES from EES#1 and EES#3, for example EES#3. 【0178】 After the edge enabler client obtains information about the second edge enabler server, steps 830 to 860 described above may be repeated. 【0179】 Note that in Figure 9, for illustrative purposes, only an example is used in which the edge configuration server receives a request message from the edge enabler client and sends a response message to the edge enabler client. In other words, Figure 9 is based on the first possible implementation of the two-stage discovery mechanism of EAS described above. Based on the related description of the second possible implementation of the two-stage discovery mechanism of EAS, it will be understood that the edge enabler client may be replaced by a source edge enabler server, and the first edge enabler server may be replaced by a target edge enabler server. 【0180】 Step 900: The edge configuration server receives a request message. The request message is used to request information about the edge enabler server, and the request message includes the identifier of the first edge application server. 【0181】 For Step 900, please refer to the related content in Step 800. Details will not be repeated here. 【0182】 Step 910: The edge configuration server sends a response message. The response message includes information about at least one edge enabler server and status information for the first edge application server corresponding to each of the at least one edge enabler servers. 【0183】 The status information of the first edge application server corresponding to at least one edge enabler server may be described as the status information of the first edge application server corresponding to at least one edge enabler server. 【0184】 For example, before the edge configuration server sends a response message, the edge configuration server can determine at least one edge enabler server based on one or more of the aforementioned criteria. Furthermore, the edge configuration server determines the status information of the first edge application server corresponding to each of the edge enabler servers, from the status information stored in the edge configuration server, using the status information of the first edge application server corresponding to each edge enabler server separately. 【0185】 The edge enabler server obtains status information of edge application servers registered with the edge enabler server using the two methods described above. Details will not be repeated here. After the edge enabler server obtains the status information of the edge application servers registered with the edge enabler server, the edge enabler server can send the edge enabler server identifier, the identifier of the edge application server registered with the edge enabler server, and the status information of the edge application server registered with the edge enabler server to the edge configuration server. For example, the above content may be conveyed in a registration request message or registration update request message sent by the edge enabler server to the edge configuration server. 【0186】 For example, Table 2 is used as an example. If the identifier of the first edge application server is EAS#2, the edge configuration server can determine, based on Table 2, that EES#1, EES#2, and EES#3 are each registered with EAS#2. Furthermore, the edge configuration server can determine EES#1, EES#2, and EES#3 from EES#1, EES#2, and EES#3 based on AC configuration information, terminal device location information, etc. The edge configuration server sends a response message. The response message includes information about EES#1, information about EES#2, and information about EES#3. The status of EAS#2 registered with EES#1 is instantiable but not yet instantiated, the status of EAS#2 registered with EES#2 is instantiable but not yet instantiated, and the status of EAS#2 registered with EES#3 is instantiable but not yet instantiated. 【0187】 For example, Table 2 is used as an example. If the identifier of the first edge application server is EAS#1, the edge configuration server can determine, based on Table 2, that EES#1, EES#2, and EES#3 are each registered with EAS#1. Furthermore, the edge configuration server can determine EES#1, EES#2, and EES#3 from EES#1, EES#2, and EES#3 based on AC configuration information, terminal device location information, etc. The edge configuration server sends a response message. The response message includes information about EES#1, information about EES#2, and information about EES#3. The status of EAS#1 registered with EES#1 is instantiated, the status of EAS#1 registered with EES#2 is instantiated, and the status of EAS#1 registered with EES#3 is instantiable but not yet instantiated. 【0188】 Step 920: The edge enabler client determines one first edge enabler server based on the status information of the first edge application server, each corresponding to at least one edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. 【0189】 For example, an edge enabler client can determine whether there is a first edge application server whose status is instantiated, based on the status information of the first edge application server corresponding to at least one edge enabler server. 【0190】 In a possible design, when the status information of a first edge application server, each corresponding to at least one edge enabler server, includes that the status of the first edge application server is instantiated, the edge enabler client can select one or more edge enabler servers from one or more edge enabler servers corresponding to the first edge application server in an instantiated state. 【0191】 For example, the response message includes information about EES#1, EES#2, and EES#3. The status information for EAS#1 registered with EES#1 is instantiated, the status of EAS#1 registered with EES#2 is instantiated, and the status of EAS#1 registered with EES#3 is instantiable but not yet instantiated. Since the status of EAS#1 registered with EES#1 is instantiated, and the status of EAS#1 registered with EES#2 is instantiated, the edge enabler client can select EES#1 and / or EES#2. 【0192】 In a possible design, if the status information of a first edge application server corresponding to at least one edge enabler server does not include the status of the first edge application server being instantiated, the edge enabler client can select one edge enabler server from one or more edge enabler servers corresponding to a first edge application server that is instantiable but not yet instantiated. In other words, before determining a first edge enabler server based on the status information of a first edge application server corresponding to at least one edge enabler server, the edge enabler client may determine, based on the status information of a first edge application server corresponding to at least one edge enabler server, that there are no first edge application servers whose status is instantiated. 【0193】 For example, the response message includes information about EES#1, EES#2, and EES#3, where the status of EAS#2 registered with EES#1 is instantiable but not yet instantiated, the status of EAS#2 registered with EES#2 is instantiable but not yet instantiated, and the status of EAS#2 registered with EES#3 is instantiable but not yet instantiated. In other words, in this case, the status information for EAS#2 is not instantiated, and the status information for each EAS#2 is instantiable but not yet instantiated. In this case, the edge enabler client can select one of EES#1, EES#2, and EES#3. 【0194】 In addition, if all status information for the first edge application server, which corresponds to at least one edge enabler server, is in an uninstantiated state, the edge enabler client determines that the discovery of the edge enabler server has failed. 【0195】 According to the design described above, the edge enabler client determines one first edge enabler server based on the status information of the first edge application server, each corresponding to at least one edge enabler server. In other words, the edge configuration server selects only one first edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. Therefore, the edge configuration server can then send only an edge application server discovery request message to the first edge enabler server. In this way, only the first edge application server on the first edge enabler server can be instantiated, but not all first edge enabler servers on multiple edge enabler servers can be instantiated, thus avoiding the problem of wasted edge data network resources caused by the instantiation of unnecessary edge application servers. 【0196】 Optionally, after the edge enabler client receives a response message, this method may further include the following steps: 【0197】 For steps 930 through 960, please refer to steps 830 through 860. 【0198】 Step 970: When the instantiation of the first edge application server corresponding to the first edge enabler server fails, the edge enabler client determines one second edge enabler server other than the first edge enabler server, based on the status information of the first edge application server corresponding to at least one edge enabler server. 【0199】 For example, an edge enabler client can determine a second edge enabler server other than the first edge enabler server based on the status information of a first edge application server that separately corresponds to an edge enabler server other than the first edge enabler server among at least one edge enabler server. 【0200】 The status of the first edge application server corresponding to the second edge enabler server is that it is instantiable but has not yet been instantiated. 【0201】 For example, the response message includes information about EES#1, EES#2, and EES#3, where the status of EAS#2 registered with EES#1 is instantiable but not yet instantiated; the status of EAS#2 registered with EES#2 is instantiable but not yet instantiated; and the status of EAS#2 registered with EES#3 is instantiable but not yet instantiated. The edge enabler client can select one of EES#1, EES#2, and EES#3, for example, EES#2. If it is determined that the instantiation of EAS#2 registered with EES#2 has failed, the edge enabler client can select one of EES#1 and EES#3, for example, EES#1. 【0202】 Current standard discussions suggest that two solutions are available to address the resource waste problem in EAS instantiation. 【0203】 Solution 1: EAS status information is provided to the EEC during the EES discovery (also known as service provisioning) procedure. The EEC performs EES selection, and the EAS discovery request message triggers the EES to determine whether EAS instantiation is necessary. 【0204】 Solution 2: EAS status information is provided in the EAS discovery procedure. In this case, the EAS discovery request does not trigger the EAS to determine whether EAS instantiation is needed, but a new procedure (for example, the EAS selection request procedure may also be called another procedure) is introduced to perform EAS selection, and the EAS is triggered based on the new procedure to determine whether EAS instantiation is needed. 【0205】 From an EES performance perspective, the differences after the EES receives an EAS discovery request message are as follows: 【0206】 In Solution 1, after receiving an EAS discovery request, the EES determines whether EAS instantiation is necessary. The decision process is as follows: If no instantiated EAS exists, the EES sends an EAS instantiation request message to the EAS management system based on information about at least one EAS that is instantiable but has not yet been instantiated. If an instantiated EAS exists, the EES does not need to send an EAS instantiation request message to the EAS management system. 【0207】 In Solution 2, the EEC can send EAS discovery request messages to multiple EESs separately. For each EES, EAS instantiation is not required after the EES receives the EAS discovery request message. In other words, the aforementioned decision process does not need to be performed, but the EES sends information to the EEC about at least one EAS that is instantiable but has not yet been instantiated. Furthermore, the EEC selects one EES from among the multiple EESs based on the multiple EAS discovery response messages fed back by the multiple EESs. If the EEC selects one EAS that is instantiable but has not yet been instantiated on the EES, the EEC notifies the EES about the EAS (i.e., the new procedure described above). The EES sends an EAS instantiation request message to the EAS management system based on the EAS notified by the EEC, and the EAS instantiation request message contains the information about the EAS notified by the EEC. 【0208】 In Solution 1 and other existing solutions, we see that after the EES receives an EAS discovery request message, it determines, based on existing logic, whether EAS instantiation is required. However, in Solution 2, the EES does not require EAS instantiation. In other words, in Solution 2, the EES's understanding of the EAS discovery request message is different from its understanding in Solution 1 (and other existing solutions). To avoid the EES not being able to accurately understand the EAS discovery request message, we provide three examples below to solve the problem. 【0209】 Example 1: Shown in Figure 10. 【0210】 S1001: The EEC sends a first EAS discovery request message to the first EES, and the EEC sends a second EAS discovery request message to the second EES. 【0211】 The first EAS discovery request message includes first instruction information and is used to request information about an EAS that meets the AC requirements on a first EES. The second EAS discovery request message includes first instruction information and is used to request information about an EAS that meets the AC requirements on a second EES. The first instruction information indicates that EAS instantiation is not required. 【0212】 For example, an EEC can send N EAS discovery request messages to N EESs. N are positive integers, and there is a one-to-one correspondence between N EAS discovery request messages and N EESs. 【0213】 Each EAS discovery request message contains a first directive, which indicates that EAS instantiation is not required. The i-th EAS discovery request message is used to request information about an EAS on the i-th EAS that satisfies the AC requirements, where i is a positive integer and is less than or equal to N. 【0214】 For example, each EAS discovery request message may further include an EEC identifier and security credentials, and may further include an EAS discovery filter. The EAS discovery filter is configured to search for information about a specific EAS or a specific type of EAS (e.g., a game application program). 【0215】 In Figure 10, for illustrative purposes, only an example is used where the value of N is 2 and the two EESs include the first and second EESs. It should be understood that the value of N can be 3 or greater. 【0216】 S1002: The first EES determines, based on the first instruction information, that EAS instantiation is not required, and the second EES determines, based on the first instruction information, that EAS instantiation is not required. 【0217】 For example, the first EES is used as an example. The fact that the first EES does not require EAS instantiation means that the first EES does not need to decide whether it needs EAS instantiation or whether there is a requirement for EAS instantiation. In other words, for an EAS that is instantiable but has not yet been instantiated, the first EES does not need to send an EAS instantiation request message to the EAS management system. For what it means that the second EES does not require EAS instantiation, please refer to what it means that the first EES does not require EAS instantiation. We will not repeat the details here. 【0218】 S1003: The first EES sends a first EAS discovery response message to the EEC, and the second EES sends a second EAS discovery response message to the EEC. 【0219】 The first EAS discovery response message includes information about at least one instantiated EAS registered with the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES, or information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES. 【0220】 The second EAS discovery response message includes information about at least one instantiated EAS registered with the second EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the second EES, or information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the second EES. 【0221】 For example, N EESs send N EAS discovery response messages to the EEC. 【0222】 N EESs correspond one-to-one with N EAS discovery response messages. 【0223】 The i-th EAS discovery response message includes information about at least one EAS that is instantiable on the i-th EES but has not yet been instantiated. Alternatively, the i-th EAS discovery response message includes information about at least one instantiated EAS registered with the i-th EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the i-th EES. 【0224】 For example, a first EES is used as an example. After the first EES receives a first EAS discovery request message, the first EES can prioritize determining information about at least one instantiated EAS registered with the first EES based on the EAS discovery filter and UE location information (e.g., obtainable from the 3GPP® core network). If it is determined that an instantiated EAS is unavailable, information about at least one EAS that is instantiable on the first EES but has not yet been instantiated may be determined. 【0225】 Alternatively, the first EES can determine, based on the EAS discovery filter and UE location information, information about at least one instantiated EAS registered with the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES, or information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES. 【0226】 Furthermore, if one EAS discovery response message does not contain information about EAS that are instantiable but have not yet been instantiated, and only contains information about at least one instantiated EAS, then after the EEC receives the EAS discovery response message, the EEC may provide the AC with information about at least one instantiated EAS, and based on the received information about at least one instantiated EAS, the AC will route the application data traffic to that one instantiated EAS. Alternatively, the EEC may select one EAS from the information about at least one instantiated EAS and provide the AC with information about the selected EAS. Based on the information about the EAS selected by the EEC, the AC will route the application data traffic to the EAS. 【0227】 For illustrative purposes, we will use only one example below in which each EAS discovery response message contains information about at least one EAS that is instantiable but has not yet been instantiated, or in which each EAS discovery response message contains information about at least one instantiated EAS and information about at least one EAS that is instantiable but has not yet been instantiated. 【0228】 S1004: If the EEC selects a first EAS on the first EES, the EEC sends a first request message to the first EES. The first request message contains information about the first EAS and indicates to the EEC to select the first EAS, i.e., requests the first EES to trigger the instantiation of the first EAS. The first EAS is one of at least one EAS that is instantiable on the first EES but has not yet been instantiated. 【0229】 The first request message may also be referred to as the EAS selection request message. The EAS selection request message indicates the EAS selected by the EEC. Alternatively, the EAS selection request message may have a different name, which is not limited to this application. 【0230】 For example, the EEC selects a first EAS based on the first EAS discovery response message and the second EAS discovery response message, and determines the EES corresponding to the first EAS based on the information about the first EAS. Here, for illustrative purposes, only examples are used where the EES corresponding to the first EAS is the first EES. 【0231】 S1005: The first EAS sends an EAS instantiation request message to the EAS management system based on the first request message it received. The EAS instantiation request message contains information about the first EAS. 【0232】 S1006: The EAS management system performs EAS instantiation. 【0233】 S1007: The EAS management system sends an EAS instantiation response message to the first EAS. The EAS instantiation response message contains the instantiation result of the first EAS. 【0234】 The result of the first EAS instantiation indicates whether the first EAS instantiation was successful or unsuccessful. 【0235】 If the instantiation of the first EAS is successful, the result of the first EAS instantiation will further include information about the instantiated first EAS, such as the configuration file (EAS profile) of the first EAS. 【0236】 S1008: The first EES sends a first response message to the EEC. 【0237】 The first response message contains the result of the first EAS instantiation. 【0238】 Furthermore, after receiving the first response message, if the instantiation of the first EAS is successful, the EEC provides the AC with information about the instantiated first EAS, and the AC routes the application data traffic to the first EAS. 【0239】 Furthermore, note that if the EAS discovery request message does not contain the first instruction information and the EES detects that an instantiated EAS is not available, the EES will send an EAS instantiation request message to the EAS management system based on information about at least one EAS that is instantiable but has not yet been instantiated, i.e., is following existing procedures. 【0240】 In Example 1 described above, the EAS discovery request message contains the first instruction information, which can resolve the problem that the EES may not be able to accurately understand the EAS discovery request message after receiving it. Furthermore, backward compatibility or compatibility issues of the EAS discovery request message to different systems can be further resolved. 【0241】 Furthermore, in conventional technology, if the EAS detects that an instantiated EAS is unavailable, the EAS sends an EAS instantiation request message to the EAS management system based on information about at least one EAS that is instantiable but has not yet been instantiated. As a result, the EAS management system can instantiate multiple EAS instances. In practice, the AC or EEC selects only one EAS. This leads to a waste of network resources. 【0242】 However, in Example 1 above, compared to conventional technology, the EES determines that EAS instantiation is not necessary based on the first instruction information in the EAS discovery request message. As a result, the EES does not send an EAS instantiation request message to the EAS management system when it receives the EAS discovery request message. Therefore, the EAS discovery request message can be accurately understood. Furthermore, since each of the multiple EAS discovery response messages contains information about at least one EAS that is instantiable but has not yet been instantiated, the EEC can select an EAS that is instantiable but has not yet been instantiated and notify the EES corresponding to that EAS. The EES then requests the EAS management system to instantiate the EAS, thus potentially avoiding the aforementioned problem of wasted network resources. 【0243】 Example 2: Shown in Figure 11. 【0244】 S1101: The EEC decides on one solution from the first solution and the second solution. 【0245】 The first and second solutions are pre-configured solutions, and the first solution does not require EAS instantiation after the EEC receives the EAS discovery request message. 【0246】 A second solution is that the EES needs to instantiate an EAS after receiving an EAS discovery request message, or that the EES needs to decide whether or not to instantiate an EAS after receiving an EAS discovery request message. The second solution may also be described as follows: if the EES detects after receiving an EAS discovery request message that no instantiated EAS is available, the EES sends an EAS instantiation request message to the EAS management system based on information about at least one EAS that is instantiable but has not yet been instantiated. 【0247】 S1102: The EEC sends a first EAS discovery request message to the first EES, and the EEC sends a second EAS discovery request message to the second EES. 【0248】 The first EAS discovery request message contains second instruction information, which contains the identifier of the solution determined by the EEC. The second EAS discovery request message contains second instruction information, which contains the identifier of the solution determined by the EEC. It will be understood that the two convey the same identifier of the solution. 【0249】 S1103: The first EES queries the pre-configured solutions based on the identifier of the received solution. If the identifier of the solution included in the second instruction information is the identifier of the first solution, S1104A is executed. If the identifier of the solution included in the second instruction information is the identifier of the second solution, S1104B is executed. Similarly, the second EES queries the pre-configured solutions based on the identifier of the received solution. If the identifier of the solution included in the second instruction information is the identifier of the first solution, S1104A is executed. If the identifier of the solution included in the second instruction information is the identifier of the second solution, S1104B is executed. 【0250】 The pre-configured solutions for each EES are the same as the pre-configured solutions for the EEC, and include the first and second solutions. 【0251】 S1104A: The first EES sends a first EAS discovery response message to the EEC. The second EES sends a second EAS discovery response message to the EEC. 【0252】 The first EAS discovery response message includes information about at least one EAS that is instantiable on the first EES but has not yet been instantiated, or information about at least one instantiated EAS registered with the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES. The second EAS discovery response message includes information about at least one EAS that is instantiable on the second EES but has not yet been instantiated, or information about at least one instantiated EAS registered with the second EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the second EES. 【0253】 For S1104A, please refer to S1003. Details will not be repeated here. 【0254】 For sections S1105A to S1109A, please refer to sections S1004 to S1008. Details will not be repeated here. 【0255】 S1104B: The first EES sends a first EAS discovery response message to the EEC. The second EES sends a second EAS discovery response message to the EEC. 【0256】 The first EAS discovery response message includes information about at least one instantiated EAS registered with the first EES. The second EAS discovery response message includes information about at least one instantiated EAS registered with the second EES. 【0257】 For example, a first EES is used as an example. Based on the EAS discovery filter and UE location information (e.g., obtainable from the 3GPP® core network), the first EES can preferentially determine information about at least one instantiated EAS registered with the first EES. If it is found that an instantiated EAS is unavailable, information about at least one EAS that is instantiable on the first EES but has not yet been instantiated may be determined. Furthermore, based on the information about at least one EAS that is instantiable on the first EES but has not yet been instantiated, the first EES sends an EAS instantiation request message to the EAS management system. Therefore, in this case, the first EAS discovery response message contains only information about at least one instantiated EAS registered with the first EES. 【0258】 Furthermore, after the EEC receives the first EAS discovery response message and the second EAS discovery response message in S1104B, the EEC provides the AC with information about at least one instantiated EAS registered in the first EES, and the AC routes the application data traffic to one of the at least one instantiated EAS based on the received information about at least one instantiated EAS. Alternatively, the EEC determines one EAS from the information about at least one instantiated EAS registered in the first EES and provides the AC with information about that EAS. The AC routes the application data traffic to the EAS based on the information about that EAS. 【0259】 In the aforementioned Example 2, the EEC and EES can pre-configure multiple solutions. The EEC selects one solution from the pre-configured solutions and includes the solution identifier in the EAS discovery request message. Based on the solution identifier in the received EAS discovery request message, the EES can accurately understand the EAS discovery request message. Furthermore, backward compatibility or compatibility issues of EAS discovery request messages to different systems can be further resolved. 【0260】 Example 3: Shown in Figure 12. 【0261】 S1201: The EEC sends a first EAS discovery request message to the first EES, and the EEC sends a second EAS discovery request message to the second EES. 【0262】 S1202: After the first EES receives the first EAS discovery request message, the first EES executes either solution A or solution B. 【0263】 Solution A: The first EES determines, based on the EES configuration information, that the EES configuration information does not include EAS status information. Furthermore, the first EES supports the EAS selection procedure (i.e., the new procedure) and does not require EAS instantiation. The EES configuration information may also be the EES profile. The EAS status information may also be referred to as the EAS instantiation status information. The EAS status information includes the state of being instantiated, or the state of being instantiable but not yet instantiated. 【0264】 Solution B: The first EES determines, based on the EES configuration information, that the EES configuration information includes EAS status information, and then determines whether EAS instantiation is required. 【0265】 In addition to the aforementioned solutions A and B, other solutions may be included. This is not limited to the present application. 【0266】 The actions performed by the second EES are the same as those performed by the first EES. We will not repeat the details here. 【0267】 If the first EES does not require EAS instantiation, S1203A is executed. If the first EES decides whether EAS instantiation is required, S1203B is executed. Similarly, if the second EES does not require EAS instantiation, S1203A is executed. If the second EES decides whether EAS instantiation is required, S1203B is executed. 【0268】 S1203A: The first EES sends a first EAS discovery response message to the EEC. The second EES sends a second EAS discovery response message to the EEC. 【0269】 The first EAS discovery response message includes information about at least one EAS that is instantiable on the first EES but has not yet been instantiated, or information about at least one instantiated EAS registered with the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES. The second EAS discovery response message includes information about at least one EAS that is instantiable on the second EES but has not yet been instantiated, or information about at least one instantiated EAS registered with the second EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered with the first EES. 【0270】 For S1203A, please refer to S1003. Details will not be repeated here. 【0271】 For sections S1204A to S1208A, please refer to sections S1004 to S1008. Details will not be repeated here. 【0272】 S1203B: The first EES sends a first EAS discovery response message to the EEC. The second EES sends a second EAS discovery response message to the EEC. 【0273】 The first EAS discovery response message includes information about at least one instantiated EAS registered with the first EES. The second EAS discovery response message includes information about at least one instantiated EAS registered with the second EES. 【0274】 For S1203B, please refer to S1104B. Details will not be repeated here. 【0275】 In Example 2 described above, when an EAS discovery request message is received, the EES understands the message by referring to whether the capability information and configuration information about the EES contain information about the EAS. In other words, the problem that the EES cannot accurately understand the EAS discovery request message after receiving it can be resolved. Furthermore, backward compatibility or compatibility issues of EAS discovery request messages to different systems can be further resolved. 【0276】 Figure 13 is a possible exemplary block diagram of a communication device according to one embodiment of the present application. The device 1300 includes a transceiver module 1320 and a processing module 1310. The transceiver module 1320 may include a receiving unit and a transmitting unit. The processing module 1310 is configured to control and manage the operation of the device 1300. The transceiver module 1320 is configured to support the device 1300 when communicating with another network entity. Optionally, the device 1300 may further include a storage unit, which is configured to store the program code and data of the device 1300. 【0277】 Optionally, each module within the device 1300 may be implemented using software. 【0278】 Optionally, the processing module 1310 may be a processor or controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, transistor logic device, hardware component, or any combination thereof. The controller / processor can implement or execute various exemplary logic blocks, modules, and circuits as described with reference to the contents disclosed in embodiments of this application. The processor may be a combination of processors that perform computing functions, for example, a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The transceiver module 1320 may be a communication interface, a transceiver, a transceiver circuit, etc. The term "communication interface" is a general term. In a specific implementation, the communication interface may include multiple interfaces, and the storage unit may be memory. 【0279】 If the device 1300 is an edge configuration server or a chip within an edge configuration server, the processing module 1310 within the device 1300 can support the device 1300 when performing the operations of the edge configuration server in the above-described example method, for example, when performing step 810 in Figure 8. 【0280】 The transceiver module 1320 can support the device 1300 when communicating with an edge enable client or a source edge enable server. For example, the transceiver module 1320 can support the device 1300 when executing step 800, step 820, step 870, step 880, or step 900 of FIG. 8, or step 910 of FIG. 9. 【0281】 For example, the transceiver module 1320 is configured to receive a request message. The request message is used to request information about the edge enable server, and the request message includes an identifier of a first edge application server. 【0282】 The processing module 1310 is configured to determine one first edge enable server based on the status information of a plurality of first edge application servers, and the status of the first edge application server corresponding to the first edge enable server is in a state where it can be instantiated but has not yet been instantiated. 【0283】 The transceiver module 1320 is configured to send a response message, and the response message includes information about the first edge enable server. 【0284】 In a possible design, the status information of the first edge application server indicates whether the status of the first edge application server has been instantiated or is in a state where it can be instantiated but has not yet been instantiated. 【0285】 In a possible design, the processing module 1310 is configured to obtain the status information of a plurality of first edge application servers from a plurality of edge enable servers. 【0286】 In a possible design, the processing module 1310 is configured to determine, based on the status information of multiple first edge application servers, that there are no first edge application servers whose status is instantiated, before determining one first edge enabler server based on the status information of multiple first edge application servers. 【0287】 In a possible design, the transceiver module 1320 is configured to receive instruction information indicating that the instantiation of the first edge application server corresponding to the first edge enabler server has failed, and is also configured to transmit information about one second edge enabler server other than the first edge enabler server, where the status of the first edge application server corresponding to the second edge enabler server is instantiable but has not yet been instantiated. 【0288】 In a possible design, the transceiver module 1320 is configured to receive a request message from the edge enabler client when it receives a request message, and to send a response message to the edge enabler client when it sends a response message. 【0289】 In a possible design, the transceiver module is configured to receive request messages from the source edge enabler server when it receives a request message, and to send response messages to the source edge enabler server when it sends a response message. 【0290】 In another example, processing module 1310 activates transceiver module 1320 to receive a request message, which is used to request information about edge enabler servers, which includes an identifier for a first edge application server, and sends a response message, which includes information about at least one edge enabler server and status information for the first edge application server corresponding to at least one edge enabler server. 【0291】 In a possible design, the status information for the first edge application server would indicate whether the first edge application server is instantiated or can be instantiated but has not yet been instantiated. 【0292】 In a possible design, the transceiver module 1320 is configured to receive a request message from the edge enabler client when it receives a request message, and to send a response message to the edge enabler client when it sends a response message. 【0293】 In a possible design, the transceiver module 1320 is configured to receive a request message from the source edge enabler server when it receives a request message, and to send a response message to the source edge enabler server when it sends a response message. 【0294】 The apparatus 1300 according to this embodiment of the present application can correspond to the edge configuration server in the method embodiment described above, and it should be understood that the operation and / or functions of the modules within the apparatus 1300 are separately intended to carry out the corresponding steps of the edge configuration server method in the method embodiment described above. Therefore, the beneficial effects of the method embodiment described above can also be implemented. For brevity, the details will not be described again here. 【0295】 If device 1300 is an edge enabler client or a source edge enabler server or a chip within an edge enabler client or a chip within a source edge enabler server, the processing module 1310 within device 1300 can support device 1300 when performing the operations of the edge enabler client or source edge enabler server in the method example described above. For example, the processing module 1310 can support device 1300 when performing step 920 or step 970 in Figure 9. 【0296】 The transceiver module 1320 can support device 1300 when communicating with the edge configuration server. For example, the transceiver module 1320 can support device 1300 when performing steps 800, 820, 830, 860, 870, or 880 in Figure 8, or steps 900, 910, 930, or 960 in Figure 9. 【0297】 For example, the transceiver module 1320 is configured to send a request message to an edge configuration server, which is used to request information about edge enabler servers, which includes an identifier for a first edge application server, and to receive a response message from the edge configuration server, which includes information about at least one edge enabler server and status information for the first edge application server corresponding to each of the at least one edge enabler server. 【0298】 The processing module 1310 determines one first edge enabler server based on the status information of the first edge application server, each corresponding to at least one edge enabler server, and the status of the first edge application server corresponding to the first edge enabler server is configured to be instantiable but not yet instantiated. 【0299】 In a possible design, the status information for the first edge application server would indicate whether the first edge application server is instantiated or can be instantiated but has not yet been instantiated. 【0300】 In a possible design, before determining a first edge enabler server based on the status information of the first edge application server corresponding to at least one edge enabler server, the processing module 1310 is configured to determine, based on the status information of the first edge application server corresponding to at least one edge enabler server, that there are no first edge application servers whose status is instantiated. 【0301】 In a possible design, the processing module 1310, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, determines one second edge enabler server other than the first edge enabler server based on the status information of the first edge application server corresponding to at least one edge enabler server, and the status of the first edge application server corresponding to the second edge enabler server is configured to be instantiable but not yet instantiated. 【0302】 The apparatus 1300 according to this embodiment of the present application can correspond to the edge enabler client or the source edge enabler server in the foregoing method embodiment. It should be understood that the operations and / or functions of the modules in the apparatus 1300 are separately intended to implement the corresponding steps of the method of the edge enabler client or the source edge enabler server in the foregoing method embodiment. Therefore, the beneficial effects in the foregoing method embodiment can also be implemented. For the sake of brevity, the details will not be described again here. 【0303】 When the apparatus 1300 is an edge enabler server or a chip within an edge enabler server, the processing module 1310 in the apparatus 1300 can support the apparatus 1300 when executing the edge enabler server in the foregoing method example. 【0304】 The transceiver module 1320 can support the apparatus 1300 when communicating with the edge configuration server. 【0305】 For example, the processing module 1310 activates the transceiver module 1320 to obtain the status information of the first edge application server, and transmits the identifier of the first edge application server and the status information of the first edge application server to the edge configuration server. 【0306】 In a possible design, when obtaining the status information of the first edge application server, the transceiver module 1320 is configured to obtain the status information of the first edge application server from the first edge application server, and the status information of the first edge application server indicates that the status of the first edge application server is an instantiated status. 【0307】 In a possible design, the transceiver module 1320 is configured to obtain status information for the first edge application server from the edge application server management system when acquiring status information for the first edge application server, and the status information for the first edge application server is configured to indicate that the first edge application server is instantiable but has not yet been instantiated. 【0308】 The apparatus 1300 according to this embodiment of the present application can correspond to the edge enabler server in the aforementioned method embodiment, and it should be understood that the operation and / or functions of the modules within the apparatus 1300 are separately configured to perform the corresponding steps of the edge enabler server method in the aforementioned method embodiment. Thus, the beneficial effects of the aforementioned method embodiment can also be implemented. For brevity, further details will not be described here. 【0309】 Figure 14 is a schematic diagram of the structure of a communication device 1400 according to one embodiment of the present application. As shown in Figure 14, the device 1400 includes a processor 1401. 【0310】 If the device 1400 is an edge configuration server or a chip within an edge configuration server, in a possible implementation, the processor 1401 is configured to activate an interface and perform the following operations: an operation to receive a request message, the request message being used to request information about an edge enabler server, and the request message including an identifier for a first edge application server; an operation to determine one first edge enabler server based on status information of a plurality of first edge application servers, the status of the first edge application server corresponding to the first edge enabler server being instantiable but not yet instantiated; and an operation to send a response message, the response message including information about the first edge enabler server. 【0311】 In another possible implementation, the processor 1401 is configured to invoke an interface and perform the following actions: receiving a request message, which is used to request information about an edge enabler server, and which includes an identifier for a first edge application server; determining a single first edge enabler server based on status information of a plurality of first edge application servers, where the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated; and sending a response message, which includes information about the first edge enabler server. 【0312】 It should be understood that device 1400 may be further configured to perform other steps and / or operations on the edge configuration server side in the embodiments described above. For brevity, the details will not be described again here. 【0313】 If the device 1400 is an edge enabler client, a source edge enabler server, a chip within the edge enabler client, or a chip within the source edge enabler server, in possible implementations, the processor 1401 is configured to activate an interface and perform the following operations: sending a request message to an edge configuration server, the request message being used to request information about edge enabler servers, and the request message including an identifier for a first edge application server; receiving a response message from the edge configuration server, the response message including information about at least one edge enabler server and status information for a first edge application server corresponding to each of the at least one edge enabler server; and determining one first edge enabler server based on the status information for a first edge application server corresponding to each of the at least one edge enabler server, the status of the first edge application server corresponding to the first edge enabler server being instantiable but not yet instantiated. 【0314】 It should be understood that device 1400 may be further configured to perform other steps and / or operations on the edge enabler client or source edge enabler server side in the embodiments described above. For brevity, the details will not be described again here. 【0315】 If the device 1400 is an edge enabler server or a chip within an edge enabler server, in possible implementations, the processor 1401 is configured to activate an interface and perform the following operations: obtaining status information of a first edge application server and sending the identifier of the first edge application server and the status information of the first edge application server to the edge configuration server. 【0316】 It should be understood that device 1400 may be further configured to perform other steps and / or operations on the edge enabler server side in the embodiments described above. For brevity, the details will not be described again here. 【0317】 It should be understood that the processor 1401 can activate an interface to perform the aforementioned receive and transmit operations. The activated interface may be a logical interface or a physical interface, but is not limited to this. Optionally, the physical interface may be implemented using a transceiver. Optionally, the device 1400 further includes a transceiver 1403. 【0318】 Optionally, the device 1400 further includes a memory 1402 which stores the program code in the embodiment of the method described above, thereby enabling the processor 1401 to invoke the program code. 【0319】 Specifically, if the device 1400 includes a processor 1401, a memory 1402, and a transceiver 1403, the processor 1401, the memory 1402, and the transceiver 1403 communicate with each other via internal connection paths to transmit control signals and / or data signals. In possible designs, the processor 1401, the memory 1402, and the transceiver 1403 may be implemented using a chip. The processor 1401, the memory 1402, and the transceiver 1403 may be implemented on the same chip, or they may be implemented separately on different chips, or any two functions of the processor 1401, the memory 1402, and the transceiver 1403 may be implemented on a single chip. The memory 1402 can store program code, and the processor 1401 invokes the program code stored in the memory 1402 to implement the corresponding functions of the device 1400. 【0320】 This application further provides a communication system. The system includes one or more of the following: an application client, an edge enabler client, an edge enabler server, an edge configuration server, an edge application server, and an edge application server management system. The edge enabler client is configured to perform the steps and / or operations on the edge enabler client side in the embodiments described above; the edge enabler server is configured to perform the steps and / or operations on the edge enabler server side in the embodiments described above; the edge configuration server is configured to perform the steps and / or operations on the edge configuration server side in the embodiments described above; and the edge application server management system is configured to perform the steps and / or operations on the edge application server management system side in the embodiments described above. 【0321】 The methods disclosed in embodiments of this application may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In the implementation process, the steps in the embodiments of the methods described above may be implemented by using hardware integrated logic circuits within the processor or by using instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on a chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or another integrated chip. A processor can implement or perform the methods, steps, and logic block diagrams disclosed in embodiments of this application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed with reference to embodiments of this application may be implemented by being performed directly using a hardware decoding processor, or by being performed using a combination of hardware and a soft module of the decoding processor.The software module may be located in a storage medium that is a mature technology in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory, and the processor reads the information in memory and, in combination with the processor hardware, completes the steps in the method described above. 【0322】 It will be understood that the memory in this embodiment of the present application may be volatile memory, non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. Rather than being a restrictive description, many forms of RAM may be used as examples, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus dynamic random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein includes, but is not limited to, these memories and any other suitable type of memory. 【0323】 In the embodiments of this application, the numbers "1st," "2nd," etc., are merely intended to distinguish different objects, for example, to distinguish different parameter information or messages, and should be understood as not limiting the scope of the embodiments of this application. This embodiment of this application is not limited thereto. 【0324】 It should be further understood that the sequence numbers of the processes described above do not represent the execution order in the embodiments of this application. The execution order of the processes should be determined based on the function and internal logic of the processes. The various numbers or sequential numbers in the processes described above are merely distinguishing for the sake of clarity and do not constitute any limitation on the implementation processes of the embodiments of this application. 【0325】 It should also be understood that the terms "and / or" in this specification describe only related relationships that describe related subjects, and that three relationships may exist. For example, A and / or B can represent the following three cases: the case where only A exists, the case where both A and B exist, and the case where only B exists. In addition, the letter " / " in this specification generally indicates an "or" relationship between related subjects. 【0326】 Unless otherwise specified, expressions used in this application similar to the expression "the item includes one or more of A, B, and C" usually mean that the item may be any one of the following: A, B, C, A and B, A and C, B and C, A and B and C, A and A, A and A and A, A and A and B, A and A and C, A and B and B, A and C and C, B and B, B and B and B, B and B and C, C and C, C and C and C, and any other combination of A, B, and C. In the above description, three elements A, B, and C are used as an example to describe the case of arbitrary selection of items. If the expression is "the item includes at least one of A, B, ..., and X," in other words, if more elements are included in the expression, there may also be cases to which the item applies, according to the rules above. 【0327】 Those skilled in the art will recognize, in combination with the examples described in the embodiments disclosed herein, that units and algorithmic steps may be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether the functions are performed by hardware or by software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the functions described for each specific application, but such implementations will not be considered beyond the scope of this application. 【0328】 For the sake of simplicity, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units can be described by referring to the corresponding processes in the embodiments of the methods described above. Details will not be repeated here. 【0329】 It should be understood that in some embodiments provided in this application, the disclosed systems, apparatus, and methods may be implemented in different ways. For example, the described apparatus embodiments are merely examples. For example, the division into units is merely a logical functional division, and in actual implementation, different divisions may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or described may be implemented using some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented in electronic, mechanical, or other forms. 【0330】 Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected based on the actual requirements in order to achieve the objectives of the solutions of the embodiments. 【0331】 In addition, the functional units of the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. 【0332】 When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a single computer-readable storage medium. Based on such understanding, the technical solution of this application, or a portion of the technical solution that contributes to the prior art, may be implemented in the form of a software product. A computer software product is stored on a single storage medium and includes several instructions that instruct a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk. [Explanation of symbols] 【0333】 1300 equipment 1310 Processing Module 1320 Transceiver Module 1400 equipment 1401 Processor 1402 memory 1403 Transceiver

Claims

[Claim 1] A method of communication, A step of sending a request message to an edge configuration server, wherein the request message is used to request information about an edge enabler server, A step of receiving a response message from the edge configuration server, wherein the response message includes information about at least one edge enabler server and status information for a first edge application server corresponding to each of the at least one edge enabler servers, and the status information for the first edge application server indicates that the status of the first edge application server is either instantiated or instantiable but not yet instantiated. The steps include determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler servers, Methods that include... [Claim 2] The method according to claim 1, wherein the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler server includes selecting one or more edge enabler servers from the one or more edge enabler servers corresponding to the first edge application server in an instantiated state when it is determined that there is a first edge application server in an instantiated state. [Claim 3] The method according to claim 1, wherein the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler server includes selecting one edge enabler server from one or more edge enabler servers corresponding to the first edge application server that is instantiable but not yet instantiated when it is determined that there are no first edge application servers whose status is instantiated. [Claim 4] Prior to the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler servers, the method: A step to determine whether there are any first edge application servers whose status is instantiated, based on the status information of the first edge application servers corresponding to each of the at least one edge enabler servers. The method according to claim 1, further comprising: [Claim 5] Prior to the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler servers, the method: A step to determine whether there are any first edge application servers whose status is instantiated, based on the status information of the first edge application servers corresponding to each of the at least one edge enabler servers. The method according to claim 3, further comprising: [Claim 6] Steps to determine a second edge enabler server other than the first edge enabler server based on the status information of the first edge application server corresponding to each of the at least one edge enabler server when the instantiation of the first edge application server corresponding to the first edge enabler server fails, wherein the status of the first edge application server corresponding to the second edge enabler server is instantiable but has not yet been instantiated. The method according to claim 1, further comprising: [Claim 7] After the step of determining one first edge enabler server, the method, The step of sending an edge application server discovery request message to the aforementioned first edge enabler server. The method according to claim 1, further comprising: [Claim 8] The method according to claim 1, wherein the method is performed by an edge enabler client. [Claim 9] The method according to claim 1, wherein the request message includes an identifier for the first edge application server. [Claim 10] The method according to claim 1, wherein the request message is an edge enabler server discovery request message, and the response message is an edge enabler server discovery response message. [Claim 11] A method of communication, The Edge Configuration Server receives a request message, the request message being used to request information about the Edge Enabler Server, and the process is as follows: A step of sending a response message by the edge configuration server, wherein the response message includes information about at least one edge enabler server and status information for a first edge application server corresponding to each of the at least one edge enabler server, the status information for the first edge application server corresponding to each of the at least one edge enabler server indicating that the status of the first edge application server is either instantiated or instantiable but not yet instantiated, and the status information for the first edge application server corresponding to each of the at least one edge enabler server is for determining one or more first edge enabler servers. Methods that include... [Claim 12] The step of receiving the request message by the edge configuration server is as follows: The edge configuration server receives the request message from the edge enabler client. Includes, The step of sending a response message by the edge configuration server is: The Edge Configuration Server sends the response message to the Edge Enabler client. including, The method according to claim 11. [Claim 13] The step of receiving the request message by the edge configuration server is as follows: The edge configuration server receives the request message from the source edge enabler server. Includes, The step of sending a response message by the edge configuration server is: The edge configuration server sends the response message to the source edge enabler server. including, The method according to claim 11. [Claim 14] The method according to claim 11, wherein the request message includes an identifier for the first edge application server. [Claim 15] A method of communication, The steps include: sending a request message to an edge configuration server via an edge enabler client, wherein the request message is used to request information about the edge enabler server; The step of the edge configuration server receiving the request message sent by the edge enabler client and sending a response message to the edge enabler client, wherein the response message includes information about at least one edge enabler server and status information of a first edge application server corresponding to each of the at least one edge enabler servers. The Edge Enabler Client receives the response message sent by the Edge Configuration Server, and determines one or more first Edge Enabler Servers based on the status information of the first Edge Application Servers corresponding to each of the at least one Edge Enabler Servers, wherein the status information of the first Edge Application Servers indicates that the status of the first Edge Application Servers is either instantiated or instantiable but not yet instantiated. Methods that include... [Claim 16] A step of obtaining status information of a first edge application server corresponding to the edge enabler server using an edge enabler server, wherein the edge enabler server is one of the at least one edge enabler servers, The edge enabler server transmits the identifier of the edge enabler server, the status information of the first edge application server corresponding to the edge enabler server, and the identifier of the first edge application server corresponding to the edge enabler server to the edge configuration server. The edge configuration server receives the identifier of the edge enabler server, the status information of the first edge application server corresponding to the edge enabler server, and the identifier of the first edge application server corresponding to the edge enabler server, transmitted by the edge enabler server. The method according to claim 15, further comprising: [Claim 17] The method according to claim 16, wherein the identifier of the edge enabler server, the status information of the first edge application server corresponding to the edge enabler server, and the identifier of the first edge application server corresponding to the edge enabler server are conveyed in a registration request message or registration update request message transmitted by the edge enabler server to the edge configuration server. [Claim 18] The method according to claim 15, wherein the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler server includes selecting one or more edge enabler servers from the one or more edge enabler servers corresponding to the first edge application server in an instantiated state when it is determined that there is a first edge application server in an instantiated state. [Claim 19] The method according to claim 15, wherein the step of determining one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler server includes selecting one edge enabler server from one or more edge enabler servers corresponding to the first edge application server that is instantiable but not yet instantiated when it is determined that there are no first edge application servers whose status is instantiated. [Claim 20] Prior to the step in which the edge enabler client determines one or more first edge enabler servers based on the status information of the first edge application server corresponding to each of the at least one edge enabler server, the method: The edge enabler client determines, based on the status information of the first edge application server corresponding to each of the at least one edge enabler servers, whether or not there are any first edge application servers whose status is instantiated. The method according to claim 15, further comprising: [Claim 21] Steps to determine a second edge enabler server other than the first edge enabler server, based on the status information of the first edge application server corresponding to each of the at least one edge enabler server, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, wherein the status of the first edge application server corresponding to the second edge enabler server is instantiable but has not yet been instantiated. The method according to claim 15, further comprising: [Claim 22] After the step in which the edge enabler client determines one first edge enabler server, the method: The Edge Enabler client sends an Edge Application Server Discovery Request message to one of the First Edge Enabler Servers, The first edge enabler server receives the edge application server discovery request message sent by the edge enabler client, The method according to claim 15, further comprising: [Claim 23] The method according to claim 15, wherein the request message includes an identifier for the first edge application server. [Claim 24] The method according to claim 15, wherein the request message is an edge enabler server discovery request message, and the response message is an edge enabler server discovery response message. [Claim 25] A communication device comprising a unit or module configured to perform the method described in any one of claims 1 to 14. [Claim 26] A communication device comprising one or more processors and one or more memories, wherein the one or more memories store one or more programs, and when the programs are executed by the one or more processors, the communication device becomes capable of performing the method according to any one of claims 1 to 14. [Claim 27] A chip system comprising at least one chip and a memory, wherein the at least one chip is configured to read and execute a program stored in the memory to carry out the method according to any one of claims 1 to 14. [Claim 28] A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 14 is performed. [Claim 29] A communication system comprising at least two devices, an edge configuration server, an edge enabler client, and an edge enabler server, wherein the edge configuration server is configured to carry out the method described in any one of claims 11 to 14, the edge enabler client is configured to carry out the method described in any one of claims 1 to 10, and the edge enabler server is configured to carry out the method of the edge enabler server described in claim 16 or 17. [Claim 30] A computer program wherein, when the computer program is executed on a device, the method described in any one of claims 1 to 14 is performed.

Images