Communication method, apparatus and system

Abstract

A communication method, apparatus and system, relating to the technical filed of communications. The method comprises: a first management server determining a first correspondence, the first correspondence comprising the correspondence between a first terminal device group and application servers and the correspondence between the first terminal device group and management servers; and when the first management server receives second connection information from a second management server, updating the first correspondence on the basis of the second connection information to obtain a second correspondence, and sending second information to other management servers other than the first management server among management servers corresponding to the first terminal device group, the second information being used for determining the second correspondence.

Description

Communication method, device and system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 29, 2023, with application number 202311871898.5 and application name “A Communication Method, Device and System”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method, device, and system. Background Art

[0004] Edge computing refers to computing and storage resources at the edge of the network. Its architectural scenarios include user equipment (UE, also known as terminal devices) and edge data networks (EDN). The EDN includes edge application servers (or application servers) and edge enablement servers (or management servers). Edge application servers are used to provide edge business services to terminal devices. Multiple edge application servers can provide the same edge services. The edge enablement server is used to provide information such as the IP address of the edge application server to the terminal device.

[0005] In an edge computing scenario, a group of terminal devices may use one or more edge application servers in the EDN that provide the same edge services, and different terminal devices in the group may connect to different edge enabling servers.

[0006] Currently, when a group of terminal devices use the same edge service, changes in the connection status of a terminal device may cause the edge service latency of this group of terminal devices to increase. Summary of the Invention

[0007] Embodiments of the present application provide a communication method, device, and system.

[0008] The embodiments of the present application can be used in a communication system including an application server and a management server, wherein the application server is used to provide business services to terminal devices, and the management server is used to provide information about the application server to the terminal devices. 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 the present application are not limited to the MEC system architecture.

[0009] In a first aspect, a communication method is provided, the method comprising: a first management server determining a first correspondence, the first correspondence comprising a correspondence between the first terminal device group and an application server and a correspondence 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 first terminal device in the first terminal device group to determine or select an application server; when the first management server receives second connection information from the second management server, it updates the first correspondence according to the second connection information to obtain a second correspondence, and sends second information to the remaining management servers corresponding to the first terminal device group except the first management server, the second information being used to determine the second correspondence; 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.

[0010] Using the above implementation method, in a 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 management server switches, the management server corresponding to the first terminal device group can update the correspondence between the first terminal device group and the application server and / or the correspondence between the first terminal device group and the management server, and synchronize the updated correspondence between the management servers, which is beneficial for the management server to optimize the application server to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency of the terminal devices in the first terminal device group.

[0011] It is understood that when a 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 stored correspondence information, send information about 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. Because the new application server selected by the terminal device typically has better performance, the above-described method can enable the terminal devices in the first terminal device group to migrate to the application server, thereby enabling the terminal device users in the first terminal device group to obtain a better service experience.

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

[0013] In one possible implementation, the first management server determines the first corresponding relationship, including: after the first management server determines the application server selected by the first terminal device, the first management server sends information about 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 first connection information sent by the management server to which the remaining terminal devices in the first terminal device group except the first terminal device are currently connected, the first connection information indicating the application server and / or management server to which the terminal device is currently connected; the first management server determines the first corresponding relationship based on the first connection information.

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

[0015] A possible implementation method also includes: when the first management server receives the second connection information from the second management server, if it is determined 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.

[0016] In one possible implementation, updating the first correspondence based on 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, deleting the correspondence between the terminal device in the first terminal device group and the source application server in the first correspondence.

[0017] A possible implementation method also includes: the first management server determines that the first terminal device switches from the source application server to the target application server, and then updates the second correspondence 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.

[0018] A possible implementation method also includes: the first management server determines that the first terminal device is switched from the first management server to the target management server, and the first management server no longer serves the first terminal device group, then the first management server updates the second correspondence according to the target management server to obtain a third correspondence, and the third correspondence does not include the correspondence 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 server corresponding to the terminal device in the first terminal device group according to the third correspondence, and the third information is used to determine the third correspondence; the first management server deletes the third correspondence.

[0019] In one possible implementation, the updating of the first correspondence according to the second connection information to obtain the second correspondence includes: the first management server sends a request message to the other management servers corresponding to the first terminal device group except the first management server, the request message including 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 the third connection information of the remaining terminal devices, the third connection information indicating 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 indicating 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.

[0020] In a second aspect, a communication method is provided, the method comprising: a first management server obtains a first correspondence, the first correspondence comprising a correspondence between a first terminal device group and an application server and a correspondence 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 first management server is configured with information of the first application server; when the first management server receives second connection information from the first application server, it updates the first correspondence according to the second connection information to obtain a second correspondence, and sends second information to the remaining management servers corresponding to the first terminal device group except the first management server, the second information being used to determine the second correspondence; 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.

[0021] Using the above implementation method, in a 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 management server switches, the management server corresponding to the first terminal device group can update the correspondence between the first terminal device group and the application server and / or the correspondence between the first terminal device group and the management server, and synchronize the updated correspondence between the management servers, which is beneficial for the management server to optimize the application server to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency of the terminal devices in the first terminal device group.

[0022] It is understood that when a 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 stored correspondence information, send information about 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. Because the new application server selected by the terminal device typically has better performance, the above-described method can enable the terminal devices in the first terminal device group to migrate to the application server, thereby enabling the terminal device users in the first terminal device group to obtain a better service experience.

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

[0024] In one possible implementation, the first management server obtains the first correspondence, 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 information about 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 server to which the remaining terminal devices in the first terminal device group except the first terminal device are currently connected, the first connection information indicating the application server and / or management server to which the terminal device is currently connected; the first management server determines the first correspondence based on the first connection information.

[0025] In one possible implementation, the first management server obtains the first correspondence, including: the first management server receives 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.

[0026] A possible implementation method also includes: the first management server sends a request message to the first application server, where the request message is used to indicate that when the first application server disconnects from or establishes a connection with a terminal device in the first terminal device group, connection information corresponding to the terminal device disconnected from or established with the first application server is sent to the first management server, where the connection information indicates the application server corresponding to the terminal device disconnected from or established with the first application server.

[0027] In one possible implementation, updating the first correspondence based on the second connection information includes: if the first management server determines based on the second connection information that the first application server no longer serves the first terminal device group, deleting the correspondence between the terminal device in the first terminal device group and the first application server in the first correspondence.

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

[0029] A possible implementation method also includes: in a case where the source management server of the second terminal device is the first management server, if the first management server determines that the source management server of the second terminal device no longer serves the first terminal device group based on the first correspondence and the second connection information, then the first management server deletes the information of the second correspondence; or, in a case where the source management server of the second terminal device is not the first management server, if the first management server determines that the source management server of the second terminal device no longer serves the first terminal device group based on the first correspondence and the second connection information, then 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.

[0030] In one possible implementation, the updating of the first correspondence according to the second connection information to obtain the second correspondence includes: the first management server sends a request message to the other management servers corresponding to the first terminal device group except the first management server, the request message including 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 the third connection information of the remaining terminal devices, the third connection information indicating 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 indicating 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.

[0031] According to a third aspect, a communication method is provided, the method comprising: a first management server obtains a first correspondence, the first correspondence comprising a correspondence between the first terminal device group and the application server and a correspondence between the first terminal device group and the management server; wherein, the first management server is configured with information of the first application server; when the first management server receives second connection information from the first terminal device, the first correspondence is updated according to the second connection information to obtain a second correspondence, and second information is sent to the remaining management servers corresponding to the first terminal device group except the first management server, the second information being used to determine the second correspondence; wherein, the second connection information indicates the application server and / or management server corresponding to the first terminal device.

[0032] Using the above implementation method, in a 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 management server switches, the management server corresponding to the first terminal device group can update the correspondence between the first terminal device group and the application server and / or the correspondence between the first terminal device group and the management server, and synchronize the updated correspondence between the management servers, which is beneficial for the management server to optimize the application server to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency of the terminal devices in the first terminal device group.

[0033] It is understood that when a 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 stored correspondence information, send information about 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. Because the new application server selected by the terminal device typically has better performance, the above-described method can enable the terminal devices in the first terminal device group to migrate to the application server, thereby enabling the terminal device users in the first terminal device group to obtain a better service experience.

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

[0035] In one possible implementation, the first management server obtains the first correspondence, 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 information about 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 server to which the remaining terminal devices in the first terminal device group except the first terminal device are currently connected, the first connection information indicating the application server and / or management server to which the terminal device is currently connected; the first management server determines the first correspondence based on the first connection information.

[0036] In one possible implementation, the first management server obtains the first correspondence, including: the first management server receives 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.

[0037] In one possible implementation, updating the first correspondence based on 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, deleting the correspondence between the terminal device in the first terminal device group and the source application server in the first correspondence.

[0038] A possible implementation method also 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, then the first management server deletes the information of the second correspondence.

[0039] In one possible implementation, the updating of the first correspondence according to the second connection information to obtain the second correspondence includes: the first management server sends a request message to the management servers corresponding to the first terminal device group other than the first management server, the request message including 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 device 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 other than the second terminal device, and obtains the third connection information of the remaining terminal devices, the third connection information indicating 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 indicating 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.

[0040] In a fourth aspect, a communication method is provided, the method comprising: a second management server receives a first request message from a first management server, the first request message including information on a first correspondence and second connection information, the first correspondence including a correspondence between a first terminal device group and an application server and a correspondence between the first terminal device group and the management server, the second connection information indicating 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, updates the first correspondence according to the second connection information, and obtains a second correspondence; the second management server sends second information to the remaining management servers corresponding to the first terminal device group except the second management server, and the second information is used to determine the second correspondence.

[0041] Using the above implementation method, in a 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 management server switches, the management server corresponding to the first terminal device group can update the correspondence between the first terminal device group and the application server and / or the correspondence between the first terminal device group and the management server, and synchronize the updated correspondence between the management servers, which is beneficial for the management server to optimize the application server to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency of the terminal devices in the first terminal device group.

[0042] It is understood that when a 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 stored correspondence information, send information about 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. Because the new application server selected by the terminal device typically has better performance, the above-described method can enable the terminal devices in the first terminal device group to migrate to the application server, thereby enabling the terminal device users in the first terminal device group to obtain a better service experience.

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

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

[0045] In one possible implementation, the second management server sends the second information to the remaining management servers except the first management server among the management servers corresponding to the first terminal device group, 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 servers corresponding to the first terminal device group in the first correspondence.

[0046] In one possible implementation, the updating of the first correspondence according to the second connection information to obtain the second correspondence includes: the second management server sends a second request message to the other management servers corresponding to the first terminal device group except the first management server and the second management server, the second request message including the information of the application server corresponding to the first terminal device, the second request message being 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 the third connection information of the remaining terminal devices, the third connection information indicating the application servers corresponding to the remaining terminal devices; the second management server receives the third connection information from the other management servers, the third connection information indicating the application servers corresponding to the terminal devices connected to the other management servers; the second management server updates the first correspondence according to the third connection information to obtain the second correspondence.

[0047] In a fifth aspect, a communication device is provided, comprising a unit or module for executing the method as described in any one of the first aspects above, or a unit or module for executing the method as described in any one of the second aspects above, or a unit or module for executing the method as described in any one of the third aspects above, or a unit or module for executing the method as described in any one of the fourth aspects above.

[0048] In a sixth aspect, a communication device is provided, comprising: one or more processors configured to execute a method as described in any one of the first aspects above, or to execute a method as described in any one of the second aspects above, or to execute a method as described in any one of the third aspects above, or to execute a method as described in any one of the fourth aspects above.

[0049] In the seventh aspect, a communication system is provided, including an application server and a management server, wherein the application server is used to provide business services for terminal devices, and the management server is used to provide information of the application server to the terminal devices, and the management server is used to implement the method as described in any one of the first aspects above, or to implement the method as described in any one of the second aspects above, or to implement the method as described in any one of the third aspects above, or to implement the method as described in any one of the fourth aspects above.

[0050] 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 summarized in any one of the first aspects is implemented, or the method described in any one of the second aspects is implemented, or the method described in any one of the third aspects is implemented, or the method described in any one of the fourth aspects is implemented.

[0051] In the ninth aspect, a chip system is provided, 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 equipped with the chip system executes the method described in any one of the first aspects above, or executes the method described in any one of the second aspects above, or executes the method described in any one of the third aspects above, or executes the method described in any one of the fourth aspects above.

[0052] In the tenth aspect, a computer program product is provided, which, when called by a computer, enables the computer to execute the method as described in any one of the first aspect above, or execute the method as described in any one of the second aspect above, or execute the method as described in any one of the third aspect above; or execute the method as described in any one of the fourth aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic diagram of an SA6 edge computing application architecture and functional model in an embodiment of the present application;

[0054] FIG2 is a schematic diagram of an EES discovery process applicable to an embodiment of the present application;

[0055] FIG3 is a schematic diagram of an EAS discovery process applicable to an embodiment of the present application;

[0056] FIG4 is a schematic diagram of UEs in a UE group connected to the same EAS in an embodiment of the present application;

[0057] FIG5 is a schematic diagram of UEs in a UE group connected to different EASs in an embodiment of the present application;

[0058] FIG6 is a schematic diagram of a process of initially connecting a terminal device in a terminal device group to an EAS according to an embodiment of the present application;

[0059] FIG7 is a schematic diagram of a synchronization process of a first correspondence relationship provided in an embodiment of the present application;

[0060] FIG8a is a flow chart of a communication method provided in an embodiment of the present application;

[0061] FIG8b is a flow chart of another communication method provided in an embodiment of the present application;

[0062] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0063] FIG10 is a schematic diagram of an EAS discovery process triggered by EAS according to an embodiment of the present application;

[0064] FIG11a is a schematic diagram of a flow chart of another communication method provided in an embodiment of the present application;

[0065] FIG11b is a schematic diagram of a flow chart of another communication method provided in an embodiment of the present application;

[0066] FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

[0067] FIG13 is a schematic diagram of a scenario in which a terminal device in a first terminal device group switches between EAS and EES in an embodiment of the present application;

[0068] FIG14 is a flow chart of a communication method implemented based on the scenario shown in FIG13 in an embodiment of the present application;

[0069] FIG15 is a flow chart of another communication method implemented based on the scenario shown in FIG13 in an embodiment of the present application;

[0070] FIG16 is a flow chart of another communication method implemented based on the scenario shown in FIG13 in an embodiment of the present application;

[0071] FIG17 is a flow chart of another communication method implemented based on the scenario shown in FIG13 in an embodiment of the present application;

[0072] FIG18 is a schematic diagram of another scenario in which a terminal device in a first terminal device group switches between EAS and EES in an embodiment of the present application;

[0073] FIG19 is a flow chart of a communication method implemented based on the scenario shown in FIG18 in an embodiment of the present application;

[0074] FIG20 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0075] Figure 21 is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to more clearly understand the embodiments of the present application, the relevant technologies involved in the embodiments of the present application are first explained.

[0077] 1. Mobile Edge Computing

[0078] In traditional mobile network architecture and deployment, user-plane equipment generally follows a tree topology. Uplink user packets pass through base stations and backhaul networks, ultimately accessing the data network through centrally deployed anchor gateways. These anchor gateways are typically located higher in the network, such as in regional central equipment rooms. This relatively simple topology facilitates centralized service control and packet processing at the anchor points.

[0079] With the explosive growth of mobile service traffic, this deployment model is increasingly unable to support the rapidly increasing mobile service traffic model. On the one hand, in a network with centralized anchor gateway deployment, the increasing traffic ultimately concentrates at the gateway and core equipment room, placing increasingly high demands on backhaul network bandwidth, equipment room throughput, and gateway specifications. On the other hand, the long backhaul network distance and complex transmission environment from access points to anchor gateways also lead to significant latency and jitter in user message transmission.

[0080] Mobile edge computing (MEC), also known as multi-access edge computing, leverages wireless access networks to provide telecom users with information technology (IT) services and cloud computing capabilities close to their locations. This creates a carrier-grade service environment with high performance, low latency, and high bandwidth, accelerating the download of content, services, and applications across the network, allowing consumers to enjoy an uninterrupted, high-quality network experience.

[0081] (2) Mobile Edge Computing Architecture

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

[0083] Edge data network (EDN): A common understanding is that an EDN corresponds to only one data network, a special local data network (local DN), which can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logical concept. Another understanding of EDN is that EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center (geographic concept), can be identified using a DNAI, and can include multiple local data networks.

[0084] Edge application server (EAS): An application deployed in an edge data network is called an application instance or application server. Specifically, it refers to an instance of a server application deployed and running on an EDN. For example, some examples of the server application 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. EASs deployed and running in different EDNs can be considered as different EASs of an application. They can share a domain name, use an IP address, or use different IP addresses. EAS can also be called 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, application servers and EASs are used as examples for description.

[0085] Application client (AC): The application client is the peer entity of the edge application on the terminal device side. The application client is used by the application user to obtain application services from the application server. The application client is the client program applied on the terminal device side. The application client can connect to the application server in the cloud to obtain application services, or it can connect to the EAS deployed and running in one or more EDNs to obtain application services.

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

[0087] Edge Enabler Client (EEC): The EES's counterpart on the terminal device side. The EEC is responsible for registering EEC information and application client information with the EES, performing security authentication and authorization, obtaining the EAS IP address from the EES, and providing edge computing capabilities to the application client. For example, the EAS discovery service returns the EAS IP address to the application client.

[0088] Edge Configuration Server (ECS): Responsible for EDN configuration, such as providing EES information to end devices. It can also directly provide application instance information to end devices and interact with the application's Domain Name System (DNS) to obtain application instance information. Furthermore, it can obtain and store application instance and IP address information from other functional entities.

[0089] Application users sign a service agreement with the application provider, which provides services to the application users. Application users log in to the application client (AC) on the terminal device and communicate with the edge application (EAS) through the connection between the application client (AC) and the edge application (EAS). The edge enabling client (EEC) is a middleware layer, generally located in the operating system or between the application client and the operating system. The application client (AC) can obtain edge enabling services from the edge enabling client (EEC) in the form of an application programming interface (API).

[0090] EDGE-X shown in FIG1 represents an interface between functional entities. For example, EDGE-1 is an interface between an edge enabling server (EES) and an edge enabling client (EEC).

[0091] In the architecture shown in Figure 1, the terminal device can be user equipment (UE), a handheld terminal, a laptop computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device (handheld), a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal or other device that can access the network, and the embodiments of the present application are not limited thereto.

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

[0093] (3) EES discovery and EAS discovery

[0094] The SA6 standard defines the EES and EAS discovery processes. Through the EES discovery process, a terminal device can obtain EES information from the ECS and connect to the EES. Through the EAS discovery process, a terminal device can select the EAS it uses and obtain information such as the EAS's IP address. The architecture and functionality are designed to use a two-level discovery mechanism: first, the EES discovery process is executed, and then the EAS discovery process is executed based on the EES to which the terminal device is connected.

[0095] Referring to FIG2 , an EES discovery process applicable to an embodiment of the present application is exemplarily shown. As shown in FIG2 , the EES discovery process may include the following steps:

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

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

[0098] Step 202: After receiving the request message, the ECS determines a candidate EES based on the information of the terminal device, such as location information.

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

[0100] Optionally, the ECS may obtain the DNAI based on the current location of the terminal device, or may obtain the DNAI based on a target location to which the terminal device may move.

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

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

[0103] It should be understood that in the process shown in FIG. 2 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0104] Referring to FIG3 , an EAS discovery process applicable to an embodiment of the present application is exemplarily shown, and the process may also be applicable to the embodiment of the present application. As shown in FIG3 , the EAS discovery process may include the following steps:

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

[0106] Optionally, the EAS discovery request message includes a discovery filter parameter corresponding to the edge service, which is used to request an EAS that meets the requirements.

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

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

[0109] 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 parameters to determine a candidate EAS.

[0110] In this step, EES determines candidate EASs that meet the requirements corresponding to the discovery filter parameters based on the information of locally registered or online EASs and the discovery filter parameters provided by the terminal device. If multiple EASs meet the requirements corresponding to the discovery filter parameters, multiple candidate EASs can be returned.

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

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

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

[0114] Optionally, when there is only one candidate EAS, the terminal device selects the candidate EAS.

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

[0116] The terminal device can connect to the EAS of its choice.

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

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

[0119] Optionally, the EAS selection declaration response message may also be replaced by a selected EAS announcement response message, or an EAS information provisioning response message, which is not limited in this application.

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

[0121] In one possible implementation, step 302 does not need to be executed. Accordingly, in step 303, the EAS discovery response message includes information of all EASs registered (or configured) on the EES. That is, the EES recommends all EASs registered (or configured) on the EES as candidate EASs to the terminal device.

[0122] It should be understood that in the process shown in FIG3 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0123] (4) Terminal device groups and application context migration

[0124] Multiple terminal devices can use the same edge service. Taking the 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 in the group of UEs can connect to the same EAS corresponding to the multiplayer game, and different UEs in the group of UEs can also connect to different EASs corresponding to the multiplayer game.

[0125] For example, Figure 4 shows a schematic diagram of UEs in a UE group connected to the same EAS. A group of UEs connected to the same EAS can reduce signaling interactions between EASs. As shown in Figure 4, EAS-1(A), EAS-1(B) and EAS-1(C) are different EASs corresponding to the same edge service. A UE group includes UE1, UE2 and UE3. UE1, UE2 and UE3 are all connected to EAS-1(B). Different UEs in the UE group can be connected 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.

[0126] It should be understood that FIG4 only describes an example in which a UE group includes 3 UEs, and the embodiment of the present application does not limit the number of UEs included in the UE group.

[0127] For example, Figure 5 shows a schematic diagram of UEs in a UE group connected to different EASs. Different UEs in a group can connect to an EAS that is closer to the UE to obtain better service performance. As shown in Figure 5, 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 connects to EAS-1x and EES1, UE2 connects to EAS-2x and EES2, and UE3 connects to EAS-3x and EES3.

[0128] It should be understood that FIG5 only describes an example in which a UE group includes 3 UEs, and the embodiment of the present application does not limit the number of UEs included in the UE group.

[0129] It should be understood that multiple UEs in a UE group may be connected to the same EAS and the same EES, for example, two UEs in the UE group are connected to EAS1 and EES1, and the other three UEs are connected to EAS2 and EES2. This embodiment of the present application does not limit this.

[0130] As shown in FIG5 , when different terminal devices in a terminal device group are connected to different EASs, application context synchronization needs to be performed between the multiple EASs to which the terminal devices in the group are connected to ensure data consistency.

[0131] The terminal devices in the terminal device group may reselect the EAS and / or EES due to reasons such as changes in location. For example, all the terminal devices connected to EAS1 in the first terminal device group are migrated to EAS2, or the second terminal device in the first terminal device group is connected to a new EAS and / or a new EES due to movement. The event that causes the terminal device to select a new EAS and / or EES can be called an application context relocation (ACR) event. For example, an ACR event may include triggering the terminal device to select a new EAS and / or EES due to movement to a new location, or because the source EAS is no longer suitable for providing services to the terminal device, such as EAS overload. This application does not limit this.

[0132] When an ACR event occurs to a terminal device in the terminal device group (or the migration of the application server and / or management server occurs to the terminal device), the correspondence between the terminal device in the terminal device group and the EAS and / or the correspondence between the terminal device and the EES may change. There is currently a lack of corresponding solutions for the above scenarios. For example, in this case, how the EES connected to other terminal devices in the terminal device group knows the new EAS and / or new EES selected by the terminal device where the ACR event occurs, 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 business or better execution of the business, is a problem that needs to be solved at present.

[0133] To this end, an embodiment of the present application provides a communication method and related devices that can implement the method.

[0134] The embodiments of the present application are described below with reference to the accompanying drawings.

[0135] For the case where terminal devices in a group of terminal devices (for example, a first terminal device group) use the same service, an embodiment of the present application provides a process for the terminal devices in the terminal device group to initially connect to the EAS. After the first terminal device in the first terminal device group (i.e., the first terminal device in the first terminal device group to select EAS) selects EAS, the first EES connected to the first terminal device notifies the EAS to the EESs corresponding to the remaining terminal devices in the terminal device group. The EESs 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 correspondence between the other terminal devices in the first terminal device group and the EAS, as well as the correspondence between the terminal devices in the first terminal device group and the EES.

[0136] 6 , which is a schematic diagram of a process for initially connecting a terminal device in a terminal device group to an EAS according to an embodiment of the present application, wherein the first terminal device is terminal device 1 and the first EES is EES1.

[0137] As shown in FIG6 , the method includes the following steps:

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

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

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

[0141] For the specific implementation of the EAS discovery process, please refer to Figure 3.

[0142] Optionally, before the terminal device 1 initiates the EAS discovery process to the EES 1, 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 EES 1. The specific implementation of the EES discovery process can be referred to FIG2 .

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

[0144] The EAS corresponding to the terminal device 1 may 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 EES1 for the terminal device 1 .

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

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

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

[0148] Step 603: The EESs corresponding to the remaining terminal devices (such as EES2 to EESm shown in FIG6 ) recommend the EAS (EAS1) corresponding to the first terminal device as a candidate EAS to the other terminal devices in the EAS discovery process initiated by the terminal device, and obtain the EASs corresponding to the other terminal devices.

[0149] In Figure 6, using terminal device 2 as an example, terminal device 2 initiates an EAS discovery process with the EES2 corresponding to (or connected to) the terminal device and selects an EAS from the candidate EASs recommended by EES2 (including EAS1 as a common EAS). The specific implementation of the EAS discovery process can be seen in Figure 3. Optionally, before initiating the EAS discovery process with EES2, terminal device 2 may first initiate an EES discovery process with the EEC to obtain the IP address and / or identification information of EES2. The specific implementation of the EES discovery process can be seen in Figure 2.

[0150] It should be understood that the EAS selected by the terminal device 2 may be EAS1 or another EAS, for example, the terminal device 2 selects EAS2, where EAS2 is the EAS registered or managed on EES2. This application is not limited thereto.

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

[0152] Step 604: The EESs corresponding to the remaining terminal devices (such as EES2 to EESm shown in FIG6 ) respectively send first connection information to EES1 , where the first connection information indicates the EAS corresponding to the terminal device.

[0153] The EAS corresponding to the terminal device can be understood as the EAS selected by the terminal device, or the EAS determined by the terminal device, or the EAS determined by the EES for the terminal device.

[0154] Taking terminal device 2 as an example, in one possible implementation, the first connection information sent by EES2 to EES1 to which terminal device 2 is connected includes information about the EAS corresponding to terminal device 2 (e.g., the IP address and / or identification information of the EAS). In another possible implementation, if terminal device 2 or EES2 selects EAS1 (that is, common EAS), the first connection information sent by EES2 to which terminal device 2 is connected to EES1 includes indication information for instructing terminal device 2 to select (or connect to) common EAS. For example, the indication information may be one or more bits of indication information with a value of 1, indicating that the EAS selected by the terminal device is common EAS.

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

[0156] In one possible implementation, the first connection information may not necessarily indicate the EES corresponding to the terminal device (the EES corresponding to the terminal device may also be understood as the EES connected to the terminal device), for example, it may not include information about the EES corresponding to the terminal device. Since the EES sending the first connection information is the EES currently connected to the terminal device, EES1 may determine the sending EES as the EES corresponding to the terminal device (i.e., 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.

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

[0158] In a possible implementation, the first connection information further includes an identifier of the terminal device.

[0159] In a possible implementation, the first connection information further includes an identifier of the first terminal device group (eg, group ID).

[0160] Optionally, EES2 may send the first connection information (eg, including EAS information corresponding to terminal device 2) to EES1 via a common EAS announcement response message, an EAS announcement response (annoucement EAS response) message, or other messages, which is not limited in this application.

[0161] Step 605: After EES1 receives the first connection information returned by the EESs to which the remaining terminal devices in the first terminal device group are connected (such as EES2 to EESm shown in Figure 6), it determines a first corresponding relationship, which 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.

[0162] The "correspondence between the first terminal device group and the EAS" can be understood as the correspondence between the terminal devices in the first terminal device group and the EAS. Accordingly, the EAS corresponding to all the terminal devices in the first terminal device group is referred to as the EAS corresponding to the first terminal device group. The "correspondence between the first terminal device group and the EES" can be understood as the EES corresponding to the terminal devices in the first terminal device group. Accordingly, the EES corresponding to all the terminal devices in the first terminal device group is referred to as the EES corresponding to the first terminal device group.

[0163] After determining the first corresponding relationship, EES1 stores information about the first corresponding relationship.

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

[0165] Illustratively, based on the example in step 603 , a data structure of the connection relationship list may be as shown in Table 1.

[0166] Table 1: Connection relationship list

[0167] In another exemplary embodiment, the connection relationship list may include an EAS list and an EES list. Based on the example of step 603, a data structure of the EAS list may be shown in Table 2, and a data structure of the EES list may be shown in Table 3.

[0168] Table 2: EAS List

[0169] Table 3: EES List

[0170] It should be understood that the embodiment of the present application does not limit the naming method of the connection relationship list.

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

[0172] It should be understood that in the process shown in FIG6 above, the number of terminal devices in the first terminal device group is greater than or equal to 2, and this application does not limit this. Accordingly, 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, and this application does not limit this.

[0173] It should be understood that in the process shown in FIG. 6 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0174] In one possible implementation, after the first EES corresponding to the first terminal device in the first terminal device group (i.e., the first terminal device that determines or selects EAS) determines the first correspondence, the first correspondence can also be synchronized to the EES corresponding to (or connected to) other terminal devices in the first terminal device group, so that the EES corresponding to (or connected to) all terminal devices in the first terminal device group stores information about the first correspondence, such as the connection relationship list shown in Table 1 above.

[0175] 7 , which is a schematic diagram of a synchronization process of a first correspondence relationship provided in an embodiment of the present application, wherein the first terminal device is terminal device 1 and the first EES is EES1.

[0176] After EES1 determines the first correspondence, EES1 stores information about the first correspondence. Optionally, the information about the first correspondence may be a list of connection relationships. Optionally, the information about the first correspondence stored by EES1 is determined by EES1. For example, an implementation of EES1 determining the first correspondence can be seen in FIG6 .

[0177] After EES1 determines the first corresponding relationship, as shown in FIG7 , the following steps are included:

[0178] Step 701: EES1 sends first information to the remaining EESs (such as EES2 to EESm shown in Figure 6) according to the EES corresponding to the terminal device in the first correspondence relationship. The first information is used to determine the first correspondence relationship.

[0179] Optionally, the first information may be information of a first correspondence, for example, the first information is a connection relationship list. An example of a connection relationship list can be found in the above text.

[0180] Steps 702a, 702b and 702c: After receiving the first information, the remaining EESs determine a first corresponding relationship according to the first information and store information about the first corresponding relationship.

[0181] Through the process shown in FIG. 7 , the EES to which the terminal devices in the first terminal device group are currently connected all stores information on the first corresponding relationship.

[0182] In the process shown in FIG7 , the number of EESs is merely an example. It should be understood that if the number of terminal devices in the first terminal device group is greater than or equal to two, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be one, two, or more, and this application does not limit this.

[0183] It should be understood that in the process shown in FIG. 7 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0184] In some embodiments of the present application, when an ACR event occurs on 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 first EES of the target EAS and / or target EES of the second terminal device, and the first EES updates its saved first correspondence based on the received information, and the first ESS synchronizes the updated first correspondence to the EES corresponding to (or connected to) the terminal devices in the first terminal device group. 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 first terminal device in the first terminal device group to determine or select the EAS. An implementation method of the above process can be referred to Figure 8a.

[0185] Referring to Figure 8a, a flow chart of a communication method provided in an embodiment of the present application is shown. The first terminal device is terminal device 1; the second terminal device is terminal device 2; the first EES is EES1, i.e., the EES corresponding to (or connected to) terminal device 1; and the second EES is EES2, i.e., the source EES to which terminal device 2 is connected.

[0186] EES1 stores information about a first correspondence, including a correspondence between a first terminal device group and an EAS, and a correspondence between the first terminal device group and an EES. The information about the first correspondence can be expressed as a connection relationship list. An example of a connection relationship list is shown in Table 1, or in Tables 2 and 3.

[0187] Optionally, EES1 may determine the first corresponding relationship through the process shown in FIG6 , and store information of the first corresponding relationship.

[0188] As shown in FIG8a , the process may include the following steps:

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

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

[0191] Optionally, the second connection information also includes an identifier of the terminal device 2.

[0192] Optionally, the second connection information further includes an identifier of the first terminal device group (eg, group ID).

[0193] In one possible implementation, an ACR event occurs on terminal device 2, and terminal device 2 switches from a source EAS to a target EAS, and / or switches from a source EES to a 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 EES1 of the EAS corresponding to terminal device 2 (i.e., the target EAS to which terminal device 2 switches) and / or the EES corresponding to terminal device 2 (i.e., the target EES to which terminal device 2 switches) through second connection information.

[0194] Optionally, the implementation manner in which the source EES of the terminal device 2 obtains the EAS corresponding to the terminal device 2 and / or the EES corresponding to the terminal device 2 may include the following manners.

[0195] Method 1: When terminal device 2 moves or the source EAS is not suitable for providing services to the terminal device, for example, when 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 the 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 the terminal device 2 to connect to the target EAS. The source EES of terminal device 2 (EES2) 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 information about the target EAS and the target EES of terminal device 2.

[0196] Method 2: After moving, terminal device 2 initiates an EES discovery process with the ECS, selects a target EES from the candidate EESs recommended by the ECS, and connects to the target EES. Terminal device 2 also initiates an EAS discovery process with the target EES, selects a target EAS from the candidate EASs recommended by the target EES, and connects to the target EAS. Terminal device 2 sends information about its target EAS and / or target EES to its source EES. For example, this information can be sent via an ACR request message.

[0197] Method 3: Terminal device 2 initiates an EES discovery request to the ECS. The ECS determines the EES for UE 2 and sends the EES information to terminal device 2 and its source EES. Terminal device 2 initiates an EAS discovery request to its source EES. 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 its source EES.

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

[0199] The EES discovery process may refer to the process shown in FIG2 , and the EAS discovery process may refer to the process shown in FIG3 .

[0200] It should be understood that the above only illustrates several possible implementation methods, and this application does not limit this. 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 scope of protection of this application.

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

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

[0203] Optionally, if the second connection information indicates the EAS corresponding to the terminal device 2, the 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.

[0204] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, then the 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.

[0205] In one possible implementation, after EES1 receives the second connection information, if it is determined that the source EAS of 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 the EAS, then EES1 deletes the correspondence between the terminal devices in the first terminal device group and the EAS in the first correspondence.

[0206] Step 803: EES1 sends second information to the remaining EESs except EES1 in the EESs corresponding to the terminal devices in the first terminal device group, where the second information is used for (or in other words, is used for) determining a second corresponding relationship.

[0207] In a possible implementation, EES1 may send the second information to the remaining EESs except EES1 among the EESs according to the EESs corresponding to the terminal devices in the second corresponding relationship (or the EESs corresponding to the first terminal device group).

[0208] In one possible implementation, the second information may be information about the second correspondence, for example, the second information may be an updated connection relationship list. For an example of a connection relationship list, refer to the above. That is, EES1 may synchronize the second correspondence to other EESs using a full update.

[0209] In another possible implementation, when terminal device 2 switches from a source EAS to a target EAS, the second information may include the identifier of terminal device 2 and information about the EAS corresponding to terminal device 2; and when terminal device 2 switches from a source EES to a target EES, the second information may include the identifier of terminal device 2 and information about the EES corresponding to terminal device 2. In other words, EES 1 can adopt an incremental update approach, notifying other EESs of only the changed correspondences, thereby reducing network overhead.

[0210] Optionally, the second information also includes an identifier of the first terminal device group.

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

[0212] In one possible implementation, after receiving the second connection information, if EES1 determines that the source EES of terminal device 2 (i.e., EES2) no longer serves the first terminal device group, that is, no terminal device in the first terminal device group is connected to EES2, EES1 sends a deletion request message to the source EES of terminal device 2 (i.e., EES2), instructing the source EES of terminal device 2 to delete the first correspondence. Optionally, the deletion request message includes an identifier of the first terminal device group.

[0213] In an embodiment of the present application, if an ACR event occurs in the terminal device 1 connected to EES1, 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 the terminal device 1, and synchronize the later corresponding relationship to other EES.

[0214] For example, before EES1 updates the second correspondence, if EES1 determines that terminal device 1 switches from the source EAS to the target EAS, EES1 may update the first correspondence according to the target EAS of terminal device 1, and notify the remaining EESs except EES1 in the EES corresponding to the first terminal device group of the updated first correspondence.

[0215] As another example, after EES1 updates and obtains the second correspondence, if EES1 determines that terminal device 1 switches from the source EAS to the target EAS, EES1 updates the second correspondence according to the target EAS of terminal device 1, and sends information indicating the updated second correspondence to the remaining EESs except EES1 in the EES corresponding to the first terminal device group. The information is used (or is used) to determine the updated second correspondence.

[0216] As another example, after EES1 updates the second correspondence, if EES1 determines that terminal device 1 has switched from EES1 to the target EES and that EES1 no longer serves the first terminal device group, EES1 updates the second correspondence based on the target EES of terminal device 1. The EES corresponding to the first terminal device group in the updated second correspondence does not include EES1. EES1 can send information indicating the updated second correspondence to the EESs corresponding to the first terminal device group in the third correspondence, and this information is used to determine the third correspondence. Furthermore, EES1 can delete the information stored thereon regarding the correspondence between the first terminal device group and the EAS, as well as the information regarding the correspondence between the first terminal device group and the EES.

[0217] In the process shown in Figure 8a above, the target EES to which the terminal device 2 switches 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, for the first terminal device group, the target EES is a new EES.

[0218] In one possible implementation, if the target EES of terminal device 2 is a new EES for the first terminal device group, the updated second correspondence includes the new EES corresponding to terminal device 2, so EES1 can send the second information to the new EES. Alternatively, EES1 can send the second information to the source EES of terminal device 2 (such as EES2 described above) based on the first correspondence, and the source EES of terminal device 2 then sends the second information to the target EES of terminal device 2. Optionally, the second information sent by EES1 to the new EES includes information about the second correspondence, that is, EES1 synchronizes the second correspondence to the new EES using a full update.

[0219] Using the method shown in FIG8a above, in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, when an EAS and / or ESS switch occurs, the ESS corresponding to the first terminal device group can update the correspondence between the first terminal device group and the EAS and / or the correspondence between the first terminal device group and the EES, and synchronize the updated correspondence between the EESs. This facilitates the EES to optimize the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group. For example, when a terminal device in the first terminal device group switches to a new EAS, the EES corresponding to the first terminal device group can send information about the new EAS to other EESs based on the stored correspondence information, so that each EES can recommend the new EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device generally has better performance, the above method can enable the terminal devices in the first terminal device group to migrate to the new EAS, thereby optimizing the EAS to which the terminal devices in the first terminal device group are connected, thereby providing users of the terminal devices in the first terminal device group with a better service experience.

[0220] In one possible implementation, after receiving the second connection relationship information indicating the EAS corresponding to terminal device 2, EES1 may send the EAS information corresponding to terminal device 2 to other EESs, so that the other EESs can recommend the EAS to other terminal devices and update the first correspondence based on the terminal device connection information fed back by the other EESs. This implementation can be seen in Figure 8b.

[0221] 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 in the above manner. 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 it may be different from the EASs connected to other terminal devices in the first terminal device group. For the first terminal device group, if the target EAS 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.

[0222] 8b , by replacing step 802 in FIG. 8a with the following steps in FIG. 8b , the target EAS of terminal device 2 can be recommended to other terminal devices, and the first correspondence relationship can be updated according to the selection of the EAS by other terminal devices:

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

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

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

[0226] Optionally, EES1 may send request messages to these EESs (eg, EES2 to EESm shown in the figure) respectively to instruct the corresponding EES to determine whether the terminal devices in the first terminal device group connected thereto should switch to the EAS corresponding to terminal device 2 .

[0227] Optionally, EES1 may send the request message to the EESs corresponding to the first terminal device group in the first correspondence, excluding EES1. For example, if EES2 only corresponds to terminal device 2 in the first correspondence, EES1 will not send the request message to EES2. For another example, if EES2 corresponds to terminal device 2 and terminal device 3 in the first correspondence, EES1 needs to send the request message to EES2.

[0228] Optionally, EES1 may also send the identifier of the first terminal device group to these EESs (eg, EES2 to EESm shown in the figure).

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

[0230] In one possible implementation, terminal device 1 may select or not select the EAS recommended by EES1. If terminal device 1 selects the EAS recommended by EES1, terminal device 1 switches from the source EAS to the EAS recommended by EES1; if terminal device 1 does not select the EAS recommended by EES1, terminal device 1 does not switch the EAS.

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

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

[0233] As another example, if the terminal device 1 does not select the EAS recommended by EES1 (i.e., the target EAS of the terminal device 2), the third connection information of the terminal device 1 includes information about the EAS to which the terminal device 1 is currently connected; or, the third connection information of the terminal device 1 includes indication information for indicating that the terminal device 1 has not selected the EAS recommended by EES1 (i.e., the target EAS of the terminal device 2), for example, the value of the indication information is 0, indicating that the terminal device 1 has not selected the EAS recommended by EES.

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

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

[0236] Step 8024: The EESs send the third connection information of the terminal device to EES1.

[0237] Step 8025: EES1 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 a second correspondence relationship.

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

[0239] The remaining steps in FIG8b are the same as those in FIG8a and are not described again.

[0240] A possible example of the process shown in FIG8b may refer to FIG14 or FIG15.

[0241] 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. 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 service performance.

[0242] It should be understood that whenever an EAS switch and / or EES switch occurs in 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 Figure 8a or Figure 8b.

[0243] In the process shown in FIG8a or FIG8b above, 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. Accordingly, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be one, two, or more, and this application does not limit this.

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

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

[0246] In some embodiments of the present 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 the terminal device) can be notified to the first EES configured with the information of the EAS, so that the first EES can update the first correspondence to obtain a second correspondence, and synchronize the second correspondence to other EESs in the EES corresponding to the terminal devices in the first terminal device group. An implementation of the above process can be referred to Figure 9.

[0247] 9 is a flow chart of a communication method provided by an embodiment of the present application, wherein the first application server is EAS2, the second terminal device is terminal device 2, the first EES is EES2, and EES2 is configured (or registered) with information of EAS2.

[0248] EES2 stores information about a first correspondence, including a correspondence between the first terminal device group and the EAS, and a correspondence between the first terminal device group and the EES. The information about the first correspondence can be expressed as a connection relationship list. An example of the connection relationship list is shown in Table 1, or in Tables 2 and 3.

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

[0250] As shown in FIG9 , the process may include the following steps:

[0251] Step 901: EES2 sends a request message to EAS2, where the request message is used to instruct EAS2 to send connection information of the terminal device disconnected from or connected to EAS2 to EES2 when disconnecting from or establishing a connection with a terminal device in the first terminal device group. The connection information indicates the EAS corresponding to the terminal device (i.e., the terminal device disconnected from or connected to EAS1).

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

[0253] Optionally, the request message may be a subscription request message.

[0254] In one possible implementation, since EAS2 is the EAS to which one or more terminal devices in the first terminal device group are connected, and the information of EAS2 is configured on EES2, EES2 can send the above-mentioned request message to EAS2 to request to subscribe to the event of change in the connection relationship between EAS2 and the terminal devices in the first terminal device group.

[0255] Step 901 is an optional step.

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

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

[0258] Take the disconnection between terminal device 2 and 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.

[0259] In a possible implementation, the process of EAS2 obtaining the target EAS of terminal device 2 may be as shown in FIG10 , and the process may include the following steps:

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

[0261] Step 1002: EES2 determines to perform application context migration, thereby triggering the execution of the following steps 1003 to 1005.

[0262] Step 1003: EES2 obtains information about the EES corresponding to terminal device 2 (or the target EES of terminal device 2) from the ECS. This process is described by taking the target EES of terminal device 2 as EESx as an example.

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

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

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

[0266] Step 903: EAS2 sends second connection information to EES2. The second connection information indicates the EAS corresponding to terminal device 2 in the first terminal device group, and further, may also indicate the EES corresponding to terminal device 2.

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

[0268] Optionally, the second connection information also includes an identifier of the terminal device 2.

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

[0270] Step 904: EES2 updates the first correspondence relationship according to the second connection information to obtain a second correspondence relationship.

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

[0272] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, then the EES2 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.

[0273] In a possible implementation, after EES2 receives the second connection information, if it is determined based on the second connection information that EAS2 no longer serves the first terminal device group, the correspondence between the terminal devices in the first terminal device group and EAS2 in the first correspondence is deleted.

[0274] Step 905: EES2 sends second information to the remaining EESs except EES1 in the EESs corresponding to the terminal devices in the first terminal device group, where the second information is used to determine a second corresponding relationship.

[0275] In a possible implementation, EES2 may send the second information to the remaining EESs except EES1 among the EESs according to the EESs corresponding to the terminal device in the second corresponding relationship.

[0276] In one possible implementation, the second information may be information about the second correspondence, for example, the second information may be an updated connection relationship list. For an example of a connection relationship list, refer to the above. That is, EES2 may synchronize the second correspondence to other EESs using a full update.

[0277] In another possible implementation, the second information may include only the identifier of terminal device 2 and the information of the EAS corresponding to terminal device 2. Furthermore, if the EAS connected to terminal device 2 changes, the second information may also include the information of the EES corresponding to terminal device 2. In other words, EES 1 can use an incremental update method to only notify other EESs of the changed correspondence, thereby reducing network overhead.

[0278] Optionally, the second information also includes an identifier of the first terminal device group.

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

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

[0281] Based on the process shown in Figure 9 above, in a possible implementation, when the terminal device 3 establishes a connection with EAS2 and the source EES of the terminal device 3 is not EES2, if EES2 determines that the source EES of the terminal device 3 no longer serves the first terminal device group based on the first correspondence and the second connection information, then EES2 can send a deletion request message to the source EES of the terminal device 3, requesting to delete the information of the first correspondence stored on the EES.

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

[0283] In one possible implementation, if the target EES of terminal device 2 is a new EES for the first terminal device group, the updated second correspondence includes the new EES corresponding to terminal device 2, so EES2 can send the second information to the new EES. Alternatively, EES2 can send the second information to the source EES of terminal device 2 based on the first correspondence, and the source EES of terminal device 2 then sends the second information to the target EES of terminal device 2. Optionally, the second information sent by EES2 to the new EES includes information about the second correspondence, that is, EES2 synchronizes the second correspondence to the new EES using a full update.

[0284] It should be understood that whenever an EAS switch and / or EES switch occurs in 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 FIG. 9 .

[0285] In the process shown in FIG9 , the number of EESs is merely an example. It should be understood that if the number of terminal devices in the first terminal device group is greater than or equal to two, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be one, two, or more, and this application does not limit this.

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

[0287] It should be understood that in the process shown in FIG. 9 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0288] Using the method shown in FIG9 , in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, when an EAS and / or ESS switch occurs, the ESS corresponding to the first terminal device group can update the correspondence between the first terminal device group and the EAS and / or the correspondence between the first terminal device group and the EES, and synchronize the updated correspondence between the EESs. This facilitates the EES to optimize the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group. For example, when a terminal device in the first terminal device group switches to a new EAS, the EES corresponding to the first terminal device group can send information about the new EAS to other EESs based on the stored correspondence 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 generally has better performance, the above method can enable the terminal devices in the first terminal device group to migrate to the new EAS, thereby optimizing the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group and providing users with a better service experience.

[0289] In one possible implementation, after receiving the request message, the target EES of terminal device 2 (e.g., EESm in FIG9 ) 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 recommend the EAS to the terminal devices in the first terminal device group, receive the third connection information of the terminal devices fed back by these EESs, and then update the first correspondence based on the received third connection information to obtain the second correspondence, and synchronize the second correspondence to the other EESs. For a specific implementation, please refer to FIG8b . For a possible example, please refer to FIG16 .

[0290] In some embodiments of the present application, when an EAS and / or EES switch occurs for a second terminal device in a first terminal device group, the second terminal device may notify the first EES of the target EAS and / or target EES of the second terminal device. The first EES updates its stored first correspondence based on the received information, and the first ESS synchronizes the updated first correspondence to the EES corresponding to (or connected to) the terminal device in the first terminal device group. The first EES is the source EES for the second terminal device. For an implementation of the above process, see Figure 11a.

[0291] 11a is a flow chart of a communication method according to an embodiment of the present application, wherein the second terminal device is terminal device 2, and the first EES is EES2, ie, the source EES corresponding to (or connected to) terminal device 2.

[0292] EES2 stores information about a first correspondence, including a correspondence between the first terminal device group and the EAS, and a correspondence between the first terminal device group and the EES. The information about the first correspondence can be expressed as a connection relationship list. An example of the connection relationship list is shown in Table 1, or in Tables 2 and 3.

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

[0294] As shown in FIG11a , the process may include the following steps:

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

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

[0297] Optionally, the second connection information also includes an identifier of the terminal device 2.

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

[0299] In one possible implementation, when an ACR event occurs on terminal device 2, terminal device 2 switches from source EAS to target EAS and / or from source EES to target EES. Terminal device 2 notifies EES2 of its target EAS and / or target EES by sending second connection information.

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

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

[0302] Optionally, if the second connection information indicates the EAS corresponding to the terminal device 2, the 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.

[0303] Optionally, if the second connection information indicates the EES corresponding to the terminal device 2, the 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.

[0304] In one possible implementation, after EES2 receives the second connection information, if it is determined that the source EAS of 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 the EAS, then EES2 deletes the correspondence between the terminal devices in the first terminal device group and the EAS in the first correspondence.

[0305] Step 1103: EES2 sends second information to the remaining EESs except EES2 in the EESs corresponding to the first terminal device group, where the second information is used for (or in other words, is used for) determining a second corresponding relationship.

[0306] In a possible implementation, EES2 may send the second information to the remaining EESs except EES2 among the EESs according to the EESs corresponding to the terminal devices in the second corresponding relationship (or the EESs corresponding to the first terminal device group).

[0307] In one possible implementation, the second information may be information about the second correspondence, for example, the second information may be an updated connection relationship list. For an example of a connection relationship list, refer to the above. That is, EES2 may synchronize the second correspondence to other EESs using a full update.

[0308] In another possible implementation, when terminal device 2 switches from a source EAS to a target EAS, the second information may include the identifier of terminal device 2 and information about the EAS corresponding to terminal device 2; when terminal device 2 switches from a source EES to a target EES, the second information may include the identifier of terminal device 2 and information about the EES corresponding to terminal device 2. In other words, EES 2 can adopt an incremental update approach, notifying other EESs of only the changed correspondences, thereby reducing network overhead.

[0309] Optionally, the second information also includes an identifier of the first terminal device group.

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

[0311] Based on the process shown in Figure 11a above, in one possible implementation method, if EES2 determines that the source EES of terminal device 2 (i.e., EES2) no longer serves the first terminal device group based on the second connection information and the first correspondence, and EES2 deletes the information of the second correspondence stored therein.

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

[0313] In one possible implementation, if the target EES of terminal device 2 is a new EES for the first terminal device group, the updated second correspondence includes the new EES corresponding to terminal device 2, so EES2 can send the second information to the new EES. Alternatively, EES2 can send the second information to the source EES of terminal device 2 based on the first correspondence, and the source EES of terminal device 2 then sends the second information to the target EES of terminal device 2. Optionally, the second information sent by EES2 to the new EES includes information about the second correspondence, that is, EES2 synchronizes the second correspondence to the new EES using a full update.

[0314] Using the method shown in FIG. 11a , in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, when an EAS and / or ESS switch occurs, the ESS corresponding to the first terminal device group can update the correspondence between the first terminal device group and the EAS and / or the correspondence between the first terminal device group and the EES, and synchronize the updated correspondence between the EESs. This facilitates the EES to optimize the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group. For example, when a terminal device in the first terminal device group switches to a new EAS, the EES corresponding to the first terminal device group can send information about the new EAS to other EESs based on the stored correspondence information, so that each EES can recommend the new EAS to other terminal devices in the first terminal device group. Since the new EAS selected by the terminal device generally has better performance, the above method can enable the terminal devices in the first terminal device group to migrate to the new EAS, thereby optimizing the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group and providing users with a better service experience.

[0315] In one possible implementation, after receiving the second connection relationship information indicating the EAS corresponding to terminal device 2, EES2 may send the EAS information corresponding to terminal device 2 to other EESs, so that the other EESs can recommend the EAS to other terminal devices and update the first correspondence based on the terminal device connection information fed back by the other EESs. This implementation can be seen in Figure 11b.

[0316] 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 in the above manner. 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 it may be different from the EASs connected to other terminal devices in the first terminal device group. For the first terminal device group, if the target EAS 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.

[0317] Referring to FIG. 11b , by replacing step 1102 in FIG. 11a with the following steps in FIG. 11b , the target EAS of terminal device 2 can be recommended to other terminal devices, and the first correspondence relationship can be updated according to the selection of the EAS by other terminal devices:

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

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

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

[0321] Optionally, EES2 may send request messages to these EESs (eg, EES2 to EESm shown in the figure) respectively to instruct the corresponding EES to determine whether the terminal devices in the first terminal device group connected thereto should switch to the EAS corresponding to terminal device 2.

[0322] Optionally, EES2 may send the request message to other EESs except EES1 among the EESs according to the EESs corresponding to the first terminal device group in the first corresponding relationship.

[0323] Optionally, EES2 may also send the identifier of the first terminal device group to these EESs (eg, EES2 to EESm shown in the figure).

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

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

[0326] The terminal device can select or not select the EAS recommended by EES2. If the terminal device selects 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 select the EAS recommended by EES1, the terminal device does not switch to the EAS.

[0327] 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 selects the EAS recommended by EES, or to indicate whether the terminal device selects the EAS corresponding to terminal device 2.

[0328] Exemplarily, if the terminal device selects the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2), the third connection information of the terminal device includes information about the EAS selected by the terminal device (i.e., the target EAS of terminal device 2); or, the third connection information of the terminal device includes indication information for instructing the terminal device to select 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.

[0329] As another example, if the terminal device does not select the EAS recommended by EES1 (i.e., the EAS corresponding to terminal device 2), the third connection information of the terminal device includes information about the EAS to which the terminal device is currently connected; or, the third connection information of the terminal device includes indication information for indicating that the terminal device has not selected 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 has not selected the EAS recommended by EES.

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

[0331] 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 EESs, and obtain the third connection information of the terminal devices. For specific implementation methods, please refer to step 11023a.

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

[0333] 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 a second correspondence relationship.

[0334] In another possible implementation, after each EES recommends the EAS corresponding to terminal device 2 to a terminal device in the first terminal device group to which it is connected, the terminal device switches from the source EAS to the EAS recommended by EES1 based on the candidate EAS recommended by the EES. In other words, 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 based on the EAS corresponding to terminal device 2, that is, updates the EAS corresponding to the terminal device in the first terminal device group to the EAS corresponding to terminal device 2.

[0335] The remaining steps in FIG11b are the same as those in FIG11a and are not described in detail. A possible example of the process shown in FIG11b can be referred to FIG17.

[0336] In the process shown in FIG. 11a or FIG. 11b , the number of EESs is merely an example. It should be understood that if the number of terminal devices in the first terminal device group is greater than or equal to two, the number of EESs corresponding to (or connected to) the terminal devices in the first terminal device group may be one, two, or more, and this application does not limit this.

[0337] It should be understood that whenever a terminal device undergoes EAS switching and / or EES switching, the EAS and / or EES corresponding to the first terminal device group on the EES can be updated according to the process shown in Figure 11a or Figure 11b.

[0338] 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. The target EAS selected by the terminal device usually has better performance. In this case, based on the process shown in Figure 11b, other terminal devices can be migrated to this EAS, thereby ensuring or improving service performance.

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

[0340] It should be understood that in the process shown in FIG. 11 a or FIG. 11 b above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0341] In the process shown in Figure 11a or Figure 11b above, in the case where a terminal device in a terminal device group disconnects from a source application server and connects to a target application server, the management server to which the terminal device in the terminal device group is connected can obtain information about the target application server so as to recommend that the terminal device in the group of terminal devices connected to the management server connect to the target application server.

[0342] Based on the communication method shown in Figure 11a or Figure 11b, if the source EES of the second terminal device (i.e., EES2 in Figure 11a or Figure 11b) where the ACR event occurs determines based on the second connection information that the EES no longer serves the first terminal device group, the EES can instruct the target EES of the second terminal device to perform an update operation on the first correspondence relationship and an operation to synchronize the updated correspondence relationship. Figure 12 exemplifies this process.

[0343] Referring to FIG. 12 , which is a flow chart of a communication method provided in an embodiment of the present application, based on the scenario of FIG. 11 a or FIG. 11 b , as shown in the figure, the flow may include the following steps:

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

[0345] For the specific implementation of this step, please refer to step 801 in Figure 8a or Figure 8b.

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

[0347] Step 1203: EES2 sends a first request message to the EES corresponding to terminal device 2 (such as EESm in the figure). The first request message is used to instruct EESm (i.e., the target EES of terminal device 2) to update the correspondence between the first terminal device group and EAS and / or EES.

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

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

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

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

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

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

[0354] Optionally, if EESm (the target EES for terminal device 2) is a new EES for the first terminal device group, the first correspondence information is not stored on the EES. Therefore, EES3 may also send the first correspondence information to EESm via the first request message. If EESm (the target EES for terminal device 2) is not a new EES for the first terminal device group, the first correspondence information is stored on the EES. Therefore, EES3 does not need to send the first correspondence information to EESm.

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

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

[0357] In a possible implementation, the specific implementation of this step may refer to step 1102 in FIG. 11 a .

[0358] In another possible implementation manner, the specific implementation manner of this step can refer to steps 11021 to 11025 in Figure 11b.

[0359] Step 1205: EESm sends second information to the remaining EESs except EES2 in the EESs corresponding to the first terminal device group, where the second information is used for (or in other words, is used for) determining a second corresponding relationship.

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

[0361] For the specific implementation of this step, please refer to step 1103 in Figure 11a or Figure 11b.

[0362] Step 1206: EES2 deletes the stored information of the first correspondence. This step is optional.

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

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

[0365] It should be understood that in the process shown in FIG. 12 above, the “terminal device” may also be replaced by the EEC or AC on the terminal device side.

[0366] Using the method shown in FIG12 , in a scenario where the connection status of at least one terminal device in the first terminal device group changes, for example, when an EAS and / or ESS switch occurs, the ESS corresponding to the first terminal device group can update the correspondence between the first terminal device group and the EAS and / or the correspondence between the first terminal device group and the EES, and synchronize the updated correspondence between the EESs. This facilitates the EES to optimize the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group. When a terminal device in the first terminal device group switches to a new EAS, the EES corresponding to the first terminal device group can send information about the new EAS to other EESs based on the stored correspondence 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 generally has better performance, the above method can enable the terminal devices in the first terminal device group to migrate to the new EAS, thereby optimizing the EAS to which the terminal devices in the first terminal device group are connected, thereby avoiding an increase in edge service latency for the terminal devices in the first terminal device group and providing users with a better service experience.

[0367] In one possible implementation, after receiving the first request message, the target EES of terminal device 2 (e.g., EESm in FIG12 ) may further 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, thereby instructing 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 correspondence based on the received third connection information to obtain the second correspondence, and synchronize the second correspondence to other EESs. For a specific implementation, please refer to FIG8 b . For a possible example, please refer to FIG18 and FIG19 .

[0368] In one possible implementation, a terminal device that undergoes EAS and / or EES switching may 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. For the subsequent process, please refer to Figure 12. Optionally, in this case, the source EES does not need to delete the information of the first correspondence.

[0369] It should be understood that the method shown in FIG. 8 a , FIG. 8 b , FIG. 9 , FIG. 11 a , FIG. 11 b or FIG. 12 may be used according to specific scenarios.

[0370] In order to more clearly understand the above embodiments of the present application, the embodiments of the present application are described below in conjunction with the specific application scenario shown in Figure 13.

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

[0372] Based on the above scenario, after the UE in the first UE group initially connects to the EES and EAS, EES1 determines the first correspondence and stores information about 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 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 correspondence relationship to EES2 and EES3, so that EES2 and EES3 also store the information of the first correspondence relationship. For the specific implementation of the above process, please refer to Figures 6 and 7.

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

[0374] Based on the scenario shown in FIG13 , FIG14 shows a process after an ACR event occurs in UE2. As shown in FIG14 , the process includes the following steps:

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

[0376] Optionally, UE 2 moves or the source EAS is not suitable for providing services for the terminal device, for example, the EAS is overloaded, so the source EES of UE 2 initiates an EES discovery process to the ECS.

[0377] Step 1402: The ECS returns an EES discovery response message to EES2, which carries information about candidate EESs, including EES4.

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

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

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

[0381] Step 1405: EES4 returns an EAS discovery response message to EES2, which carries information of candidate EASs, including EAS4.

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

[0383] Step 1407a and step 1407b: EES2 sends the second connection information of UE2 to the EESs other than EES2 (including EES1 and EES3) according to the EES corresponding to the first UE group in the first correspondence. The second connection information of UE2 indicates the EAS and EES corresponding to UE2, wherein the EAS corresponding to UE2 is EAS4, and the EES corresponding to UE2 is EES4.

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

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

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

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

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

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

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

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

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

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

[0394] It should be understood that steps 1401 to 1406 may also be replaced by other implementations. In other words, other implementations may be used to enable the source EES of UE2 to obtain the EAS and / or EES corresponding to UE2, or to obtain the target EAS and / or target EES of UE2. For details, please refer to the relevant content of the aforementioned embodiments.

[0395] For example, one implementation is as follows: UE2 initiates an EES discovery request to the ECS. The ECS determines EES4 for UE2 and sends EES4 information to UE2 and UE2's source EES (EES2). UE2 initiates an EAS discovery request to its source EES (EES2). EES2 determines EAS4 for UE2 and sends EAS4 information to UE2.

[0396] For the specific implementation of each step in the process shown in FIG14 , please refer to FIG8 a or FIG8 b .

[0397] It should be understood that the process shown in FIG14 is only a possible implementation method under the scenario shown in FIG13 and does not constitute a limitation to the present application.

[0398] Based on the scenario shown in FIG13 , FIG15 shows a process after an ACR event occurs in UE2. As shown in FIG15 , the process includes the following steps:

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

[0400] Optionally, after the terminal device 2 moves, it initiates an EES discovery process to the ECS, selects EES 4 from the candidate EESs recommended by the ECS, and connects to the EES 4. The specific implementation method can be found in FIG2 .

[0401] Step 1502: UE2 initiates an EAS discovery process to EES4 and selects EAS4 from the candidate EASs provided by EES4. For a specific implementation, please refer to FIG3 .

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

[0403] Step 1504a and step 1504b: EES2 sends the second connection information of UE2 to the EESs other than EES2 (including EES1 and EES3) according to the EES corresponding to the first UE group in the first correspondence. The second connection information of UE2 indicates the EAS and EES corresponding to UE2, wherein the EAS corresponding to UE2 is EAS4, and the EES corresponding to UE2 is EES4.

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

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

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

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

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

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

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

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

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

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

[0414] It should be understood that steps 1501 to 1503 may also be replaced by other implementations. In other words, other implementations may be used to enable the source EES of UE2 to obtain the EAS and / or EES corresponding to UE2, or to obtain the target EAS and / or target EES of UE2. For details, please refer to the relevant content of the aforementioned embodiments.

[0415] For example, one implementation is as follows: UE2 initiates an EES discovery request to the ECS. The ECS determines EES4 for UE2 and sends EES4 information to UE2. UE2 initiates an EAS discovery request to EES4. EES4 determines EAS4 for UE2 and sends EAS4 information to UE2. UE2 sends EAS4 information and EES4 information to UE2's source EES.

[0416] For the specific implementation of each step in the process shown in FIG15 , please refer to FIG8 a or FIG8 b .

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

[0418] Based on the scenario shown in FIG13 , FIG16 shows a process after an ACR event occurs in UE2. As shown in FIG16 , the process includes the following steps:

[0419] Step 1601: EES2 sends a request message to EAS2, which is used to instruct EAS2 to send the connection information of the UE to EES2 when disconnecting or establishing a connection with the UE in the first UE group.

[0420] Step 1602: EAS2 determines that UE2 is disconnected from EAS2, and EAS2 obtains information of UE2's target EAS (EAS4) and target EES (EES4).

[0421] The specific implementation of this step can be found in FIG10 .

[0422] Step 1603: EAS2 sends second connection information to EES2, where the second connection information indicates the EAS information and EES information corresponding to UE2, wherein the EAS corresponding to UE2 is ESA4 to which UE2 switches, and the EES corresponding to UE2 is EES4 to which UE2 switches.

[0423] Step 1604: EES2 recommends EAS4 to UE4 based on EAS4 corresponding to UE2, and obtains third connection information of UE4. The third connection information of UE4 indicates that UE4 has not selected EAS4.

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

[0425] Steps 1606a and 1607a: After receiving the second connection information, EES1 recommends EAS4 to UE1 and obtains UE1's third connection information, which EES1 sends to EES2. In this example, UE1's third connection information indicates that UE1 has not selected EAS4.

[0426] Steps 1606b and 1607b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains UE3's third connection information, which EES3 sends to EES2. In this example, UE3's third connection information indicates that UE3 has not selected EAS4.

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

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

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

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

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

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

[0433] It should be understood that steps 1601 to 1603 may also be replaced by other implementations. In other words, other implementations may be used to enable the source EES of UE2 to obtain the EAS and / or EES corresponding to UE2, or to obtain the target EAS and / or target EES of UE2. For details, please refer to the relevant content in the aforementioned embodiments.

[0434] For the specific implementation of each step in the process shown in Figure 16 above, please refer to Figure 9.

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

[0436] Based on the scenario shown in FIG13 , FIG17 shows a process after an ACR event occurs in UE2, which includes the following steps:

[0437] Step 1701: After selecting or switching to EES4 and EAS4, UE2 sends an ACR request message to UE2's source EES (EES2), including second connection information. The second connection information indicates the EAS and EES corresponding to UE2. The EAS corresponding to UE2 is ESA4 to which UE2 has switched, and the EES corresponding to UE2 is EES4 to which UE2 has switched.

[0438] Step 1702: EES2 recommends EAS4 to UE4 based on EAS4 corresponding to UE2, and obtains third connection information of UE4. The third connection information of UE4 indicates that UE4 has not selected EAS4.

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

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

[0441] Steps 1704b and 1705b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains UE3's third connection information, which EES3 sends to EES2. In this example, UE3's third connection information indicates that UE3 has not selected EAS4.

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

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

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

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

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

[0447] Steps 1708a, 1708b, and 1708c: After receiving the second information, EES1, EES3, and EES4 respectively determine a second corresponding relationship based on the second information and store the information of the second corresponding relationship.

[0448] It should be understood that step 1701 may be replaced by other implementations, that is, other implementations may be used to enable the source EES of UE2 to obtain the EAS and / or EES corresponding to UE2, or to obtain the target EAS and / or target EES of UE2. For details, please refer to the relevant content of the aforementioned embodiments.

[0449] For the specific implementation of each step in the process shown in Figure 17 above, please refer to Figure 11a or Figure 11b.

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

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

[0452] Based on the above scenario, after the UE in the first UE group initially connects to the EES and EAS, EES1 determines the first correspondence and stores information about 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 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 correspondence relationship to EES2 and EES3, so that EES2 and EES3 also store the information of the first correspondence relationship. For the specific implementation of the above process, please refer to Figures 6 and 7.

[0453] UE1 has an ACR event, switches (or migrates) from EES1 to EES4, and switches (or migrates) from EAS1 to EAS4. Accordingly, 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 corresponding relationship between the first UE group and the EES {<UE1,EES4> ,<UE2,EES4> ,<UE3,EES3> ,<UE4,EES2>}.

[0454] Based on the scenario shown in FIG18 , FIG19 shows a process after an ACR event occurs in UE1. As shown in FIG19 , the process includes the following steps:

[0455] Step 1901: After selecting or switching to EES4 and EAS4, UE1 sends an ACR request message to UE1's source EES (EES1), including second connection information. The second connection information indicates the EAS and EES corresponding to UE1. The EAS corresponding to UE1 is ESA4 to which UE1 switches, and the EES corresponding to UE1 is EES4 to which UE1 switches.

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

[0457] This step is optional. In some other embodiments, even if EES1 is still serving the first UE group, EES1 may send a request message to the target EES of UE1.

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

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

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

[0461] Optionally, EES1 may delete EES1 from the EES corresponding to the first UE group in the first corresponding relationship, and then send the corresponding relationship information after EES1 is deleted to EES4.

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

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

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

[0465] Steps 1906a and 1907a: After receiving the second connection information, EES2 recommends EAS4 to UE2 and UE4, obtains third connection information for UE2 and UE4, and sends the third connection information for UE2 and UE4 to EES4. In this example, UE2's third connection information indicates that UE2 has not selected EAS4, and UE4's third connection information indicates that UE4 has not selected EAS4.

[0466] Steps 1906b and 1907b: After receiving the second connection information, EES3 recommends EAS4 to UE3 and obtains UE3's third connection information, which EES3 sends to EES2. In this example, UE3's third connection information indicates that UE3 has not selected EAS4.

[0467] Step 1908: EES4 updates the first corresponding relationship according to the EAS and EES corresponding to UE1 and the third connection information of UE2, UE3 and UE4 to obtain a second corresponding relationship.

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

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

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

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

[0472] Steps 1910a and 1910b: After receiving the second information, EES3 and EES4 respectively determine a second corresponding relationship based on the second information and store information about the second corresponding relationship.

[0473] It should be understood that step 1901 may be replaced by other implementations, that is, the source EES of UE1 may obtain the EAS and / or EES corresponding to UE1, or obtain the target EAS and / or target EES of UE1, through other implementations.

[0474] For the specific implementation of each step in the process shown in Figure 19 above, please refer to Figure 12.

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

[0476] It is understood that in order to implement the functions in the above embodiments, the management server includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples 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 hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0477] Figures 20 and 21 are schematic diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the management server in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be a management server or a module (such as a chip) used to manage the server.

[0478] As shown in Figure 20, the communication device 2000 includes a processing unit 2010 and a transceiver unit 2020. The communication device 2000 is used to implement the management server function in the method embodiment shown in any of Figures 2, 3, 6, 7, 8a, 8b, 9, 10, 11a, 11b, 12, and 14 to 19.

[0479] For example, when the communication device 2000 is used to implement the function of the management server in the method embodiment shown in Figure 8a or Figure 8b: the processing unit 2010 determines a first correspondence, and 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; 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 first terminal device in the first terminal device group to determine or select the application server; when the transceiver unit 2020 receives the second connection information from the second management server, the processing unit 2010 updates the first correspondence according to the second connection information to obtain a second correspondence, and sends second information to the remaining management servers corresponding to the first terminal device group except the first management server through the transceiver unit 2020, and the second information is used to determine the second correspondence; 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.

[0480] For another example, when the communication device 2000 is used to implement the function of the management server in the method embodiment shown in Figure 9: the processing unit 2010 is used to obtain a first correspondence, and the first correspondence includes a correspondence between the first terminal device group and the application server and a correspondence 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 first management server is configured with information of the first application server; when the transceiver unit 2020 receives the second connection information from the first application server, the processing unit 2010 updates the first correspondence according to the second connection information to obtain a second correspondence, and sends second information to the remaining management servers corresponding to the first terminal device group except the first management server through the transceiver unit 2020, and the second information is used to determine the second correspondence; 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.

[0481] For another example, when the communication device 2000 is used to implement the function of the management server in the method embodiment shown in Figure 11a or Figure 11b: the processing unit 2010 is used to obtain a first correspondence, and 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; wherein, the first management server is configured with information of the first application server; when the transceiver unit 2020 receives the second connection information from the first terminal device, the processing unit 2010 updates the first correspondence according to the second connection information to obtain a second correspondence, and sends second information to the remaining management servers corresponding to the first terminal device group except the first management server, and the second information is used to determine the second correspondence; wherein, the second connection information indicates the application server and / or management server corresponding to the first terminal device.

[0482] For another example, when the communication device 2000 is used to implement the function of the management server in the method embodiment shown in Figure 12: the transceiver unit 2020 receives a first request message from the first management server, the first request message includes information on a first correspondence and second connection information, the first correspondence includes a correspondence between the first terminal device group and the application server and a 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 processing unit 2010 responds to the first request message, updates the first correspondence according to the second connection information, and obtains a second correspondence; and sends second information to the remaining management servers corresponding to the first terminal device group except the second management server through the transceiver unit 2020, and the second information is used to determine the second correspondence.

[0483] A more detailed description of the processing unit 2010 and the transceiver unit 2020 can be directly obtained by referring to the relevant description in the method embodiment described above, and will not be repeated here.

[0484] As shown in Figure 21, 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 is understood that the interface circuit 2120 can be a transceiver or an input / output interface. Optionally, the communication device 2100 may also include a memory 2130 for storing instructions executed by the processor 2110, or storing input data required by the processor 2110 to execute instructions, or storing data generated after the processor 1310 executes instructions.

[0485] When the communication device 2100 is used to implement the method embodiment 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 .

[0486] When the communication device is a chip used in a device, the chip implements the functions of the device in the above method embodiment. The chip receives information from other modules in the device; or the chip sends information to other modules in the device.

[0487] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), 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.

[0488] The present application provides another example of a communication device, which includes at least one processor and at least one memory, the at least one processor and the at least one memory being coupled, the at least one memory being used to store instructions. When the instructions are executed by the at least one processor, the communication device performs the method in the above-described embodiment. For example, as shown in FIG21 , a communication device 2100 includes a processor 2110 and a memory 2130. The processor 2110 and the memory 2130 are coupled, and the memory 2130 stores instructions. When the instructions stored in the memory 2130 are executed by the processor 2110, the communication device 2100 performs the method executed by the management server in the above-described embodiment.

[0489] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, 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 an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal. The processor and storage medium can also exist in a network device or a terminal as discrete components.

[0490] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented 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 performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0491] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0492] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of this application, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

[0493] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent 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 an 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 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 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 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 to 5, characterized in that, 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 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 server 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 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.

7. The method according to any one of claims 1-6, characterized in that, 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, it updates the second correspondence relationship according to the target application server of the first terminal device to obtain the third correspondence relationship; 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 relationship. The third information is used to determine the third correspondence relationship.

8. The method according to any one of claims 1-6, characterized in that, It further includes: When the first management server determines that the first terminal device switches from the first management server to the 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 the third correspondence relationship. 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. The third information is used to determine the third correspondence relationship; The first management server deletes the third correspondence relationship.

9. The method according to any one of claims 1-8, characterized in that, Sending the second information to the remaining management servers in the management server 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, send the second information to other management servers except the first management server among these management servers.

10. A communication method, characterized in that, The method includes: The first management server obtains a first correspondence relationship, which 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 first management server receives the 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, and 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.

11. The method according to claim 10, wherein The first management server obtaining the first correspondence 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 other 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 the 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, and 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 correspondence relationship according to the first connection information.

12. The method according to claim 10, wherein The first management server obtaining the first correspondence relationship includes: The first management server receives the first information from the 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 the application server.

13. The method according to any one of claims 10-12, characterized in that, 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 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.

14. The method according to any one of claims 10 to 13, 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 first application server 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 first application server in the first correspondence.

15. The method according to any one of claims 10-14, characterized in that, The second connection information further indicates the management server corresponding to the second terminal device.

16. The method according to claim 15, 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, based on 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 in 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, based on 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 in the first correspondence.

17. The method according to any one of claims 10-16, characterized in that, 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 other than the first management server in the management servers corresponding to the first terminal device group, 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 other than 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, and 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.

18. The method according to any one of claims 10-17, characterized in that, The sending the second information to other management servers other than the first management server in the management servers corresponding to the first terminal device group includes: According to the management servers corresponding to the first terminal device group in the second correspondence, the second information is sent to other management servers other than the first management server among these management servers.

19. A communication method, characterized in that, The method includes: The first management server obtains a first correspondence relationship, which 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, information of the first application server is configured on the first management server; When the first management server receives second connection information from the 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; wherein, the second connection information indicates the application server and / or management server corresponding to the first terminal device.

20. The method according to claim 19, wherein The first management server obtaining the first correspondence 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 an application server. The first management server receives first connection information sent by the management servers currently connected by 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 by the terminal device. The first management server determines the first correspondence relationship according to the first connection information.

21. The method according to claim 19, wherein The first management server obtaining the first correspondence relationship includes: The first management server receives first information from the second management server, where 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.

22. The method according to any one of claims 19-21, characterized in that, The 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 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.

23. The method according to any one of claims 19-22, characterized in that, It further includes: If the first management server determines according to the second connection information and the first correspondence relationship 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 relationship.

24. The method according to any one of claims 19-23, characterized in that, 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 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 server 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 server 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.

25. The method according to any one of claims 19-24, characterized in that, Sending the second information to the remaining management servers in the management server 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, send the second information to other management servers in these management servers except the first management server.

26. 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; In response to the first request message, the second management server updates the first correspondence according to 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.

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

28. The method according to claim 26 or 27, 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.

29. The method according to any one of claims 26-28, characterized in that, Sending the second information to the remaining management servers in the management server corresponding to the first terminal device group except the first management server by the second management server includes: The second management server sends the second information to 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 correspondence relationship.

30. The method according to any one of claims 26-29, 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 except the first management server and the second management server in the management server corresponding to the first terminal device group. The second request message includes information about the application server corresponding to the first terminal device. 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 except the second terminal device in the first terminal device group connected to the second management server, 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 second 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 second management server updates the first correspondence relationship according to the third connection information to obtain the second correspondence relationship.

31. A communication device, characterized in that, It includes a unit or module for executing the method according to any one of claims 1-9, or includes a unit or module for executing the method according to any one of claims 10-18, or includes a unit or module for executing the method according to any one of claims 19-25, or includes a unit or module for executing the method according to any one of claims 26-30.

32. 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-9, or to execute the method according to any one of claims 10-18, or to execute the method according to any one of claims 19-25, or to execute the method according to any one of claims 26-30.

33. 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. 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-9, or to implement the method according to any one of claims 10-18, or to implement the method according to any one of claims 19-25, or to implement the method according to any one of claims 26-30.

34. 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-9, or implements the method according to any one of claims 10-18, or implements the method according to any one of claims 19-25, or implements the method according to any one of claims 26-30.

35. 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 equipped with the chip system is caused to execute the method according to any one of claims 1-9, or execute the method according to any one of claims 10-18, or execute the method according to any one of claims 19-25, or execute the method according to any one of claims 26-30.

36. A computer program product, characterized in that, When the computer program product is called by a computer, the computer is caused to execute the method according to any one of claims 1-9, or execute the method according to any one of claims 10-18, or execute the method according to any one of claims 19-25, or execute the method according to any one of claims 26-30.

Images