Communication Method and Apparatus

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 the priority of Chinese Patent Application No. 202210731521.9, titled "Communication Method and Device", filed with the China National Intellectual Property Administration on June 24, 2022, the entire content of which is incorporated herein by reference, and also claims the priority of Chinese Patent Application No. 202211218366.7, titled "Communication Method and Device", 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 the present application relate to the field of wireless communication, and in particular, to communication methods and devices.

Background Art

[0003] Mobile Edge Computing (MEC), also referred to 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, in order to enable the terminal device to determine the EAS that needs to be accessed, there is currently a two-stage EAS discovery mechanism. 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 needs to be discovered first before the EAS can be discovered. Therefore, how to select an appropriate EES is a problem worthy of attention. Summary of the Invention Means for Solving the Problems

[0006] This application provides a communication method and apparatus for selecting an appropriate EES.

[0007] According to a first aspect, this application provides a communication method. 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 one first edge enabler server based on the 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 transmits a response message, where the response message includes information about the first edge enabler server.

[0008] According to the foregoing design, the edge configuration server can determine one first edge enabler 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 enabler server in this specification is 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 the 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 the first edge enabler servers on a plurality of edge enabler servers can be instantiated. As a result, the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0009] In a possible design, the status information of the first edge application server indicates whether the status of the first edge application server is instantiated or is instantiable but not yet instantiated.

[0010] In a possible design, the edge configuration server obtains the status information of a plurality of first edge application servers from a plurality of edge enabler servers.

[0011] For example, the edge configuration server can obtain the status information of the first edge application server from the edge enabler server by using a registration request message or a registration update message.

[0012] In a possible design, before the edge configuration server determines one first edge enabler server based on the status information of a plurality of first edge application servers, it determines, based on the status information of the plurality of first edge application servers, that there is no first edge application server in a status where the status is instantiated.

[0013] For example, the edge configuration server can determine whether there is a first edge application server in a status where the status is instantiated based on the status information of the plurality of first edge application servers.

[0014] If it is determined that there is a first edge application server in a status where the status is instantiated, the edge configuration server can send information about the edge enabler server corresponding to the first edge application server in a status where the status is instantiated. As a result, the edge enabler client or the source edge enabler server can preferentially select a first edge application server that is in an instantiated state and meets the conditions without instantiating a new edge application server.

[0015] If it is determined that there is no first edge application server in an instantiated state, the edge configuration server can determine one first edge enabler server based on the status information of a plurality of 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 is no first edge application server in an instantiated state, a new first edge application server can be instantiated to provide the corresponding service application to the terminal device.

[0016] In a possible design, the edge configuration server receives indication information, which indicates that the instantiation of the first edge application server corresponding to the first edge enabler server has failed. The edge configuration server transmits 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 foregoing 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, and the status of the first edge application server corresponding to the edge enabler server is instantiable but not yet instantiated.

[0018] It will be understood that the edge configuration server can receive instruction information from the edge enable client and send information about the second edge enable server to the edge enable client. Alternatively, the edge configuration server can receive instruction information from the source edge enable server and send information about the second edge enable server to the source edge enable server.

[0019] In a possible design, when the edge configuration server receives a request message, the edge configuration server receives the request message from the edge enable client, and when the edge configuration server sends a response message, the edge configuration server sends the response message to the edge enable client.

[0020] 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 enable server, and when the edge configuration server sends a response message, the edge configuration server sends the response message to the source edge enable server.

[0021] According to a second aspect, the present application provides a communication method. 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 enable server and the request message includes an identifier of a first edge application server, and a step in which the edge configuration server sends a response message, where the response message includes information about at least one edge enable server and status information of a first edge application server corresponding to each of the at least one edge enable server.

[0022] The status information of the first edge application server corresponding to each of at least one edge enabler server may be described as the status information of the first edge application server corresponding to each of at least one edge enabler server.

[0023] According to the above design, the edge configuration server can provide the status information of the first edge application server corresponding to each of at least one edge enabler server, whereby the edge enabler client or the source edge enabler server can be assisted in determining one first edge enabler server. The status of the first edge application server corresponding to the first edge enabler server herein 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 the 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 the first edge enabler servers on multiple edge enabler servers can be instantiated, and as a result, the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0024] In a possible design, the status information of the first edge application server corresponding to each of 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 a first edge application server corresponding to each of the at least one edge enable server; and determining, based on the status information of the first edge application server corresponding to each of the at least one edge enable server, a first 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 may send an edge application server discovery request message to the first edge enable server.

[0030] According to the foregoing design, an edge enable client or a source edge enable server can determine one first edge enable server based on the status information of the first edge application server corresponding to each of at least one edge enable server provided by the edge configuration server. The status of the first edge application server corresponding to the first edge enable server herein is instantiable but not yet instantiated. In other words, the edge configuration server selects only one first edge enable server. Therefore, the edge configuration server can then send only the edge application server discovery request message to the first edge enable server. In this way, only the first edge application server on the first edge enable server can be instantiated, but not all the first edge enable servers on multiple edge enable servers can be instantiated. As a result, the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0031] In a possible design, the status information of the first edge application server indicates whether the first edge application server is in an instantiated state or is instantiable but not yet instantiated.

[0032] In a possible design, before the step of determining one first edge enable server based on the status information of the first edge application server corresponding to each of at least one edge enable server, it is determined, based on the status information of the first edge application server corresponding to each of at least one edge enable server, that there is no first edge application server in an instantiated state.

[0033] For example, an edge enable client or a source edge enable server can determine whether there is a first edge application server in a status-instantiated state based on the status information of the first edge application server corresponding to at least one edge enable server respectively.

[0034] If it is determined that there is a first edge application server in a status-instantiated state, the edge enable client or the source edge enable server can send an edge application server discovery request message to the edge enable server corresponding to one or more first edge application servers in a status-instantiated state. Thereby, the edge enable client or the source edge enable server can preferentially select a first edge application server that is in an instantiated state and meets the conditions without instantiating a new edge application server.

[0035] If it is determined that there is no first edge application server in a status-instantiated state, the edge enable client or the source edge enable server can determine one first edge enable server based on the status information of the first edge application server corresponding to at least one edge enable server respectively. Since the status of the first edge application server corresponding to the first edge enable server is instantiable but not yet instantiated, if there is no first edge application server in an instantiated state, in order to provide the corresponding service application to the terminal device, it can be implemented that a new first edge application server can be instantiated.

[0036] In a possible design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, based on the status information of the first edge application servers respectively corresponding to at least one edge enabler server, one second edge enabler server other than the first edge enabler server is determined, and the status of the first edge application server corresponding to the second edge enabler server is in a state where it can be instantiated but has not yet been instantiated.

[0037] According to the foregoing design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, the edge enabler client or the source edge enabler server can determine a new edge enabler server, and the first edge application server corresponding to the edge enabler server is in a state where it can be instantiated 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 sending an 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 foregoing design, the edge enabler server can obtain the identifier of the first edge application server and the status information of the first edge application server, and send the identifier of the first edge application server and the status information of the first edge application server to the edge configuration server.

[0040] In a possible design, when the edge enabler server obtains the status information of the first edge application server, the edge enabler server has obtained 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 in an instantiated state.

[0041] In a possible design, when the edge enabler server obtains the status information of the first edge application server, the edge enabler server has obtained the status information of the first edge application server from the edge application server management system, and the status information of the first edge application server indicates that the first edge application server is instantiable but not yet instantiated.

[0042] According to a fifth aspect, the present application further provides an apparatus. The apparatus can execute the foregoing method design. The apparatus may be a chip or a circuit capable of executing the functions corresponding to the foregoing method, or may be a device including the chip or the circuit.

[0043] In a possible implementation, the apparatus includes a memory configured to store computer-executable program code and a processor coupled to the memory. The program code stored in the memory includes instructions. When the processor executes the instructions, the apparatus or the device in which the apparatus is installed can execute the method in any one of the foregoing possible designs.

[0044] The apparatus may further include a communication interface. The communication interface may be a transceiver. Alternatively, when the apparatus is a chip or a circuit, the communication interface may be an input / output interface of the chip, such as an input / output pin.

[0045] In a possible design, the apparatus includes corresponding functional units separately configured to perform the steps of the foregoing method. This function may be implemented by hardware or by executing corresponding software by the hardware. The hardware or software includes one or more units corresponding to the foregoing functions.

[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 a device, any one of the foregoing possible design methods is executed.

[0047] According to a seventh aspect, the present application provides a computer program product. The computer program product includes a computer program, and when the computer program is executed on a device, any one of the foregoing possible design methods is executed.

Brief Description of the Drawings

[0048]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0049] Hereinafter, with reference to the accompanying drawings of the embodiments of this application, the technical solutions of the embodiments of this application will be clearly and completely described. It is obvious that the described embodiments are only a part of the embodiments of this application, not all of them. In the specification, claims, and accompanying drawings of this application, terms such as "first", "second", and corresponding term numbers are intended to distinguish similar objects and do not necessarily indicate a specific order or sequence. Such terms are interchangeable in appropriate situations and are only an identification method used when objects with the same attributes are described in the embodiments of this application. Further, the terms "include", "contain", and any other variations are meant to cover non-exclusive inclusion, so a process, method, system, product, or device that includes a series of units is not necessarily limited to those units, but may include other units that are not explicitly listed or inherent in such a process, method, system, product, or device.

[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" only describes the association relationship for describing related objects, indicating that three relationships may exist. For example, A and / or B can represent the following three cases, namely, 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 "a plurality of items" means two or more items. "At least one of the following items (articles)" or similar expressions mean any combination of these, including a single item (article) or any combination of a plurality of items (articles). For example, at least one of a, b, or c can indicate a, b, c, a-b, a-c, b-c, or a-b-c, and a, b, and c may be in singular or plural form.

[0051] Referring to the edge computing application architecture and function model shown in FIG. 1, the functional entities in this application will be briefly described.

[0052] 1. EDN: In general understanding, EDN corresponds to only one data network and is a special local data network (local DN). EDN includes the edge enablement function and can be identified by the data network access identifier (DNAI) and the data network name (DNN), and is a network logical concept. In another understanding of EDN, EDN is the peer concept of the central cloud. EDN may be understood as a local data center (geographical location concept), can be identified by DNAI, and can include a plurality of local data networks.

[0053] 2. EAS: EAS is an application deployed on an edge data network, specifically referring to an instance of a server application program (such as social media software, augmented reality (AR), or virtual reality (VR)) deployed and executed on the EDN.

[0054] One or more EASs can be deployed on one application on one or more EDNs. EASs deployed on different EDNs may be considered different EASs of one application. EASs can share one domain name, use one IP address, or use different IP addresses. EASs may also be referred to as edge application instances, application instances, MEC applications (servers), EAS functions, etc.

[0055] 3. Application client (AC): AC is the peer entity of the EAS on the terminal device side. The application client is the client program of the application on the terminal side. The application client may be connected to the application server on the cloud to obtain application services, or may be connected to the EAS deployed and executed in one or more EDNs to obtain application services.

[0056] 4. EES: To better support the deployment of applications in the EDN, the EES can provide some enabling functions to the EAS deployed in the EDN. The EES can support the registration of the EAS, support the authentication and authorization of the terminal device, and provide the IP address information of the EAS to the terminal device. The EES can further support the acquisition of the identifier and IP address information of the EAS, and can further send the identifier and IP address information of the EAS to the ECS. The 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). The EES is referred to as the EES associated with the EAS. The EES can control, manage, or configure the EAS on the EES.

[0058] 5. Edge Enabler Client (EEC): The EEC is a peer entity of the EES on the terminal device side. The EEC is configured to register information about the EEC and information about the AC with the EES, perform security authentication and authorization, obtain the IP address of the EAS from the EES, and provide edge computing enabling functions to the AC. For example, the EAS discovery service returns the IP address of the EAS to the AC.

[0059] The application user concludes a service contract with the provider of the application that provides services to the application user. The application user logs in to the AC on the terminal device and communicates with the EAS using the connection between the AC and the EAS. The EEC is a middleware layer and is generally arranged within the operating system or between the AC and the operating system. The AC can obtain edge enable services from the EEC via an application programming interface (API).

[0060] 6. Edge Configuration Server (ECS): The ECS is responsible for the configuration of the EDN. One or more EESs can be registered with the ECS, and then the EES information can be provided to the terminal device.

[0061] To facilitate the understanding of the embodiments of this application, some basic concepts of the embodiments of this application are briefly described.

[0062] 1. Two-stage discovery mechanism of EAS: The two-stage discovery mechanism of EAS can include, but is not limited to, the following two possible implementation forms.

[0063] In the first possible implementation form, the EEC first discovers the EES using the ECS corresponding to the EES discovery (also referred to 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 EES discovery procedure.

[0065] Step 201: The EEC sends an EES discovery request (also referred to as a service provisioning request) message to the ECS.

[0066] For example, the 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 can include an identifier of the EAS.

[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 the EES registered with the ECS, that is, the EES that matches the EES discovery request message, based on the AC configuration information and the 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 includes information about at least one EES. The message may further include, for example, EDN connection information.

[0071] The information about each EES can be shown in Table 1. The information about each EES includes, but is not limited to, the following content: an EES identifier and an endpoint address of the EES (for example, a uniform resource identifier (URI) or an 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, and the EES discovery response message includes a cause of 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, the EAS discovery request message can include the identifier and security credentials of the EEC, and can 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 an EAS based on the EAS discovery request message.

[0077] For example, the EES can identify an EAS based on the EAS discovery filter and the UE's location information (obtainable from the 3GPP (registered trademark) 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 the EAS discovery filter, the EES can send an EAS instantiation request message to the EAS management system. After receiving the EES's EAS instantiation request message, the EAS management system performs EAS instantiation and sends the instantiation result to the EES. If the EAS instantiation is successful, the instantiation result includes 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 the EAS discovery fails, for example, the EAS discovery fails because the instantiation of the EAS fails. The EAS discovery response message includes the cause of the failure.

[0081] Furthermore, after receiving the EAS discovery response message, the EEC routes the application data traffic to the EAS based on the information about the received EAS.

[0082] [Table 1]

[0083] The above-described two-stage discovery mechanism of the EAS is applicable to the case initiated by the EEC, applicable to the initial discovery of the EAS (for example, the initial EAS is discovered after the AC is installed or activated), or the EEC detects an application context relocation event (for example, the movement of the UE, and the above-described two-stage discovery mechanism of the EAS aims to discover the target EAS (T-EAS)).

[0084] In a second possible implementation form, the source edge application server (S-EAS) triggers the source edge enabler server (S-EES) to request the ECS to discover the target edge enabler server (T-EES), and then the S-EES requests the T-EES to discover the T-EAS.

[0085] As shown in FIG. 5, the S-EAS detects an application context relocation event and starts the EAS discovery procedure, specifically as follows.

[0086] Step 501: The S-EAS sends an EAS discovery request message to the S-EES.

[0087] The EAS discovery request message may include an EAS ID, security credentials, an EAS discovery filter, etc.

[0088] Step 502: The S-EES checks whether the S-EES is permitted to discover the requested T-EAS. If the S-EES is permitted to discover the requested T-EAS, the S-EES performs T-EAS discovery.

[0089] For the specific process, please refer to the procedure shown in Figure 6.

[0090] Step 503: The S-EES sends the EAS discovery request message to the T-EES.

[0091] Step 504: The T-EES determines the 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 the S-EES initiates an EAS discovery request message to the T-EES, if the T-EES does not have an available EAS corresponding to the current UE location or AC application requirements, the T-EES sends an EAS instantiation request message to the EAS management system. After receiving the EAS instantiation request of the EES, the EAS management system performs EAS instantiation and sends the instantiation result to the T-EES. If the EAS instantiation is successful, the instantiation result includes information about the instantiated EAS, that is, information about the T-EAS.

[0094] Step 505: The T-EES sends an EAS discovery response message to the S-EES. The EAS discovery response message includes information about the 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 for S-EES to discover T-EES.

[0097] Step 601: S-EES sends a target EES discovery (also referred to as retrieve EES) request message to ECS.

[0098] For example, the retrieve EES request message may include UE location information, UE ID, EAS ID corresponding to S-EAS, target DNAI, etc.

[0099] Step 602: ECS determines T-EES based on the target EES discovery request message.

[0100] For details, refer to step 202 in Figure 2.

[0101] Step 603: ECS sends a target EES discovery response message to S-EES.

[0102] For example, the target EES discovery response message includes information about T-EES, etc.

[0103] The aforementioned two-step discovery mechanism of EAS is for the case 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 an application context relocation event (e.g., UE movement).

[0104] 2. EAS instantiation To dynamically schedule and flexibly use resources, the EAS can be dynamically instantiated to meet application requirements. For example, when the EAS corresponding to application A in the edge data network is not accessed by a user (or after the last user finishes accessing and leaves), the EAS may be terminated. When a user accesses the EAS (or when the first user accesses the EAS), the EAS can be dynamically instantiated based on application requirements (such as virtual resource information, required bandwidth, or required latency).

[0105] In the current standard, dynamic instantiation of the EAS is possible. In other words, when the edge data network accessed by the user does not have the required EAS, a request to the EAS management system can be initiated to trigger the instantiation of the EAS.

[0106] 3. Status Information of EAS The status information of the EAS can indicate that the status of the EAS is an instantiated state, or a state where it can be instantiated but has not yet been instantiated, etc.

[0107] The status of the EAS is the instantiated state, which means that the EAS has completed the instantiation process. When the status of the EAS is the instantiated state, the EAS may be an available EAS, that is, an instantiated and available EAS. In other words, the EAS can provide a service application corresponding to the terminal device. In this case, the status can also be referred to as the available state, or the instantiated and available state. Alternatively, when the status of the EAS is the instantiated state, the EAS may be an unavailable EAS, that is, an instantiated and unavailable EAS. For example, the load of the EAS may be greater than a preset threshold, or the EAS may be a failed EAS. As a result, even if the EAS is instantiated, the EAS cannot provide a service application corresponding to the terminal device. In this case, the status can also be referred to as the unavailable state, or the instantiated and unavailable state. Furthermore, an instantiated and unavailable state EAS can become an instantiated and available EAS again when the load decreases or the failure is corrected.

[0108] In this application, it should be noted that the following status of the EAS is the instantiated state, which specifically means that the EAS is an available EAS, or an instantiated and available EAS, and the EAS can provide a service application corresponding to the terminal device.

[0109] The status of the EAS is a state where it is instantiable but not yet instantiated, which means that the EAS can be instantiated but has not been instantiated.

[0110] The status of the EAS is instantiable but not yet instantiated, which can be understood as the EAS being an available EAS (i.e., an EAS available after instantiation). The state of being instantiable but not yet instantiated can also be explained as a specific case of the available state.

[0111] Alternatively, the status of the EAS is instantiable but not yet instantiated, which can be understood as the EAS being an unavailable EAS (i.e., an EAS currently unavailable because it has not been instantiated). The state of being instantiable but not yet instantiated can also be explained as a specific case of the unavailable state.

[0112] Alternatively, the state of being instantiable but not yet instantiated is a new status other than the unusable state and the available state.

[0113] In addition, the status information of the EAS may further include a non-instantiable state. The status of the EAS is non-instantiable, which means that the virtual resources required for EAS instantiation are not available, so EAS instantiation cannot be completed. If the status of the EAS is non-instantiable, it can be understood that the EAS is an unavailable EAS. The non-instantiable state can also be explained as a specific case of the unavailable state.

[0114] To select an appropriate EES, one embodiment of the present application provides a communication method. First, status information of a plurality of edge application servers is obtained, and one edge enabler server is further determined based on the status information of the plurality of edge application servers. In this case, the status of the edge application server 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 the edge enabler servers on a plurality of edge enabler servers need to be instantiated. Therefore, the problem of waste of edge data network resources caused by instantiation of unnecessary edge application servers can be avoided.

[0115] Hereinafter, the above method will be described with reference to FIGS. 8 and 9.

[0116] As shown in FIG. 8, the 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 an identifier of a first edge application server.

[0118] In a possible implementation form, the edge configuration server can receive a request message from the edge enable client. Corresponding to step 820, the edge configuration server sends a response message to the edge enable 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 the specific content included in the EES discovery request message and the specific content included in the EES discovery response message, please refer to steps 201 and 203. Details will not be repeated here. In this case, the request message can include AC configuration information, and the identifier of the first edge application server can be conveyed in the AC configuration information.

[0119] In another possible implementation form, the edge configuration server can receive a request message from the source edge enable server. Corresponding to step 820, the edge configuration server can send a response message to the source edge enable 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 the specific content included in the target EES discovery request message and the specific content included in the target EES discovery response message, please refer to steps 601 and 603. Details will not be repeated here. In this case, the identifier of the first edge application server can be provided to the source edge enable server using the source edge application server. For example, please refer to step 501. The EAS discovery request message sent from the S-EAS to the S-EES can include an EAS ID.

[0120] In FIG. 8, for the sake of explanation, note that only an example is used in which the edge configuration server receives a request message from the edge enable client and sends a response message to the edge enable client. In other words, FIG. 8 is described based on the first possible implementation form of the aforementioned two-step discovery mechanism of EAS. Based on the related description of the second possible implementation form of the two-step discovery mechanism of EAS, it will be understood that the edge enable client may alternatively be replaced by the source edge enable server, and the first edge enable server may be replaced by the target edge enable server.

[0121] Step 810: Based on the status information of a plurality of first edge application servers, the edge configuration server determines one first edge enable server, 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.

[0122] It will be understood that before the edge configuration server determines one first edge enable server based on the status information of a plurality of first edge application servers, the edge configuration server can first obtain the status information of the plurality of first edge application servers. For example, before step 800, the edge configuration server obtains the status information of a plurality of first edge application servers. Alternatively, after step 800, the edge configuration server obtains the status information of a plurality of first edge application servers. This is not limited in this application.

[0123] In a possible implementation form, the edge configuration server can obtain the status information of a plurality of first edge application servers from a plurality of edge enabler servers. It can also be explained that a plurality of edge enabler servers provide the status information of the corresponding first edge application servers for the edge configuration server.

[0124] Here, a plurality of edge enabler servers are respectively registered with the first edge application servers. It can be understood that the first edge application servers registered with different edge enabler servers are different edge application servers of 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. EAS#1 registered with EES#1 and EAS#1 registered with EES#2 are different EASs of the same application.

[0125] For example, the edge enabler server sends the identifier of the edge enabler server, 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 a 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 the ECS, EES#1 sends the identifier of EES#1, the status information of EAS#1, the identifier of EAS#1, the status information of EAS#2, and the identifier of EAS#2 to the ECS. EES#2 sends the identifier of EES#2, the status information of EAS#1, the identifier of EAS#1, the status information of EAS#3, and the identifier of EAS#3 to the ECS.

[0127] Note that the edge enable server can obtain the status information of edge application servers registered in the edge enable server in multiple ways.

[0128] Method 1: The edge enable server receives the identifier of the edge application server and the status information of the edge application server from the edge application server. The status of the edge application server is in an instantiated state.

[0129] For example, the edge application server sends a registration request message to the edge enable server. The registration request message includes the identifier of the edge application server and the status information of the edge application server. Alternatively, the edge application server sends a registration update message to the edge enable server. The registration update message includes the identifier of the edge application server and the status information of the edge application server.

[0130] Method 2: The edge enable server receives the identifier of the edge application server and the status information of the edge application server from the edge application server management system. The status of the edge application server is in a state where it can be instantiated but has not yet been instantiated.

[0131] Furthermore, the edge enable server can store the acquired content in the configuration information (EES profile) of the edge enable server.

[0132] For example, Table 2 shows the correspondence between the EES registered in the ECS, the EAS registered in the EES, and the status information of the EAS registered in the EES.

[0133]

Table 2

[0134] The following can be understood from Table 2.

[0135] a. The EESs registered in the ECS include EES#1, EES#2, EES#3, and EES#4.

[0136] b. The EASs registered in EES#1 include EAS#1 and EAS#2.

[0137] The EASs registered in EES#2 include EAS#1, EAS#2, and EAS#3.

[0138] The EASs registered in EES#3 include EAS#1 and EAS#2.

[0139] The EASs registered in EES#4 include EAS#4 and EAS#5.

[0140] c: The status of EAS#1 registered in EES#1 is the instantiated state, the status of EAS#1 registered in EES#2 is the instantiated state, and the status of EAS#1 registered in EES#3 is instantiable but not yet instantiated.

[0141] 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.

[0142] The status of EAS#3 registered in EES#2 is the instantiated state.

[0143] The status of EAS#4 registered in EES#4 is the instantiated state.

[0144] The status of EAS#5 registered in EES#4 is the instantiated state.

[0145] In a possible implementation, the edge configuration server can first determine the status information of a plurality of first edge application servers based on the identifier of the first edge application server. For example, the edge configuration server can execute a query or search to obtain the status information of a plurality of first edge application servers based on the identifier of the first edge application server, and further determine whether there is a first edge application server in the instantiated state based on the status information of the plurality of first edge application servers.

[0146] If there is a first edge application server in the instantiated state, the edge configuration server can send information about the edge enabler server corresponding to one or more first edge application servers in the instantiated state, so that the edge enabler client or the source edge enabler server can preferentially select a first edge application server that is in the instantiated state 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 can further refer to one or more of the following criteria bases.

[0148] That is, a list of edge computing service providers (ECSPs) prioritized by the AC, an application context relocation (ACR) scenario prioritized by the AC, a service area of the EES, DNAI information of the EES, and location information of the terminal device.

[0149] The list of ECSPs prioritized by the AC and the ACR scenario prioritized by the AC are the content included in the AC configuration information.

[0150] The above-mentioned content may be included in the request message or may be obtained by the edge configuration server. The specific content based on the standard is not limited in this application.

[0151] For example, Table 2 is used as an example. When the identifier of the first edge application server is EAS#1, the edge configuration server determines the status information of a plurality of EAS#1 including the following based on EAS#1 and Table 2.

[0152] That is, the status of EAS#1 registered in EES#1 is the instantiated state, the status of EAS#1 registered in EES#2 is the instantiated state, and the status of EAS#1 registered in EES#3 is instantiable but not yet 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. The status information of EAS#1 registered in EES#3 is instantiable but not yet instantiated. However, the edge application server selected by the edge configuration server can only include EES#1 and / or EES#2 and does not include EES#3. As a result, it can be understood that available EASs are preferentially used to avoid wasting resources caused by instantiating new EASs. Furthermore, when 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, that is, it can send an edge application server discovery request message to one or more EESs.

[0154] If it is determined that there is no first edge application server in an instantiated state, 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 is no first edge application server in an instantiated state, a new first edge application server can be instantiated to provide the corresponding service application to the terminal device.

[0155] In other words, before the edge configuration server determines one first edge enabler server based on the status information of a plurality of first edge application servers, the edge configuration server determines, based on the status information of the plurality of first edge application servers, that there is no first edge application server in a state where the status is instantiated.

[0156] For example, Table 2 is used as an example. When the identifier of the first edge application server is EAS#2, the edge configuration server can determine the status information of a plurality of EAS#2 including the following based on EAS#2 and Table 2, that is, 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, the status of EAS#2 registered in EES#3 is instantiable but not yet instantiated. In other words, the statuses of EAS#2 registered in EES#1, EES#2, and EES#3 are instantiable but not yet instantiated. Further, the edge configuration server can select one EES from EES#1, EES#2, and EES#3 based on AC configuration information, location information of the terminal device, etc.

[0157] According to the foregoing design, the edge configuration server determines one first edge enabler server based on the status information of a plurality of 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 in a state where it can be instantiated but has not yet been instantiated. Therefore, the edge configuration server can then send only the 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 all the first edge enabler servers on multiple edge enabler servers cannot be instantiated. As a result, the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0158] In a possible implementation form, it will be understood that the edge configuration server determines a plurality of first edge enabler servers based on the status information of a plurality of first edge application servers and sends a response message. The response message includes information about the plurality of first edge enabler servers. In this case, by using an instruction information or a protocol, the edge enabler client can send the edge application server discovery request message to only one first edge enabler server each time. As a result, it will be further convinced that the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0159] In addition, in a possible scenario, if the edge configuration server fails to obtain the status information of the first edge application server, or if the statuses of multiple first edge application servers are each in a non-instantiable state, the discovery of the edge enabler server fails. The edge configuration server sends a response message, and the response message indicates that the discovery of the edge enabler server has failed and can convey the cause of the failure in discovering the edge enabler server.

[0160] Step 820: The edge configuration server sends a response message. The response message includes information about the first edge enabler server.

[0161] The information about the first edge enabler server can include the identifier of the first edge enabler server, the endpoint address of the first edge enabler server, etc. For details, please refer to Table 1.

[0162] Optionally, after the edge enabler client receives the response message, the method can 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 can further include other content. For details, please refer to Step 301.

[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, based on the received edge application server discovery request message, the first edge enabler server queries the status information of the first edge application server discovery request message, and 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 not yet instantiated, and then 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 instantiation result of the edge application server to the first edge enabler server.

[0168] For example, based on the received edge application server instantiation request message, the edge application server management system executes the instantiation of the edge application server and determines the instantiation result of the edge application server.

[0169] If the instantiation result of the edge application server indicates that the instantiation of the first edge application server is 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 fails, 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, when 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 includes information about the first edge application server, and the procedure ends.

[0173] For example, when 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 indicates that the discovery of the first edge application server failed. In addition, the edge application server discovery response message can 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 indication information to the edge configuration server, and the indication information indicates that the instantiation of the first edge application server corresponding to the first edge enabler server failed.

[0175] Step 880: The edge configuration server sends information about one second edge enabler server other than the first edge enabler server to the edge enabler client, and the status of the first edge application server corresponding to the second edge enabler server is in a state where it can be instantiated but has not yet been instantiated.

[0176] For example, based on the status information of a plurality of first edge application servers, can the edge configuration server determine information about one second edge enabler server other than the first edge enabler server? Or, based on the status information of a plurality of first edge application servers other than the status information of the first edge application server corresponding to the first edge application enabler server, can the edge configuration server determine information about one second edge enabler server other than the first edge enabler server?

[0177] For example, Table 2 is used as an example. When the identifier of the first edge application server is EAS#2, the edge configuration server can determine the status information of a plurality of EAS#2 including the following based on EAS#2 and Table 2, that is, 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. Further, the edge configuration server can determine one EES, for example, EES#2, from EES#1, EES#2, and EES#3 based on, for example, AC configuration information and the location information of the terminal device. When 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, for example, EES#3, from EES#1 and 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] In FIG. 9, for the sake of explanation, note that only an example where an edge configuration server receives a request message from an edge enable client and sends a response message to the edge enable client is used. In other words, FIG. 9 is described based on the first possible implementation form of the aforementioned two-stage discovery mechanism of EAS. Based on the related description of the second possible implementation form of the two-stage discovery mechanism of EAS, it should be understood that the edge enable client may alternatively be replaced by a source edge enable server, and the first edge enable server may be replaced by a target edge enable server.

[0180] Step 900: The edge configuration server receives a request message. The request message is used to request information about the edge enable server, and the request message includes an identifier of the first edge application server.

[0181] Regarding step 900, refer to the related content of step 800. Details are not repeated here.

[0182] Step 910: The edge configuration server sends a response message. 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.

[0183] 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

[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. Further, the edge configuration server determines the status information of the first edge application server corresponding to each of the at least one edge enabler server from the status information of the first edge application server corresponding separately to the edge enabler server and the status information stored in the edge configuration server.

[0185] The edge enabler server obtains the status information of the edge application server registered with the edge enabler server in the two aforementioned ways. Details are not repeated here. After the edge enabler server obtains the status information of the edge application server registered with the edge enabler server, the edge enabler server can send the identifier of the edge enabler server, 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 a 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. When the identifier of the first edge application server is EAS#2, the edge configuration server can determine, based on Table 2, that each of EES#1, EES#2, and EES#3 is registered with EAS#2. Further, 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, location information of the terminal device, 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. When the identifier of the first edge application server is EAS#1, the edge configuration server can determine, based on Table 2, that each of EES#1, EES#2, and EES#3 is registered with EAS#1. Further, 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, location information of the terminal device, 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 in an instantiated state, the status of EAS#1 registered with EES#2 is in an instantiated state, 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 corresponding to at least one edge enabler server respectively, and the status of the first edge application server corresponding to the first edge enabler server is in a state where it can be instantiated but has not been instantiated yet.

[0189] For example, the edge enabler client can determine whether there is a first edge application server in a state where the status has been instantiated based on the status information of the first edge application server corresponding to at least one edge enabler server respectively.

[0190] In a possible design, when the status information of the first edge application server corresponding to at least one edge enabler server respectively includes that the status of the first edge application server is in an instantiated state, 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, information about EES#2, and information about EES#3. The status information of EAS#1 registered in EES#1 is in an instantiated state, the status of EAS#1 registered in EES#2 is in an instantiated state, and the status of EAS#1 registered in EES#3 is instantiable but not yet instantiated. Since the status of EAS#1 registered in EES#1 is in an instantiated state and the status of EAS#1 registered in EES#2 is in an instantiated state, the edge enabler client can select EES#1 and / or EES#2.

[0192] In a possible design, when the status information of the first edge application server corresponding to at least one edge enabler server does not include that the status of the first edge application server is in an instantiated state, the edge enabler client can select 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. In other words, based on the status information of the first edge application server corresponding to at least one edge enabler server, before determining one first edge enabler server, the edge enabler client determines that there is no first edge application server in an instantiated state based on the status information of the first edge application server corresponding to at least one edge enabler server.

[0193] For example, the response message includes information about EES#1, information about EES#2, and information about EES#3. 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. The status of EAS#2 registered in EES#3 is instantiable but not yet instantiated. In other words, in this case, the status information of EAS#2 is not instantiated, and the status information of 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, when all the status information of the first edge application server corresponding to at least one edge enabler server is in a state where it cannot be instantiated, the edge enabler client determines that the discovery of the edge enabler server has failed.

[0195] According to the foregoing design, the edge enabler client determines one first edge enabler server based on the status information of the first edge application server corresponding to at least one edge enabler server respectively. 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 the 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 all the first edge enabler servers on multiple edge enabler servers cannot be instantiated, and as a result, the problem of waste of edge data network resources caused by the instantiation of unnecessary edge application servers can be avoided.

[0196] Optionally, after the edge enabler client receives the response message, the method can further include the following steps.

[0197] For steps 930 to 960, refer to steps 830 to 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 respectively.

[0199] For example, the edge enable client can determine a second edge enable server other than the first edge enable server among at least one edge enable server based on the status information of the first edge application server that separately corresponds to the edge enable servers other than the first edge enable server.

[0200] The status of the first edge application server corresponding to the second edge enable server is instantiable but not yet instantiated.

[0201] For example, the response message includes information about EES#1, information about EES#2, and information about EES#3. 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. The status of EAS#2 registered in EES#3 is instantiable but not yet instantiated. The edge enable 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 in EES#2 has failed, the edge enable client can select one of EES#1 and EES#3, for example, EES#1.

[0202] In the current standard discussions, two solutions are available to solve the problem of resource waste in EAS instantiation.

[0203] Solution 1: The status information of the EAS is provided to the EEC in the EES discovery (also referred to as service provisioning) procedure. The EEC executes EES selection, and the EAS discovery request message triggers the EES to determine whether EAS instantiation is necessary.

[0204] Solution 2: The status information of the EAS is provided in the EAS discovery procedure. In this case, the EAS discovery request does not trigger the EES to determine whether EAS instantiation is required, but a new procedure is introduced to perform EAS selection (for example, the EAS selection request procedure can also be referred to as another procedure), and based on the new procedure, the EES is triggered to determine whether EAS instantiation is required.

[0205] From the perspective of EES performance, the differences after the EES receives the EAS discovery request message are as follows.

[0206] In Solution 1, after receiving the EAS discovery request, the EES determines whether EAS instantiation is required. The decision process is as follows: that is, if there is no instantiated EAS, the EES sends an EAS instantiation request message to the EAS management system based on the information about at least one EAS that can be instantiated but has not yet been instantiated. If there is an instantiated EAS, the EES does not need to send an EAS instantiation request message to the EAS management system.

[0207] In Solution 2, the EEC can separately send the EAS discovery request message to multiple EESs. For each EES, after the EES receives the EAS discovery request message, EAS instantiation is not necessary. In other words, it is not necessary to execute the aforementioned decision process, but the EES sends information about at least one EAS that is instantiable but not yet instantiated to the EEC. Further, the EEC selects one EES from multiple EESs based on multiple EAS discovery response messages fed back by multiple EESs. When the EEC selects one EAS that is instantiable but not yet instantiated on the EES, the EEC notifies the EES of the information about the EAS (i.e., the aforementioned new procedure). 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 includes information about the EAS notified by the EEC.

[0208] In Solution 1 and another existing solution, it can be seen that after the EES receives the EAS discovery request message, the EES determines whether EAS instantiation is required based on the existing logic. 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 the EES's understanding of the EAS discovery request message in Solution 1 (and another existing solution). In order to avoid the EES not being able to accurately understand the EAS discovery request message, three examples for solving the problem are provided below.

[0209] Example 1: As shown in Figure 10.

[0210] S1001: The EEC sends the first EAS discovery request message to the first EES, and the EEC sends the second EAS discovery request message to the second EES.

[0211] The first EAS discovery request message includes first instruction information, and the first EAS discovery request message is used to request information about an EAS that meets the AC requirements on the first EES. The second EAS discovery request message includes first instruction information, and the second EAS discovery request message is used to request information about an EAS that meets the AC requirements on the second EES. The first instruction information indicates that EAS instantiation is not required.

[0212] For example, the EEC can send N EAS discovery request messages to N EESs. N is a positive integer, and the N EESs correspond one-to-one with the N EAS discovery request messages.

[0213] Each EAS discovery request message includes first instruction information, and the first instruction information indicates that EAS instantiation is not required. The i-th EAS discovery request message is used to request information about an EAS that meets the AC requirements on the i-th EES, where i is a positive integer and i is less than or equal to N.

[0214] For example, each EAS discovery request message can further include an EEC identifier and security credentials, and can 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 FIG. 10, for the sake of illustration, only an example where the value of N is 2 and two EESs include a first EES and a second EES is used. It will be understood that the value of N may be 3 or more.

[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 it is not necessary to determine whether the first EES requires EAS instantiation or has requirements for EAS instantiation. In other words, in the case of an EAS that is instantiable but not yet instantiated, the first EES does not need to send an EAS instantiation request message to the EAS management system. For the meaning that the second EES does not require EAS instantiation, refer to the meaning that the first EES does not require EAS instantiation. Details are not repeated 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 in the first EES, and information about at least one EAS that is instantiable but not yet instantiated and registered in the first EES, or information about at least one EAS that is instantiable but not yet instantiated and registered in the first EES.

[0220] The second EAS discovery response message includes information about at least one instantiated EAS registered in the second EES, and information about at least one EAS that is instantiable but not yet instantiated and registered in the second EES, or information about at least one EAS that is instantiable but not yet instantiated and registered in the second EES.

[0221] For example, N EESs send N EAS discovery response messages to the EEC.

[0222] The N EESs correspond one-to-one with the N EAS discovery response messages.

[0223] The i-th EAS discovery response message contains 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 contains information about at least one instantiated EAS registered on the i-th EES and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on the i-th EES.

[0224] For example, the first EES is used as an example. After the first EES receives the first EAS discovery request message, the first EES can preferentially determine information about at least one instantiated EAS registered on the first EES based on the EAS discovery filter and the UE's location information (e.g., obtainable from the 3GPP (registered trademark) core network). If it is found that the instantiated EAS is not available, information about at least one EAS that is instantiable on the first EES but has not yet been instantiated can be determined.

[0225] Alternatively, the first EES can determine information about at least one instantiated EAS registered on the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on the first EES, or information about at least one EAS that is instantiable but has not yet been instantiated and is registered on the first EES, based on the EAS discovery filter and the UE's location information.

[0226] Furthermore, when an EAS discovery response message is instantiable but does not contain information about EASs that are not yet instantiated and contains only information about at least one instantiated EAS, after the EEC receives the EAS discovery response message, the EEC can provide information about at least one instantiated EAS to the AC. Based on the received information about at least one instantiated EAS, the AC routes application data traffic to that one instantiated EAS. Alternatively, the EEC selects one EAS from the information about at least one instantiated EAS and provides information about the selected EAS to the AC. The AC routes application data traffic to the EAS based on the information about the EAS selected by the EEC.

[0227] In the following, for the sake of explanation, only one example is used where each EAS discovery response message contains information about at least one EAS that is instantiable but not yet instantiated, or each EAS discovery response message contains information about at least one instantiated EAS and information about at least one EAS that is instantiable but not yet instantiated.

[0228] S1004: When the EEC selects a first EAS on a first EES, the EEC sends a first request message to the first EES. The first request message contains information about the first EAS, and the first request message requests the first EES to select the first EAS, that is, to trigger the instantiation of the first EAS. The first EAS is one of at least one EAS that is instantiable but not yet instantiated on the first EES.

[0229] The first request message may also be referred to as an EAS selection request message. The EAS selection request message indicates the EAS selected by the EEC. Alternatively, the EAS selection request message can have another name instead. This is not limited in this application.

[0230] For example, the EEC selects the 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 the sake of explanation, only an example where the EES corresponding to the first EAS is the first EES is used.

[0231] S1005: The first EES sends an EAS instantiation request message to the EAS management system based on the received first request message. The EAS instantiation request message contains information about the first EAS.

[0232] S1006: The EAS management system executes the EAS instantiation.

[0233] S1007: The EAS management system sends an EAS instantiation response message to the first EES. The EAS instantiation response message contains the instantiation result of the first EAS.

[0234] The instantiation result of the first EAS indicates whether the instantiation of the first EAS is successful or failed.

[0235] If the instantiation of the first EAS is successful, the instantiation result of the first EAS further includes information about the instantiated first EAS, for example, 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 includes the instantiation result of the first EAS.

[0238] Furthermore, after receiving the first response message, if the instantiation of the first EAS is successful, the EEC provides information about the instantiated first EAS to the AC, and the AC routes the application data traffic to the first EAS.

[0239] It should be noted that if the EAS discovery request message does not include the first indication information and the EES detects that the EAS instantiated by the EES is not 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 not yet instantiated, that is, following the existing procedure.

[0240] In the aforementioned Example 1, since the EAS discovery request message includes the first indication information, the problem that the EES cannot accurately understand the EAS discovery request message after receiving it can be solved. Furthermore, the backward compatibility or compatibility problem of the EAS discovery request message for different systems can be further solved.

[0241] Furthermore, in the prior art, if the EES detects that the instantiated EAS is not 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 not yet instantiated. As a result, the EAS management system can instantiate multiple EASs. In practice, the AC or the EEC selects only one EAS. Therefore, it causes waste of network resources.

[0242] However, in the above Example 1, compared with the prior art, based on the first indication information in the EAS discovery request message, the EES determines that EAS instantiation is not necessary. As a result, when the EES receives the EAS discovery request message, it does not send an EAS instantiation request message to the EAS management system. Therefore, the EAS discovery request message can be accurately understood. Further, each of the plurality of EAS discovery response messages includes information about at least one EAS that is instantiable but not yet instantiated. Thus, the EEC can select an EAS that is instantiable but not yet instantiated and notify the corresponding EES of the EAS. The EES requests the EAS management system to instantiate the EAS, and as a result, the aforementioned problem of waste of network resources can be avoided.

[0243] Example 2: As shown in FIG. 11.

[0244] S1101: The EEC determines one solution from the first solution and the second solution.

[0245] The first solution and the second solution are pre-set solutions. The first solution is that the EEC does not require EAS instantiation after receiving the EAS discovery request message.

[0246] The second solution is that the EES requires EAS instantiation after receiving the EAS discovery request message, or the EES needs to determine whether EAS instantiation is necessary after receiving the EAS discovery request message. The second solution may also be described as follows: that is, when the EES detects that the instantiated EAS is not available after receiving the EAS discovery request message, the EES sends an EAS instantiation request message to the EAS management system based on the information about at least one EAS that is instantiable but not yet instantiated.

[0247] S1102: The EEC sends the first EAS discovery request message to the first EES, and the EEC sends the second EAS discovery request message to the second EES.

[0248] The first EAS discovery request message includes second instruction information, and the second instruction information includes an identifier of a solution determined by the EEC. The second EAS discovery request message includes the second instruction information. The second instruction information includes an identifier of a 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 a preset solution based on the received identifier of the 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 a preset solution based on the received identifier of the 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 preset solutions of each EES are the same as the preset solutions of the EEC and include the first solution and the second solution.

[0251] S1104A: The first EES sends the first EAS discovery response message to the EEC. The second EES sends the 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 on the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on 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 on the second EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on the second EES.

[0253] For S1104A, refer to S1003. Details are not repeated here.

[0254] For S1105A - S1109A, refer to S1004 - S1008. Details are not repeated here.

[0255] S1104B: The first EES sends the first EAS discovery response message to the EEC. The second EES sends the second EAS discovery response message to the EEC.

[0256] The first EAS discovery response message includes information about at least one instantiated EAS registered on the first EES. The second EAS discovery response message includes information about at least one instantiated EAS registered on the second EES.

[0257] For example, a first EES is used as an example. The first EES can preferentially determine information regarding at least one instantiated EAS registered on the first EES based on an EAS discovery filter and the UE's location information (e.g., obtainable from a 3GPP (registered trademark) core network). If it is found that the instantiated EAS is not available, information regarding at least one EAS that can be instantiated but has not yet been instantiated on the first EES can be determined. Further, the first EES transmits an EAS instantiation request message to the EAS management system based on information regarding at least one EAS that can be instantiated but has not yet been instantiated on the first EES. Therefore, in this case, the first EAS discovery response message includes only information regarding at least one instantiated EAS registered on 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 information regarding at least one instantiated EAS registered on the first EES to the AC, and the AC routes application data traffic to one of at least one instantiated EAS based on the received information regarding at least one instantiated EAS. Alternatively, the EEC determines one EAS from the information regarding at least one instantiated EAS registered on the first EES and provides the information regarding the EAS to the AC. The AC routes application data traffic to the EAS based on the information regarding the EAS.

[0259] In the foregoing Example 2, the EEC and EES can preset a plurality of solutions. The EEC selects one solution from the plurality of preset solutions and includes the identifier of the solution in the EAS discovery request message. The EES can accurately understand the EAS discovery request message based on the identifier of the solution in the received EAS discovery request message. Furthermore, the backward compatibility or compatibility issues of the EAS discovery request message for different systems can be further resolved.

[0260] Example 3: As shown in FIG. 12.

[0261] S1201: The EEC sends the first EAS discovery request message to the first EES, and the EEC sends the 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 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 the status information of the EAS. Furthermore, the first EES supports the EAS selection procedure (i.e., a new procedure), and the first EES does not require EAS instantiation. The EES configuration information may be an EES profile. The status information of the EAS may also be referred to as the instantiation status information of the EAS. The status information of the EAS includes the instantiated state or the state that can be instantiated but has not yet been instantiated.

[0264] Solution B: The first EES determines, based on the EES configuration information, that the EES configuration information includes the status information of the EAS, and the first EES determines whether EAS instantiation is required.

[0265] In addition to the aforementioned solution A and solution B, another solution may be included. This is not limited in this application.

[0266] The operations performed by the second EES are the same as those performed by the first EES. Details will not be repeated here.

[0267] If the first EES does not require EAS instantiation, S1203A is executed. If the first EES determines 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 determines whether EAS instantiation is required, S1203B is executed.

[0268] S1203A: The first EES sends the first EAS discovery response message to the EEC. The second EES sends the 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 on the first EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on 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 on the second EES, and information about at least one EAS that is instantiable but has not yet been instantiated and is registered on the first EES.

[0270] Regarding S1203A, refer to S1003. Details will not be repeated here.

[0271] For S1204A to S1208A, refer to S1004 to S1008. Details will not be repeated here.

[0272] S1203B: The first EES sends the first EAS discovery response message to the EEC. The second EES sends the second EAS discovery response message to the EEC.

[0273] The first EAS discovery response message includes information about at least one instantiated EAS registered in the first EES. The second EAS discovery response message includes information about at least one instantiated EAS registered in the second EES.

[0274] For S1203B, refer to S1104B. Details will not be repeated here.

[0275] In the aforementioned Example 2, when receiving an EAS discovery request message, the EES refers to whether the capability information and EES configuration information regarding the EES include information about the EAS to understand the EAS discovery request message. In other words, after the EES receives the EAS discovery request message, the problem that the EES cannot accurately understand the EAS discovery request message can be solved. Furthermore, the backward compatibility or compatibility issue of the EAS discovery request message for different systems can be further solved.

[0276] FIG. 13 is a possible exemplary block diagram of a communication device according to an embodiment of the present application. Device 1300 includes transceiver module 1320 and processing module 1310. Transceiver module 1320 can include a receiving unit and a transmitting unit. Processing module 1310 is configured to control and manage the operation of device 1300. Transceiver module 1320 is configured to support device 1300 when communicating with another network entity. Optionally, device 1300 may further include a storage unit, which is configured to store program code and data of device 1300.

[0277] Optionally, each module within device 1300 may be implemented using software.

[0278] Optionally, the processing module 1310 may be a processor or a controller, for example, a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuits (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The controller / processor can implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the embodiments of the present application. The processor may be a combination of processors that implement 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 communication interface is a generic term. In a specific implementation, the communication interface may include multiple interfaces, and the storage unit may be a memory.

[0279] When the device 1300 is an edge configuration server or a chip within the edge configuration server, the processing module 1310 within the device 1300 can support the device 1300 when executing the operations of the edge configuration server in the foregoing method example, for example, can support the device 1300 when executing step 810 of FIG. 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 instantiable but not yet 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 is instantiated or is instantiable but not yet 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, before determining one first edge enabling server based on the status information of a plurality of first edge application servers, the processing module 1310 is configured to determine that there is no first edge application server in a status where the status is instantiated based on the status information of the plurality of first edge application servers.

[0287] In a possible design, the transceiver module 1320 is configured to receive instruction information, where the instruction information indicates that the instantiation of the first edge application server corresponding to the first edge enabling server has failed, and is also configured to transmit information about one second edge enabling server other than the first edge enabling server, and the status of the first edge application server corresponding to the second edge enabling server is in a state where it can be instantiated but has not yet been instantiated.

[0288] In a possible design, when receiving a request message, the transceiver module 1320 is configured to receive the request message from the edge enabling client, and when transmitting a response message, is configured to transmit the response message to the edge enabling client.

[0289] In a possible design, when receiving a request message, the transceiver module is configured to receive the request message from the source edge enabling server, and when transmitting a response message, is configured to transmit the response message to the source edge enabling server.

[0290] In another example, the processing module 1310 activates the transceiver module 1320 to receive a request message, which is used to request information about the edge enabler server. The request message includes the identifier of the first edge application server, and sends a response message, which includes information about at least one edge enabler server and status information of the first edge application server corresponding to each of the at least one edge enabler server.

[0291] In a possible design, the status information of the first edge application server indicates whether the status of the first edge application server is instantiated or can be instantiated but has not been instantiated yet.

[0292] In a possible design, when receiving a request message, the transceiver module 1320 is configured to receive the request message from the edge enabler client and, when sending a response message, send the response message to the edge enabler client.

[0293] In a possible design, when receiving a request message, the transceiver module 1320 is configured to receive the request message from the source edge enabler server and, when sending a response message, send the response message to the source edge enabler server.

[0294] It should be understood that the apparatus 1300 according to this embodiment of the present application can correspond to the edge configuration server in the foregoing method embodiment, and 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 configuration 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 are not described again here.

[0295] When the device 1300 is an edge enable client or a source edge enable server or a chip within the edge enable client or a chip within the source edge enable server, the processing module 1310 within the device 1300 can support the device 1300 when executing the operations of the edge enable client or the source edge enable server in the foregoing method examples. For example, the processing module 1310 can support the device 1300 when executing step 920 or step 970 of FIG. 9.

[0296] The transceiver module 1320 can support the device 1300 when communicating with the edge configuration server. For example, the transceiver module 1320 can support the device 1300 when executing step 800, step 820, step 830, step 860, step 870, or step 880 of FIG. 8, or step 900, step 910, step 930, or step 960 of FIG. 9.

[0297] For example, the transceiver module 1320 is configured to send a request message to the edge configuration server, the request message is used to request information about the edge enable server, the request message includes an identifier of a first edge application server, receive a response message from the edge configuration server, and 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.

[0298] The processing module 1310 determines one first edge enabler server based on the status information of the first edge application servers respectively 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 of the first edge application server indicates whether the first edge application server is in an instantiated state or is instantiable but not yet instantiated.

[0300] In a possible design, before determining one first edge enabler server based on the status information of the first edge application servers respectively corresponding to at least one edge enabler server, the processing module 1310 is configured to determine that there is no first edge application server with a status of instantiated based on the status information of the first edge application servers respectively corresponding to at least one edge enabler server.

[0301] In a possible design, when the instantiation of the first edge application server corresponding to the first edge enabler server fails, the processing module 1310 determines one second edge enabler server other than the first edge enabler server based on the status information of the first edge application servers respectively 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 device 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 embodiments, and it should be understood that the operations and / or functions of the modules in the device 1300 are separately intended to implement the corresponding steps of the methods of the edge enabler client or the source edge enabler server in the foregoing method embodiments. Therefore, the beneficial effects in the foregoing method embodiments can also be implemented. For the sake of brevity, the details will not be described again here.

[0303] When the device 1300 is an edge enabler server or a chip in the edge enabler server, the processing module 1310 in the device 1300 can support the device 1300 when executing the edge enabler server in the foregoing method example.

[0304] The transceiver module 1320 can support the device 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, when obtaining the status information of the first edge application server, the transceiver module 1320 obtains the status information of the first edge application server from the edge application server management system, and the status information of the first edge application server is configured to indicate that the first edge application server is instantiable but not yet instantiated.

[0308] It should be understood that the apparatus 1300 according to this embodiment of the present application can correspond to the edge enable server in the foregoing method embodiment, and the operations and / or functions of the modules in the apparatus 1300 are separately configured to perform the corresponding steps of the method of the edge enable 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.

[0309] FIG. 14 is a schematic diagram of the structure of a communication apparatus 1400 according to an embodiment of the present application. As shown in FIG. 14, the apparatus 1400 includes a processor 1401.

[0310] When the apparatus 1400 is an edge configuration server or a chip in the edge configuration server, in a possible implementation form, the processor 1401 activates an interface to perform the following operations: an operation of receiving a request message, where the request message is used to request information about the edge enable server and the request message includes an identifier of the first edge application server; an operation of determining one first edge enable server based on the status information of a plurality of first edge application servers, where the status of the first edge application server corresponding to the first edge enable server is instantiable but not yet instantiated; and an operation of sending a response message, where the response message includes information about the first edge enable server.

[0311] In another possible implementation, the processor 1401 activates an interface to perform the following operations: receiving a request message, where the request message is used to request information about the edge enabler server and includes the identifier of the first edge application server; determining one first edge enabler server based on the status information of the 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, where the response message includes information about the first edge enabler server.

[0312] It should be understood that the apparatus 1400 may be further configured to perform other steps and / or operations on the edge configuration server side in the foregoing embodiments. For the sake of brevity, the details are not described again here.

[0313] When the device 1400 is an edge enable client, a source edge enable server, a chip within the edge enable client, or a chip within the source edge enable server, in a possible implementation, the processor 1401 activates an interface to perform the following operations, namely, an operation of sending a request message to an edge configuration server, where the request message is used to request information about the edge enable server, the request message includes an identifier of a first edge application server, an operation of 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 a first edge application server corresponding to each of the at least one edge enable server, and an operation of 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.

[0314] It should be understood that the device 1400 may be further configured to perform other steps and / or operations on the edge enable client or source edge enable server side in the foregoing embodiments. For the sake of brevity, the details are not described again here.

[0315] When the device 1400 is an edge enable server or a chip within the edge enable server, in a possible implementation, the processor 1401 activates an interface to perform the following operations, namely, an operation of obtaining status information of a first edge application server and an operation of sending the identifier of the first edge application server and the status information of the first edge application server to an edge configuration server.

[0316] It should be understood that the device 1400 may be further configured to perform other steps and / or operations on the edge enabling server side in the foregoing embodiments. For the sake of 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 foregoing receiving and transmitting operations. The activated interface may be a logical interface or a physical interface. This is not limited. 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, and the memory 1402 stores the program code in the foregoing method embodiments, whereby the processor 1401 can activate the program code.

[0319] Specifically, when the device 1400 includes the processor 1401, the memory 1402, and the transceiver 1403, the processor 1401, the memory 1402, and the transceiver 1403 communicate with each other via an internal connection path to transmit control signals and / or data signals. In a possible design, the processor 1401, the memory 1402, and the transceiver 1403 may be implemented using chips. The processor 1401, the memory 1402, and the transceiver 1403 may be implemented on the same chip, or may be separately implemented on different chips, or any two functions of the processor 1401, the memory 1402, and the transceiver 1403 may be implemented on one chip. The memory 1402 can store program code, and the processor 1401 activates 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 an application client, an edge enable client, an edge enable server, an edge configuration server, an edge application server, and an edge application server management system. The edge enable client is configured to execute the steps and / or operations on the edge enable client side in the foregoing embodiments, the edge enable server is configured to execute the steps and / or operations on the edge enable server side in the foregoing embodiments, the edge configuration server is configured to execute the steps and / or operations on the edge configuration server side in the foregoing embodiments, and the edge application server management system is configured to execute the steps and / or operations on the edge application server management system side in the foregoing embodiments.

[0321] The method disclosed in the embodiments of the present 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 foregoing method may be implemented by using the hardware integrated logic circuit in the processor or by using instructions in the form of software. The foregoing 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 chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or another integrated chip. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the method disclosed with reference to the embodiments of the present application may be directly executed and realized by using a hardware decoding processor, or may be executed and realized by using a combination of hardware and a software module of the decoding processor.The software module may be disposed in a storage medium that is a mature technology in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is disposed in the memory, and the processor reads information in the memory and completes the steps in the foregoing method in combination with the hardware of the processor.

[0322] It should be understood that the memory in this embodiment of the present application may be a volatile memory, a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM may be used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM). Note 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 the present application, numerical terms such as "first" and "second" are only intended to distinguish different objects, for example, to distinguish different parameter information or messages, and are not intended to limit the scope of the embodiments of the present application. It should be understood that the embodiments of the present application are not limited thereto.

[0324] It should be further understood that the serial numbers of the foregoing processes do not mean the execution order in the embodiments of the present application. The execution order of the processes should be determined based on the functions and internal logics of the processes. The various numbers or serial numbers in the foregoing processes are merely for easy distinction and do not constitute any limitation to the implementation process of the embodiments of the present application.

[0325] It should also be understood that the term "and / or" in this specification only describes the relevant relationship for describing the relevant objects and represents that three relationships may exist. For example, A and / or B can represent the following three cases, that is, the case where only A exists, the case where both A and B exist, and the case where only B exists. In addition, the character " / " in this specification generally indicates the "or" relationship between the relevant objects.

[0326] Unless otherwise specified, the expressions used in the present application similar to the expression "the item includes any one or more of A, B, and C" usually mean that the item can be any one of the following, that is, 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, as well as other combinations of A, B, and C. In the above description, three elements A, B, and C are used as an example for describing the case of optional selection of items. When the expression is "the item includes at least one of A, B,..., and X", in other words, when more elements are included in the expression, according to the foregoing rules, the cases corresponding to the item may also be obtained.

[0327] Those skilled in the art can recognize that, in combination with the examples described in the embodiments disclosed herein, units and algorithm steps can be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether a function is executed by hardware or by software depends on the specific application of the technical solution and design constraints. Those skilled in the art can use different methods to implement the functions described for each specific application, but such implementation is not considered to exceed the scope of this application.

[0328] For the sake of simplicity in description, those skilled in the art can clearly understand by referring to the corresponding processes in the embodiments of the foregoing method for the detailed operation processes of the foregoing systems, devices, and units. Details will not be repeated here.

[0329] It should be understood that in some embodiments provided in this application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into units is only a logical function division, and there may be other divisions during actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or described mutual coupling, direct coupling, or communication connection may be implemented using some interfaces. The indirect coupling or communication connection between devices or units may be implemented in electronic form, mechanical form, or other forms.

[0330] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units. They may be arranged in one place or distributed over multiple network units. To achieve the purpose of the solution of the embodiment, some or all of the units may be selected based on actual requirements.

[0331] In addition, the functional units of the embodiments of the present application may be integrated into one processing unit, each unit may physically exist independently, or two or more units may be integrated into one unit.

[0332] When the function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of the technical solution, may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium that can store 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.

Description of Reference Numerals

[0333] 1300 Device 1310 Processing Module 1320 Transceiver Module 1400 Device 1401 Processor 1402 Memory 1403 Transceiver

Claims

1. A communication method, comprising: receiving, by an edge configuration server, a request message, wherein 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; determining, by the edge configuration server, one first edge enabler server based on status information of a plurality of first edge application servers, wherein a status of a first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated; transmitting, by the edge configuration server, a response message, wherein the response message includes information about the first edge enabler server; The method comprising the above steps.

2. The method according to claim 1, wherein the status information of the first edge application server indicates whether the status of the first edge application server is instantiated or instantiable but not yet instantiated.

3. The method according to claim 1 or 2, further comprising: obtaining, by the edge configuration server, the status information of the plurality of first edge application servers from a plurality of edge enabler servers.

4. Before the step of determining, by the edge configuration server, one first edge enabler server based on status information of a plurality of first edge application servers, the method further comprises: determining, based on the status information of the plurality of first edge application servers, that there is no first edge application server whose status is instantiated. The method according to any one of claims 1 to 3.

5. receiving, by the edge configuration server, instruction information, wherein the instruction information indicates that instantiation of a first edge application server corresponding to the first edge enabler server has failed. ​ A step of transmitting, by the edge configuration server, information regarding one second edge enabler server other than the first edge enabler server, wherein a status of a first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated The method according to any one of claims 1 to 4, further comprising

6. The step of receiving, by the edge configuration server, a request message The step of receiving, by the edge configuration server, the request message from an edge enabler client comprises The step of transmitting, by the edge configuration server, a response message The step of transmitting, by the edge configuration server, the response message to the edge enabler client comprises The method according to any one of claims 1 to 5

7. The step of receiving, by the edge configuration server, a request message The step of receiving, by the edge configuration server, the request message from a source edge enabler server comprises The step of transmitting, by the edge configuration server, a response message The step of transmitting, by the edge configuration server, the response message to the source edge enabler server comprises The method according to any one of claims 1 to 5

8. A communication method comprising A step of receiving, by the edge configuration server, a request message, wherein the request message is used to request information regarding an edge enabler server A step of transmitting, by the edge configuration server, a response message, wherein the response message includes information regarding at least one edge enabler server and status information of a first edge application server respectively corresponding to the at least one edge enabler server comprises

9. The status information of the first edge application server corresponding to each of the at least one edge enabler server indicates whether the status of the first edge application server is in an instantiated state or is instantiable but not yet instantiated. The method according to claim 8.

10. The step of receiving a request message by the edge configuration server is The step of receiving the request message by the edge configuration server from the edge enabler client including The step of transmitting a response message by the edge configuration server is The step of transmitting the response message by the edge configuration server to the edge enabler client including The method according to claim 8 or 9.

11. The step of receiving a request message by the edge configuration server is The step of receiving the request message by the edge configuration server from the source edge enabler server including The step of transmitting a response message by the edge configuration server is The step of transmitting the response message by the edge configuration server to the source edge enabler server including The method according to claim 8 or 9.

12. The method according to any one of claims 8 to 11, wherein the request message includes an identifier of the first edge application server.

13. A communication method comprising: Transmitting a request message to an edge configuration server, the request message being used to request information about an edge enabler 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 of a first edge application server corresponding to each of the at least one edge enabler server. A step of determining one 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, wherein the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. A method including the above. **Claim 14** The method according to claim 13, wherein the status information of the first edge application server corresponding to each of the at least one edge enabler server indicates whether the first edge application server is in an instantiated state or is instantiable but not yet instantiated. **Claim 15** Before the step of determining one 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, the method further includes: A step of determining that there is no first edge application server in an instantiated state based on the status information of the first edge application server corresponding to each of the at least one edge enabler server. The method according to claim 13 or 14, further including the above. **Claim 16** The step of determining one 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 includes: A step of selecting one first edge enabler server from one or more edge enabler servers corresponding to the first edge application server in an instantiable but not yet instantiated state. The method according to claim 15, including the above. **Claim 17** When the instantiation of the instance of the first edge application server corresponding to the first edge enabler server fails, based on the status information of the first edge application server corresponding to each of the at least one edge enabler server, determining one second edge enabler server other than the first edge enabler server, wherein the status of the first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated, step The method according to any one of claims 13 to 16, further comprising. **Claim 18** When the status information of the first edge application server corresponding to each of the at least one edge enabler server includes that the status of the first edge application server is in an instantiated state, selecting one or more edge enabler servers from one or more edge enabler servers corresponding to the first edge application server in the instantiated state The method according to any one of claims 13, 14, or 17, further comprising. **Claim 19** After the step of determining one first edge enabler server, the method Sending an edge application server discovery request message to the one first edge enabler server The method according to any one of claims 13 to 18, further comprising. **Claim 20** The method according to any one of claims 13 to 19, wherein the method is executed by an edge enabler client. **Claim 21** The method according to any one of claims 13 to 20, wherein the request message includes an identifier of the first edge application server. **Claim 22** The method according to any one of claims 13 to 21, 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 23** A communication method, comprising: Obtaining, by an edge enabler server, status information of a first edge application server The step of transmitting, by the edge enabler server, the identifier of the first edge application server and the status information of the first edge application server to an edge configuration server A method comprising the above **Claim 24** The step of obtaining, by an edge enabler server, status information of a first edge application server is The step of obtaining, by the edge enabler server, the status information of the first edge application server from the first edge application server, wherein the status information of the first edge application server indicates that the status of the first edge application server is in an instantiated state The method according to claim 23, comprising the above **Claim 25** The step of obtaining, by an edge enabler server, status information of a first edge application server is The step of obtaining, by the edge enabler server, the status information of the first edge application server from an edge application server management system, wherein the status information of the first edge application server indicates that the first edge application server is instantiable but not yet instantiated The method according to claim 23 or 24, comprising the above **Claim 26** A communication method, comprising The step of transmitting, by an edge enabler client, a request message to an edge configuration server, wherein the request message is used to request information about an edge enabler server The step of receiving, by the edge configuration server, the request message transmitted by the edge enabler client and transmitting 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 server A step of receiving, by the edge enabler client, the response message sent by the edge configuration server, and determining one 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, wherein the status of the first edge application server corresponding to the first edge enabler server is instantiable but not yet instantiated. A method including the above. **Claim 27** A step of obtaining, by the edge enabler server, status information of a first edge application server corresponding to the edge enabler server, wherein the edge enabler server is one of the at least one edge enabler servers. A step of sending, by the edge enabler server, 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. A step of receiving, by the edge configuration server, 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 sent by the edge enabler server. The method according to claim 26, further including the above. **Claim 28** The method according to claim 27, 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 a registration update request message sent by the edge enabler server to the edge configuration server. **Claim 29** The method according to any one of claims 26 to 28, wherein the status information of the first edge application server respectively corresponding to the at least one edge enabler server indicates whether the first edge application server is in an instantiated state or is instantiable but not yet instantiated.

30. Before the step of determining, by the edge enabler client, one first edge enabler server based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server, the method further comprises: a step of determining, by the edge enabler client, that there is no first edge application server in an instantiated state based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server The method according to any one of claims 26 to 29, further comprising the above step.

31. The step of determining, by the edge enabler client, one first edge enabler server based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server comprises: a step of selecting, by the edge enabler client, one first edge enabler server from one or more edge enabler servers corresponding to a first edge application server that is instantiable but not yet instantiated The method according to claim 30, comprising the above step.

32. When the instantiation of the first edge application server corresponding to the first edge enabler server fails, a step of determining, by the edge enabler client, 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 each of the at least one edge enabler server, wherein the status of the first edge application server corresponding to the second edge enabler server is in a state where it can be instantiated but has not yet been instantiated The method according to any one of claims 26 to 31, further comprising this step

33. When the status information of the first edge application server corresponding to each of the at least one edge enabler server includes a state where the status of the first edge application server has been instantiated, a step of selecting, by the edge enabler client, one or more edge enabler servers from one or more edge enabler servers corresponding to the first edge application server in the instantiated state The method according to any one of claims 26 to 29 or claim 32, further comprising this step

34. After the step of determining, by the edge enabler client, one first edge enabler server, the method comprises A step of transmitting, by the edge enabler client, an edge application server discovery request message to the one first edge enabler server A step of receiving, by the one first edge enabler server, the edge application server discovery request message transmitted by the edge enabler client The method according to any one of claims 26 to 33, further comprising these steps

35. The method according to any one of claims 26 to 34, wherein the request message includes an identifier of the first edge application server

36. The method according to any one of claims 26 to 35, wherein the request message is an edge enabler server discovery request message and the response message is an edge enabler server discovery response message

37. A communication device comprising a transceiver module and a processing module, wherein the transceiver module is configured to receive a request message, the request message being used to request information about an edge enabler server, the request message including an identifier of a first edge application server, wherein the processing module is configured to determine 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, wherein the transceiver module is configured to transmit a response message, the response message including information about the first edge enabler server, Device.

38. The device according to claim 37, wherein the status information of the first edge application server indicates whether the status of the first edge application server is instantiated or instantiable but not yet instantiated.

39. The device according to claim 37 or 38, wherein the processing module is configured to obtain the status information of the plurality of first edge application servers from a plurality of edge enabler servers.

40. The device according to any one of claims 37 to 39, wherein the processing module is configured to determine that there is no first edge application server whose status is instantiated based on the status information of the plurality of first edge application servers before determining the one first edge enabler server based on the status information of the plurality of first edge application servers.

41. wherein the transceiver module, receives indication information, the indication information indicating that instantiation of a first edge application server corresponding to the first edge enabler server has failed, Transmitting information regarding one second edge enabler server other than the first edge enabler server, wherein the status of the first edge application server corresponding to the second edge enabler server is instantiable but not yet instantiated; The apparatus according to any one of claims 37 to 40, configured to perform. **Claim 42** The apparatus according to any one of claims 37 to 41, wherein the transceiver module is configured to receive the request message from an edge enabler client when receiving the request message, and to transmit the response message to the edge enabler client when transmitting the response message. **Claim 43** The apparatus according to any one of claims 37 to 42, wherein the transceiver module is configured to receive the request message from a source edge enabler server when receiving the request message, and to transmit the response message to the source edge enabler server when transmitting the response message. **Claim 44** A communication device comprising a transceiver module and a processing module, The processing module activates the transceiver module to Receive a request message, wherein the request message is used to request information regarding an edge enabler server; Transmit a response message, wherein the response message includes information regarding 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 server; Perform Device. **Claim 45** The status information of the first edge application server corresponding to each of the at least one edge enabler server indicates whether the status of the first edge application server is instantiated or is instantiable but not yet instantiated. The apparatus according to claim 44. **Claim 46** The apparatus according to claim 44 or 45, wherein when the transceiver module receives the request message, it receives the request message from the edge enabler client, and when the transceiver module transmits the response message, it is configured to transmit the response message to the edge enabler client.

47. The apparatus according to claim 44 or 45, wherein when the transceiver module receives the request message, it receives the request message from the source edge enabler server, and when the transceiver module transmits the response message, it is configured to transmit the response message to the source edge enabler server.

48. The apparatus according to any one of claims 44 to 47, wherein the request message includes an identifier of the first edge application server.

49. A communication device comprising a transceiver module and a processing module, wherein the transceiver module is configured to transmit a request message to an edge configuration server, the request message being used to request information about an edge enabler server, configured to receive a response message from the edge configuration server, the response message including 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 server, and the processing module is configured to determine one 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, the status of the first edge application server corresponding to the first edge enabler server being instantiable but not yet instantiated. Device.

50. The status information of the first edge application server respectively corresponding to the at least one edge enabler server indicates whether the first edge application server is in an instantiated state or is in a state where it can be instantiated but has not yet been instantiated. The apparatus according to claim 49.

51. Based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server, before determining the one first edge enabler server, the processing module is configured to determine that there is no first edge application server in an instantiated state based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server. The apparatus according to claim 49 or 50.

52. When determining the one first edge enabler server based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server, the processing module is configured to select one first edge enabler server from one or more edge enabler servers corresponding to the first edge application server in a state where it can be instantiated but has not yet been instantiated. The apparatus according to claim 51.

53. When the instantiation of the first edge application server corresponding to the first edge enabler server fails, the processing module is configured to determine, based on the status information of the first edge application server respectively corresponding to the at least one edge enabler server, a 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 in a state where it can be instantiated but has not yet been instantiated. The apparatus according to any one of claims 49 to 52.

54. The apparatus according to any one of claims 49 to 50 or claim 53, further configured to select one or more edge enabler servers from one or more edge enabler servers corresponding to the first edge application server respectively corresponding to the at least one edge enabler server when the status information of the first edge application server corresponding to each of the at least one edge enabler server includes that the status of the first edge application server is in an instantiated state.

55. The apparatus according to any one of claims 49 to 54, further configured such that after determining the one first edge enabler server, the transceiver module transmits an edge application server discovery request message to the one first edge enabler server.

56. The apparatus according to any one of claims 49 to 55, wherein the apparatus is an edge enabler client or a chip within the edge enabler client.

57. The apparatus according to any one of claims 49 to 56, wherein the request message includes an identifier of the first edge application server.

58. The apparatus according to any one of claims 48 to 57, wherein the request message is an edge enabler server discovery request message and the response message is an edge enabler server discovery response message.

59. A communication apparatus, comprising a transceiver module and a processing module, wherein the processing module activates the transceiver module to obtain status information of a first edge application server, and transmit an identifier of the first edge application server and the status information of the first edge application server to an edge configuration server. to perform the apparatus.

60. The apparatus according to claim 59, wherein when the transceiver module acquires the status information of the first edge application server, it acquires 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 in an instantiated state, and is configured to perform the acquisition.

61. The apparatus according to claim 59 or 60, wherein when the transceiver module acquires the status information of the first edge application server, it acquires the status information of the first edge application server from an edge application server management system, and the status information of the first edge application server indicates that the first edge application server is instantiable but not yet instantiated, and is configured to perform the acquisition.

62. A communication method, comprising: a step of an edge enabler client (EEC) sending N edge application server (EAS) discovery request messages to N edge enabler servers (EES), each EAS discovery request message including first indication information indicating that EAS instantiation is not required, and the i-th EAS discovery request message being used to request information about an EAS that meets the requirements of an application client (AC) on the i-th EES, where i is a positive integer and i is less than or equal to N; a step of the EEC receiving N EAS discovery response messages from the N EES, the i-th EAS discovery response message including information about at least one EAS that is instantiable but not yet instantiated on the i-th EES; When the EEC selects a first EAS on a first EES, a step of transmitting, by the EEC, a first request message to the first EES, where the first request message includes information about the first EAS, the first EES is one of the N EESs, and the first EAS is one of at least one EAS that can be instantiated on the first EES but has not yet been instantiated. A method including the above. **Claim 63** A step of receiving, by the EEC, a first response message from the first EES, where the first response message includes the instantiation result of the first EAS. The method according to claim 62, further including the above. **Claim 64** A communication method, A step of receiving, by a first edge enablement server (EES), an edge application server (EAS) discovery request message from an edge enablement client (EEC), where the EAS discovery request message includes first indication information indicating that EAS instantiation is not required, and the EAS discovery request message is used to request information about an EAS that meets the requirements of an application client (AC) on the first EES. A step of determining, by the first EES, based on the first indication information, that EAS instantiation is not required. A step of transmitting, by the first EES, an EAS discovery response message to the EEC, where the EAS discovery response message includes information about at least one EAS that can be instantiated on the first EES but has not yet been instantiated. A step of receiving, by the first EES, a first request message from the EEC, where the first request message includes information about a first EAS, and the first EAS is one of the at least one EAS that can be instantiated but has not yet been instantiated. A method including the above. **Claim 65** After the first EES receives the first request message from the EEC, a step of the first EES sending an EAS instantiation request message to an EAS management system, where the EAS instantiation request message includes information about the first EAS. A step of the first EES receiving an EAS instantiation response message from the EAS management system, where the EAS instantiation response message includes the instantiation result of the first EAS. A step of the first EES sending a first response message to the EEC, where the first response message includes the instantiation result of the first EAS. The method according to claim 64 further includes this step.

66. A step of skipping, by the first EES, sending an EAS instantiation request message to the EAS management system after receiving the EAS discovery request message. The method according to claim 64 or 65 further includes this step.

67. A communication method, A step of an edge enabler client (EEC) sending an edge application server (EAS) discovery request message to a first edge enabler server (EES), where the EAS discovery request message includes first indication information indicating that EAS instantiation is not required, and the EAS discovery request message is used to request information about an EAS that meets the requirements of an application client (AC) on the first EES. A step of the first EES receiving the EAS discovery request message sent by the EEC and determining, based on the first indication information, that EAS instantiation is not required. A step of the first EES sending an EAS discovery response message to the EEC, where the EAS discovery response message includes information about at least one EAS that can be instantiated on the first EES but has not yet been instantiated. The step of receiving, by the EEC, the EAS discovery response message transmitted by the first EES and transmitting a first request message to the first EES, where the first request message includes information about a first EAS, and the first EAS is one of the at least one EAS that can be instantiated but has not yet been instantiated. The step of receiving, by the first EES, the first request message transmitted by the EEC. A method comprising the above.

68. After the first EES receives the first request message transmitted by the EEC, the step of transmitting, by the first EES, an EAS instantiation request message to an EAS management system, where the EAS instantiation request message includes information about the first EAS. The step of receiving, by the EAS management system, the EAS instantiation request message transmitted by the first EES and transmitting an EAS instantiation response message to the first EES, where the EAS instantiation response message includes the instantiation result of the first EAS. The step of receiving, by the first EES, the EAS instantiation response message transmitted by the EAS management system. The step of transmitting, by the first EES, a first response message to the EEC, where the first response message includes the instantiation result of the first EAS. The step of receiving, by the EEC, the first response message transmitted by the first EES. The method according to claim 67, further comprising the above.

69. The step of skipping, by the first EES, transmitting an EAS instantiation request message to an EAS management system after the first EES receives the EAS discovery request message. The method according to claim 67 or 68, further comprising the above.

70. A communication device comprising a unit or module configured to execute the method according to any one of claims 1 to 25 or claims 62 to 66.

71. 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 is capable of executing the method according to any one of claims 1 to 25 or claims 62 to 66.

72. 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 implement the method according to any one of claims 1 to 25 or claims 62 to 66.

73. A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive a signal from another communication device other than the communication device and transmit the signal to the processor, or transmit a signal from the processor to another communication device other than the communication device, and the processor is configured to implement the method according to any one of claims 1 to 25 or claims 62 to 66 by using a logic circuit or by executing code instructions.

74. A computer-readable storage medium storing a computer program or instructions, and when the computer program or the instructions are executed by a communication device, the method according to any one of claims 1 to 25 or claims 62 to 66 is implemented.

75. A communication system comprising at least two devices of an edge configuration server, an edge enable client, and an edge enable server, wherein the edge configuration server is configured to implement the method according to any one of claims 8 to 12, the edge enable client is configured to implement the method according to any one of claims 13 to 22, and the edge enable server is configured to implement the method according to any one of claims 23 to 25.

76. A communication system comprising an edge enable client and an edge enable server, wherein the edge enable client is configured to implement the method according to claim 62 or 63, and the edge enable server is configured to implement the method according to any one of claims 64 to 66.

Images