Communication method, device and system

Abstract

A communication method, device and system relate to the technical field of communication. The method comprises the following steps: a first management server determines a first corresponding relationship, wherein the first corresponding relationship comprises a corresponding relationship between a first terminal device group and an application server and a corresponding relationship between the first terminal device group and a management server; after the first management server receives second connection information from a second management server, updating the first corresponding relation according to the second connection information to obtain a second corresponding relation, and sending second information to other management servers except the first management server in the management servers corresponding to the first terminal device group, wherein the second information is used for determining the second corresponding relationship.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a communication method, apparatus, and system. Background Art

[0002] Edge computing refers to computing and storage resources at the network edge. Its architecture scenarios include user equipment (UE, also referred to as terminal equipment) and an edge data network (EDN). The EDN includes an edge application server (or referred to as an application server) and an edge enabler server (or referred to as a management server). The edge application server is used to provide edge service for terminal equipment, and multiple edge application servers can provide the same edge service. The edge enabler server is used to provide information such as the IP address of the edge application server to terminal equipment.

[0003] In the edge computing scenario, a group of terminal equipment can use one or more edge application servers in the EDN that provide the same edge service. Different terminal equipment in this group of terminal equipment may be connected to different edge enabler servers.

[0004] Currently, when a group of terminal equipment uses the same edge service, a change in the connection situation of a certain terminal equipment may cause an increase in the edge service latency of this group of terminal equipment. Summary of the Invention

[0005] Embodiments of this application provide a communication method, apparatus, and system.

[0006] Embodiments of this application can be used in a communication system including an application server and a management server. The application server is used to provide service for terminal equipment, and the management server is used to provide information of the application server for terminal equipment. An example of the communication system is a mobile edge computing (MEC) system architecture. Based on this system architecture, the application server is an edge application server (EAS), and the management server is an edge enabler server (EES). It should be understood that the embodiments of this application are not limited to the MEC system architecture.

[0007] In a first aspect, a communication method is provided. The method includes: a first management server determines a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and an application server and the correspondence relationship between the first terminal device group and the management server; wherein, the first management server is the management server corresponding to a first terminal device in the first terminal device group, and the first terminal device is the terminal device that first determines or selects an application server in the first terminal device group; when the first management server receives second connection information from a second management server, it updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers in the management servers corresponding to the first terminal device group except the first management server, where the second information is used to determine the second correspondence relationship; wherein, the second server is the source management server corresponding to a second terminal device in the first terminal device group, and the second connection information indicates the application server and / or management server corresponding to the second terminal device.

[0008] With the above implementation, in a scenario where the connection situation of at least one terminal device in the first terminal device group changes, for example, in the case of application server and / or management server switching, the management server corresponding to the first terminal device group can update the correspondence relationship between the first terminal device group and the application server and / or the correspondence relationship between the first terminal device group and the management server, and synchronize the updated correspondence relationship among the management servers, which is beneficial for the management server to optimize the application server connected by the terminal devices in the first terminal device group, thereby avoiding an increase in the edge service delay of the terminal devices in the first terminal device group.

[0009] It can be understood that when the terminal device in the first terminal device group switches to a new application server, the management server corresponding to the first terminal device group can, based on the information of the saved correspondence relationship, send the information of the new application server to other management servers, so that each management server can recommend the application server to other terminal devices in the first terminal device group. Since the new application server selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the application server, so that the terminal device users in the first terminal device group can obtain a better service experience.

[0010] Optionally, the sending the second information to the remaining management servers in the management servers corresponding to the first terminal device group except the first management server includes: according to the management servers corresponding to the first terminal device group in the second correspondence relationship, sending the second information to the other management servers except the first management server among these management servers.

[0011] In a possible implementation, the first management server determines the first correspondence, including: after the first management server determines the application server selected by the first terminal device, it sends the information of the application server selected by the first terminal device to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device; the first management server receives the first connection information sent by the management servers currently connected to the remaining terminal devices in the first terminal device group except the first terminal device, and the first connection information indicates the application server and / or management server to which the terminal device is currently connected; the first management server determines the first correspondence according to the first connection information.

[0012] In a possible implementation, after the first management server determines the first correspondence, it further includes: the first management server sends first information to the remaining management servers except the first management server according to the management servers corresponding to the first terminal device group in the first correspondence, and the first information is used to determine the first correspondence.

[0013] In a possible implementation, it further includes: when the first management server receives the second connection information from the second management server, if it determines that the source management server of the second terminal device no longer serves the first terminal device group, the first management server sends a deletion request message to the source management server of the second terminal device, and the deletion request message is used to instruct the source management server to delete the first correspondence.

[0014] In a possible implementation, updating the first correspondence according to the second connection information includes: if the first management server determines according to the second connection information that the source application server of the second terminal device no longer serves the first terminal device group, the correspondence between the terminal device in the first terminal device group and the source application server in the first correspondence is deleted.

[0015] In a possible implementation, it further includes: when the first management server determines that the first terminal device switches from the source application server to the target application server, the second correspondence is updated according to the target application server of the first terminal device to obtain a third correspondence; the first management server sends third information to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device according to the third correspondence, and the third information is used to determine the third correspondence.

[0016] In a possible implementation, it further includes: when the first management server determines that the first terminal device switches from the first management server to a target management server and the first management server no longer serves the first terminal device group, the first management server updates the second correspondence relationship according to the target management server to obtain a third correspondence relationship, and the third correspondence relationship does not include the correspondence relationship between the terminal devices in the first terminal device group and the first management server; the first management server sends third information to the management servers corresponding to the terminal devices in the first terminal device group according to the third correspondence relationship, and the third information is used to determine the third correspondence relationship; the first management server deletes the third correspondence relationship.

[0017] In a possible implementation, the updating the first correspondence relationship according to the second connection information to obtain a second correspondence relationship includes: the first management server sends a request message to other management servers in the management servers corresponding to the first terminal device group except the first management server, the request message includes information about the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; the first management server recommends the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the first management server except the second terminal device, and obtains third connection information of the remaining terminal devices, where the third connection information indicates the application servers corresponding to the remaining terminal devices; the first management server receives third connection information from the other management servers, where the third connection information indicates the application servers corresponding to the terminal devices connected to the other management servers; the first management server updates the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

[0018] Second aspect, a communication method is provided. The method includes: a first management server obtains a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between a first terminal device group and an application server and the correspondence relationship between the first terminal device group and the management server; wherein, the first management server is one of the management servers corresponding to the terminal devices in the first terminal device group, and information of a first application server is configured on the first management server; when the first management server receives second connection information from the first application server, it updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the other management servers in the management servers corresponding to the first terminal device group except the first management server, where the second information is used to determine the second correspondence relationship; wherein, the second connection information indicates the application server corresponding to a second terminal device in the first terminal device group, the source application server of the second terminal device is the first application server, or the target application server of the second terminal device is the first application server.

[0019] With the above implementation manner, in a scenario where the connection situation of at least one terminal device in the first terminal device group changes, for example, in the case of application server and / or management server switching, the management server corresponding to the first terminal device group can update the correspondence relationship between the first terminal device group and the application server and / or the correspondence relationship between the first terminal device group and the management server, and synchronize the updated correspondence relationship among the management servers, which is beneficial for the management server to optimize the application servers connected by the terminal devices in the first terminal device group, thereby avoiding the increase of the edge service delay of the terminal devices in the first terminal device group.

[0020] It can be understood that when the terminal device in the first terminal device group switches to a new application server, the management server corresponding to the first terminal device group can, based on the information of the saved correspondence relationship, send the information of the new application server to other management servers, so that each management server can recommend the application server to other terminal devices in the first terminal device group. Since the new application server selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the application server, so that the terminal device users in the first terminal device group can obtain a better service experience.

[0021] Optionally, the sending the second information to the other management servers in the management servers corresponding to the first terminal device group except the first management server includes: sending the second information to the other management servers except the first management server among these management servers according to the management servers corresponding to the first terminal device group in the second correspondence relationship.

[0022] In a possible implementation, the first management server obtains a first correspondence relationship, including: after the first management server determines the application server selected by the first terminal device in the first terminal device group, the first management server sends the information of the application server selected by the first terminal device to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device; wherein, the first management server is the management server corresponding to the first terminal device, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server; the first management server receives first connection information sent by the management servers currently connected to the remaining terminal devices in the first terminal device group except the first terminal device, and the first connection information indicates the application server and / or management server to which the terminal device is currently connected; the first management server determines the first correspondence relationship according to the first connection information.

[0023] In a possible implementation, the first management server obtains a first correspondence relationship, including: the first management server receives first information from a second management server, and the first information is used to determine the first correspondence relationship; wherein, the second management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server.

[0024] In a possible implementation, it further includes: the first management server sends a request message to the first application server, and the request message is used to indicate that when the first application server disconnects from or establishes a connection with the terminal devices in the first terminal device group, the connection information corresponding to the terminal device that disconnects from or establishes a connection with the first application server is sent to the first management server, and the connection information indicates the application server corresponding to the terminal device that disconnects from or establishes a connection with the first application server.

[0025] In a possible implementation, updating the first correspondence relationship according to the second connection information includes: if the first management server determines according to the second connection information that the first application server no longer serves the first terminal device group, the correspondence relationship between the terminal devices in the first terminal device group and the first application server in the first correspondence relationship is deleted.

[0026] In a possible implementation, the second connection information further indicates the management server corresponding to the second terminal device.

[0027] In a possible implementation, it further includes: when the source management server of the second terminal device is the first management server, if the first management server determines, according to the first correspondence and the second connection information, that the source management server of the second terminal device no longer serves the first terminal device group, the first management server deletes the information of the second correspondence; or, when the source management server of the second terminal device is not the first management server, if the first management server determines, according to the first correspondence and the second connection information, that the source management server of the second terminal device no longer serves the first terminal device group, the first management server sends a deletion request message to the source management server of the second terminal device, and the deletion request message is used to instruct the source management server to delete the information of the first correspondence.

[0028] In a possible implementation, the updating the first correspondence according to the second connection information to obtain a second correspondence includes: the first management server sends a request message to other management servers except the first management server in the management server corresponding to the first terminal device group, the request message includes information of the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; the first management server recommends the application server corresponding to the second terminal device to the remaining terminal devices except the second terminal device in the first terminal device group connected to the first management server, and obtains third connection information of the remaining terminal devices, where the third connection information indicates the application servers corresponding to the remaining terminal devices; the first management server receives the third connection information from the other management servers, where the third connection information indicates the application servers corresponding to the terminal devices connected to the other management servers; the first management server updates the first correspondence according to the third connection information to obtain the second correspondence.

[0029] In a third aspect, a communication method is provided. The method includes: a first management server obtains a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and an application server and the correspondence relationship between the first terminal device group and the management server; wherein, information of a first application server is configured on the first management server; when the first management server receives second connection information from a first terminal device, it updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers other than the first management server in the management server corresponding to the first terminal device group, where the second information is used to determine the second correspondence relationship; wherein, the second connection information indicates the application server and / or management server corresponding to the first terminal device.

[0030] With the above implementation, in a scenario where the connection situation of at least one terminal device in the first terminal device group changes, for example, in the case of application server and / or management server switching, the management server corresponding to the first terminal device group can update the correspondence relationship between the first terminal device group and the application server and / or the correspondence relationship between the first terminal device group and the management server, and synchronize the updated correspondence relationship among the management servers, which is beneficial for the management server to optimize the application server connected by the terminal devices in the first terminal device group, thereby avoiding the increase in the edge service delay of the terminal devices in the first terminal device group.

[0031] It can be understood that when the terminal device in the first terminal device group switches to a new application server, the management server corresponding to the first terminal device group can, based on the information of the saved correspondence relationship, send the information of the new application server to other management servers, so that each management server can recommend the application server to other terminal devices in the first terminal device group. Since the new application server selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the application server, so that the terminal device users in the first terminal device group can obtain a better service experience.

[0032] Optionally, the sending the second information to the remaining management servers other than the first management server in the management server corresponding to the first terminal device group includes: according to the management servers corresponding to the first terminal device group in the second correspondence relationship, sending the second information to the other management servers other than the first management server among these management servers.

[0033] In a possible implementation, the first management server obtaining the first correspondence includes: after the first management server determines the application server selected by the first terminal device in the first terminal device group, sending the information of the application server selected by the first terminal device to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device; wherein, the first management server is the management server corresponding to the first terminal device, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server; the first management server receives first connection information sent by the management servers currently connected to the remaining terminal devices in the first terminal device group except the first terminal device, and the first connection information indicates the application server and / or management server to which the terminal device is currently connected; the first management server determines the first correspondence according to the first connection information.

[0034] In a possible implementation, the first management server obtaining the first correspondence includes: the first management server receiving first information from the second management server, and the first information is used to determine the first correspondence; wherein, the second management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server.

[0035] In a possible implementation, updating the first correspondence according to the second connection information includes: if the first management server determines according to the second connection information that the source application server of the second terminal device no longer serves the first terminal device group, deleting the correspondence between the terminal device in the first terminal device group and the source application server in the first correspondence.

[0036] In a possible implementation, it further includes: if the first management server determines according to the second connection information and the first correspondence that the source management server of the second terminal device no longer serves the first terminal device group, and the first management server is the source management server of the second terminal device, the first management server deletes the information of the second correspondence.

[0037] In a possible implementation, updating the first correspondence relationship according to the second connection information to obtain a second correspondence relationship includes: the first management server sending a request message to other management servers in the management server corresponding to the first terminal device group except the first management server, where the request message includes information about the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; the first management server recommending the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the first management server except the second terminal device, and obtaining third connection information of the remaining terminal devices, where the third connection information indicates the application servers corresponding to the remaining terminal devices; the first management server receiving the third connection information from the other management servers, where the third connection information indicates the application servers corresponding to the terminal devices connected to the other management servers; and the first management server updating the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

[0038] In a fourth aspect, a communication method is provided, and the method includes: a second management server receiving a first request message from a first management server, where the first request message includes information about a first correspondence relationship and second connection information, the first correspondence relationship includes a correspondence relationship between a first terminal device group and an application server and a correspondence relationship between the first terminal device group and a management server, and the second connection information indicates the application server corresponding to a first terminal device in the first terminal device group; where the second management server is the source management server of the first terminal device and the second management server is the target management server of the first terminal device; the second management server responding to the first request message, updating the first correspondence relationship according to the second connection information to obtain a second correspondence relationship; and the second management server sending second information to other management servers in the management server corresponding to the first terminal device group except the second management server, where the second information is used to determine the second correspondence relationship.

[0039] In the scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, when the application server and / or the management server switches, the management server corresponding to the first terminal device group can update the corresponding relationship between the first terminal device group and the application server and / or the corresponding relationship between the first terminal device group and the management server, and synchronize the updated corresponding relationship among the management servers, which is beneficial for the management server to optimize the application server connected by the terminal devices in the first terminal device group, thus avoiding the increase in the edge service latency of the terminal devices in the first terminal device group.

[0040] It can be understood that when the terminal device in the first terminal device group switches to a new application server, the management server corresponding to the first terminal device group can, based on the saved corresponding relationship information, send the information of the new application server to other management servers, so that each management server can recommend the application server to other terminal devices in the first terminal device group. Since the new application server selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the application server, so that the terminal device users in the first terminal device group can obtain a better service experience.

[0041] In a possible implementation manner, the first request message further includes information about the management server corresponding to the first terminal device.

[0042] In a possible implementation manner, the first request message further includes indication information, and the indication information indicates that the second management server no longer serves the first terminal device group.

[0043] In a possible implementation manner, the second management server sends second information to the other management servers in the management servers corresponding to the first terminal device group except the first management server, including: the second management server sends the second information to the other management servers except the first management server and the second management server according to the management server corresponding to the first terminal device group in the first corresponding relationship.

[0044] In a possible implementation manner, updating the first correspondence relationship according to the second connection information to obtain a second correspondence relationship includes: the second management server sends a second request message to other management servers in the management server corresponding to the first terminal device group except the first management server and the second management server, where the second request message includes information about the application server corresponding to the first terminal device, and the second request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; the second management server recommends the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the second management server except the second terminal device, and obtains third connection information of the remaining terminal devices, where the third connection information indicates the application server corresponding to the remaining terminal devices; the second management server receives the third connection information from the other management servers, where the third connection information indicates the application server corresponding to the terminal devices connected to the other management servers; and the second management server updates the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

[0045] In a fifth aspect, a communication device is provided, including units or modules for executing the method according to any one of the above first aspects, or including units or modules for executing the method according to any one of the above second aspects, or including units or modules for executing the method according to any one of the above third aspects, or including units or modules for executing the method according to any one of the above fourth aspects.

[0046] In a sixth aspect, a communication device is provided, including: one or more processors configured to execute the method according to any one of the above first aspects, or to execute the method according to any one of the above second aspects, or to execute the method according to any one of the above third aspects, or to execute the method according to any one of the above fourth aspects.

[0047] In a seventh aspect, a communication system is provided, including an application server and a management server, where the application server is used to provide service for terminal devices, and the management server is used to provide information about the application server for terminal devices, and the management server is used to implement the method according to any one of the above first aspects, or to implement the method according to any one of the above second aspects, or to implement the method according to any one of the above third aspects, or to implement the method according to any one of the above fourth aspects.

[0048] In an eighth aspect, a readable storage medium is provided, in which a program is stored. When the program is executed by a communication device, the method described in any one of the above first aspects is implemented, or the method described in any one of the above second aspects is implemented, or the method described in any one of the above third aspects is implemented, or the method described in any one of the above fourth aspects is implemented.

[0049] In a ninth aspect, a chip system is provided, including: a memory for storing a computer program; a processor; when the processor calls and runs the computer program from the memory, the communication device installed with the chip system executes the method described in any one of the above first aspects, or executes the method described in any one of the above second aspects, or executes the method described in any one of the above third aspects, or executes the method described in any one of the above fourth aspects.

[0050] In a tenth aspect, a computer program product is provided. When the computer program product is called by a computer, the computer executes the method described in any one of the above first aspects, or executes the method described in any one of the above second aspects, or executes the method described in any one of the above third aspects; or executes the method described in any one of the above fourth aspects. Description of the Drawings

[0051] Figure 1 It is a schematic diagram of a SA6 edge computing application architecture and function model in an embodiment of the present application;

[0052] Figure 2 It is a schematic diagram of an EES discovery process applicable to an embodiment of the present application;

[0053] Figure 3 It is a schematic diagram of an EAS discovery process applicable to an embodiment of the present application;

[0054] Figure 4 It is a schematic diagram of UEs in a UE group connecting to the same EAS in an embodiment of the present application;

[0055] Figure 5 It is a schematic diagram of UEs in a UE group connecting to different EASs in an embodiment of the present application;

[0056] Figure 6 It is a schematic diagram of the process of initial connection of terminal devices in a terminal device group to an EAS provided by an embodiment of the present application;

[0057] Figure 7 It is a schematic diagram of the synchronization process of the first corresponding relationship provided by an embodiment of the present application;

[0058] Figure 8aSchematic flowchart of a communication method provided by an embodiment of this application;

[0059] Figure 8b Schematic flowchart of another communication method provided by an embodiment of this application;

[0060] Figure 9 Schematic flowchart of another communication method provided by an embodiment of this application;

[0061] Figure 10 Schematic diagram of an EAS discovery process triggered by EAS provided by an embodiment of this application;

[0062] Figure 11a Schematic flowchart of another communication method provided by an embodiment of this application;

[0063] Figure 11b Schematic flowchart of another communication method provided by an embodiment of this application;

[0064] Figure 12 Schematic flowchart of another communication method provided by an embodiment of this application;

[0065] Figure 13 Schematic diagram of a scenario where a terminal device in a first terminal device group switches between EAS and EES in an embodiment of this application;

[0066] Figure 14 In an embodiment of this application, based on Figure 13 Schematic flowchart of a communication method implemented according to the scenario shown;

[0067] Figure 15 In an embodiment of this application, based on Figure 13 Schematic flowchart of another communication method implemented according to the scenario shown;

[0068] Figure 16 In an embodiment of this application, based on Figure 13 Schematic flowchart of another communication method implemented according to the scenario shown;

[0069] Figure 17 In an embodiment of this application, based on Figure 13 Schematic flowchart of another communication method implemented according to the scenario shown;

[0070] Figure 18 Schematic diagram of another scenario where a terminal device in a first terminal device group switches between EAS and EES in an embodiment of this application;

[0071] Figure 19 In an embodiment of this application, based on Figure 18 Schematic flowchart of a communication method implemented according to the scenario shown;

[0072] Figure 20 A structural schematic diagram of a communication device provided by an embodiment of the present application;

[0073] Figure 21 A structural schematic diagram of another communication device provided by an embodiment of the present application. Detailed implementation manners

[0074] To more clearly understand the embodiments of the present application, the related technologies involved in the embodiments of the present application will be described first.

[0075] (1) Mobile edge computing

[0076] In the traditional mobile network architecture and deployment, user plane devices basically follow a tree topology for deployment. The uplink user packets pass through the base station and the backhaul network, and finally access the data network through the centrally deployed anchor gateway. These anchor gateways are generally deployed at relatively high positions in the network, such as the central computer room of a large area. This topological structure is relatively simple, which is convenient for operators to perform centralized service management and packet processing at the anchor point.

[0077] With the explosive growth of mobile service traffic, this deployment method is increasingly difficult to support the rapidly growing mobile service traffic model. On the one hand, in the network with centralized deployment of anchor gateways, the increasing traffic is finally concentrated at the gateway and the core computer room, which puts higher and higher requirements on the backhaul network bandwidth, computer room throughput and gateway specifications; on the other hand, the long-distance backhaul network from the access point to the anchor gateway and the complex transmission environment also result in large delays and jitters in the transmission of user packets.

[0078] Mobile edge computing (MEC), also known as multi-access edge computing, can use the radio access network to provide the services and cloud computing functions required by telecommunications users' information technology (IT) nearby, and create a telecommunications-level service environment with high performance, low latency and high bandwidth, accelerating the rapid download of various contents, services and applications in the network, and enabling consumers to enjoy an uninterrupted high-quality network experience.

[0079] (2) Mobile edge computing architecture

[0080] 3GPP SA6 is conducting research on application-enabled mobile edge computing (MEC) and defines an architecture model as Figure 1 shown. The main functions of each network function entity in this architecture are described as follows:

[0081] Edge Data Network (EDN): Generally understood, an EDN corresponds to only one data network and is a special local data network (local DN). It can be identified using a Data Network Access Identifier (DNAI) and a Data Network Name (DNN), and it is a network logical concept. Another understanding of EDN is that it is the peer concept of the central cloud and can be regarded as a local data center (a geographical location concept). It can be identified using DNAI and can contain multiple local data networks.

[0082] Edge Application Server (EAS): An application deployed in an edge data network is called an application instance or an application server. Specifically, it refers to an instance in which a server application program runs on an EDN. For example, some examples of the server application program include: social media software, augmented reality (AR) applications, virtual reality (VR) applications, etc. For an application, one or more EASs can be deployed in one or more EDNs. The EASs deployed and running in different EDNs can be regarded as different EASs of an application. They can share a domain name, can use one IP address, or can also use different IP addresses. EAS can also be referred to as an edge application (server), an application instance, an edge application instance, a MEC application (server), or an EAS function, etc. In some embodiments of the present application, the description is given by taking the application server and EAS as examples.

[0083] Application Client (AC): It is the peer entity of an edge application on the terminal device side. The application client is used for an application user to obtain application services from an application server. The application client is the client program of the application on the terminal device side. The application client can connect to the application server on the cloud to obtain application services, or can also connect to the EASs deployed and running in one or more EDNs to obtain application services.

[0084] Edge Enablement Server (EES): It can provide some enabling capabilities for application instances deployed in the EDN, which can better support the deployment of applications in the MEC. It can support the registration of edge applications, the authentication and authorization of terminal devices, and provide the IP address information of application instances to terminal devices. It can further support obtaining the identifiers and IP addresses of application instances, and further send the identifiers and IP addresses of application instances to the edge configuration server. The EES is deployed in the EDN. Generally, an EAS registers with an EES, or, through the management system, the information of an EAS is configured on an EES, and this EES is called the EES associated with this EAS. The EES can control, manage, register, etc. the EAS configured on it. In some embodiments of this application, the management server and the EES are taken as examples for description.

[0085] Edge Enablement Client (EEC): It is the peer entity of the EES on the terminal device side. The EEC is used to register the information of the EEC and the application client with the EES, perform security authentication and authorization, obtain the IP address of the EAS from the EES, and provide edge computing enabling capabilities to the application client, such as the EAS discovery service returning the IP address of the EAS to the application client.

[0086] Edge Configuration Server (ECS): It is responsible for the configuration of the EDN, such as providing the information of the EES to the terminal device. It can also directly provide the information of application instances to the terminal device, and interact with the domain name system (DNS) of the application to obtain the information of application instances. Further, it can also obtain and save the information of application instances and IP addresses from other functional entities.

[0087] The application user signs a service agreement with the application provider to provide services for the application user. The application user communicates through the connection between the application client (AC) on the login terminal device and the edge application (EAS). The edge enablement client (EEC) is the middleware layer, generally located in the operating system or between the application client and the operating system. The application client (AC) can obtain the edge enablement service from the edge enablement client (EEC) in the form of an application programming interface (API).

[0088] Figure 1 EDGE-X shown in the figure represents the interface between functional entities. For example, EDGE-1 is the interface between the edge enablement server (EES) and the edge enablement client (EEC).

[0089] Figure 1 In the architecture shown, the terminal device may be a user equipment (UE), a handheld terminal, a laptop computer, a subscriber unit, a cellular phone, a smartphone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device, a laptop computer, a cordless phone, or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, or other devices that can access the network. The embodiments of the present application do not make any restrictions.

[0090] In the embodiments of the present application, the application server or EAS is taken as an example for description. For an application server, the EES that registers (or configures) the relevant information of the application server is called the management server corresponding to the application server, or the server for managing the application server, or the server for registering the application server, or the server associated with the application server. For a terminal device, the application server selected or used by the terminal device is called the application server corresponding to the terminal device, or the application server connected to the terminal device. For an application server connected to a terminal device, the management server that registers (or configures) the relevant information of the application server is called the management server corresponding to the terminal device, or the management server connected to the terminal device.

[0091] (3) EES discovery and EAS discovery

[0092] The SA6 standard defines the EES discovery process and the EAS discovery process. Through the EES discovery process, the terminal device can obtain the information of the EES from the ECS, and the terminal device can connect to the EES. Through the EAS discovery process, the terminal device can select the EAS used by the terminal device and obtain information such as the IP address of the EAS. The architecture and function are designed to use a two-level discovery mechanism: first, execute the EES discovery process, and then execute the EAS discovery process based on the EES connected by the terminal device.

[0093] See Figure 2 , which exemplarily shows an EES discovery process applicable to the embodiments of the present application. As Figure 2 shown, the EES discovery process may include the following steps:

[0094] Step 201: The terminal device sends a request message to the ECS, and the request message is used to request or subscribe to the EES corresponding to the terminal device.

[0095] Optionally, the request message may include the identifier of the EAS to request to obtain the EES registered with the corresponding EAS.

[0096] Step 202: After receiving the request message, the ECS determines candidate EESs according to the information of the terminal device, such as location information.

[0097] Optionally, the number of the candidate EESs may be one or more. For example, the ECS may obtain the DNAI according to the location of the terminal device, and combine the DNAI, the fully qualified domain name (FQDN), and the EES configuration information to select a suitable EES for each EAS requested by the terminal device.

[0098] Optionally, the ECS may obtain the DNAI according to the current location of the terminal device, or may obtain the DNAI according to the target location that the terminal device may move to.

[0099] Step 203: The ECS sends a response message to the terminal device, which includes the information of the candidate EESs determined for the terminal device (such as including the IP address and / or identifier of the EES).

[0100] Step 204: After receiving the response message, the EEC selects an EES from the candidate EESs and connects to the EES.

[0101] It should be understood that in the above Figure 2 shown process, the "terminal device" may also be replaced by the EEC or AC on the terminal device side.

[0102] See Figure 3 , which exemplarily shows an EAS discovery process applicable to an embodiment of the present application, and this process may also be applicable to the embodiment of the present application. As Figure 3 shown, the EAS discovery process may include the following steps:

[0103] Step 301: The terminal device sends an EAS discovery request message to the EES, and the EAS discovery request message is used to request to obtain the information of the EAS.

[0104] Optionally, the EAS discovery request message includes discovery filtering parameters corresponding to the edge service, and is used to request EASs that meet the requirements.

[0105] Optionally, the EAS discovery request message further includes the identifier of the terminal device and the identifier of the terminal device group to which the terminal device belongs.

[0106] Optionally, the EAS discovery request message may be an EAS discovery request message or other messages, which is not limited in the embodiments of the present application.

[0107] Step 302: After receiving the EAS discovery request message, the EES matches the information of the EAS registered on the EES based on the filtering parameter to determine the candidate EAS.

[0108] In this step, the EES determines the candidate EAS that meets the requirements corresponding to the discovery filtering parameter according to the information of the locally registered or online EAS and the discovery filtering parameter provided by the terminal device. If multiple EASs meet the requirements corresponding to the discovery filtering parameter, multiple candidate EASs may be returned.

[0109] Step 303: The EES sends an EAS discovery response message to the terminal device, and the EAS discovery response message includes the information of the candidate EAS, such as the IP address and / or identifier of the candidate EAS.

[0110] Optionally, the EAS discovery response message may be an EAS discovery response message, which is not limited in the embodiments of the present application.

[0111] Step 304: The terminal device selects an EAS from the candidate EASs.

[0112] Optionally, when there is only one candidate EAS, the terminal device uses the candidate EAS.

[0113] Step 305: The terminal device sends an EAS selection declaration request message to the EES, which includes the information of the EAS selected by the terminal device (such as the IP address and / or identifier of the EAS) to notify the EES of the EAS selected (or connected) by the terminal device.

[0114] The terminal device can connect to the EAS it selects.

[0115] Optionally, the EAS selection declaration request message may also be replaced with a selected EAS announcement request message, or an EAS information provisioning request message, which is not limited in the present application.

[0116] Step 306: After receiving the EAS selection declaration request message, the EES returns an EAS selection declaration response message to the terminal device.

[0117] Optionally, the EAS selection announcement response message can also be replaced with a selected EAS announcement response message, or an EAS information provisioning response message, which is not limited in this application.

[0118] Steps 304 to 306 are optional steps. When in step 303, the candidate EASs returned by the EES to the terminal device include only one, the terminal device does not have to perform the operation of selecting an EAS from the candidate EASs, nor does it have to notify the EES of the EAS.

[0119] In a possible implementation, step 302 does not have to be executed. Correspondingly, in step 303, the EAS discovery response message includes information about all the EASs registered (or configured) on the EES. That is to say, the EES recommends all the EASs registered (or configured) on the EES as candidate EASs to the terminal device.

[0120] It should be understood that in the Figure 3 shown process, the "terminal device" can also be replaced with the EEC or AC on the terminal device side.

[0121] (IV) Terminal device group and application context migration

[0122] Multiple terminal devices can use the same edge service. Taking an edge service as a game that can be participated by multiple people as an example, a group of UEs can participate in the multiplayer game. Different UEs within the group of UEs can connect to the same EAS corresponding to the multiplayer game, and different UEs within the group of UEs can also connect to different EASs corresponding to the multiplayer game.

[0123] Exemplarily, Figure 4 shows a schematic diagram of UEs in a group of UEs connecting to the same EAS. Connecting a group of UEs to the same EAS can reduce the signaling interaction between EASs. As Figure 4 shown, EAS-1(A), EAS-1(B), and EAS-1(C) are different EASs corresponding to the same edge service. A group of UEs includes UE1, UE2, and UE3. UE1, UE2, and UE3 are all connected to EAS-1(B). Different UEs in the group of UEs can connect to the same EES or different EESs. For example, in Figure 4 , UE1 is connected to EES-x, UE2 and UE3 are connected to EES-y, and EAS-1(B) is registered on both EES-x and EES-y.

[0124] It should be understood that Figure 4Taking the example that a UE group includes 3 UEs, the embodiments of the present application do not limit the number of UEs included in the UE group.

[0125] Exemplarily, Figure 5 FIG. shows a schematic diagram of UEs in a UE group connecting to different EASs. Different UEs in a group of UEs can be connected to the EAS closer to the UE, so as to obtain better service performance. As Figure 5 shown, EAS-1x, EAS-2x, and EAS-3x are different EASs corresponding to the same edge service. A UE group includes UE1, UE2, and UE3. UE1 is connected to EAS-1x and EES1, UE2 is connected to EAS-2x and EES2, and UE3 is connected to EAS-3x and EES3.

[0126] It should be understood that Figure 5 Taking the example that a UE group includes 3 UEs, the embodiments of the present application do not limit the number of UEs included in the UE group.

[0127] It should be understood that multiple UEs in a UE group can be connected to the same EAS and the same EES. For example, 2 UEs in a UE group are connected to EAS1 and EES1, and another 3 UEs are connected to EAS2 and EES2. The embodiments of the present application do not limit this.

[0128] As Figure 5 shown, in the case where different terminal devices in a terminal device group are connected to different EASs, application context synchronization is required between the multiple EASs connected by the group of terminal devices to ensure data consistency.

[0129] The terminal devices in a terminal device group may reselect an EAS and / or an EES due to reasons such as a change in location. For example, all the terminal devices connected to EAS1 in the first terminal device group migrate to EAS2, or the second terminal device in the first terminal device group connects to a new EAS and / or a new EES due to movement. An event that causes a terminal device to select a new EAS and / or a new EES can be referred to as an application context relocation (ACR) event. For example, an ACR event can include that the terminal device moves to a new location and triggers the terminal device to select a new EAS and / or a new EES, or the source EAS is no longer suitable for providing services to the terminal device, such as EAS overload. The present application does not limit this.

[0130] After an ACR event occurs in a terminal device in the terminal device group (or the terminal device migrates the application server and / or the management server), the corresponding relationship between the terminal devices in the terminal device group and the EAS and / or the corresponding relationship with the EES may change. There is currently a lack of corresponding solutions for the above scenarios. For example, in this case, how does the EES connected to other terminal devices in the terminal device group know the new EAS and / or new EES selected by the terminal device that has an ACR event, so as to recommend the new EAS and / or EES to other terminal devices in the group of terminal devices to ensure the progress of the service or better execute the service, which is a problem that needs to be solved currently.

[0131] For this reason, the embodiments of the present application provide a communication method and related devices that can implement this method.

[0132] The embodiments of the present application will be described below with reference to the accompanying drawings.

[0133] For the case where terminal devices in a group of terminal devices (such as the first terminal device group) use the same service, the embodiments of the present application provide a process for the terminal devices in the terminal device group to initially connect to the EAS. When the first terminal device (i.e., the first terminal device in the first terminal device group to select the EAS) in the first terminal device group selects the EAS, the first EES connected to the first terminal device notifies the EAS to the EES corresponding to the remaining terminal devices in the terminal device group. The EES corresponding to the remaining terminal devices can recommend the EAS as a candidate EAS to the terminal device, and send the EAS selected by the terminal device (further including the EES connected to the terminal device) to the first EES connected to the first terminal device, so that the first EES can obtain the corresponding relationship between other terminal devices in the first terminal device group and the EAS, and the corresponding relationship between the terminal devices in the first terminal device group and the EES.

[0134] See Figure 6 , which is a schematic diagram of the process for the terminal devices in the terminal device group to initially connect to the EAS provided by the embodiments of the present application. Among them, the first terminal device is terminal device 1, and the first EES is EES1.

[0135] As Figure 6 shown, the method includes the following steps:

[0136] Step 601: Terminal device 1 in the first terminal device group initiates an EAS discovery process to the EES1 corresponding to (or connected to) the terminal device. Terminal device 1 selects an EAS from the candidate EASs recommended by EES1 and connects to the EAS. This process is described by taking terminal device 1 selecting EAS1 as an example.

[0137] Among them, EAS1 is registered on EES1.

[0138] Among them, the terminal device 1 is the first terminal device in the first terminal device group to select the EAS.

[0139] For the specific implementation of the EAS discovery process, reference can be made to Figure 3 .

[0140] Optionally, before the terminal device 1 initiates the EAS discovery process to the EES1, the terminal device 1 may first initiate the EES discovery process to the EEC to obtain the IP address and / or identification information of the EES1. For the specific implementation of the EES discovery process, reference can be made to Figure 2 .

[0141] Step 602: The EES1 sends the information of the EAS (EAS1) corresponding to the terminal device 1 to the EESs corresponding to the remaining terminal devices in the first terminal device group (denoted as EES2 to EESm in the figure).

[0142] Among them, the EAS corresponding to the terminal device 1 can be understood as the EAS selected by the terminal device 1, or the EAS determined by the terminal device 1, or the EAS determined by the EES1 for the terminal device 1.

[0143] Optionally, the information of the EAS may include information such as the IP address and / or identification information of the EAS, which is not limited in this application.

[0144] Optionally, the EES1 may use the EAS1 as the common EAS and send the information of this common EAS to the EESs corresponding to the remaining terminal devices in the first terminal device group (denoted as EES2 to EESm in the figure).

[0145] Optionally, the EES1 may send the information of the EAS corresponding to the terminal device 1 to the EESs corresponding to the remaining terminal devices in the first terminal device group through a common EAS declaration request message, or an EAS announcement request message, or other messages, which is not limited in this application.

[0146] Step 603: In the EAS discovery process initiated by the terminal device, the EESs corresponding to the remaining terminal devices (such as Figure 6 the EES2 to EESm shown in

[0147] Figure 6Taking the terminal device 2 as an example, the terminal device 2 initiates an EAS discovery process to the EES2 corresponding to (or connected to) the terminal device, and selects an EAS from the candidate EASs recommended by the EES2 (including EAS1 as the common EAS). For the specific implementation manner of the EAS discovery process, reference can be made to Figure 3 . Optionally, before the terminal device 2 initiates an EAS discovery process to the EES2, the terminal device 2 may first initiate an EES discovery process to the EEC to obtain the IP address and / or identification information of the EES2. For the specific implementation manner of the EES discovery process, reference can be made to Figure 2 .

[0148] It should be understood that the EAS selected by the terminal device 2 may be EAS1, or may be other EASs. For example, the terminal device 2 selects EAS2, where EAS2 is an EAS registered or managed on the EES2. This application does not impose any restrictions.

[0149] Similarly, other terminal devices in the first terminal device group interact with the EESs connected to the terminal device in the above manner, so that the EESs connected to other terminal devices obtain the EASs corresponding to other terminal devices and the EESs corresponding to other terminal devices. Exemplarily, the terminal device 3 initiates an EAS discovery process to the EES3 corresponding to the terminal device, and selects EAS3 from the candidate EASs recommended by the EES3 (including EAS1). Another example is that the terminal device 4 initiates an EAS discovery process to the EES3 corresponding to the terminal device, and selects EAS3 from the candidate EASs recommended by the EES3 (including EAS1). That is to say, multiple terminal devices may be connected to the same EES and may select the same EAS.

[0150] Step 604: The EESs corresponding to the remaining terminal devices (such as Figure 6 the EES2 to EESm shown in

[0151] send first connection information to the EES1 respectively, and the first connection information indicates the EAS corresponding to the terminal device.

[0152] Taking the terminal device 2 as an example, in one possible implementation, the first connection information sent by the EES2 connected to the terminal device 2 to the EES1 includes the information of the EAS corresponding to the terminal device 2 (such as including the IP address and / or identification information of the EAS). In another possible implementation, if the terminal device 2 or the EES2 selects the EAS1 (that is, selects the common EAS), the first connection information sent by the EES2 connected to the terminal device 2 to the EES1 includes the indication information for indicating that the terminal device 2 selects (or connects to) the common EAS. For example, the indication information can be one or more bit indication information with a value of 1, used to indicate that the EAS selected by the terminal device is the common EAS.

[0153] Based on the example in step 603, in step 604, the EES2 sends the information of the EAS corresponding to the terminal device 2 to the EES1; the EES3 sends the information of the EAS selected by the terminal device 3 and the information of the EAS selected by the terminal device 4 to the EES1.

[0154] In one possible implementation, the first connection information may not need to indicate the EES corresponding to the terminal device (the EES corresponding to the terminal device can also be understood as the EES connected to the terminal device). For example, it does not include the information of the EES corresponding to the terminal device. Since the EES sending the first connection information is the EES currently connected to the terminal device, for the EES1, it can determine the sending EES as the EES corresponding to the terminal device (that is, the terminal device corresponding to the first connection information) based on information such as the IP address and / or identification information of the sending EES of the first connection information.

[0155] In another possible implementation, the first connection information can also indicate the EES corresponding to the terminal device. For example, the first connection information includes the information of the EES corresponding to the terminal device, such as including information such as the IP address and / or identification information of the EES.

[0156] In one possible implementation, the first connection information further includes the identification of the terminal device.

[0157] In one possible implementation, the first connection information further includes the identification of the first terminal device group (such as group ID).

[0158] Optionally, the EES2 can send the first connection information (such as including the information of the EAS corresponding to the terminal device 2) to the EES1 through a common EAS declaration response message, or an EAS announcement response message, or other messages, which is not limited in this application.

[0159] Step 605: After EES1 receives the first connection information returned by the EESs (such as EES2 to EESm shown in Figure 6 ), which are connected to the remaining terminal devices in the first terminal device group, it determines the first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the EAS, and the correspondence relationship between the first terminal device group and the EES.

[0160] Among them, the "correspondence relationship between the first terminal device group and the EAS" can be understood as the correspondence relationship between the terminal devices in the first terminal device group and the EAS. Correspondingly, the EASs corresponding to all the terminal devices in the first terminal device group are called the EASs corresponding to the first terminal device group. The "correspondence relationship between the first terminal device group and the EES" can be understood as the EESs corresponding to the terminal devices in the first terminal device group. Correspondingly, the EESs corresponding to all the terminal devices in the first terminal device group are called the EESs corresponding to the first terminal device group.

[0161] After EES1 determines the first correspondence relationship, it stores the information of the first correspondence relationship.

[0162] In a possible implementation manner, the correspondence relationship between the first terminal device group and the EAS and the correspondence relationship between the first terminal device group and the EES can be presented in the form of a connection relationship list. That is to say, the information of the first correspondence relationship can be a connection relationship list.

[0163] Exemplarily, based on the example in step 603, a data structure of the connection relationship list can be shown in Table 1.

[0164] Table 1: Connection relationship list

[0165] Identification of the terminal device EAS corresponding to (or connected to) the terminal device EES corresponding to or (connected to connected) the terminal device Identification of UE1 IP address and / or identification information of EAS1 IP address and / or identification information of EES1 Identification of UE2 IP address and / or identification information of EAS2 IP address and / or identification information of EES2 Identification of UE3 IP address and / or identification information of EAS3 IP address and / or identification information of EES3 Identification of UE4 IP address and / or identification information of EAS3 IP address and / or identification information of EES3

[0166] Another exemplarily, the connection relationship list may include an EAS list and an EES list. Based on the example in step 603, a data structure of the EAS list can be shown in Table 2, and a data structure of the EES list can be shown in Table 3.

[0167] Table 2: EAS list

[0168] Identification of the terminal device EAS corresponding to (or connected to) the terminal device Identification of UE1 IP address and / or identification information of EAS1 Identification of UE2 IP address and / or identification information of EAS2 Identification of UE3 IP address and / or identification information of EAS3 Identification of UE4 IP address and / or identification information of EAS3

[0169] Table 3: EES list

[0170] Identification of the terminal device EES corresponding to or (connected to connected) the terminal device Identification of UE1 IP address and / or identification information of EES1 Identification of UE2 IP address and / or identification information of EES2 Identification of UE3 IP address and / or identification information of EES3 Identification of UE4 IP address and / or identification information of EES3

[0171] It should be understood that the naming method of the connection relationship list in the embodiments of the present application is not limited.

[0172] It should be understood that the embodiments of the present application do not limit the "information of the first correspondence" or the data structure of the connection relationship list.

[0173] It should be understood that in the Figure 6 process shown above, the number of terminal devices in the first terminal device group is greater than or equal to 2, which is not limited in the present application. Correspondingly, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be 1, or may be two or more, which is not limited in the present application.

[0174] It should be understood that in the Figure 6 process shown above, the "terminal device" can also be replaced by the EEC or AC on the terminal device side.

[0175] In a possible implementation manner, after the first EES corresponding to the first terminal device (i.e., the terminal device that first determines or selects the EAS) in the first terminal device group determines the first correspondence, the first correspondence can also be synchronized to the EESs corresponding to (or connected to) other terminal devices in the first terminal device group, so that the information of the first correspondence, such as the connection relationship list shown in Table 1 above, is stored on all the EESs corresponding to (or connected to) the terminal devices in the first terminal device group.

[0176] See Figure 7 , which is a schematic diagram of the synchronization process of the first correspondence provided by the embodiments of the present application. Among them, the first terminal device is terminal device 1, and the first EES is EES1.

[0177] After EES1 determines the first correspondence, EES1 stores the information of the first correspondence. Optionally, the information of the first correspondence may be a connection relationship list. Optionally, the information of the first correspondence stored by EES1 is determined by EES1. Exemplarily, an implementation manner for EES1 to determine the first correspondence can refer to Figure 6 .

[0178] After EES1 determines the first correspondence, as Figure 7 shown, it includes the following steps:

[0179] Step 701: EES1 sends the first information to the remaining EESs except EES1 (such as Figure 6 the EES2 to EESm shown in ) according to the EESs corresponding to the terminal devices in the first correspondence, and the first information is used for (or is used to) determining the first correspondence.

[0180] Optionally, the first information may be the information of the first correspondence. For example, the first information is a connection relationship list. An example of the connection relationship list can refer to the foregoing.

[0181] Steps 702a, 702b, and 702c: After the remaining EESs receive the first piece of information, they determine the first corresponding relationship according to the first piece of information and store the information of the first corresponding relationship.

[0182] Via Figure 7 the process shown, the information of the first corresponding relationship is stored on the EESs currently connected to the terminal devices in the first terminal device group.

[0183] The above Figure 7 In the process shown above, the number of EESs is only one example. It should be understood that the number of terminal devices in the first terminal device group is greater than or equal to 2. Correspondingly, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be 1, or may be two or more, which is not limited in this application.

[0184] It should be understood that in the process shown above Figure 7 the "terminal device" can also be replaced by the EEC or AC on the terminal device side.

[0185] In some embodiments of this application, when an ACR event occurs to the second terminal device in the first terminal device group, the second EES (i.e., the source EES of the second terminal device) can notify the target EAS and / or target EES of the second terminal device to the first EES. The first EES updates the first corresponding relationship it stores according to the received information, and the first ESS synchronizes the updated first corresponding relationship to the EESs corresponding to (or connected to) the terminal devices in the first terminal device group. Wherein, the first EES is the EES corresponding to the first terminal device in the first terminal device group, and the first terminal device is the terminal device that first determines or selects the EAS in the first terminal device group. One implementation manner of the above process can be referred to Figure 8a .

[0186] See Figure 8a , which is a schematic flowchart of a communication method provided by an embodiment of this application. Wherein, the first terminal device is terminal device 1; the second terminal device is terminal device 2; the first EES is EES1, that is, the EES corresponding to (or connected to) terminal device 1; the second EES is EES2, that is, the source EES connected to terminal device 2.

[0187] The information of the first corresponding relationship is stored on EES1. The first corresponding relationship includes the corresponding relationship between the first terminal device group and the EAS, and the corresponding relationship between the first terminal device group and the EES. The information of the first corresponding relationship can be represented as a connection relationship list. An example of the connection relationship list is shown in Table 1, or as shown in Tables 2 and 3.

[0188] Optionally, EES1 can pass throughFigure 6 For the process shown, determine the first correspondence relationship and store the information of the first correspondence relationship.

[0189] As Figure 8a shown, the process may include the following steps:

[0190] Step 801: EES2 sends second connection information to EES1, where the second connection information indicates the application server corresponding to terminal device 2 and / or the EES corresponding to terminal device 2.

[0191] In a possible implementation, the second connection information includes the information of the EAS corresponding to terminal device 2 (for example, including the IP address and / or identification information of the EAS) and / or the information of the EES corresponding to terminal device 2 (for example, including the IP address and / or identification information of the EES).

[0192] Optionally, the second connection information further includes the identification of terminal device 2.

[0193] Optionally, the second connection information further includes the identification of the first terminal device group (for example, gourp ID).

[0194] In a possible implementation, an ACR event occurs on terminal device 2, and terminal device 2 switches from the source EAS to the target EAS, and / or from the source EES to the target EES. The source EES of terminal device 2 can obtain the target EAS and / or target EES of terminal device 2, and then notify the EAS corresponding to terminal device 2 (that is, the target EAS to which terminal device 2 switches) and / or the EES corresponding to terminal device 2 (that is, the target EES to which terminal device 2 switches) to EES1 through the second connection information.

[0195] Optionally, the implementation manner for the source EES of terminal device 2 to obtain the EAS corresponding to terminal device 2 and / or the EES corresponding to terminal device 2 may include the following several ways.

[0196] Way 1: When terminal device 2 moves or the source EAS is not suitable for providing services to terminal device 2, for example, after the EAS is overloaded, the source EES of terminal device 2 initiates an EES discovery process to the ECS, selects a target EES from the candidate EESs recommended by the ECS, and terminal device 2 connects to the target EES; the source EES of terminal device 2 (EES2 in this process) initiates an EAS discovery process to the target EES of terminal device 2, selects a target EAS from the candidate EASs recommended by the target EES, and instructs terminal device 2 to connect to the target EAS. The source EES (EES2) of terminal device 2 can trigger the source EAS of terminal device 2 to migrate the application context to the target EAS. Through the above process, the source EES of terminal device 2 can obtain the information of the target EAS of terminal device 2 and the information of the target EES.

[0197] Method 2: After the terminal device 2 moves, it initiates an EES discovery process to the ECS, selects a target EES from the candidate EESs recommended by the ECS, and connects to the target EES; the terminal device 2 initiates an EAS discovery process to the target EES, selects a target EAS from the candidate EASs recommended by the target EES, and connects to the target EAS. The terminal device 2 sends the information of its target EAS and / or the information of the target EES to the source EES of the terminal device 2, for example, the information of the target EAS and / or the information of the target EES of the terminal device 2 can be sent to the source EES of the terminal device 2 through an ACR request message.

[0198] Method 3: Terminal device 2 initiates an EES discovery request to ECS, ECS determines the EES for UE2 and sends the EES information to terminal device 2 and the source EES of terminal device 2. Terminal device 2 initiates an EAS discovery request to its source EES, and the EES determines the EAS for terminal device 2 and sends the EAS information to terminal device 2. Terminal device 2 then sends the corresponding EAS information to the source EES of the terminal device.

[0199] Mode 4: The source EES of terminal device 2 initiates an EES discovery request to the ECS, and the ECS determines the EES for the terminal device 2 and sends the EES information to the terminal device 2 and the source EES of the terminal device 2. The source EES of the terminal device 2 determines the EAS for the terminal device.

[0200] Among them, the EES discovery process can refer to Figure 2 The process shown in the figure can be referred to for the EAS discovery process. Figure 3 The process shown.

[0201] It should be understood that the above only illustrates several possible implementation methods, and the present application is not limited thereto. As long as the source EES of the terminal device can obtain the EAS and / or EES corresponding to the terminal device, it is within the protection scope of the present application.

[0202] In one possible implementation, the common EAS information received by EES2 comes from EES1, so EES2 can determine that EES1 is the EES connected to the first terminal device (here, the first terminal device) in the first terminal device group that determines or selects EAS, and therefore sends the second connection information to EES1. In another possible implementation, EES2 stores information about the first corresponding relationship (for a specific implementation, see Figure 7 ), EES2 can send the second connection information to the remaining EESs except EES2 in the EES corresponding to the first terminal device group according to the first corresponding relationship.

[0203] Step 802: After receiving the second connection information, EES1 updates the first corresponding relationship according to the second connection information to obtain the second corresponding relationship.

[0204] Optionally, if the second connection information indicates the EAS corresponding to the terminal device 2, then EES1 updates the EAS corresponding to the terminal device 2 in the first corresponding relationship, or updates the EAS corresponding to the first terminal device group.

[0205] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, then EES1 updates the EES corresponding to the terminal device 2 in the first corresponding relationship, or updates the EES corresponding to the first terminal device group.

[0206] In a possible implementation, after receiving the second connection information, if EES1 determines that the source EAS of the terminal device 2 no longer serves the first terminal device group, that is, any terminal device in the first terminal device group is not connected to this EAS, then EES1 deletes the corresponding relationship between the terminal devices in the first terminal device group and this EAS in the first corresponding relationship.

[0207] Step 803: EES1 sends the second information to the remaining EESs other than EES1 in the EESs corresponding to the terminal devices in the first terminal device group, and the second information is used to (or is used for) determine the second corresponding relationship.

[0208] In a possible implementation, EES1 can send the second information to the remaining EESs other than EES1 in these EESs according to the EESs corresponding to the terminal devices in the second corresponding relationship (or the EES corresponding to the first terminal device group).

[0209] In a possible implementation, the second information may be the information of the second corresponding relationship. For example, the second information is the updated connection relationship list. An example of the connection relationship list can be referred to the previous text. That is, EES1 can synchronize the second corresponding relationship to other EESs in a full - update manner.

[0210] In another possible implementation, in the case where the terminal device 2 switches from the source EAS to the target EAS, the second information may include the identifier of the terminal device 2 and the information of the EAS corresponding to the terminal device 2; in the case where the terminal device 2 switches from the source EES to the target EES, the second information may include the identifier of the terminal device 2 and the information of the EES corresponding to the terminal device 2. That is, EES1 can adopt an incremental - update method to only notify other EESs of the changed corresponding relationships, thereby reducing network overhead.

[0211] Optionally, the second information further includes the identifier of the first terminal device group.

[0212] Steps 804a, 804b, and 804c: After the EESs corresponding to the remaining terminal devices receive the second information, they determine the second correspondence according to the second information and store the information of the second correspondence.

[0213] In a possible implementation, after EES1 receives the second connection information, if it determines that the source EES of terminal device 2 (i.e., EES2) no longer serves the first terminal device group, that is, any terminal device in the first terminal device group is not connected to EES2, then EES1 sends a deletion request message to the source EES of terminal device 2 (i.e., EES2), and the deletion request message is used to instruct the source EES of terminal device 2 to delete the first correspondence. Optionally, the deletion request message includes the identifier of the first terminal device group.

[0214] In the embodiment of the present application, if an ACR event occurs to terminal device 1 connected to EES1, then EES1 can update the EAS corresponding to the first terminal device group and / or the EES corresponding to the first terminal device group according to the target EAS and / or target EES of terminal device 1, and synchronize the updated correspondence to other EESs.

[0215] Exemplarily, before EES1 obtains the second correspondence, if EES1 determines that terminal device 1 switches from the source EAS to the target EAS, then EES1 can update the first correspondence according to the target EAS of terminal device 1 and notify the remaining EESs other than EES1 in the EES corresponding to the first terminal device group of the updated first correspondence.

[0216] Exemplarily again, after EES1 obtains the second correspondence, if EES1 determines that terminal device 1 switches from the source EAS to the target EAS, then EES1 updates the second correspondence according to the target EAS of terminal device 1 and sends the information indicating the updated second correspondence to the remaining EESs other than EES1 in the EES corresponding to the first terminal device group, and this information is used to (or is used to) determine the updated second correspondence.

[0217] Exemplarily, after EES1 obtains the second corresponding relationship through update, if EES1 determines that the terminal device 1 switches from EES1 to the target EES, and EES1 no longer serves the first terminal device group, then EES1 updates the second corresponding relationship according to the target EES of the terminal device 1. In the updated second corresponding relationship, the EES corresponding to the first terminal device group does not include EES1; EES1 may send information indicating the updated second corresponding relationship to these EESs according to the EES corresponding to the first terminal device group in the third corresponding relationship, and this information is used to determine the third corresponding relationship. Further, EES1 may delete the information on the corresponding relationship between the first terminal device group and the EAS, and the information on the corresponding relationship between the first terminal device group and the EES stored thereon.

[0218] In the above Figure 8a In the process shown above, the target EES that the terminal device 2 switches to may be the same as the EES corresponding to other terminal devices in the first terminal device group, or may be different from the EES corresponding to other terminal devices in the first terminal device group. That is to say, for the first terminal device group, this target EES is a new EES.

[0219] In a possible implementation, if the target EES of the terminal device 2 is a new EES for the first terminal device group, then the updated second corresponding relationship includes the new EES corresponding to the terminal device 2. Therefore, EES1 may send the second information to this new EES; alternatively, EES1 may also send the second information to the source EES of the terminal device 2 (such as the above-mentioned EES2) according to the first corresponding relationship, and then the source EES of the terminal device 2 sends the second information to the target EES of the terminal device 2. Optionally, the second information sent by EES1 to this new EES includes the information of the second corresponding relationship. That is to say, EES1 synchronizes the second corresponding relationship to this new EES in a full-update manner.

[0220] Using the above Figure 8aIn the method shown, in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, in the case of EAS and / or ESS handover, the ESS corresponding to the first terminal device group can update the corresponding relationship between the first terminal device group and the EAS and / or the corresponding relationship between the first terminal device group and the EES, and synchronize the updated corresponding relationship among the EESs, which is beneficial for the EESs to optimize the EASs connected by the terminal devices in the first terminal device group, thereby avoiding an increase in the edge service latency of the terminal devices in the first terminal device group. For example, when the terminal devices in the first terminal device group switch to a new EAS, the EES corresponding to the first terminal device group can, based on the information of the saved corresponding relationship, send the information of the new EAS to other EESs so that each EES can recommend the EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the EAS, that is, the EASs connected by the terminal devices in the first terminal device group are optimized, so that the terminal device users in the first terminal device group can obtain a better service experience.

[0221] In a possible implementation, after receiving the second connection relationship information indicating the EAS corresponding to terminal device 2, EES1 can send the information of the EAS corresponding to terminal device 2 to other EESs, so that other EESs can recommend the EAS to other terminal devices, and update the first corresponding relationship according to the connection information of the terminal devices fed back by other EESs. This implementation can refer to Figure 8b .

[0222] Optionally, if the target EAS of terminal device 2 is a new EAS for the first terminal device group, it can be recommended to other terminal devices through the above method. Among them, the target EAS of terminal device 2 may be the same as the EASs corresponding to other terminal devices in the first terminal device group, or may be different from all the EASs connected by other terminal devices in the first terminal device group. For the first terminal device group, if the target ESA of terminal device 2 is different from the EASs corresponding to other terminal devices, the target EAS of terminal device 2 is a new EAS.

[0223] See Figure 8b , by replacing step 802 in Figure 8a with the following steps in Figure 8b , the target EAS of terminal device 2 can be recommended to other terminal devices, and the first corresponding relationship can be updated according to the selection of EASs by other terminal devices:

[0224] Step 8021: EES1 determines, based on the received second connection information, that the EAS corresponding to the terminal device 2 is different from the EAS corresponding to the terminal device in the first correspondence relationship. That is to say, the target EAS of the terminal device 2 is a new EAS for the first terminal device group.

[0225] This step is optional. For example, in some other implementations, after receiving the second connection information, EES1 can execute the subsequent steps.

[0226] Step 8022: EES1 sends the information of the EAS corresponding to the terminal device 2 to other EESs (such as EES2 to EESm shown in the figure) in the EES corresponding to the first terminal device group except EES1.

[0227] Optionally, EES1 can send request messages to these EESs (such as EES2 to EESm shown in the figure) respectively, to instruct the corresponding EES to determine whether the terminal device in the first terminal device group it is connected to has switched to the EAS corresponding to the terminal device 2.

[0228] Optionally, EES1 can send the request message to other EESs except EES1 in these EESs according to the EES corresponding to the first terminal device group in the first correspondence relationship. Exemplarily, if in the first correspondence relationship, EES2 has a corresponding relationship only with the terminal device 2, then EES1 will not send the request message to EES2. Another exemplarily, if in the first correspondence relationship, EES2 has a corresponding relationship with the terminal device 2 and the terminal device 3, then EES1 needs to send the request message to EES2.

[0229] Optionally, EES1 can also send the identifier of the first terminal device group to these EESs (such as EES2 to EESm shown in the figure).

[0230] Step 8023a: EES1 recommends the EAS corresponding to the terminal device 2 as a candidate EAS to the terminal device 1 connected to EES1, and obtains the third connection information of the terminal device 1.

[0231] In a possible implementation, the terminal device 1 can choose or not choose the EAS recommended by EES1. If the terminal device 1 chooses the EAS recommended by EES1, the terminal device 1 switches from the source EAS to the EAS recommended by EES1; if the terminal device 1 does not choose the EAS recommended by EES1, the terminal device 1 does not perform the EAS switch.

[0232] Optionally, the third connection information of the terminal device 1 is used to indicate the EAS corresponding to the terminal device 1, or to indicate whether the terminal device 1 chooses the EAS recommended by the EES, or to indicate whether the terminal device 1 chooses the EAS corresponding to the terminal device 2.

[0233] Exemplarily, if the terminal device 1 selects the EAS recommended by the EES1 (i.e., the EAS corresponding to the terminal device 2), the third connection information of the terminal device 1 includes the information of the EAS selected by the terminal device 1 (i.e., the target EAS of the terminal device 2); alternatively, the third connection information of the terminal device 1 includes indication information for indicating that the terminal device 1 selects the EAS recommended by the EES1 (i.e., the target EAS of the terminal device 2). For example, the value of this indication information is 1, indicating that the terminal device 1 selects the EAS recommended by the EES.

[0234] Another exemplarily, if the terminal device 1 does not select the EAS recommended by the EES1 (i.e., the target EAS of the terminal device 2), the third connection information of the terminal device 1 includes the information of the EAS to which the terminal device 1 is currently connected; alternatively, the third connection information of the terminal device 1 includes indication information for indicating that the terminal device 1 does not select the EAS recommended by the EES1 (i.e., the target EAS of the terminal device 2). For example, the value of this indication information is 0, indicating that the terminal device 1 does not select the EAS recommended by the EES.

[0235] Optionally, the terminal device 1 may send its third connection information to the EES1.

[0236] Steps 8023b, 8023c, and 8023d: These EESs recommend the target EAS as a candidate EAS to the terminal devices in the first terminal device group connected to the EESs, and obtain the third connection information of the terminal devices. The specific implementation manner may refer to step 8023a.

[0237] Step 8024: These EESs send the third connection information of the terminal devices to the EES1.

[0238] Step 8025: The EES1 updates the first correspondence relationship according to the third connection information of the terminal devices (including the third connection information obtained by the EES1 and the third connection information sent by other EESs), and obtains the second correspondence relationship.

[0239] In another possible implementation manner, after each EES recommends the EAS corresponding to the terminal device 2 to the terminal devices in the first terminal device group connected to it, the terminal device switches from the source EAS to the EAS recommended by the EES1 according to the EAS recommended by the EES, that is, the EES forces the terminal device to switch to the target EAS of the terminal device 2. In this case, steps 8023a, 8023b, 8023c, 8023d, and 8024 may be omitted, and in step 8025, the EES1 updates the first correspondence relationship according to the EAS corresponding to the terminal device 2, that is, updates the EAS corresponding to the terminal devices in the first terminal device group to the EAS corresponding to the terminal device 2.

[0240] Figure 8b The remaining steps in Figure 8a are the same and will not be elaborated here.

[0241] Figure 8b A possible example of the process shown can be referred to Figure 14 or Figure 15 .

[0242] If the terminal device switches from the source EAS to the target EAS, it may be because the source EAS is no longer suitable for use. For example, if the source EAS is overloaded, the target EAS selected by the terminal device usually has better performance. In this case, based on the process shown in Figure 8b , other terminal devices can be migrated to this EAS, thereby ensuring or improving the service performance.

[0243] It should be understood that whenever there is an EAS switch and / or an EES switch for a terminal device, the EAS and / or EES corresponding to the first terminal device group on the EES can be updated according to the process shown in the above Figure 8a or Figure 8b .

[0244] In the above Figure 8a or Figure 8b shown process, the number of EES is only an example. It should be understood that the number of terminal devices in the first terminal device group is greater than or equal to 2. Correspondingly, the number of EES corresponding to (or connected to) the terminal devices in the first terminal device group may be 1, or may be two or more, which is not limited in this application.

[0245] It should be understood that the timing relationship of the steps in the above Figure 8a or Figure 8b shown process is only an example and is not limited in this application.

[0246] It should be understood that in the above Figure 8a or Figure 8b shown process, the "terminal device" can also be replaced by the EEC or AC on the terminal device side.

[0247] In some embodiments of this application, if the first application server determines that the second terminal device in the first terminal device group is disconnected from or connected to the first application server, the EAS corresponding to the second terminal device (further including the EES corresponding to this terminal device) can be notified to the first EES configured with the information of this EAS, so that the first EES can update the first correspondence relationship to obtain the second correspondence relationship and synchronize the second correspondence relationship to other EESs in the EESs corresponding to the terminal devices in the first terminal device group. One implementation method of the above process can be referred to Figure 9 .

[0248] SeeFigure 9 This is a schematic flowchart of a communication method provided by an embodiment of this application. Among them, the first application server is EAS2, the second terminal device is terminal device 2, the first EES is EES2, and the information of EAS2 is configured (or registered) on EES2.

[0249] The information of the first correspondence is stored on EES2. The first correspondence includes the correspondence between the first terminal device group and the EAS, and the correspondence between the first terminal device group and the EES. The information of the first correspondence can be presented as a connection relationship list. An example of the connection relationship list is shown in Table 1, or as shown in Tables 2 and 3.

[0250] Optionally, if EES2 is the EES connected to the first terminal device that determines or selects the EAS first in the first terminal device group, the first correspondence can be determined through the Figure 6 process shown, and the information of the first correspondence is stored; if EES2 is not the EES connected to the first terminal device that determines or selects the EAS first in the first terminal device group, the first correspondence can be obtained through the Figure 7 process shown.

[0251] As Figure 9 shown, this process may include the following steps:

[0252] Step 901: EES2 sends a request message to EAS2. The request message is used to indicate that when EAS2 disconnects from or establishes a connection with the terminal device in the first terminal device group, the connection information of the terminal device that disconnects from or establishes a connection with EAS2 is sent to EES2. The connection information indicates the EAS corresponding to this terminal device (i.e., the terminal device that disconnects from or establishes a connection with EAS1).

[0253] Optionally, the identification of the first terminal device group is included in the request message.

[0254] Optionally, the request message can be a subscription request message.

[0255] In a possible implementation, since EAS2 is the EAS connected to one or more terminal devices in the first terminal device group, and the information of this EAS2 is configured on EES2, EES2 can send the above request message to EAS2 to request to subscribe to the event that the connection relationship between EAS2 and the terminal devices in the first terminal device group changes.

[0256] Step 901 is an optional step.

[0257] Step 902: When EAS2 determines to disconnect from or establish a connection with terminal device 2, it determines the EAS corresponding to terminal device 2, and optionally, it can also determine the EES corresponding to terminal device 2.

[0258] Taking the establishment of a connection between terminal device 2 and EAS2 as an example, the target EAS of terminal device 2 is this EAS2.

[0259] Taking the disconnection of terminal device 2 from EAS2 as an example, in this case, EAS2 is the source EAS of terminal device 2, and EAS2 can obtain the target EAS of terminal device 2.

[0260] In a possible implementation, the process for EAS2 to obtain the target EAS of terminal device 2 can be as Figure 10 shown, and this process can include the following steps:

[0261] Step 1001: EAS2 (the source EAS of terminal device 2) sends an EAS discovery request message to EES2 (the source EES of terminal device 2), which carries the identifier of terminal device 2.

[0262] Step 1002: EES2 determines to perform application context migration, and then triggers the execution of the following steps 1003 to 1005.

[0263] Step 1003: EES2 obtains the information of the EES corresponding to terminal device 2 (or the target EES of terminal device 2) from the ECS. In this process, the target EES of terminal device 2 is taken as EESx for description.

[0264] Step 1004: EES2 sends an EAS discovery request message to EESx according to the information of the EES corresponding to terminal device 2, which carries the identifier of terminal device 2.

[0265] Step 1005: EESx returns an EAS discovery response message to EES2, which carries the information of the EAS corresponding to terminal device 2 (or the target EAS of terminal device 2).

[0266] Step 1006: EES2 sends a discovery response message to EAS2, which carries the information of the EAS corresponding to terminal device 2, and further, it can also carry the information of the EES corresponding to terminal device 2.

[0267] Step 903: EAS2 sends second connection information to EES2, and the second connection information indicates the EAS corresponding to terminal device 2 in the first terminal device group. Further, it can also indicate the EES corresponding to terminal device 2.

[0268] Optionally, the second connection information includes information about the EAS corresponding to the terminal device 2 (for example, including the IP address and / or identifier of the EAS). Further, it may also include information about the EES corresponding to the terminal device 2 (for example, including the IP address and / or identifier of the EES).

[0269] Optionally, the second connection information further includes the identifier of the terminal device 2.

[0270] Optionally, the second connection information may further include the identifier of the first terminal device group.

[0271] Step 904: The EES2 updates the first corresponding relationship according to the second connection information to obtain a second corresponding relationship.

[0272] Optionally, the EES2 updates the information about the EAS corresponding to the terminal device 2 in the first corresponding relationship, or updates the EAS corresponding to the first terminal device group, according to the EAS corresponding to the terminal device 2.

[0273] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, the EES2 updates the information about the EES corresponding to the terminal device 2 in the first corresponding relationship, or updates the EES corresponding to the first terminal device group.

[0274] In a possible implementation, when the EES2 receives the second connection information, if it is determined according to the second connection information that the EAS2 no longer serves the first terminal device group, the corresponding relationship between the terminal devices in the first terminal device group and the EAS2 in the first corresponding relationship is deleted.

[0275] Step 905: The EES2 sends the second information to the remaining EESs other than the EES1 in the EESs corresponding to the terminal devices in the first terminal device group. The second information is used to determine the second corresponding relationship.

[0276] In a possible implementation, the EES2 may send the second information to the remaining EESs other than the EES1 among these EESs according to the EESs corresponding to the terminal devices in the second corresponding relationship.

[0277] In a possible implementation, the second information may be information about the second corresponding relationship. For example, the second information is an updated connection relationship list. An example of the connection relationship list can be referred to in the previous text. That is to say, the EES2 may synchronize the second corresponding relationship to other EESs in a full-update manner.

[0278] In another possible implementation, the second information may only include the identifier of the terminal device 2 and the information of the EAS corresponding to the terminal device 2. Further, when the EAS connected to the terminal device 2 changes, the second information may further include the information of the EES corresponding to the terminal device 2. That is to say, EES1 may adopt an incremental update method to only notify other EESs of the changed corresponding relationships, thereby reducing network overhead.

[0279] Optionally, the second information further includes the identifier of the first terminal device group.

[0280] Steps 906a, 906b, and 906c: After the EESs corresponding to the remaining terminal devices receive the second information, they determine the second corresponding relationship according to the second information and store the information of the second corresponding relationship.

[0281] Based on the above Figure 9 In a possible implementation manner shown in the above process, when the terminal device 2 disconnects from the EAS2 and the source EES of the terminal device 2 is EES2, if EES2 determines according to the first corresponding relationship and the second connection information that the source EES of the terminal device 2 (i.e., EES2) no longer serves the first terminal device group, then EES2 deletes the information of the second corresponding relationship stored thereon.

[0282] Based on the above Figure 9 In a possible implementation manner shown in the above process, when the terminal device 3 establishes a connection with the EAS2 and the source EES of the terminal device 3 is not EES2, if EES2 determines according to the first corresponding relationship and the second connection information that the source EES of the terminal device 3 no longer serves the first terminal device group, then EES2 may send a deletion request message to the source EES of the terminal device 3 to request deleting the information of the first corresponding relationship stored on this EES.

[0283] In the above Figure 9 In the process shown above, the target EES of the terminal device 2 may be the same as the EESs connected to other terminal devices in the first terminal device group, or may be different from all the EESs connected to other terminal devices in the first terminal device group. That is to say, for the first terminal device group, this target EES is a new EES.

[0284] In a possible implementation, if the target EES of the terminal device 2 is a new EES for the first terminal device group, the updated second correspondence includes the new EES corresponding to the terminal device 2. Therefore, EES2 can send the second information to the new EES; alternatively, EES2 can also send the second information to the source EES of the terminal device 2 according to the first correspondence, and then the source EES of the terminal device 2 sends the second information to the target EES of the terminal device 2. Optionally, the second information sent by EES2 to the new EES includes the information of the second correspondence, that is, EES2 synchronizes the second correspondence to the new EES in a full update manner.

[0285] It should be understood that whenever an EAS switch and / or an EES switch occurs for a terminal device, the EAS and / or EES corresponding to the first terminal device group on the EES can be updated according to the process shown above. Figure 9 shown in the process.

[0286] The above Figure 9 In the process shown, the number of EESs is only an example. It should be understood that the number of terminal devices in the first terminal device group is greater than or equal to 2. Correspondingly, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be 1, or may be two or more, which is not limited in this application.

[0287] It should be understood that the step timing relationship in the above Figure 9 shown process is only an example and is not limited in this application.

[0288] It should be understood that in the process shown above Figure 9 the "terminal device" can also be replaced by the EEC or AC on the terminal device side.

[0289] Using the above Figure 9In the method shown, in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, in the case of EAS and / or ESS handover, the ESS corresponding to the first terminal device group can update the corresponding relationship between the first terminal device group and the EAS and / or the corresponding relationship between the first terminal device group and the EES, and synchronize the updated corresponding relationship among the EESs, which is beneficial for the EESs to optimize the EASs connected by the terminal devices in the first terminal device group, thereby avoiding an increase in the edge service latency of the terminal devices in the first terminal device group. For example, when the terminal devices in the first terminal device group switch to a new EAS, the EES corresponding to the first terminal device group can send the information of the new EAS to other EESs based on the saved corresponding relationship information, so that each EES can recommend the EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the EAS, that is, the EASs connected by the terminal devices in the first terminal device group are optimized, thereby avoiding an increase in the edge service latency of the terminal devices in the first terminal device group and enabling users to obtain a better service experience.

[0290] In a possible implementation, after receiving the request message, the target EES of terminal device 2 (such as Figure 9 EESm in) can also send the EAS corresponding to terminal device 2 to other EESs in the EES corresponding to the first terminal device group, so that these other EESs can recommend the EAS to the terminal devices in the first terminal device group, and receive the third connection information of the terminal devices fed back by these EESs, and then update the first corresponding relationship according to the received third connection information to obtain a second corresponding relationship, and synchronize the second corresponding relationship to other EESs. The specific implementation can refer to Figure 8b . A possible example can refer to Figure 16 .

[0291] In some embodiments of the present application, when the second terminal device in the first terminal device group undergoes EAS and / or EES handover, the second terminal device can notify the target EAS and / or target EES of the second terminal device to the first EES, and the first EES updates the first corresponding relationship it saves according to the received information, and the first ESS synchronizes the updated first corresponding relationship to the EES corresponding to (or connected to) the terminal devices in the first terminal device group. Among them, the first EES is the source EES of the second terminal device. One implementation of the above process can refer to Figure 11a .

[0292] See Figure 11a, which is a schematic flowchart of a communication method provided by an embodiment of the present application. Among them, the second terminal device is terminal device 2, and the first EES is EES2, that is, the source EES corresponding to (or connected to) terminal device 2.

[0293] The information of the first correspondence is stored on EES2. The first correspondence includes the correspondence between the first terminal device group and the EAS, and the correspondence between the first terminal device group and the EES. The information of the first correspondence can be presented as a connection relationship list. An example of the connection relationship list is shown in Table 1, or as shown in Tables 2 and 3.

[0294] Optionally, if EES2 is the EES connected to the first terminal device (terminal device 1 in this embodiment) that determines or selects the EAS first, the first correspondence can be determined through the Figure 6 shown process, and the information of the first correspondence is stored; if EES2 is not the EES connected to the first terminal device (i.e., terminal device 1) that determines or selects the EAS first, the first correspondence can be obtained through the Figure 7 shown process.

[0295] As Figure 11a shown, this process may include the following steps:

[0296] Step 1101: Terminal device 2 sends second connection information to EES2 (the source EES of terminal device 2), and the second connection information indicates the application server and / or EES corresponding to terminal device 2.

[0297] In a possible implementation manner, the second connection information includes the information of the EAS corresponding to terminal device 2 (such as including the IP address and / or identification information of the EAS) and / or the information of the EES corresponding to terminal device 2 (such as including the IP address and / or identification information of the EES).

[0298] Optionally, the second connection information further includes the identification of terminal device 2.

[0299] Optionally, the second connection information further includes the identification of the first terminal device group.

[0300] In a possible implementation manner, terminal device 2 has an ACR event, and terminal device 2 switches from the source EAS to the target EAS, and / or from the source EES to the target EES. Terminal device 2 notifies EES2 of the target EAS and / or target EES of terminal device 2 by sending the second connection information.

[0301] Optionally, terminal device 2 may send an ACR request message to EES2, which includes the second connection information.

[0302] Step 1102: After receiving the second connection information, EES2 updates the first corresponding relationship according to the second connection information to obtain the second corresponding relationship.

[0303] Optionally, if the second connection information indicates the EAS corresponding to the terminal device 2, EES1 updates the information of the EAS corresponding to the terminal device 2 in the first corresponding relationship, or updates the EAS corresponding to the first terminal device group.

[0304] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, EES1 updates the information of the EES corresponding to the terminal device 2 in the first corresponding relationship, or updates the EES corresponding to the first terminal device group.

[0305] In a possible implementation, when EES2 receives the second connection information, if it is determined that the source EAS of the terminal device 2 no longer serves the first terminal device group, that is, any terminal device in the first terminal device group is not connected to this EAS, then EES2 deletes the corresponding relationship between the terminal devices in the first terminal device group and this EAS in the first corresponding relationship.

[0306] Step 1103: EES2 sends the second information to the other EESs except EES2 in the EES corresponding to the first terminal device group, and the second information is used to (or is used for) determine the second corresponding relationship.

[0307] In a possible implementation, EES2 can send the second information to the other EESs except EES2 in these EESs according to the EES corresponding to the terminal device in the second corresponding relationship (or the EES corresponding to the first terminal device group).

[0308] In a possible implementation, the second information may be the information of the second corresponding relationship. For example, the second information is the updated connection relationship list. An example of the connection relationship list can be referred to the previous text. That is, EES2 can synchronize the second corresponding relationship to other EESs in a full update manner.

[0309] In another possible implementation, in the case where the terminal device 2 switches from the source EAS to the target EAS, the second information may include the identifier of the terminal device 2 and the information of the EAS corresponding to the terminal device 2; in the case where the terminal device 2 switches from the source EES to the target EES, the second information may include the identifier of the terminal device 2 and the information of the EES corresponding to the terminal device 2. That is, EES2 can adopt an incremental update method to only notify other EESs of the changed corresponding relationship, thereby reducing network overhead.

[0310] Optionally, the second information further includes the identifier of the first terminal device group.

[0311] Steps 1104a, 1104b, and 1104c: After the EESs corresponding to the remaining terminal devices receive the second information, they determine the second corresponding relationship according to the second information and store the information of the second corresponding relationship.

[0312] Based on the above Figure 11a In a possible implementation manner according to the flow shown above, if EES2 determines that the source EES of terminal device 2 (i.e., EES2) no longer serves the first terminal device group according to the second connection information and the first corresponding relationship, and EES2 deletes the information of the second corresponding relationship stored by it.

[0313] The above Figure 11a In the flow shown above, the target EES of terminal device 2 may be the same as the EESs to which other terminal devices in the first terminal device group are connected, or may be different from the EESs to which other terminal devices in the first terminal device group are connected. That is to say, for the first terminal device group, the target EES of terminal device 2 is a new EES.

[0314] In a possible implementation manner, if the target EES of terminal device 2 is a new EES for the first terminal device group, the updated second corresponding relationship includes the new EES corresponding to terminal device 2. Therefore, EES2 can send the second information to the new EES; alternatively, EES2 can also send the second information to the source EES of terminal device 2 according to the first corresponding relationship, and then the source EES of terminal device 2 sends the second information to the target EES of terminal device 2. Optionally, the second information sent by EES2 to the new EES includes the information of the second corresponding relationship. That is to say, EES2 synchronizes the second corresponding relationship to the new EES in a full-update manner.

[0315] Using the above Figure 11aIn the method shown, in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, in the case of EAS and / or ESS handover, the ESS corresponding to the first terminal device group can update the corresponding relationship between the first terminal device group and the EAS and / or the corresponding relationship between the first terminal device group and the EES, and synchronize the updated corresponding relationship among the EESs, which is beneficial for the EESs to optimize the EASs connected by the terminal devices in the first terminal device group, thereby avoiding an increase in the edge service latency of the terminal devices in the first terminal device group. For example, when the terminal devices in the first terminal device group switch to a new EAS, the EES corresponding to the first terminal device group can send the information of the new EAS to other EESs based on the saved corresponding relationship information, so that each EES can recommend the EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the EAS, that is, the EASs connected by the terminal devices in the first terminal device group are optimized, thereby avoiding an increase in the edge service latency of the terminal devices in the first terminal device group and enabling users to obtain a better service experience.

[0316] In a possible implementation, after receiving the second connection relationship information indicating the EAS corresponding to terminal device 2, EES2 can send the information of the EAS corresponding to terminal device 2 to other EESs, so that other EESs can recommend the EAS to other terminal devices, and update the first corresponding relationship according to the connection information of the terminal devices fed back by other EESs. This implementation can refer to Figure 11b .

[0317] Optionally, if the target EAS of terminal device 2 is a new EAS for the first terminal device group, it can be recommended to other terminal devices through the above method. Among them, the target EAS of terminal device 2 may be the same as the EASs corresponding to other terminal devices in the first terminal device group, or may be different from all the EASs connected by other terminal devices in the first terminal device group. For the first terminal device group, if the target ESA of terminal device 2 is different from the EASs corresponding to other terminal devices, then the target EAS of terminal device 2 is a new EAS.

[0318] See Figure 11b , by replacing step 1102 in Figure 11a with the following steps in Figure 11b , the target EAS of terminal device 2 can be recommended to other terminal devices, and the first corresponding relationship can be updated according to the selection situation of other terminal devices for the EAS:

[0319] Step 11021: EES2 determines, based on the received second connection information, that the EAS corresponding to the terminal device 2 is different from the EAS corresponding to the terminal device in the first correspondence relationship. That is to say, the target EAS of the terminal device 2 is a new EAS for the first terminal device group.

[0320] This step is optional. For example, in some other implementations, after receiving the second connection information, EES2 can execute the subsequent steps.

[0321] Step 11022: EES2 sends the information of the EAS corresponding to the terminal device 2 to other EESs (such as EES2 to EESm shown in the figure) in the EES corresponding to the first terminal device group except EES1.

[0322] Optionally, EES2 can send request messages to these EESs (such as EES2 to EESm shown in the figure) respectively, to instruct the corresponding EES to determine whether the terminal device in the first terminal device group it is connected to has switched to the EAS corresponding to the terminal device 2.

[0323] Optionally, EES2 can send the request message to other EESs except EES1 in these EESs according to the EES corresponding to the first terminal device group in the first correspondence relationship.

[0324] Optionally, EES2 can also send the identifier of the first terminal device group to these EESs (such as EES2 to EESm shown in the figure).

[0325] Step 11023a: EES2 recommends the EAS corresponding to the terminal device 2 as a candidate EAS to other terminal devices in the first terminal device group connected to EES2 except the terminal device 2, and obtains the third connection information of the other terminal devices.

[0326] It can be understood that if EES2 is not connected to other terminal devices in the first terminal device group except the terminal device 2, EES2 does not have to execute this step.

[0327] The terminal device can choose or not choose the EAS recommended by EES2. If the terminal device chooses the EAS recommended by EES2, the terminal device switches from the source EAS to the EAS recommended by EES2; if the terminal device does not choose the EAS recommended by EES1, the terminal device does not perform the EAS switch.

[0328] Optionally, the third connection information of the terminal device is used to indicate the EAS corresponding to the terminal device, or to indicate whether the terminal device chooses the EAS recommended by the EES, or to indicate whether the terminal device chooses the EAS corresponding to the terminal device 2.

[0329] Exemplarily, if the terminal device selects the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2), then the third connection information of the terminal device includes the information of the EAS selected by the terminal device (i.e., the target EAS of terminal device 2); alternatively, the third connection information of the terminal device includes indication information for indicating that the terminal device selects the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2). For example, the value of the indication information is 1, indicating that the terminal device selects the EAS recommended by EES.

[0330] Again exemplarily, if the terminal device does not select the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2), then the third connection information of the terminal device includes the information of the EAS to which the terminal device is currently connected; alternatively, the third connection information of the terminal device includes indication information for indicating that the terminal device does not select the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2). For example, the value of the indication information is 0, indicating that the terminal device does not select the EAS recommended by EES.

[0331] Optionally, the terminal device may send its third connection information to EES2.

[0332] Steps 11023b, 11023c, and 11023d: These EESs recommend the EAS corresponding to terminal device 2 as a candidate EAS to the terminal devices in the first terminal device group connected to the EES, and obtain the third connection information of the terminal device. The specific implementation manner may refer to step 11023a.

[0333] Step 11024: These EESs send the third connection information of the terminal device to EES2.

[0334] Step 11025: EES2 updates the first correspondence relationship according to the third connection information of the terminal device (including the third connection information obtained by EES1 and the third connection information sent by other EESs) to obtain the second correspondence relationship.

[0335] In another possible implementation manner, after each EES recommends the EAS corresponding to terminal device 2 to the terminal devices in the first terminal device group connected to it, the terminal device switches from the source EAS to the EAS recommended by EES1 according to the candidate EAS recommended by the EES. That is to say, the EES forces the terminal device to switch to the EAS corresponding to terminal device 2. In this case, steps 11023a, 11023b, 11023c, 11023d, and 11024 can be omitted, and in step 11025, EES1 updates the first correspondence relationship according to the EAS corresponding to terminal device 2, that is, updates the EAS corresponding to the terminal devices in the first terminal device group to the EAS corresponding to terminal device 2.

[0336] Figure 11b The remaining steps in Figure 11a are the same and will not be elaborated here. Figure 11b A possible example of the process shown can be referred to Figure 17 .

[0337] In the above Figure 11a or Figure 11b shown process, the number of EES is only one example. It should be understood that the number of terminal devices in the first terminal device group is greater than or equal to 2. Correspondingly, the number of EES corresponding to (or connected to) the terminal devices in the first terminal device group may be 1, or may be two or more, which is not limited in this application.

[0338] It should be understood that whenever an EAS handover and / or an EES handover occurs for a terminal device, the EAS and / or EES corresponding to the first terminal device group on the EES can be updated according to the above Figure 11a or Figure 11b shown process.

[0339] If a terminal device switches from a source EAS to a target EAS, it may be because the source EAS is no longer suitable for use. For example, the source EAS is overloaded, and the target EAS selected by the terminal device usually has better performance. In this case, based on the Figure 11b shown process, other terminal devices can be migrated to this EAS, thereby ensuring or improving service performance.

[0340] It should be understood that the sequential relationship of the steps in the above Figure 11a or Figure 11b shown process is only one example and is not limited in this application.

[0341] It should be understood that in the above Figure 11a or Figure 11b shown process, "terminal device" can also be replaced by EEC or AC on the terminal device side.

[0342] In the above Figure 11a or Figure 11b shown process, for the situation where the terminal devices in the terminal device group disconnect from the source application server and connect to the target application server, the management server connected to the terminal devices in this terminal device group can obtain information about the target application server, so as to recommend that the terminal devices in this group of terminal devices connected to the management server connect to the target application server.

[0343] Based on the Figure 11a or Figure 11b shown communication method, if the source EES of the second terminal device that has an ACR event (i.e., Figure 11a or Figure 11bIf, according to the second connection information, it is determined that the EES no longer serves the first terminal device group, the EES may instruct the target EES of the second terminal device to perform an update operation on the first corresponding relationship and synchronize the updated corresponding relationship. Figure 12 Exemplarily shows this process.

[0344] See Figure 12 , which is a schematic flowchart of a communication method provided by an embodiment of this application. Based on Figure 11a or Figure 11b scenarios, as shown in the figure, this process may include the following steps:

[0345] Step 1201: The terminal device 2 sends second connection information to EES2 (the source EES of the terminal device 2), and the second connection information indicates the EAS and / or EES corresponding to the terminal device 2.

[0346] The specific implementation manner of this step may refer to Figure 8a or Figure 8b step 801 in.

[0347] Step 1202: After receiving the second connection information, EES2 determines that EES2 (that is, the source EES of the terminal device 2) no longer serves the first terminal device group.

[0348] Step 1203: EES2 sends a first request message to the EES corresponding to the terminal device 2 (EESm in the figure), and the first request message is used to instruct EESm (that is, the target EES of the terminal device 2) to update the corresponding relationship between the first terminal device group and the EAS and / or EES.

[0349] Optionally, the first request message includes the identifier of the terminal device 2.

[0350] Optionally, the first request message includes the identifier of the first terminal device group.

[0351] Optionally, the first request message includes information about the EAS corresponding to the terminal device 2, and further may include information about the EES corresponding to the terminal device 2.

[0352] Optionally, the first request message includes information about the first corresponding relationship.

[0353] Optionally, EES2 may delete EES2 in the EES corresponding to the first terminal device group in the first corresponding relationship, and then send the corresponding relationship information after deleting EES2 to EESm.

[0354] Optionally, the first request message includes indication information for indicating that EES2 no longer serves the first UE group.

[0355] Optionally, if EESm (the target EES of terminal device 2) is a new EES for the first terminal device group, there is no information about the first corresponding relationship stored on this EES. Therefore, EES3 can also send the information about the first corresponding relationship to EESm through this first request message. If EESm (the target EES of terminal device 2) is not a new EES for the first terminal device group, the information about the first corresponding relationship is stored on this EES. Therefore, EES3 does not need to send the information about the first corresponding relationship to EESm.

[0356] Step 1204: After receiving the first request message, EESm updates the first corresponding relationship according to the EAS and / or EES corresponding to terminal device 2.

[0357] In this step, optionally, EESm can further update the first corresponding relationship according to the information about the EAS corresponding to terminal device 2 carried in the first request message and also according to the information about the EES corresponding to terminal device 2 carried in the first request message.

[0358] In one possible implementation, the specific implementation of this step can refer to Figure 11a Step 1102 in

[0359] In another possible implementation, the specific implementation of this step can refer to Figure 11b Steps 11021 to 11025 in

[0360] Step 1205: EESm sends the second information to the other EESs in the EESs corresponding to the first terminal device group except EES2. The second information is used to (or is used for) determine the second corresponding relationship.

[0361] Optionally, EESm can send the second information to other EESs except EESm according to the EESs corresponding to the first terminal device group in the second corresponding relationship.

[0362] The specific implementation of this step can refer to Figure 11a or Figure 11b Step 1103 in

[0363] Step 1206: EES2 deletes the information about the first corresponding relationship it stores. This step is an optional step.

[0364] Steps 1207a, 1207b: After receiving the second information, the EESs corresponding to the other terminal devices determine the second corresponding relationship according to the second information and store the information about the second corresponding relationship.

[0365] It should be understood that the above Figure 12The time sequence relationship of the steps in the shown process is only an example and is not limited in this application.

[0366] It should be understood that in the process shown above Figure 12 the "terminal device" can also be replaced by the EEC or AC on the terminal device side.

[0367] Using the method shown above Figure 12 in a scenario where the connection situation of at least one terminal device in the first terminal device group changes, for example, in the case of EAS and / or ESS handover, the ESS corresponding to the first terminal device group can update the corresponding relationship between the first terminal device group and the EAS and / or the corresponding relationship between the first terminal device group and the EES, and synchronize the updated corresponding relationship among the EESs, which is beneficial for the EESs to optimize the EASs connected by the terminal devices in the first terminal device group, thereby avoiding the increase in the edge service delay of the terminal devices in the first terminal device group. When the terminal device in the first terminal device group switches to a new EAS, the EES corresponding to the first terminal device group can, based on the information of the saved corresponding relationship, send the information of the new EAS to other EESs so that each EES can recommend the EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device usually has better performance, through the above method, the terminal devices in the first terminal device group can be migrated to the EAS, that is, the EASs connected by the terminal devices in the first terminal device group are optimized, thereby avoiding the increase in the edge service delay of the terminal devices in the first terminal device group and enabling users to obtain a better service experience.

[0368] In a possible implementation, after the target EES of terminal device 2 (such as Figure 12 EESm in Figure 8b receives the first request message, it can also send the EAS corresponding to terminal device 2 to other EESs in the EES corresponding to the first terminal device group through a second request message to instruct these other EESs to recommend the EAS to the terminal devices in the first terminal device group, and receive the third connection information of the terminal devices fed back by these EESs, and then update the first corresponding relationship according to the received third connection information to obtain a second corresponding relationship, and synchronize the second corresponding relationship to other EESs. The specific implementation can refer to Figure 18 and Figure 19 .

[0369] In a possible implementation, the terminal device that has an EAS and / or EES handover can instruct the target EES of the terminal device to send the second connection information of the terminal device to the source EES of the terminal device. The subsequent process can refer to Figure 12Optionally, in this case, the source EES may not have to delete the information of the first corresponding relationship.

[0370] It should be understood that, according to the specific scenario, the above Figure 8a , Figure 8b , Figure 9 , Figure 11a , Figure 11b or Figure 12 shown methods can be used.

[0371] To understand the above embodiments of the present application more clearly, the following describes the embodiments of the present application in combination with Figure 13 the specific application scenarios shown.

[0372] Refer to Figure 13 , which is a schematic diagram of the scenario where the terminal devices in a terminal device group switch EAS and EES in the embodiments of the present application. As Figure 13 shown, the first UE group includes UE1, UE2, UE3, and UE4. Initially, UE1 initiates an EES discovery process to the ECS, obtains the information of EES1 from the ECS and connects to EES1, and UE1 initiates an EAS discovery process to EES1, obtains the information of EAS1 from EES1 and connects to EAS1. Similarly, UE2 connects to EES2 and EAS2 by initiating the EES process and the EAS process, UE3 connects to EES3 and EAS3 by initiating the EES process and the EAS process, and UE4 connects to EES2 and EAS2 by initiating the EES process and the EAS process. Among them, UE1 is the first UE in the first UE group to connect to the EAS.

[0373] Based on the above scenario, after the UEs in the first UE group initially connect to the EES and the EAS, EES1 determines the first corresponding relationship and stores the information of the first corresponding relationship. The first corresponding relationship includes the corresponding relationship between the first UE group and the EAS {<UE1, EAS1>, <UE2, EAS2>, <UE3, EAS3>, <UE4, EAS2>}, and the corresponding relationship between the first UE group and the EES {<UE1, EES1>, <UE2, EES2>, <UE3, EES3>, <UE4, EES2>}. EES1 can send the information of the first corresponding relationship to EES2 and EES3, so that the information of the first corresponding relationship is also stored on EES2 and EES3. The specific implementation manner of the above process can refer to Figure 6 and Figure 7 .

[0374] UE2 experiences an ACR event and switches (or migrates) from EES2 to EES4 and from EAS2 to EAS4. Correspondingly, the first correspondence is updated to the second correspondence. The second correspondence includes the correspondence between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0375] Based on Figure 13 the scenario shown Figure 14 illustrates the process after UE2 experiences an ACR event, as Figure 14 shown, and this process includes the following steps:

[0376] Step 1401: The source EES (EES2) of UE2 sends an EES discovery request message to the ECS.

[0377] Optionally, due to a location movement of UE2 or because the source EAS is not suitable for providing services to the terminal device, for example, after the EAS is overloaded, the source EES of UE2 initiates an EES discovery process to the ECS.

[0378] Step 1402: The ECS returns an EES discovery response message to EES2, which carries information about candidate EESs, and EES4 is included in the candidate EESs.

[0379] Step 1403: EES2 selects EES4 from the candidate EESs.

[0380] Optionally, EES2 also instructs UE2 to connect to EES4.

[0381] Step 1404: EES2 sends an EAS discovery request message to EES4.

[0382] Step 1405: EES4 returns an EAS discovery response message to EES2, which carries information about candidate EASs, and EAS4 is included in the candidate EASs.

[0383] Step 1406: EES2 selects EAS4 from the candidate EASs.

[0384] Steps 1407a and 1407b: According to the EES corresponding to the first UE group in the first correspondence, EES2 sends the second connection information of UE2 to the EESs other than EES2 (including EES1 and EES3). The second connection information of UE2 indicates the EAS and EES corresponding to UE2. Among them, the EAS corresponding to UE2 is EAS4, and the EES corresponding to UE2 is EES4.

[0385] Step 1408: After receiving the second connection information, EES1 recommends EAS4 to UE1 and obtains the third connection information of UE1. The third connection information of UE1 indicates the EAS corresponding to UE1 or indicates whether UE1 has selected EAS4. In this example, the third connection information of UE1 indicates that UE1 has not selected EAS4.

[0386] Step 1409: According to the EES corresponding to the first UE group in the first correspondence relationship, EES1 sends the information of the EAS (EAS4) corresponding to UE2 to the EESs other than EES1 (including EES2 and EES3), and optionally, also includes the identifier of the first UE group.

[0387] Steps 1410a and 1411a: After receiving the second connection information, EES2 recommends EAS4 to UE4 and obtains the third connection information of UE4. EES2 sends the third connection information of UE4 to EES1. In this example, the third connection information of UE4 indicates that UE4 has not selected EAS4.

[0388] Steps 1410b and 1411b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains the third connection information of UE3. EES3 sends the third connection information of UE3 to EES1. In this example, the third connection information of UE3 indicates that UE3 has not selected EAS4.

[0389] Step 1412: EES1 updates the first correspondence relationship according to the third connection information of UE1, UE3, and UE4 to obtain the second correspondence relationship.

[0390] Among them, the second correspondence relationship includes the correspondence relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0391] Step 1413: According to the EES corresponding to the first UE group in the second correspondence relationship, EES1 sends the second information to the remaining EESs other than EES1 (including EES2, EES3, and EES4). The second information is used to determine the second correspondence relationship.

[0392] Optionally, the second information sent to EES4 is information on the second corresponding relationship, such as the corresponding relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the corresponding relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0393] Optionally, the second information sent to EES2 and EES3 can be: <UE2, EAS4> and <UE2, EES4>.

[0394] Steps 1414a, 1414b, and 1414c: After receiving the second information, EES2, EES3, and EES4 respectively determine the second corresponding relationship according to the second information and store the information on the second corresponding relationship.

[0395] It should be understood that steps 1401 to 1406 can also be replaced by other implementation manners, that is, the source EES of UE2 can also obtain the corresponding EAS and / or EES of UE2 through other implementation manners, or obtain the target EAS and / or target EES of UE2. For specific details, reference can be made to the relevant content in the foregoing embodiments.

[0396] Exemplarily, one implementation manner is: UE2 sends an EES discovery request to ECS. ECS determines EES4 for this UE2 and sends the information on EES4 to UE2 and the source EES (EES2) of UE2. UE2 sends an EAS discovery request to its source EES (EES2). EES2 determines EAS4 for UE2 and sends the information on EAS4 to UE2.

[0397] The above Figure 14 The specific implementation manners of the steps in the shown process can be referred to Figure 8a or Figure 8b .

[0398] It should be understood that Figure 14 The shown process is only Figure 13 A possible implementation manner in the shown scenario and does not constitute a limitation to this application.

[0399] Based on Figure 13 The shown scenario, Figure 15 Shows the process after UE2 has an ACR event. As Figure 15 Shown, this process includes the following steps:

[0400] Step 1501: UE2 initiates an EES discovery process to ECS and selects EES4 from the candidate EESs provided by ECS.

[0401] Optionally, after the terminal device 2 moves, it initiates an EES discovery process to the ECS, selects EES4 from the candidate EESs recommended by the ECS, and connects to the EES4. The specific implementation method can refer to Figure 2 。

[0402] Step 1502: UE2 initiates an EAS discovery process to EES4, and selects EAS4 from the candidate EASs provided by EES4. The specific implementation method can refer to Figure 3 。

[0403] Step 1503: UE2 sends an ACR request message to its source EES (EES2), which carries the information of the EAS (EAS4) corresponding to UE2 and the information of the EES (EES4). It should be understood that the message in step 1503 is not limited in this application.

[0404] Steps 1504a and 1504b: According to the EES corresponding to the first UE group in the first correspondence relationship, EES2 sends the second connection information of UE2 to the EESs other than EES2 (including EES1 and EES3), and the second connection information of UE2 indicates the EAS and EES corresponding to UE2, where the EAS corresponding to UE2 is EAS4, and the EES corresponding to UE2 is EES4.

[0405] Step 1505: After receiving the second connection information, EES1 recommends EAS4 to UE1 and obtains the third connection information of UE1. The third connection information of UE1 indicates the EAS corresponding to UE1, or indicates whether UE1 has selected EAS4. In this example, the third connection information of UE1 indicates that UE1 has not selected EAS4.

[0406] Step 1506: According to the EES corresponding to the first UE group in the first correspondence relationship, EES1 sends the information of the EAS (EAS4) corresponding to UE2 to the EESs other than EES1 (including EES2 and EES3), and optionally, also includes the identifier of the first UE group.

[0407] Steps 1507a and 1508a: After receiving the second connection information, EES2 recommends EAS4 to UE4 and obtains the third connection information of UE4. EES2 sends the third connection information of UE4 to EES1. In this example, the third connection information of UE4 indicates that UE4 has not selected EAS4.

[0408] Steps 1507b and 1508b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains the third connection information of UE3. EES3 sends the third connection information of UE3 to EES1. In this example, the third connection information of UE3 indicates that UE3 has not selected EAS4.

[0409] Step 1509: EES1 updates the first corresponding relationship according to the third connection information of UE1, UE3, and UE4 to obtain a second corresponding relationship.

[0410] Among them, the second corresponding relationship includes the corresponding relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the corresponding relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0411] Step 1510: EES1 sends second information to the remaining EESs other than EES1 (including EES2, EES3, and EES4) according to the EESs corresponding to the first UE group in the second corresponding relationship. The second information is used to determine the second corresponding relationship.

[0412] Optionally, the second information sent to EES4 is the information of the second corresponding relationship, such as including the corresponding relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the corresponding relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0413] Optionally, the second information sent to EES2 and EES3 can be: <UE2, EAS4> and <UE2, EES4>.

[0414] Steps 1511a, 1511b, and 1511c: After receiving the second information, EES2, EES3, and EES4 respectively determine the second corresponding relationship according to the second information and store the information of the second corresponding relationship.

[0415] It should be understood that steps 1501 to 1503 can also be replaced by other implementation manners. That is to say, it is also possible to obtain the EAS and / or EES corresponding to UE2, or the target EAS and / or target EES of UE2 through other implementation manners. Specifically, reference can be made to the relevant content in the foregoing embodiments.

[0416] Exemplarily, one implementation is as follows: UE2 sends an EES discovery request to ECS. ECS determines EES4 for this UE2 and sends the information of EES4 to UE2. UE2 sends an EAS discovery request to EES4. EES4 determines EAS4 for UE2 and sends the information of EAS4 to UE2. UE2 sends the information of ESA4 and the information of EES4 to the source EES of UE2.

[0417] The above Figure 15 For the specific implementation methods of each step in the shown process, reference can be made to Figure 8a or Figure 8b .

[0418] It should be understood that Figure 15 the shown process is only Figure 13 a possible implementation method in the shown scenario and does not constitute a limitation to this application.

[0419] Based on Figure 13 the shown scenario, Figure 16 the process after UE2 has an ACR event is shown. As Figure 16 shown, this process includes the following steps:

[0420] Step 1601: EES2 sends a request message to EAS2, which is used to indicate that when EAS2 disconnects from or establishes a connection with a UE in the first UE group, the connection information of this UE is sent to EES2.

[0421] Step 1602: EAS2 determines that UE2 disconnects from EAS2. EAS2 obtains the information of the target EAS (EAS4) of UE2 and the information of the target EES (EES4).

[0422] For the specific implementation method of this step, reference can be made to Figure 10 .

[0423] Step 1603: EAS2 sends second connection information to EES2. The second connection information indicates the information of the EAS corresponding to UE2 and the information of EES. Among them, the EAS corresponding to UE2 is the ESA4 that UE2 switches to, and the EES corresponding to UE2 is the EES4 that UE2 switches to.

[0424] Step 1604: EES2 recommends EAS4 to UE4 according to the EAS4 corresponding to UE2, and obtains the third connection information of UE4. The third connection information of UE4 indicates that UE4 does not select EAS4.

[0425] Step 1605: According to the EES corresponding to the first UE group in the first correspondence relationship, EES2 sends the information of the EAS (EAS4) corresponding to UE2 to the EESs other than EES2 (including EES1 and EES3), and optionally, also includes the identifier of the first UE group.

[0426] Steps 1606a and 1607a: After receiving the second connection information, EES1 recommends EAS4 to UE1 and obtains the third connection information of UE1. EES1 sends the third connection information of UE1 to EES2. In this example, the third connection information of UE1 indicates that UE1 does not select EAS4.

[0427] Steps 1606b and 1607b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains the third connection information of UE3. EES3 sends the third connection information of UE3 to EES2. In this example, the third connection information of UE3 indicates that UE3 does not select EAS4.

[0428] Step 1608: EES2 updates the first correspondence relationship according to the third connection information of UE1, UE3, and UE4 to obtain the second correspondence relationship.

[0429] Among them, the second correspondence relationship includes the correspondence relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0430] Step 1609: According to the EES corresponding to the first UE group in the second correspondence relationship, EES2 sends the second information to the remaining EESs other than EES2 (including EES1, EES3, and EES4). The second information is used to determine the second correspondence relationship.

[0431] Optionally, the second information sent to EES4 is the information of the second correspondence relationship, such as including the correspondence relationship between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence relationship between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0432] Optionally, the second information sent to EES1 and EES3 can be: <UE2, EAS4> and <UE2, EES4>.

[0433] Steps 1610a, 1610b, and 1610c: After receiving the second information, EES1, EES3, and EES4 respectively determine the second corresponding relationship according to the second information and store the information of the second corresponding relationship.

[0434] It should be understood that steps 1601 to 1603 can also be replaced by other implementation manners. That is to say, it is also possible to obtain the EAS and / or EES corresponding to UE2, or the target EAS and / or target EES of UE2, through other implementation manners. Specifically, reference can be made to the relevant content in the foregoing embodiments.

[0435] The above Figure 16 The specific implementation manners of the steps in the above Figure 9 .

[0436] It should be understood that Figure 16 The process shown above is only Figure 13 a possible implementation manner in the scenario shown above, and does not constitute a limitation to this application.

[0437] Based on Figure 13 the scenario shown above, Figure 17 the process after UE2 has an ACR event is shown, and this process includes the following steps:

[0438] Step 1701: After UE2 selects or switches to EES4 and EAS4, it sends an ACR request message to the source EES (EES2) of UE2, including second connection information, where the second connection information indicates the EAS and EES corresponding to UE2. Among them, the EAS corresponding to UE2 is ESA4 to which UE2 switches, and the EES corresponding to UE2 is EES4 to which UE2 switches.

[0439] Step 1702: EES2 recommends EAS4 to UE4 according to the EAS4 corresponding to UE2, and obtains the third connection information of UE4, where the third connection information of UE4 indicates that UE4 has not selected EAS4.

[0440] Step 1703: EES2 respectively sends the information of the EAS (EAS4) corresponding to UE2 to the EESs other than EES2 (including EES1 and EES3) according to the EES corresponding to the first UE group in the first corresponding relationship. Optionally, the identifier of the first UE group is also included.

[0441] Steps 1704a and 1705a: After receiving the second connection information, EES1 recommends EAS4 to UE1 and obtains the third connection information of UE1, and EES1 sends the third connection information of UE1 to EES2. In this example, the third connection information of UE1 indicates that UE1 has not selected EAS4.

[0442] Steps 1704b and 1705b: After EES3 receives the second connection information, it recommends EAS4 to UE3 and obtains the third connection information of UE3. EES3 sends the third connection information of UE3 to EES2. In this example, the third connection information of UE3 indicates that UE3 does not select EAS4.

[0443] Step 1706: EES2 updates the first correspondence according to the third connection information of UE1, UE3, and UE4 to obtain the second correspondence.

[0444] Among them, the second correspondence includes the correspondence between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0445] Step 1707: EES2 sends the second information to the remaining EESs (including EES1, EES3, and EES4) other than EES2 according to the EESs corresponding to the first UE group in the second correspondence. The second information is used to determine the second correspondence.

[0446] Optionally, the second information sent to EES4 is the information of the second correspondence, such as including the correspondence between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0447] Optionally, the second information sent to EES1 and EES3 can be: <UE2, EAS4> and <UE2, EES4>.

[0448] Steps 1708a, 1708b, and 1708c: After EES1, EES3, and EES4 receive the second information, they respectively determine the second correspondence according to the second information and store the information of the second correspondence.

[0449] It should be understood that step 1701 can also be replaced by other implementation manners, that is, it is also possible to obtain the EAS and / or EES corresponding to UE2, or the target EAS and / or target EES of UE2 through other implementation manners. Specifically, reference can be made to the relevant content in the foregoing embodiments.

[0450] The above Figure 17 The specific implementation manners of each step in the shown process can be referred toFigure 11a or Figure 11b 。

[0451] It should be understood that Figure 17 the process shown is only Figure 13 a possible implementation under the scenario shown, and does not constitute a limitation to this application.

[0452] Refer to Figure 18 , which is a schematic diagram of the scenario where a terminal device in a terminal device group switches between EAS and EES in an embodiment of this application. As Figure 18 shown, the first UE group includes UE1, UE2, UE3, and UE4. Initially, UE1 initiates an EES discovery process to the ECS, obtains the information of EES1 from the ECS and connects to EES1, and then UE1 initiates an EAS discovery process to EES1, obtains the information of EAS1 from EES1 and connects to EAS1. Similarly, UE2 connects to EES2 and EAS2 by initiating the EES process and the EAS process, UE3 connects to EES3 and EAS3 by initiating the EES process and the EAS process, and UE4 connects to EES2 and EAS2 by initiating the EES process and the EAS process. Among them, UE1 is the first UE in the first UE group to connect to the EAS.

[0453] Based on the above scenario, after the UEs in the first UE group initially connect to the EES and the EAS, EES1 determines the first correspondence and stores the information of the first correspondence. The first correspondence includes the correspondence between the first UE group and the EAS {<UE1, EAS1>, <UE2, EAS2>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and the EES {<UE1, EES1>, <UE2, EES2>, <UE3, EES3>, <UE4, EES2>}. EES1 can send the information of the first correspondence to EES2 and EES3 so that the information of the first correspondence is also stored on EES2 and EES3. The specific implementation of the above process can refer to Figure 6 and Figure 7 。

[0454] UE1 has an ACR event and switches (or migrates) from EES1 to EES4 and from EAS1 to EAS4. Correspondingly, the first correspondence is updated to the second correspondence. The second correspondence includes the correspondence between the first UE group and the EAS {<UE1, EAS4>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and the EES {<UE1, EES4>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0455] Based on Figure 18 the scenario shown, Figure 19 it shows the process after the ACR event occurs in UE1, such as Figure 19 shown, this process includes the following steps:

[0456] Step 1901: After UE1 selects or switches to EES4 and EAS4, it sends an ACR request message to the source EES (EES1) of UE1, which includes second connection information indicating the EAS and EES corresponding to UE1. Among them, the EAS corresponding to UE1 is ESA4 to which UE1 switches, and the EES corresponding to UE1 is EES4 to which UE1 switches.

[0457] Step 1902: EES1 determines, according to the received second connection information and the first correspondence stored on EES1, that EES1 no longer serves the first UE group.

[0458] This step is an optional step. In some other embodiments, even if EES1 still serves the first UE group, EES1 can also send a request message to the target EES of UE1.

[0459] Step 1903: EES1 sends a request message to the target EES (EES4) of UE1, for requesting the target EES (EES4) of UE1 to perform operations of correspondence update and synchronization according to the EAS corresponding to UE1.

[0460] Optionally, the request message includes the information of the EAS corresponding to UE1 and the information of the EES corresponding to UE1.

[0461] Optionally, the request message includes the information of the first correspondence.

[0462] Optionally, EES1 can delete EES1 in the EES corresponding to the first UE group in the first correspondence, and then send the correspondence information after deleting EES1 to EES4.

[0463] Optionally, the request message includes indication information for indicating that EES1 no longer serves the first UE group.

[0464] Step 1904: After receiving the request message, EES4 stores the information of the first correspondence.

[0465] Step 1905: EES4 sends the information of the EAS (EAS4) corresponding to UE1 to the EESs other than EES1 (including EES2 and EES3) according to the EES corresponding to the first UE group in the first correspondence. Optionally, it also includes the identifier of the first UE group.

[0466] Steps 1906a and 1907a: After receiving the second connection information, EES2 recommends EAS4 to UE2 and UE4, obtains the third connection information of UE2 and UE4, and EES2 sends the third connection information of UE2 and UE4 to EES4. In this example, the third connection information of UE2 indicates that UE2 does not select EAS4, and the third connection information of UE4 indicates that UE4 does not select EAS4.

[0467] Steps 1906b and 1907b: After receiving the second connection information, EES3 recommends EAS4 to UE3, obtains the third connection information of UE3, and EES3 sends the third connection information of UE3 to EES2. In this example, the third connection information of UE3 indicates that UE3 does not select EAS4.

[0468] Step 1908: EES4 updates the first correspondence according to the EAS and EES corresponding to UE1, and the third connection information of UE2, UE3, and UE4, and obtains the second correspondence.

[0469] Among them, the second correspondence includes the correspondence between the first UE group and EAS {<UE1, EAS4>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and EES {<UE1, EES4>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0470] Step 1909: EES2 sends the second information to the remaining EESs (including EES1, EES3, and EES4) other than EES2 according to the EES corresponding to the first UE group in the second correspondence, and the second information is used to determine the second correspondence.

[0471] Optionally, the second information sent to EES4 is the information of the second correspondence, for example, it includes the correspondence between the first UE group and EAS {<UE1, EAS1>, <UE2, EAS4>, <UE3, EAS3>, <UE4, EAS2>}, and the correspondence between the first UE group and EES {<UE1, EES1>, <UE2, EES4>, <UE3, EES3>, <UE4, EES2>}.

[0472] Optionally, the second information sent to EES1 and EES3 can be: <UE2, EAS4> and <UE2, EES4>.

[0473] Steps 1910a and 1910b: After receiving the second information, EES3 and EES4 respectively determine the second correspondence according to the second information and store the information of the second correspondence.

[0474] It should be understood that step 1901 can also be replaced by other implementation manners, that is, the source EES of UE1 can also obtain the EAS and / or EES corresponding to UE1 through other implementation manners, or obtain the target EAS and / or target EES of UE1.

[0475] The above Figure 19 The specific implementation manners of the steps in the shown process can refer to Figure 12 .

[0476] It should be understood that Figure 19 The shown process is only Figure 18 A possible implementation manner in the shown scenario, which does not constitute a limitation to this application.

[0477] It can be understood that, in order to implement the functions in the above embodiments, the management server includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and method steps of each example described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether the above functions are executed in the manner of hardware or computer software driving hardware depends on the specific application scenario and design constraint conditions of the technical solution.

[0478] Figure 20 and Figure 21 are schematic structural diagrams of possible communication devices provided by the embodiments of this application. These communication devices can be used to implement the functions of the management server in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of this application, the communication device can be the management server or a module (such as a chip) applied to the management server.

[0479] Such as Figure 20 shown, the communication device 2000 includes a processing unit 2010 and a transceiver unit 2020. The communication device 2000 is used to implement the above Figure 2 , Figure 3 , Figure 6 , Figure 7 , Figure 8a , Figure 8b , Figure 9 , Figure 10 , Figure 11a , Figure 11b , Figure 12 , Figures 14 to 19 The functions of the management server in any of the method embodiments shown in the drawings.

[0480] For example, when the communication device 2000 is used to implement Figure 8a or Figure 8bWhen the communication device 2000 is used to implement the functions of the management server in the method embodiment shown: The processing unit 2010 determines a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server; wherein, the first management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the terminal device that first determines or selects the application server in the first terminal device group; when the transceiver unit 2020 receives second connection information from the second management server, the processing unit 2010 updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers other than the first management server in the management server corresponding to the first terminal device group through the transceiver unit 2020, where the second information is used to determine the second correspondence relationship; wherein, the second server is the source management server corresponding to the second terminal device in the first terminal device group, and the second connection information indicates the application server and / or management server corresponding to the second terminal device.

[0481] For another example, when the communication device 2000 is used to implement Figure 9 When the communication device 2000 is used to implement the functions of the management server in the method embodiment shown: The processing unit 2010 is used to obtain a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server; wherein, the first management server is one of the management servers corresponding to the terminal devices in the first terminal device group, and the information of the first application server is configured on the first management server; when the transceiver unit 2020 receives second connection information from the first application server, the processing unit 2020 updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers other than the first management server in the management server corresponding to the first terminal device group through the transceiver unit 2010, where the second information is used to determine the second correspondence relationship; wherein, the second connection information indicates the application server corresponding to the second terminal device in the first terminal device group, the source application server of the second terminal device is the first application server, or the target application server of the second terminal device is the first application server.

[0482] For another example, when the communication device 2000 is used to implement Figure 11a or Figure 11bWhen implementing the functions of the management server in the method embodiment shown: The processing unit 2010 is used to obtain a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server; among them, information of the first application server is configured on the first management server; when the transceiver unit 2020 receives second connection information from the first terminal device, the processing unit 2010 updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers in the management server corresponding to the first terminal device group except the first management server, where the second information is used to determine the second correspondence relationship; among them, the second connection information indicates the application server and / or management server corresponding to the first terminal device.

[0483] For another example, when the communication device 2000 is used to implement Figure 12 When implementing the functions of the management server in the method embodiment shown: The transceiver unit 2010 receives a first request message from the first management server, where the first request message includes information of the first correspondence relationship and second connection information, the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server, and the second connection information indicates the application server corresponding to the first terminal device in the first terminal device group; among them, the second management server is the source management server of the first terminal device, and the second management server is the target management server of the first terminal device; the processing unit 2010 responds to the first request message, updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship; and sends second information to the remaining management servers in the management server corresponding to the first terminal device group except the second management server through the transceiver unit 2020, where the second information is used to determine the second correspondence relationship.

[0484] For a more detailed description of the above processing unit 2010 and transceiver unit 2020, reference can be directly made to the relevant descriptions in the foregoing method embodiment, and details are not elaborated here.

[0485] As Figure 21 As shown, the communication device 2100 includes a processor 2110 and an interface circuit 2120. The processor 2110 and the interface circuit 2120 are coupled to each other. It can be understood that the interface circuit 2120 can be a transceiver or an input / output interface. Optionally, the communication device 2100 may further include a memory 2130, which is used to store instructions executed by the processor 2110 or store input data required for the processor 2110 to run instructions or store data generated after the processor 1310 runs instructions.

[0486] When the communication device 2100 is used to implement the method embodiments described above, the processor 2110 is used to implement the functions of the processing unit 2010, and the interface circuit 2120 is used to implement the functions of the transceiver unit 2020.

[0487] When the communication device is a chip applied to a device, the chip implements the functions of the device in the method embodiments described above. The chip receives information from other modules in the device; or, the chip sends information to other modules in the device.

[0488] It can be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0489] In the present application, another example of a communication device is provided. The communication device includes at least one processor and at least one memory. The at least one processor is coupled to the at least one memory. The at least one memory is used to store instructions. When the instructions are executed by the at least one processor, the communication device executes the method in the above embodiments. Taking the communication device including one processor and one memory as an example, as Figure 21 shown, the communication device 2100 includes one processor 2110 and one memory 2130. The processor 2110 is coupled to the memory 2130. Instructions are stored in the memory 2130. When the instructions stored in the memory 2130 are executed by the processor 2110, the communication device 2100 executes the method executed by the management server in the above embodiments.

[0490] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions executable by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium well-known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a network device or a terminal. The processor and the storage medium can also exist as discrete components in a network device or a terminal.

[0491] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile types of storage media.

[0492] In the various embodiments of the present application, if there is no special indication and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0493] In this application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally represents an "or" relationship between the associated objects before and after; in the formulas of this application, the character " / " represents a "division" relationship between the associated objects before and after. "Including at least one of A, B, and C" can represent: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0494] It can be understood that the various numerical numbers involved in the embodiments of this application are only for convenience of description and are not used to limit the scope of the embodiments of this application. The magnitudes of the serial numbers of the above processes do not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method includes: The first management server determines a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server; wherein, the first management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the terminal device in the first terminal device group that first determines or selects the application server. When the first management server receives second connection information from the second management server, it updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the other management servers in the management server corresponding to the first terminal device group except the first management server, where the second information is used to determine the second correspondence relationship; wherein, the second server is the source management server corresponding to the second terminal device in the first terminal device group, and the second connection information indicates the application server and / or management server corresponding to the second terminal device.

2. The method according to claim 1, wherein The first management server determines the first correspondence relationship, including: After the first management server determines the application server selected by the first terminal device, it sends the information of the application server selected by the first terminal device to the management servers corresponding to the other terminal devices in the first terminal device group except the first terminal device. The first management server receives first connection information sent by the management servers currently connected to the other terminal devices in the first terminal device group except the first terminal device, where the first connection information indicates the application server and / or management server to which the terminal device is currently connected. The first management server determines the first correspondence relationship according to the first connection information.

3. The method according to claim 1 or 2, characterized in that, After the first management server determines the first correspondence relationship, it further includes: The first management server sends first information to the other management servers except the first management server according to the management server corresponding to the first terminal device group in the first correspondence relationship, where the first information is used to determine the first correspondence relationship.

4. The method according to claim 3, wherein It further includes: When the first management server receives second connection information from the second management server, if it determines that the source management server of the second terminal device no longer serves the first terminal device group, the first management server sends a deletion request message to the source management server of the second terminal device, where the deletion request message is used to instruct the source management server to delete the first correspondence relationship.

5. The method according to any one of claims 1-4, characterized in that, The updating of the first correspondence relationship according to the second connection information includes: If the first management server determines according to the second connection information that the source application server of the second terminal device no longer serves the first terminal device group, it deletes the correspondence relationship between the terminal device in the first terminal device group and the source application server in the first correspondence relationship.

6. The method according to any one of claims 1-5, characterized in that, The updating of the first correspondence relationship according to the second connection information to obtain a second correspondence relationship includes: The first management server sends a request message to other management servers in the management server corresponding to the first terminal device group except the first management server. The request message includes information about the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; The first management server recommends the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the first management server except the second terminal device, and obtains third connection information of the remaining terminal devices. The third connection information indicates the application server corresponding to the remaining terminal devices; The first management server receives third connection information from the other management servers. The third connection information indicates the application server corresponding to the terminal devices connected to the other management servers; The first management server updates the first corresponding relationship according to the third connection information to obtain the second corresponding relationship.

7. A communication method, characterized in that, The method includes: The first management server obtains a first corresponding relationship, which includes the corresponding relationship between the first terminal device group and the application server and the corresponding relationship between the first terminal device group and the management server; wherein, the first management server is one of the management servers corresponding to the terminal devices in the first terminal device group, and the information of the first application server is configured on the first management server; After the first management server receives the second connection information from the first application server, it updates the first corresponding relationship according to the second connection information to obtain the second corresponding relationship, and sends second information to the remaining management servers in the management server corresponding to the first terminal device group except the first management server. The second information is used to determine the second corresponding relationship; wherein, the second connection information indicates the application server corresponding to the second terminal device in the first terminal device group, the source application server of the second terminal device is the first application server, or the target application server of the second terminal device is the first application server.

8. The method according to claim 7, wherein The first management server obtaining the first corresponding relationship includes: After the first management server determines the application server selected by the first terminal device in the first terminal device group, it sends the information of the application server selected by the first terminal device to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device; wherein, the first management server is the management server corresponding to the first terminal device, and the first terminal device is the first terminal device in the first terminal device group to determine or select the application server; The first management server receives first connection information sent by the management servers currently connected to the remaining terminal devices in the first terminal device group except the first terminal device. The first connection information indicates the application server and / or management server currently connected to the terminal device; The first management server determines the first corresponding relationship according to the first connection information.

9. The method according to claim 7, wherein The first management server obtains the first corresponding relationship, including: The first management server receives first information from a second management server, where the first information is used to determine the first corresponding relationship; among them, the second management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the terminal device in the first terminal device group that first determines or selects an application server.

10. The method according to any one of claims 7-9, characterized in that, It further includes: The first management server sends a request message to the first application server, where the request message is used to instruct that when the first application server disconnects from or establishes a connection with a terminal device in the first terminal device group, the connection information corresponding to the terminal device that disconnects from or establishes a connection with the first application server is sent to the first management server, and the connection information indicates the application server corresponding to the terminal device that disconnects from or establishes a connection with the first application server.

11. The method according to any one of claims 7 to 10, characterized in that, The updating the first corresponding relationship according to the second connection information includes: If the first management server determines according to the second connection information that the first application server no longer serves the first terminal device group, the corresponding relationship between the terminal device in the first terminal device group and the first application server in the first corresponding relationship is deleted.

12. The method according to any one of claims 7-11, characterized in that, The second connection information also indicates the management server corresponding to the second terminal device.

13. The method according to claim 12, wherein It further includes: When the source management server of the second terminal device is the first management server, if the first management server determines according to the first corresponding relationship and the second connection information that the source management server of the second terminal device no longer serves the first terminal device group, the first management server deletes the information of the second corresponding relationship; Or When the source management server of the second terminal device is not the first management server, if the first management server determines according to the first corresponding relationship and the second connection information that the source management server of the second terminal device no longer serves the first terminal device group, the first management server sends a deletion request message to the source management server of the second terminal device, and the deletion request message is used to instruct the source management server to delete the information of the first corresponding relationship.

14. The method according to any one of claims 7-13, characterized in that, The updating the first corresponding relationship according to the second connection information to obtain a second corresponding relationship includes: The first management server sends a request message to other management servers except the first management server among the management servers corresponding to the first terminal device group, where the request message includes the information of the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; The first management server recommends the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the first management server except the second terminal device, and obtains third connection information of the remaining terminal devices, where the third connection information indicates the application server corresponding to the remaining terminal devices; The first management server receives third connection information from other management servers, where the third connection information indicates the application server corresponding to the terminal devices connected to the other management servers; The first management server updates the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

15. A communication method, characterized in that, The method includes: A first management server obtains a first correspondence relationship, where the first correspondence relationship includes the correspondence relationship between the first terminal device group and the application server and the correspondence relationship between the first terminal device group and the management server; where information of a first application server is configured on the first management server; When the first management server receives second connection information from a first terminal device, it updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship, and sends second information to the remaining management servers in the management server corresponding to the first terminal device group except the first management server, where the second information is used to determine the second correspondence relationship; where the second connection information indicates the application server and / or management server corresponding to the first terminal device.

16. The method according to claim 15, wherein The first management server obtaining the first correspondence relationship includes: After the first management server determines the application server selected by a first terminal device in the first terminal device group, it sends the information of the application server selected by the first terminal device to the management servers corresponding to the remaining terminal devices in the first terminal device group except the first terminal device; where the first management server is the management server corresponding to the first terminal device, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server; The first management server receives first connection information sent by the management servers currently connected to the remaining terminal devices in the first terminal device group except the first terminal device, where the first connection information indicates the application server and / or management server currently connected to the terminal devices; The first management server determines the first correspondence relationship according to the first connection information.

17. The method according to claim 15, wherein The first management server obtaining the first correspondence relationship includes: The first management server receives first information from a second management server, where the first information is used to determine the first correspondence relationship; where the second management server is the management server corresponding to the first terminal device in the first terminal device group, and the first terminal device is the first terminal device in the first terminal device group to determine or select an application server.

18. The method according to any one of claims 15 to 17, characterized in that, The updating the first correspondence relationship according to the second connection information includes: If the first management server determines, based on the second connection information, that the source application server of the second terminal device no longer serves the first terminal device group, the first management server deletes the correspondence between the terminal devices in the first terminal device group and the source application server in the first correspondence.

19. The method according to any one of claims 15-18, characterized in that, It further includes: If the first management server determines, based on the second connection information and the first correspondence, that the source management server of the second terminal device no longer serves the first terminal device group, and the first management server is the source management server of the second terminal device, the first management server deletes the information in the second correspondence.

20. The method according to any one of claims 15-19, characterized in that, The updating of the first correspondence based on the second connection information to obtain the second correspondence includes: The first management server sends a request message to other management servers in the management server corresponding to the first terminal device group except the first management server. The request message includes information about the application server corresponding to the second terminal device, and the request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; The first management server recommends the application server corresponding to the second terminal device to the remaining terminal devices in the first terminal device group connected to the first management server except the second terminal device, and obtains the third connection information of the remaining terminal devices. The third connection information indicates the application servers corresponding to the remaining terminal devices; The first management server receives the third connection information from the other management servers. The third connection information indicates the application servers corresponding to the terminal devices connected to the other management servers; The first management server updates the first correspondence based on the third connection information to obtain the second correspondence.

21. A communication method, characterized in that, The method includes: The second management server receives a first request message from the first management server. The first request message includes information about the first correspondence and second connection information. The first correspondence includes the correspondence between the first terminal device group and the application server and the correspondence between the first terminal device group and the management server. The second connection information indicates the application server corresponding to the first terminal device in the first terminal device group; wherein, the second management server is the source management server of the first terminal device, and the second management server is the target management server of the first terminal device; The second management server responds to the first request message and updates the first correspondence based on the second connection information to obtain the second correspondence; The second management server sends second information to the remaining management servers in the management server corresponding to the first terminal device group except the second management server. The second information is used to determine the second correspondence.

22. The method according to claim 21, wherein The first request message further includes information about the management server corresponding to the first terminal device.

23. The method according to claim 21 or 22, characterized in that, The first request message further includes indication information, and the indication information indicates that the second management server no longer serves the first terminal device group.

24. The method according to any one of claims 21-23, characterized in that, The second management server sends second information to the remaining management servers other than the first management server in the management servers corresponding to the first terminal device group, including: The second management server sends the second information to other management servers other than the first management server and the second management server according to the management servers corresponding to the first terminal device group in the first correspondence relationship.

25. The method according to any one of claims 21 to 24, characterized in that Updating the first correspondence relationship according to the second connection information to obtain a second correspondence relationship includes: The second management server sends a second request message to other management servers other than the first management server and the second management server in the management servers corresponding to the first terminal device group. The second request message includes information about the application server corresponding to the first terminal device, and the second request message is used to request the other management servers to recommend the application server corresponding to the second terminal device to the terminal devices in the first terminal device group; The second management server recommends the application server corresponding to the second terminal device to the remaining terminal devices other than the second terminal device in the first terminal device group connected by the second management server, and obtains third connection information of the remaining terminal devices. The third connection information indicates the application servers corresponding to the remaining terminal devices; The second management server receives third connection information from the other management servers, and the third connection information indicates the application servers corresponding to the terminal devices connected by the other management servers; The second management server updates the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

26. A communication device, characterized in that, It includes units or modules for executing the method according to any one of claims 1-6, or includes units or modules for executing the method according to any one of claims 7-14, or includes units or modules for executing the method according to any one of claims 15-20, or includes units or modules for executing the method according to any one of claims 21-25.

27. A communication device, characterized in that, It includes: One or more processors are configured to execute the method according to any one of claims 1-6, or to execute the method according to any one of claims 7-14, or to execute the method according to any one of claims 15-20, or to execute the method according to any one of claims 21-25.

28. A communication system, characterized in that, It includes an application server and a management server. The application server is used to provide service for terminal devices, and the management server is used to provide information about the application server for terminal devices. The management server is used to implement the method according to any one of claims 1-6, or to implement the method according to any one of claims 7-14, or to implement the method according to any one of claims 15-20, or to implement the method according to any one of claims 21-25.

29. A readable storage medium, characterized in that, The readable storage medium stores a program which, when executed by a communication device, implements the method according to any one of claims 1-6, or implements the method according to any one of claims 7-14, or implements the method according to any one of claims 15-20, or implements the method according to any one of claims 21-25.

30. A chip system, characterized in that, Comprising: a memory for storing a computer program; a processor; When the processor calls and runs the computer program from the memory, the communication device installed with the chip system is caused to execute the method according to any one of claims 1-6, or execute the method according to any one of claims 7-14, or execute the method according to any one of claims 15-20, or execute the method according to any one of claims 21-25.

Images